Level3 newyork - london, anyone else seeing issues?

Mailman List Mirror (Read Only)
1

C:\Users\aweaver>tracert 123.237.32.1

Tracing route to 123.237.32.1 over a maximum of 30 hops

5 5 ms 5 ms 5 ms ae-2-6.bar2.Cleveland1.Level3.net [4.69.132.202]
  6 5 ms 4 ms 4 ms ae-0-11.bar1.Cleveland1.Level3.net [4.69.136.185]
  7 13 ms 17 ms 17 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190]
  8 16 ms 16 ms 17 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.142]
  9 15 ms 17 ms 17 ms ae-93-93.ebr3.Washington1.Level3.net [4.69.134.173]
10 22 ms 18 ms 18 ms ae-3.ebr3.NewYork1.Level3.net [4.69.132.90]
11 30 ms 18 ms 18 ms ae-63-63.csw1.NewYork1.Level3.net [4.69.134.98]
12 18 ms 19 ms 19 ms ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Looks like it began occurring around 4am. We're getting reports from some international users that they are unable to reach destinations within our network.

-Drew

2

Drew-

Contact me offlist, that CAR router is our border. We pass to
another entity after that.

regards
-Craig

* Drew Weaver was thought to have said:

3

I was seeing the same thing around the same time. However, the "issue" corrected itself after 10 minutes. Not quite long enough to get Level3 support on the phone. Support's answer: "OOps, our bad....."

John Menerick
http://www.icehax.us
twitter: aeonice
aim: glacilwing

4

I'm sorry to say that whoever said that didn't know the issue since it wasn't a level 3 problem. That router in NYC is the border and bgp was up and routing fine over that interface to another entity. Something was wrong on the return path on the other side past that customer access router.

I worked with Drew offline and after clearing one side, efforts were underway to contact the other entity and get it resolved when it returned to normal.

regards
-Craig

5

We saw an outage from 7:35am to 8:14am (partially back up) 8:20 (fully up) on 7/24. I was on the phone with Level 3 at the time. A tech was supposed to get back to me with an explanation so I could pass that on to my customers, but it never happened.