To: [EMAIL PROTECTED]
Subject: Re: Level 3 TPA routing today?
On Tue, 26 Aug 2008, david raistrick wrote:
On Tue, 26 Aug 2008, David Hubbard wrote:
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas? We've
Internap just reported problems with L3 out
On Wed, 27 Aug 2008, Jay R. Ashworth wrote:
I too have a cage at Hampton Oaks, 10M up and 10M tail to me over OC-12,
and I had problems 15-1630ish to wired.com and zimbra.com, among other
sites; mtr had no appreciable loss tracing, but upper layer protocols
were hincky. It was clear by the
From: Jon Lewis [mailto:[EMAIL PROTECTED]
We have gigE to Level3 in Orlando, and saw something happen
around 1pm today. Customers were complaining of latency and
packet loss, and our traffic to/from L3 dropped noticably if
only for a few minutes.
It sounded like based on Craig's post
On Wed, Aug 27, 2008 at 4:40 PM, David Hubbard
[EMAIL PROTECTED] wrote:
From: Jon Lewis [mailto:[EMAIL PROTECTED]
We have gigE to Level3 in Orlando, and saw something happen
around 1pm today. Customers were complaining of latency and
packet loss, and our traffic to/from L3 dropped
On Wed, 27 Aug 2008, David Hubbard wrote:
be. The tech I spoke to this morning said he had no
knowledge of any issues yesterday, of course my ticket
also had none of the information I sent in to them
yesterday or even a clear description of what the
problem was
We opened a ticket for
Most likely the issue was communication between the NOC and the
service management center. The NOC deals with the core facing events
versus the SMC which takes the incoming calls from the customers. In
this case the issue was identified and resolved in the NOC.
Perhaps the RFO was not
Has anyone noticed significant Level3 transit issues this evening?
[wrl@REDACTED ~]$ traceroute ae-23-52.car3.Chicago1.Level3.net
traceroute to ae-23-52.car3.Chicago1.Level3.net (4.68.101.39), 30 hops max, 40
byte packets
[...]
4 ge-6-1-101.hsa1.Cleveland1.Level3.net (64.156.66.29) 2.627 ms
Some infrastructure blocks are not routed to portions of the network
but should not affect ultimate reachability as long as the correct
loopbacks and directly connected networks are advertised properly.
regards
On Aug 27, 2008, at 6:42 PM, William R. Lorenz wrote:
Has anyone noticed
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas? We've
seen lots of outbound issues and customers calling
about their sites being down or slow. Ultimately
turned our two links to them off and then everyone
says looks better. I opened a ticket with
On Tue, Aug 26, 2008 at 6:44 PM, David Hubbard
[EMAIL PROTECTED] wrote:
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas? We've
seen lots of outbound issues and customers calling
about their sites being down or slow. Ultimately
turned our two
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas?
We just have co-lo in Tampa, but our upstream's connectivity is through
Level3 and we've been seeing intermittent packet loss up there all day. We
alerted our upstream but no updates so far. It
On Tue, 26 Aug 2008, David Hubbard wrote:
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas? We've
Internap just reported problems with L3 out of Miami:
we are seeing latency, minor packet loss and path problems to a
number of destinations and
On Tue, 26 Aug 2008, david raistrick wrote:
On Tue, 26 Aug 2008, David Hubbard wrote:
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas? We've
Internap just reported problems with L3 out of Miami:
we are seeing latency, minor packet loss and
3 response?
-Scott
-Original Message-
From: Peter Beckman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 26, 2008 9:40 PM
To: [EMAIL PROTECTED]
Subject: Re: Level 3 TPA routing today?
On Tue, 26 Aug 2008, david raistrick wrote:
On Tue, 26 Aug 2008, David Hubbard wrote:
Anyone
14 matches
Mail list logo
