Anyone else seeing this:: (1sec+ delay to my idle DSL line across sprintlink...)
traceroute is definitely taking an asymmetric path, since pings and tcp connections are consistent 1sec plus RTT starting somewhere in seattle or tacoma.....tok? tokyo? Anyway before I start rattling this around I wanted to see if anyone else is seeing this to/from other destinations.
root@crazyhorse:~# traceroute shell.wgops.com
traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets
1 r1 (216.129.251.1) 0.196 ms 0.230 ms 0.257 ms
2 ag125.montanavision.com (216.220.20.125) 0.447 ms 0.300 ms 0.351 ms
3 ag102.montanavision.com (216.220.20.102) 8.643 ms 13.078 ms 8.646 ms
4 sl-gw10-che-2-0-TS1.sprintlink.net (144.223.8.57) 19.749 ms 17.973 ms 19.443 ms
5 sl-bb20-che-3-0.sprintlink.net (144.232.15.145) 19.545 ms 19.301 ms 19.513 ms
6 sl-bb23-chi-6-0.sprintlink.net (144.232.19.194) 37.906 ms 37.168 ms 37.574 ms
7 sl-bb24-chi-15-0.sprintlink.net (144.232.26.101) 36.751 ms 35.515 ms 35.890 ms
8 sl-bb21-sj-8-0.sprintlink.net (144.232.20.161) 153.128 ms 133.215 ms 272.201 ms
9 sl-bb22-sj-15-0.sprintlink.net (144.232.3.162) 84.783 ms 83.089 ms 83.520 ms
10 sl-bb20-tok-10-0.sprintlink.net (144.232.9.243) 207.685 ms 208.017 ms 209.261 ms
11 sl-bb21-tac-8-2.sprintlink.net (144.232.19.243) 449.450 ms 446.199 ms 447.872 ms
12 sl-bb22-tac-15-0.sprintlink.net (144.232.17.94) 463.037 ms 1243.175 ms 444.169 ms
13 sl-bb20-sea-0-0.sprintlink.net (144.232.9.150) 1300.127 ms 1245.757 ms 1247.772 ms
14 sl-gw11-sea-7-0.sprintlink.net (144.232.6.126) 1247.891 ms 1246.780 ms 1245.041 ms
15 sl-internap-89-0.sprintlink.net (144.228.94.118) 198.635 ms 196.617 ms 196.579 ms
16 border26s.ge2-1-bbnet2.sea.pnap.net (206.253.192.227) 196.374 ms 196.691 ms 196.872 ms
17 * * ge0-0-0.brd-1-sea.speakeasy.net (206.191.168.200) 206.800 ms
18 fe2-0.spk-2-sea.speakeasy.net (206.191.168.196) 198.894 ms 197.410 ms 197.248 ms
19 kurak.wgops.com (66.92.192.248) 228.267 ms 225.835 ms 226.328 ms
20 shell.wgops.com (66.92.192.108) 226.949 ms 223.640 ms 224.977 ms
Anyone else seeing this:: (1sec+ delay to my idle DSL line across
sprintlink...)
traceroute is definitely taking an asymmetric path, since pings and tcp
connections are consistent 1sec plus RTT starting somewhere in seattle or
tacoma.....tok? tokyo? Anyway before I start rattling this around I
wanted
to see if anyone else is seeing this to/from other destinations.
Sprint Naming Conventions:
TOK Tokyo, Japan
9 sl-bb22-sj-15-0.sprintlink.net (144.232.3.162)
10 sl-bb20-tok-10-0.sprintlink.net (144.232.9.243)
11 sl-bb21-tac-8-2.sprintlink.net (144.232.19.243)
Why they are sending it through Tokyo is another question....
Mark
I'm seeing this on my cable connection too.
(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) 7.106 ms 11.420 ms 40.080 ms
2 srp4-0.chrlncsa-rtr4.carolina.rr.com (24.93.66.110) 6.847 ms 7.323 ms 11.712 ms
3 srp4-0.chrlncsa-rtr1.carolina.rr.com (24.93.66.177) 29.755 ms 16.082 ms 45.525 ms
4 srp2-0.chrlncsa-rtr2.carolina.rr.com (24.93.66.178) 8.266 ms 34.051 ms 25.087 ms
5 son0-0-3.chrlncsa-rtr6.carolina.rr.com (24.93.64.61) 49.495 ms 25.806 ms 16.876 ms
6 pop1-cha-P4-0.atdn.net (66.185.132.45) 6.783 ms 9.692 ms 10.515 ms
7 bb2-cha-P0-2.atdn.net (66.185.132.38) 15.873 ms 8.138 ms 23.847 ms
8 bb2-atm-P6-0.atdn.net (66.185.152.30) 13.266 ms 26.131 ms 12.746 ms
9 pop1-atm-P1-0.atdn.net (66.185.147.195) 38.277 ms 10.954 ms 26.400 ms
10 sl-bb23-atl-10-2.sprintlink.net (144.232.8.209) 24.077 ms 14.744 ms 11.853 ms
11 sl-bb26-rly-14-1.sprintlink.net (144.232.20.65) 25.304 ms 57.111 ms 24.054 ms
12 sl-bb22-rly-9-0.sprintlink.net (144.232.14.173) 23.962 ms 45.089 ms 24.062 ms
13 sl-bb22-sj-10-0.sprintlink.net (144.232.20.186) 87.757 ms 112.474 ms 89.224 ms
14 sl-bb20-tok-10-0.sprintlink.net (144.232.9.243) 241.300 ms 219.623 ms 208.599 ms
15 sl-bb21-tac-8-2.sprintlink.net (144.232.19.243) 1261.167 ms 1255.433 ms 1261.609 ms
16 sl-bb22-tac-15-0.sprintlink.net (144.232.17.94) 1281.169 ms 1260.407 ms 1256.265 ms
17 sl-bb20-sea-0-0.sprintlink.net (144.232.9.150) 1272.078 ms 1292.073 ms 1379.581 ms
18 sl-gw11-sea-7-0.sprintlink.net (144.232.6.126) 1251.479 ms 1266.041 ms 1280.311 ms
19 sl-internap-88-0.sprintlink.net (144.228.95.46) 244.087 ms 264.212 ms 243.985 ms
20 border26s.ge1-1-bbnet1.sea.pnap.net (206.253.192.163) 242.164 ms 270.265 ms 253.408 ms
21 * * *
22 fe2-0.spk-2-sea.speakeasy.net (206.191.168.196) 250.064 ms 244.734 ms 248.823 ms
23 kurak.wgops.com (66.92.192.248) 295.366 ms 291.939 ms 366.895 ms
24 shell.wgops.com (66.92.192.108) 302.626 ms 298.338 ms 276.849 ms
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.
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.