[ale] slashdot? [OT]

Wed Aug 13 08:54:51 EDT 2008

2008/8/13 Forsaken <forsaken at targaryen.us>

>
> On Aug 13, 2008, at 7:24 AM, Jim Kinney wrote:
>
> I can get to slashdot now. Router appears to be back online.
>
> I'm pretty sure that the "multiple paths" mentality should have prevented
> that from occuring but I guess it was cheaper to have controllable nodes
> that can be switched off... </conspiracy theory>
>
>
> This is what I see from home for an mtr to slashdot.
>
>  1. gw-vl3-dorne.targaryen.local  0.0%    10    1.1   1.1   1.1   1.2   0.0
>   2. valyria.targaryen.local       0.0%    10   63.8  12.4   2.5  63.8
>  19.4
>   3. c-76-17-32-1.hsd1.ga.comcast 10.0%    10   16.4  13.0   8.5  22.9
> 5.7
>   4. ge-2-2-ur01.g3lilburn.ga.atl 10.0%    10    8.1  15.1   8.1  29.8
> 7.2
>   5. te-9-1-ur01.g4snellville.ga.  0.0%    10   10.6  10.9   8.0  23.9
> 4.7
>   6. te-9-1-ur01.g5snellville.ga. 10.0%    10   13.9  13.0   9.5  26.0
> 5.2
>   7. te-9-1-ur01.d2lithonia.ga.at  0.0%    10    9.0  10.1   8.4  14.0
> 1.7
>   8. te-9-2-ur01.d1stonemtn.ga.at 10.0%    10   10.1   9.6   8.4  10.7
> 0.7
>   9. po-3-ar01.d1stonemtn.ga.atla 10.0%    10    8.6  10.2   8.6  12.3
> 1.2
>  10. te-8-1-ar02.b0atlanta.ga.atl  0.0%    10   12.8  13.0  11.3  17.6
> 1.8
>  11. te-0-1-0-4-cr01.atlanta.ga.i  0.0%    10   13.7  14.9  10.7  30.0
> 5.7
>  12. pos-0-12-0-0-cr01.mclean.va.  0.0%    10   26.1  27.5  26.1  29.7
> 1.3
>  13. 208.173.158.5                10.0%    10   28.1  30.2  26.5  36.7
> 3.9
>  14. cpr1-pos-11-0.virginiaequini 10.0%    10   26.5  30.0  26.2  52.6
> 8.5
>  15. ber1-tenge-2-1.virginiaequin 10.0%    10   26.8  29.8  25.8  51.2
> 8.1
>  16. cr1-tengig0-7-2-0.washington 50.0%    10   27.8  28.5  27.5  29.4
> 0.8
>  17. cr2-loopback.chd.savvis.net   0.0%    10   74.6  65.7  53.2 102.0
>  15.0
>  18. hr2-tengigabitethernet-12-1.  0.0%    10   50.6  55.2  49.1  78.4
> 8.8
>  19. csr1-ve243.elkgrovech3.savvi  0.0%    10   52.5  74.9  51.1 259.4
>  65.2
>  20. 64.27.160.194                 0.0%    10   50.9  73.5  50.2 208.0
>  48.3
>  21. slashdot.org                  0.0%    10   48.7  67.8  48.7 158.6
>  32.8
>
> Hop 16 looks like it's probably overloaded. 50% packetloss tells me it's
> probably dropping ICMP traffic as low priority, and the average latency for
> the next hop more than doubles, so I'd suspect something is up with the
> handoff there. It might be they're having to suck in a DDoS or something.
>
> I'm seeing similar stats here as well.  My speakeasy connection looks like:
traceroute to slashdot.org (216.34.181.45), 30 hops max, 40 byte packets
 1  192.168.0.101 (192.168.0.101)  0.193 ms  0.159 ms  0.154 ms
 2  dsl027-165-001.atl1.dsl.speakeasy.net (216.27.165.1)  13.690 ms  14.606
ms  16.606 ms
 3  110.ge-0-0-0.cr1.atl1.speakeasy.net (69.17.82.137)  16.575 ms  16.520
ms  19.532 ms
 4  Vlan106.msfc1.A56-Atlanta.teleglobe.net (64.86.13.69)  20.432 ms  20.412
ms  22.371 ms
 5  if-2-2.har1.A56-Atlanta.teleglobe.net (64.86.9.33)  25.413 ms  26.287
ms  26.272 ms
 6  if-11-0-0.core3.AEQ-Ashburn.teleglobe.net (64.86.9.18)  43.343 ms
26.917 ms  27.760 ms
 7  Vlan22.icore1.AEQ-Ashburn.teleglobe.net (216.6.51.2)  27.764 ms  25.364
ms  27.357 ms
 8  ix-13-20.icore1.AEQ-Ashburn.teleglobe.net (209.58.27.46)  27.342 ms
30.312 ms ix-13-21.icore1.AEQ-Ashburn.teleglobe.net (216.6.42.2)  31.180 ms
 9  * * *
10  cr2-tengig-0-0-5-0.chicago.savvis.net (204.70.195.117)  65.132 ms
70.164 ms  72.137 ms
11  hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (204.70.195.122)
65.041 ms  50.744 ms  50.738 ms
12  csr1-ve243.elkgrovech3.savvis.net (216.64.194.50)  55.743 ms  55.736 ms
59.850 ms
13  64.27.160.194 (64.27.160.194)  55.814 ms  55.803 ms  55.788 ms
14  slashdot.org (216.34.181.45)  58.785 ms  59.616 ms  59.608 ms

yet a different system gets a different path through savvis:

traceroute to slashdot.org (216.34.181.45), 30 hops max, 38 byte packets
 1  64.238.111.129 (64.238.111.129)  1.330 ms  1.648 ms  1.536 ms
 2  172.16.142.65 (172.16.142.65)  3.427 ms  3.389 ms  3.348 ms
 3  192.168.14.65 (192.168.14.65)  4.006 ms  3.818 ms  3.599 ms
 4  192.168.34.26 (192.168.34.26)  4.359 ms  4.394 ms  4.343 ms
 5  w005.z207088188.cle-oh.dsl.cnc.net (207.88.188.5)  19.119 ms  19.092 ms
19.292 ms
 6  te-11-4-0.rar3.washington-dc.us.xo.net (207.88.12.201)  19.731 ms
19.684 ms  19.392 ms
 7  207.88.12.202.ptr.us.xo.net (207.88.12.202)  19.367 ms  19.395 ms
19.107 ms
 8  cpr2-pos-1-1.VirginiaEquinix.savvis.net (208.173.52.5)  19.195 ms
19.735 ms  19.197 ms
 9  ber1-tenge-2-1.virginiaequinix.savvis.net (204.70.193.6)  19.170 ms
19.259 ms  19.626 ms
10  cr1-tengig0-7-2-0.washington.savvis.net (204.70.197.242)  20.258 ms
20.358 ms  20.169 ms
11  cr2-loopback.chd.savvis.net (208.172.2.71)  34.466 ms  38.917 ms  35.241
ms
12  hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (204.70.195.122)
34.259 ms  32.110 ms  32.082 ms
13  csr1-ve243.elkgrovech3.savvis.net (216.64.194.50)  33.010 ms  33.136 ms
32.887 ms
14  64.27.160.194 (64.27.160.194)  36.046 ms  34.869 ms  36.174 ms
15  slashdot.org (216.34.181.45)  31.961 ms  33.812 ms  32.026 ms

Note that 2-4 are showing as private subnets. Hmm. They are clearly outside
of network but still inside the ISP boundaries. Hmm.

-- 
-- 
James P. Kinney III
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20080813/7b4fabb3/attachment-0001.html 