Anyone else seeing intermittent issues between Level3 and XO? Sincerely, Eric Tykwinski TrueNet, Inc. P: 610-429-8300 F: 610-429-3222
Not at this time: 5 ae-41-80.car1.Washington3.Level3.net (4.69.149.140) 5.761 ms 6.227 ms 5.934 ms 6 XO-COMMUNIC.car1.Washington3.Level3.net (4.71.204.26) 6.511 ms 6.379 ms 6.673 ms 7 207.88.14.162.ptr.us.xo.net (207.88.14.162) 9.133 ms 10.785 ms 10.929 ms 8 te-3-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.9) 47.998 ms 43.876 ms 43.534 ms 9 te-3-0-0.rar3.dallas-tx.us.xo.net (207.88.12.2) 42.113 ms 42.468 ms 42.781 ms traceroute has been giving consistent results. Nothing and nobody yelled at me earlier either, but of course I wasn't specifically looking. --Jon Radel On 6/3/11 2:48 PM, Eric Tykwinski wrote:
Anyone else seeing intermittent issues between Level3 and XO?
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300
F: 610-429-3222
On 06/03/2011 11:48 AM, Eric Tykwinski wrote:
Anyone else seeing intermittent issues between Level3 and XO?
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300
F: 610-429-3222
We just had a brief outage off our San Diego POP and we peer with LEVEL3 and AIS. We did notice that we were getting dropped at XO. regards, /virendra
We had two outages over the last 30 minutes on XOs path between Las Vegas and Los Angeles (at least from the router names) . Traces stopped at an IP of 216.156.1.73. Under normal routing the next hop is 216.156.0.145 2 ms 2 ms 2 ms ge11-1-3d0.mcr2.lasvegas-nv.us.xo.net [207.88.81.245] 3 ms 2 ms 2 ms ae1d0.mcr1.lasvegas-nv.us.xo.net [216.156.1.73] * * * Request timed out. * * * Request timed out. Todd Graham | Manager, Network Engineering Leading Edge Communications, Inc
XO has a fiber cut in the NJ-NY area. From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Todd Graham Sent: Friday, June 03, 2011 3:12 PM To: Eric Tykwinski Cc: outages@outages.org; outages-bounces@outages.org Subject: Re: [outages] XO/Level3 outage in DC area? We had two outages over the last 30 minutes on XOs path between Las Vegas and Los Angeles (at least from the router names) . Traces stopped at an IP of 216.156.1.73. Under normal routing the next hop is 216.156.0.145 2 ms 2 ms 2 ms ge11-1-3d0.mcr2.lasvegas-nv.us.xo.net [207.88.81.245] 3 ms 2 ms 2 ms ae1d0.mcr1.lasvegas-nv.us.xo.net [216.156.1.73] * * * Request timed out. * * * Request timed out. Todd Graham | Manager, Network Engineering Leading Edge Communications, Inc
On 06/03/2011 12:12 PM, Todd Graham wrote:
We had two outages over the last 30 minutes on XOs path between Las Vegas and Los Angeles (at least from the router names) . Traces stopped at an IP of 216.156.1.73. Under normal routing the next hop is 216.156.0.145
2 ms 2 ms 2 ms ge11-1-3d0.mcr2.lasvegas-nv.us.xo.net [207.88.81.245] 3 ms 2 ms 2 ms ae1d0.mcr1.lasvegas-nv.us.xo.net [216.156.1.73] * * * Request timed out. * * * Request timed out. Todd Graham | Manager, Network Engineering Leading Edge Communications, Inc
---------------------------- Yes I can confirm the same that our Las Vegas DC took a hit as well. regards, /virendra
participants (5)
-
Eric Tykwinski -
Jon Radel -
Sandone, Nicholas -
Todd Graham -
virendra rode