On 09/12/12 16:08 -0400, Josh Luthman wrote:
Is anyone seeing any issues to 4.2.2.2?
At 3:35 EST I starting seeing packet loss (icmp ping) to it - http://imgur.com/ITGL1
I noticed at the same time we had a route change with RR (Time Warner Cable) in Chicago.
I am not seeing loss to the 4.2.2.2 located near Dallas: ~$ traceroute 4.2.2.2 traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 60 byte packets 1 olp-67-217-151-193.olp.net (67.217.151.193) 0.484 ms 0.563 ms 0.645 ms 2 olp-67-217-152-34.olp.net (67.217.152.34) 0.988 ms 1.063 ms 1.135 ms 3 ae5-694.edge9.Dallas1.Level3.net (4.30.66.17) 7.891 ms 9.835 ms 7.910 ms 4 ae-4-90.edge3.Dallas1.Level3.net (4.69.145.200) 7.904 ms ae-2-70.edge3.Dallas1.Level3.net (4.69.145.72) 7.961 ms ae-1-60.edge3.Dallas1.Level3.net (4.69.145.8) 7.939 ms 5 b.resolvers.Level3.net (4.2.2.2) 36.606 ms 8.030 ms 8.034 ms ~# ping -A -c 100 -q 4.2.2.2 PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. --- 4.2.2.2 ping statistics --- 100 packets transmitted, 100 received, 0% packet loss, time 890ms rtt min/avg/max/mdev = 7.913/8.796/13.416/1.326 ms, pipe 2, ipg/ewma 8.996/8.421 ms -- Dan White