Level 3 in Ohio

Thu Sep 20 12:54:24 UTC 2007

Level3 was experiencing problems with their own 8xx number yesterday.
====================================
Start Date/Time: 9/19/2007 17:30 GMT
End Date/Time: Ongoing

Summary: Level 3 Communications is currently investigating issues with 
calls to our Toll Free 8774538353. If you are attempting to call 
8774538353 and get fast busy please send e-mail to SMCVoice at level3.com.  A 
detailed update will shortly follow informing you of the results of the 
investigation.

Mike

-----Original Message-----
From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu]On Behalf Of
Marshall Eubanks
Sent: Wednesday, September 19, 2007 1:34 PM
To: nanog list
Subject: Level 3 in Ohio

Is anyone reporting Level3 outages in Ohio or DC ?

One of my clients is down, and L3 is not answering the phones (!)

traceroute 65.89.42.1

(From Cogent in Tyson's Corner)

traceroute to 65.89.42.1 (65.89.42.1), 30 hops max, 38 byte packets
1  dmz-mct2.multicasttech.com (63.105.122.1)  0.367 ms  0.265 ms   
0.238 ms
2  g0-7.na21.b002176-1.dca01.atlas.cogentco.com (38.99.206.153)   
0.598 ms  0.548 ms  0.529 ms
3  g2-1-3587.core01.dca01.atlas.cogentco.com (38.20.32.13)  0.862 ms   
0.834 ms  0.740 ms
4  t4-1.mpd01.dca01.atlas.cogentco.com (154.54.3.158)  0.801 ms   
0.879 ms *
5  v3493.mpd01.dca02.atlas.cogentco.com (154.54.7.2)  1.328 ms  1.311  
ms  1.247 ms
6  t1-4.mpd01.iad01.atlas.cogentco.com (154.54.7.162)  1.693 ms   
1.598 ms  1.605 ms
7  g4-0-3490.core01.iad01.atlas.cogentco.com (154.54.3.225)  1.411  
ms  1.453 ms  1.552 ms
8  oc48-6-0-2.edge2.Washington3.Level3.net (4.68.127.9)  1.577 ms   
1.588 ms  16.498 ms
9  ae-44-99.car4.Washington1.Level3.net (4.68.17.198)  2.766 ms  
ae-24-79.car4.Washington1.Level3.net (4.68.17.70)  3.282 ms  
ae-34-89.car4.Washington1.Level3.net (4.68.17.134)  2.808 ms
<time out>

Cox Cable in Northern Virginia
[TME-Laptop-2:~/Movies/NoisiVision] tme% traceroute 65.89.42.1
traceroute to 65.89.42.1 (65.89.42.1), 64 hops max, 40 byte packets
1  * * *
2  ip70-179-104-1.dc.dc.cox.net (70.179.104.1)  14.989 ms  11.563 ms   
11.782 ms
3  ip68-100-1-161.dc.dc.cox.net (68.100.1.161)  18.078 ms  12.329 ms   
12.036 ms
4  ip68-100-0-1.dc.dc.cox.net (68.100.0.1)  13.368 ms  12.301 ms   
11.960 ms
5  mrfddsrj01-ge110.rd.dc.cox.net (68.100.0.161)  12.504 ms  11.729 ms *
6  xe-9-2-0.edge1.washington1.level3.net (4.79.228.61)  59.189 ms   
12.721 ms  11.749 ms
7  ae-44-99.car4.washington1.level3.net (4.68.17.198)  13.502 ms   
13.389 ms ae-34-89.car4.washington1.level3.net (4.68.17.134)  14.290 ms
<time out>

(Note that both trace routes appear to be flapping at the last  
reported hop.

Regards
Marshall