Level3 Routing Problems in Atlanta?

Scott Howard scott at doc.net.au
Thu Aug 6 01:02:16 CDT 2009


Starting a little closer and I'm seeing :

traceroute to 70.164.18.1 (70.164.18.1), 64 hops max, 52 byte packets
 1  ge-7-21.car1.Atlanta1.Level3.net (4.71.24.129)  0.393 ms  1.590 ms
1.492 ms
 2  ge-6-0-0-51.gar2.Atlanta1.Level3.net (4.68.103.7)  3.484 ms  3.981 ms
5.614 ms
 3  COX-COMMUNI.gar2.Atlanta1.Level3.net (65.59.222.6)  14.860 ms  124.165
ms  120.303 ms  <---
 4  mrfddsrj01-ge710.rd.dc.cox.net (68.1.1.5)  28.224 ms  28.221 ms  23.729
ms
 5  nova-gw.nova.org (70.164.18.1)  26.850 ms  34.466 ms  24.355 ms

Hop 4 seems a bit variable - sometimes it's there, sometimes it's not :
 3  COX-COMMUNI.gar2.Atlanta1.Level3.net (65.59.222.6)  10.614 ms  5.734 ms
15.114 ms
 4  * * *
 5  nova-gw.nova.org (70.164.18.1)  33.154 ms  27.222 ms  30.242 ms

Overall ping times to the host are jumping between 30ms and 130ms :

$ ping 70.164.18.1
PING 70.164.18.1 (70.164.18.1): 56 data bytes
64 bytes from 70.164.18.1: icmp_seq=0 ttl=251 time=122.090 ms
64 bytes from 70.164.18.1: icmp_seq=1 ttl=251 time=141.325 ms
64 bytes from 70.164.18.1: icmp_seq=2 ttl=251 time=137.261 ms
64 bytes from 70.164.18.1: icmp_seq=3 ttl=251 time=39.210 ms
64 bytes from 70.164.18.1: icmp_seq=4 ttl=251 time=33.649 ms
64 bytes from 70.164.18.1: icmp_seq=5 ttl=251 time=24.591 ms
64 bytes from 70.164.18.1: icmp_seq=6 ttl=251 time=128.027 ms
64 bytes from 70.164.18.1: icmp_seq=7 ttl=251 time=33.224 ms

  Scott.




On Wed, Aug 5, 2009 at 10:20 PM, Peter Beckman <beckman at angryox.com> wrote:

> I'm having a few troubles with L3 on this fine, dreadfully humid evening.
>
> HOST: max                         Loss%   Snt   Last   Avg  Best  Wrst
> StDev
>  1. mph                           0.0%    10    0.7   0.6   0.5   0.8   0.1
>  2. 10.1.41.89                    0.0%    10    1.7   1.9   1.7   2.3   0.2
>  3. G2-0-3-891.WASHDC-LCR-08.ver  0.0%    10    1.8   1.8   1.7   1.9   0.1
>  4. so-1-1-0-0.RES-BB-RTR2.veriz  0.0%    10    2.3   2.4   2.2   2.6   0.1
>  5. 0.so-1-2-0.XL4.IAD8.ALTER.NE  0.0%    10    2.8   2.8   2.6   3.0
> 0.1
>  6. 0.xe-8-1-0.BR1.IAD8.ALTER.NE  0.0%    10    4.8   4.6   2.9   4.9
> 0.6
>  7. te-11-3-0.edge1.Washington4.  0.0%    10    5.1   3.4   2.8   5.1   0.9
>  8. vlan69.csw1.Washington1.Leve  0.0%    10    3.6   6.7   3.5  14.6   4.1
>  9. ae-61-61.ebr1.Washington1.Le  0.0%    10   12.8   9.2   5.7  16.0   3.6
>  10. ae-2.ebr3.Atlanta2.Level3.ne 10.0%    10   19.9  23.9  19.9  31.8
> 4.1
>  11. ge-5-0-0-52.gar2.Atlanta1.Le  0.0%    10   21.4  21.3  21.0  21.8
> 0.2
>  12. COX-COMMUNI.gar2.Atlanta1.Le  0.0%    10  209.8 201.7 197.4 209.8
> 4.0 <-- ew
>  13. mrfddsrj01-ge710.rd.dc.cox.n 10.0%    10  230.3 230.5 223.9 234.1
> 3.4
>  14. 70.164.18.1                  10.0%    10  233.3 231.7 225.1 236.7
> 4.0
>
> Return trip:
> HOST: 70.164.19.xx                Loss%   Snt   Last   Avg  Best  Wrst
> StDev
>  1. 70.164.19.3                   0.0%    20    0.2   0.2   0.2   0.4   0.0
>  2. wsip-70-168-111-17.dc.dc.cox  5.0%    20   11.2  17.7   1.6  97.1  28.5
>  3. mrfddsrj01-ge706.rd.dc.cox.n 10.0%    20   36.9  42.0   1.4 282.6  79.5
>  4. 68.1.1.121                    0.0%    20   31.4  39.1  24.0 157.9  28.6
>  5. ae-2-52.edge2.Atlanta2.Level  5.0%    20  211.9 212.2 208.0 215.7   2.1
> <-- ew
>  6. 0.so-1-1-0.BR2.ATL4.ALTER.NE  0.0%    20  214.4 213.7 209.0 224.7
> 3.8
>  7. 0.so-2-1-0.XT1.ATL4.ALTER.NE  0.0%    20   51.7  55.6  50.6  62.5
> 3.3
>  8. 0.so-6-2-0.ATL01-BB-RTR1.VER  0.0%    20   56.7  60.0  51.0 123.1  15.1
>  9. so-7-1-0-0.LCC1-RES-BB-RTR1-  0.0%    20  229.6 231.6 228.6 239.7   2.8
>  10. P14-0.WASHDC-LCR-01.verizon-  0.0%    20   51.5  50.3  46.5  59.0
> 2.5
>  11. P13-0.WASHDC-LCR-03.verizon-  0.0%    20  226.9 245.0 226.9 363.4
>  33.0
>  12. P12-0.WASHDC-LCR-05.verizon-  0.0%    20  229.3 231.7 225.6 236.5
> 3.1
>  13. P15-0.WASHDC-LCR-07.verizon-  5.0%    20  320.0 243.6 226.6 324.9
>  29.3
>  14. ???                          100.0    20    0.0   0.0   0.0   0.0
> 0.0
>  15. mph (verizon vios in DC)      5.0%    20  231.3 232.1 227.2 235.2
> 2.3
>
> Anyone else see this?  Know what's going on?
>
> My route is kind of silly... I'm in Northern VA on Verizon FIOS, about 2
> physical miles from the IP on Cox.  Thank goodness for the speed of light.
>
> ---------------------------------------------------------------------------
> Peter Beckman                                                  Internet Guy
> beckman at angryox.com
> http://www.angryox.com/
> ---------------------------------------------------------------------------
>
>



More information about the NANOG mailing list