Re: Any Cox.net ops in here?

[Marshall Eubanks <tme () multicasttech com>]

I get similar numbers from my house in Clifton, Virginia (through Cox  
Head End 8)

- to the server you used
--- 67.18.76.10 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 228.745/246.773/258.999/13.015 ms

- to AOL in Ashburn (25 miles)
--- 172.128.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 143.525/186.410/219.875/31.873 ms

- to Multicasttech in Tysons (20 miles)
--- 63.105.122.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 112.704/213.443/335.319/92.103 ms

I know that typical ping to the latter two boxes are order 30 msec or  
less normally, as I use
them all the time for debugging.

Both pinging to some boxes I know of in Cox, and doing a traceroute  
indicates that things go bad quickly.

[TME-Laptop-2:~/dump] tme% traceroute 63.105.122.1
traceroute to 63.105.122.1 (63.105.122.1), 64 hops max, 40 byte packets
1  10.0.1.1 (10.0.1.1)  8.530 ms  12.148 ms  8.774 ms
2  192.168.15.1 (192.168.15.1)  14.132 ms  47.469 ms  36.718 ms
3  ip70-179-104-1.dc.dc.cox.net (70.179.104.1)  295.610 ms  252.071  
ms  322.577 ms
4  ip68-100-1-177.dc.dc.cox.net (68.100.1.177)  272.860 ms  267.143  
ms  269.626 ms
5  ip68-100-0-65.dc.dc.cox.net (68.100.0.65)  368.170 ms  267.966 ms   
306.120 ms
6  mrfddsrj01gex070003.rd.dc.cox.net (68.100.0.141)  125.968 ms   
110.826 ms  116.504 ms
7  mrfdbbrj01-ge020.rd.dc.cox.net (68.1.1.4)  127.576 ms  156.926 ms   
173.118 ms
8  68.1.0.251 (68.1.0.251)  200.335 ms  271.170 ms  266.525 ms
9  68.105.31.74 (68.105.31.74)  204.000 ms  138.558 ms 68.105.31.86  
(68.105.31.86)  148.519 ms
10  v3495.mpd03.jfk02.atlas.cogentco.com (154.54.6.45)  155.448 ms   
161.556 ms  159.102 ms
11  t9-3.mpd01.dca01.atlas.cogentco.com (154.54.6.142)  131.390 ms   
203.528 ms  144.263 ms
12  g11-0-0.core01.dca01.atlas.cogentco.com (154.54.5.53)  160.153  
ms  156.100 ms  160.320 ms
13  v3587.na21.b002176-1.dca01.atlas.cogentco.com (38.20.32.14)   
116.804 ms  120.872 ms  135.297 ms

Regards
Marshall


On Oct 19, 2006, at 8:27 AM, Jamie Bowden wrote:

> For about the last two weeks, you've had something broken in your
> internal routing (here's a traceroute from my house in Reston to a
> server in TX, just as a sample):
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\jamie>tracert 67.18.76.10
>
> Tracing route to a.4c.1243.static.theplanet.com [67.18.76.10]
> over a maximum of 30 hops:
>
>   1    <1 ms    <1 ms    <1 ms  192.168.1.254
>   2     9 ms     9 ms     8 ms  ip68-100-160-1.dc.dc.cox.net
> [68.100.160.1]
>   3     8 ms     8 ms     7 ms  68.100.1.113
>   4    36 ms    38 ms    37 ms  ip68-100-0-65.dc.dc.cox.net
> [68.100.0.65]
>   5    60 ms    62 ms    57 ms  mrfddsrj02gex070003.rd.dc.cox.net
> [68.100.0.149]
>
>   6    68 ms    69 ms    68 ms  mrfdbbrj02-ge020.rd.dc.cox.net
> [68.1.1.6]
>   7    70 ms    67 ms    60 ms  nrfkbbrj02-so000000.rd.hr.cox.net
> [68.1.1.235]
>   8    54 ms    56 ms    87 ms  nrfkbbrj01-ge030.rd.hr.cox.net
> [68.1.0.22]
>   9    77 ms    83 ms    70 ms  dukebbrj01-so000100.rd.at.cox.net
> [68.1.0.20]
>  10   127 ms    92 ms    75 ms  dukebbrj02-ge030.tc.at.cox.net
> [68.1.0.3]
>  11   116 ms   134 ms   117 ms  nrfkbbrj01-as0.rd.hr.cox.net  
> [68.1.0.9]
>  12    98 ms    96 ms   101 ms  btnrbbrj01-ge030.rd.br.cox.net
> [68.1.1.204]
>  13   114 ms   111 ms   110 ms  dalsbbrj01-so-010000.r2.dl.cox.net
> [68.1.1.194]
>
>  14   106 ms   109 ms   114 ms  et2-25.ibr05.dllstx3.theplanet.com
> [70.85.126.22
> 5]
>  15    98 ms   101 ms    99 ms  vl31.dsr02.dllstx3.theplanet.com
> [70.85.127.30]
>
>  16   105 ms   107 ms   107 ms  vl22.dsr02.dllstx2.theplanet.com
> [70.85.127.76]
>
>  17   122 ms   116 ms   118 ms  vl1.car04.dllstx2.theplanet.com
> [12.96.160.14]
>  18   123 ms   124 ms   129 ms  a.4c.1243.static.theplanet.com
> [67.18.76.10]
>
> Trace complete.
>
> Until your internal routing went to hell, this normally took  
> <40ms.  Of
> course, the huge jump in latency from one router in NoVA to another
> didn't used to happen either, and the interesting routing through
> Norfolk two different times is just a bonus, so I have no idea what
> you've done to your network.
>
> Do you?
>
> Jamie