[outages] Intermittent ICMP and DNS for 4.2.2.[123]

Taner Halicioglu taner at taner.net
Wed Oct 19 13:38:32 EDT 2011 

Not to possibly point out the obvious, but 4.2.2.2 is an anycast address, so
you'll be hitting all sorts of different destiantions when trying to trace to
it, depending on where you are.

e.g., I tested from a few shells I have around:

LA:
  6. ae-21-70.car1.LosAngeles1.Le  0.0%     5   10.8  11.8   9.3  18.2   3.6
  7. vnsc-bak.sys.gtei.net         0.0%     5    9.7  11.0   9.7  12.6   1.2

TX:
  6. xe-8-1-0.edge4.Dallas3.Level  0.0%     5    0.6   0.7   0.6   0.9   0.1
  7. ae-31-80.car1.Dallas1.Level3  0.0%     5  163.2 157.8 123.5 181.6  22.2
  8. vnsc-bak.sys.gtei.net        80.0%     5   30.0  30.0  30.0  30.0   0.0


Bay Area (Fremont):
  6. ae-11-60.car1.SanJose1.Level  0.0%     5    2.1   6.0   1.9  22.0   9.0
  7. vnsc-bak.sys.gtei.net         0.0%     5    2.0   2.0   1.9   2.1   0.1

So it seems that (at least) the one in TX might have issues).

	-T


On Wed, Oct 19, 2011 at 12:08:11PM -0500, Dan White <dwhite at olp.net> wrote:

> 10-4:
> 
> ~$ mtr -n -c 100 --report 4.2.2.2
> HOST: quark                       Loss%   Snt   Last   Avg  Best  Wrst StDev
>   1.|-- 10.0.2.1                   0.0%   100    1.9   1.9   0.8   4.5 0.7
>   2.|-- 67.217.152.5               0.0%   100    1.5   2.4   0.8  10.3 1.8
>   3.|-- 67.217.151.97              0.0%   100    1.1   4.1   0.9 136.6 15.9
>   4.|-- 67.217.152.34              0.0%   100    1.5   1.6   1.5   2.4 0.1
>   5.|-- 4.71.13.121                0.0%   100    8.6  23.7   8.5 341.7 49.5
>   6.|-- 4.2.2.2                   60.0%   100   47.4  45.0  40.0  54.7 3.2
> 
> Under normal circumstances, I typically see at least one more hop in front
> of 4.2.2.2, and much lower latency.
> 
> From this, I assume the packet loss I'm seeing is due to a problem within
> Level 3's network. And may be limited to a Dallas link/router, based on
> others' reports.
> 
> On 19/10/11 11:45 -0500, Frank Bulk wrote:
> >If you're seeing packet loss on pings, please use a tool like mtr to show
> >where it's happening.
> >
> >Frank
> >
> >-----Original Message-----
> >From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
> >Behalf Of Dan White
> >Sent: Wednesday, October 19, 2011 11:21 AM
> >To: Josh Luthman
> >Cc: outages at outages.org
> >Subject: Re: [outages] Intermittent ICMP and DNS for 4.2.2.[123]
> >
> >Additional information (I'm still seeing the problem)
> >
> >~$ traceroute 4.2.2.2
> >traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 60 byte packets
> > 1  10.0.2.1 (10.0.2.1)  3.813 ms  3.779 ms  4.183 ms
> > 2  olp-67-217-152-5.olp.net (67.217.152.5)  2.547 ms  2.582 ms  2.761 ms
> > 3  router.olp.net (67.217.151.97)  2.520 ms  2.514 ms  2.509 ms
> > 4  olp-67-217-152-34.olp.net (67.217.152.34)  2.678 ms  2.659 ms  2.582 ms
> > 5  ge-6-10-183.car1.dallas1.level3.net (4.71.13.121)  11.008 ms  11.010 ms
> >11.002 ms
> > 6  * * *
> > 7  * * *
> > 8  * * *
> > 9  * * *
> >10  vnsc-bak.sys.gtei.net (4.2.2.2)  56.222 ms  61.235 ms  61.239 ms
> >
> >~$ ping -c 10 4.2.2.2
> >PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
> >64 bytes from 4.2.2.2: icmp_req=1 ttl=59 time=51.1 ms
> >64 bytes from 4.2.2.2: icmp_req=6 ttl=59 time=57.0 ms
> >64 bytes from 4.2.2.2: icmp_req=7 ttl=59 time=35.5 ms
> >64 bytes from 4.2.2.2: icmp_req=8 ttl=59 time=31.7 ms
> >
> >--- 4.2.2.2 ping statistics ---
> >10 packets transmitted, 4 received, 60% packet loss, time 9045ms
> >rtt min/avg/max/mdev = 31.754/43.865/57.000/10.493 ms
> >
> >~$ ping -c 10 4.71.13.121
> >PING 4.71.13.121 (4.71.13.121) 56(84) bytes of data.
> >64 bytes from 4.71.13.121: icmp_req=1 ttl=251 time=14.7 ms
> >64 bytes from 4.71.13.121: icmp_req=2 ttl=251 time=9.15 ms
> >64 bytes from 4.71.13.121: icmp_req=3 ttl=251 time=9.14 ms
> >64 bytes from 4.71.13.121: icmp_req=4 ttl=251 time=8.82 ms
> >64 bytes from 4.71.13.121: icmp_req=5 ttl=251 time=11.3 ms
> >64 bytes from 4.71.13.121: icmp_req=6 ttl=251 time=9.72 ms
> >64 bytes from 4.71.13.121: icmp_req=7 ttl=251 time=8.47 ms
> >64 bytes from 4.71.13.121: icmp_req=8 ttl=251 time=8.47 ms
> >64 bytes from 4.71.13.121: icmp_req=9 ttl=251 time=9.57 ms
> >64 bytes from 4.71.13.121: icmp_req=10 ttl=251 time=9.49 ms
> >
> >--- 4.71.13.121 ping statistics ---
> >10 packets transmitted, 10 received, 0% packet loss, time 9014ms
> >rtt min/avg/max/mdev = 8.471/9.898/14.793/1.809 ms
> >
> >
> >On 19/10/11 12:14 -0400, Josh Luthman wrote:
> >ping -c 10 4.2.2
> >>Rock solid at 26 ms for me
> >>
> >>-> traceroute 4.2.2.2
> >>traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 40 byte packets
> >>1  rrcs-74-218-208-193.central.biz.rr.com (74.218.208.193)  0.531 ms
> >>0.485 ms  0.450 ms
> >>2  rrcs-74-218-88-133.central.biz.rr.com (74.218.88.133)  0.418 ms
> >>0.390 ms  0.589 ms
> >>3  rrcs-74-218-88-129.central.biz.rr.com (74.218.88.129)  1.061 ms
> >>2.046 ms  2.024 ms
> >>4  vln864.dytnoh1-swt101.woh.rr.com (74.218.88.73)  3.000 ms  2.977
> >>ms  2.943 ms
> >>5  gig2-1-801.dytnoh1-rtr102.woh.rr.com (70.60.47.5)  2.910 ms  2.884
> >>ms  2.858 ms
> >>6  gig5-0.dytnoh1-rtr1.woh.rr.com (24.29.160.21)  2.840 ms  2.845 ms
> >1.922 ms
> >>7  tge5-1-0.tr00.clmkohpe.mwrtn.rr.com (65.25.137.177)  8.852 ms
> >>8.812 ms  8.788 ms
> >>8  ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68)  18.744 ms  18.953 ms
> >>ae-9-0.cr0.chi30.tbone.rr.com (107.14.19.16)  18.692 ms
> >>9  107.14.17.147 (107.14.17.147)  18.899 ms
> >>ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155)  18.874 ms  18.839 ms
> >>10  xe-10-2-0.edge2.Chicago2.Level3.net (4.59.28.109)  25.573 ms
> >>xe-10-0-0.edge2.Chicago2.Level3.net (4.59.28.101)  25.549 ms
> >>xe-10-2-0.edge2.Chicago2.Level3.net (4.59.28.109)  25.507 ms
> >>11  vlan51.ebr1.Chicago2.Level3.net (4.69.138.158)  25.482 ms  25.458
> >>ms vlan52.ebr2.Chicago2.Level3.net (4.69.138.190)  25.432 ms
> >>12  ae-6-6.ebr1.Chicago1.Level3.net (4.69.140.189)  41.152 ms  34.879
> >>ms  35.936 ms
> >>13  ae-11-51.car1.Chicago1.Level3.net (4.69.138.3)  35.880 ms
> >>ae-21-52.car1.Chicago1.Level3.net (4.69.138.35)  35.848 ms  35.822 ms
> >>14  vnsc-bak.sys.gtei.net (4.2.2.2)  36.780 ms  36.755 ms
> >>
> >>Josh Luthman
> >>Office: 937-552-2340
> >>Direct: 937-552-2343
> >>1100 Wayne St
> >>Suite 1337
> >>Troy, OH 45373
> >>
> >>
> >>
> >>On Wed, Oct 19, 2011 at 11:59 AM, Dan White <dwhite at olp.net> wrote:
> >>>I've been noticing packet loss while pinging 4.2.2.1, 4.2.2.2, and
> >4.2.2.3
> >>>in the last few minutes, which are usually my go to IP addresses for
> >>>testing external server connectivity.
> >>>
> >>>DNS also seems to be intermittent.
> >>>
> >>>--
> >>>Dan White
> >>>_______________________________________________
> >>>Outages mailing list
> >>>Outages at outages.org
> >>>https://puck.nether.net/mailman/listinfo/outages
> >>>
> >>
> >
> >-- 
> >Dan White
> >BTC Broadband
> >Ph  918.366.0248 (direct)   main: (918)366-8000
> >Fax 918.366.6610            email: dwhite at olp.net
> >http://www.btcbroadband.com
> >_______________________________________________
> >Outages mailing list
> >Outages at outages.org
> >https://puck.nether.net/mailman/listinfo/outages
> >
> >
> >
> >_______________________________________________
> >Outages mailing list
> >Outages at outages.org
> >https://puck.nether.net/mailman/listinfo/outages
> >
> 
> -- 
> Dan White
> BTC Broadband
> Ph  918.366.0248 (direct)   main: (918)366-8000
> Fax 918.366.6610            email: dwhite at olp.net
> http://www.btcbroadband.com
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages

More information about the Outages mailing list