Level3 newyork - london, anyone else seeing issues?

John Menerick onewingaengel at gmail.com
Sat Jul 26 08:49:48 CDT 2008


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


On Jul 25, 2008, at 6:13 AM, Drew Weaver wrote:

> 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
>





More information about the NANOG mailing list