Re: Massive sprintlink problems?

[Roy Bentley <roy () royb org>]

Judging by traceroutes to livejournal.com, which is hosted at Internap, 
there are problems with Sprintlink after that hop to Toyko. I'm now hitting 
Verio instead.

(roy@odin/pts/1:~) traceroute shell.wgops.com
traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets
 1  10.65.80.1 (10.65.80.1)  10.362 ms  38.902 ms  9.224 ms
 2  srp4-0.chrlncsa-rtr4.carolina.rr.com (24.93.66.110)  18.458 ms  6.839 
ms  12.004 ms
 3  srp4-0.chrlncsa-rtr1.carolina.rr.com (24.93.66.177)  7.037 ms  28.487 
ms  15.410 ms
 4  srp2-0.chrlncsa-rtr2.carolina.rr.com (24.93.66.178)  10.310 ms  9.481 
ms  37.424 ms
 5  son0-0-3.chrlncsa-rtr6.carolina.rr.com (24.93.64.61)  13.586 
ms  11.723 ms  24.317 ms
 6  pop1-cha-P4-0.atdn.net (66.185.132.45)  14.614 ms  31.363 ms  38.061 ms
 7  bb2-cha-P0-2.atdn.net (66.185.132.38)  11.488 ms  8.203 ms  17.804 ms
 8  bb2-ash-P13-0.atdn.net (66.185.152.50)  23.358 ms  24.676 ms  19.804 ms
 9  pop3-ash-P1-0.atdn.net (66.185.148.211)  47.522 ms  18.185 ms  19.961 ms
10  Verio.atdn.net (66.185.140.242)  39.030 ms  49.868 ms  19.934 ms
11  p16-0-1-1.r21.nycmny01.us.bb.verio.net (129.250.5.98)  48.592 
ms  40.081 ms  98.193 ms
12  p16-1-1-3.r20.sttlwa01.us.bb.verio.net (129.250.5.61)  102.310 
ms  93.037 ms  111.446 ms
13  ge-0-1-0.a12.sttlwa01.us.ra.verio.net (129.250.28.20)  108.693 
ms  101.358 ms  89.893 ms
14  p1-0-0-0.a12.sttlwa01.us.ce.verio.net (204.203.3.6)  107.124 
ms  145.143 ms pos-0-0-1.a12.sttlwa01.us.ce.verio.net 
(198.104.203.66)  139.623 ms
15  border26s.ge1-1-bbnet1.sea.pnap.net (206.253.192.163)  105.869 
ms  107.906 ms  103.090 ms
16  ge0-0-0.brd-1-sea.speakeasy.net (206.191.168.200)  123.558 ms * *
17  fe2-0.spk-2-sea.speakeasy.net (206.191.168.196)  119.556 ms  109.804 
ms  102.145 ms
18  kurak.wgops.com (66.92.192.248)  134.806 ms  141.694 ms  164.366 ms
19  shell.wgops.com (66.92.192.108)  148.167 ms  158.066 ms  141.841 ms

Quite a bit faster.

At 01:09 PM 10/1/2003 -0600, Michael Loftis wrote:

> According to speakeasy system status page (my DSL provider at the other 
> end there)...  It seems though it's rather more widespread than what this 
> notice makes it out to be.
>
> 09/26/03 02:18:07 PM  Seattle POP Packet Loss
>
> Region : Seattle
> E.T.A. : (none)
> Services Affected : Some broadband services
>
> We are presently seeing packet loss on one of our Seattle POP's backhaul 
> circuits caused by an unexpected increase in traffic caused by Internet 
> worms. We will be fully upgrading this POP within the next few months and 
> are presently investigating interim solutions to these packet loss issues.
>
>
>
>
> --
> GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E