
On Apr 4, 2016, at 2:14 PM, Adam Greene via Outages <outages@outages.org> wrote:
Hi,
We’re troubleshooting some customer reports of sluggish Internet performance. Issues do not seem to be originating on our network. Pings to www.google.com <http://www.google.com/> [216.58.219.228] show 25 – 50% packet loss, via multiple carriers.
Anyone else seeing issues?
From FIOS in NNJ: PING 216.58.219.228 (216.58.219.228): 56 data bytes 64 bytes from 216.58.219.228: icmp_seq=0 ttl=57 time=3.926 ms 64 bytes from 216.58.219.228: icmp_seq=1 ttl=57 time=3.654 ms Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 64 bytes from 216.58.219.228: icmp_seq=4 ttl=57 time=3.531 ms 64 bytes from 216.58.219.228: icmp_seq=5 ttl=57 time=3.696 ms 64 bytes from 216.58.219.228: icmp_seq=6 ttl=57 time=3.131 ms 64 bytes from 216.58.219.228: icmp_seq=7 ttl=57 time=3.223 ms 64 bytes from 216.58.219.228: icmp_seq=8 ttl=57 time=3.304 ms Request timeout for icmp_seq 9 64 bytes from 216.58.219.228: icmp_seq=10 ttl=57 time=3.389 ms 64 bytes from 216.58.219.228: icmp_seq=11 ttl=57 time=3.481 ms ^C --- 216.58.219.228 ping statistics --- 12 packets transmitted, 9 packets received, 25.0% packet loss round-trip min/avg/max/stddev = 3.131/3.482/3.926/0.237 ms Via HE.net in NYC: PING 216.58.219.228 (216.58.219.228): 56 data bytes 64 bytes from 216.58.219.228: icmp_seq=0 ttl=58 time=1.316 ms 64 bytes from 216.58.219.228: icmp_seq=1 ttl=58 time=1.479 ms 64 bytes from 216.58.219.228: icmp_seq=3 ttl=58 time=1.120 ms 64 bytes from 216.58.219.228: icmp_seq=4 ttl=58 time=1.203 ms 64 bytes from 216.58.219.228: icmp_seq=5 ttl=58 time=1.436 ms 64 bytes from 216.58.219.228: icmp_seq=7 ttl=58 time=1.191 ms 64 bytes from 216.58.219.228: icmp_seq=8 ttl=58 time=1.736 ms 64 bytes from 216.58.219.228: icmp_seq=9 ttl=58 time=3.806 ms 64 bytes from 216.58.219.228: icmp_seq=11 ttl=58 time=1.583 ms 64 bytes from 216.58.219.228: icmp_seq=13 ttl=58 time=1.066 ms 64 bytes from 216.58.219.228: icmp_seq=14 ttl=58 time=3.659 ms 64 bytes from 216.58.219.228: icmp_seq=15 ttl=58 time=1.215 ms 64 bytes from 216.58.219.228: icmp_seq=16 ttl=58 time=1.138 ms 64 bytes from 216.58.219.228: icmp_seq=17 ttl=58 time=1.054 ms 64 bytes from 216.58.219.228: icmp_seq=18 ttl=58 time=1.235 ms 64 bytes from 216.58.219.228: icmp_seq=19 ttl=58 time=1.057 ms 64 bytes from 216.58.219.228: icmp_seq=20 ttl=58 time=2.597 ms ^C --- 216.58.219.228 ping statistics --- 21 packets transmitted, 17 packets received, 19.0% packet loss round-trip min/avg/max/stddev = 1.054/1.641/3.806/0.845 ms AWS in VA: ubuntu@ucontrol:~$ ping 216.58.219.228 PING 216.58.219.228 (216.58.219.228) 56(84) bytes of data. 64 bytes from 216.58.219.228: icmp_seq=1 ttl=47 time=8.16 ms 64 bytes from 216.58.219.228: icmp_seq=2 ttl=47 time=17.7 ms 64 bytes from 216.58.219.228: icmp_seq=3 ttl=47 time=8.55 ms 64 bytes from 216.58.219.228: icmp_seq=5 ttl=47 time=8.24 ms 64 bytes from 216.58.219.228: icmp_seq=6 ttl=47 time=8.26 ms 64 bytes from 216.58.219.228: icmp_seq=7 ttl=47 time=8.62 ms 64 bytes from 216.58.219.228: icmp_seq=8 ttl=47 time=8.32 ms 64 bytes from 216.58.219.228: icmp_seq=9 ttl=47 time=8.26 ms 64 bytes from 216.58.219.228: icmp_seq=10 ttl=47 time=16.7 ms 64 bytes from 216.58.219.228: icmp_seq=11 ttl=47 time=8.29 ms 64 bytes from 216.58.219.228: icmp_seq=12 ttl=47 time=8.14 ms 64 bytes from 216.58.219.228: icmp_seq=13 ttl=47 time=8.12 ms 64 bytes from 216.58.219.228: icmp_seq=14 ttl=47 time=8.30 ms 64 bytes from 216.58.219.228: icmp_seq=16 ttl=47 time=8.16 ms 64 bytes from 216.58.219.228: icmp_seq=17 ttl=47 time=8.20 ms 64 bytes from 216.58.219.228: icmp_seq=18 ttl=47 time=8.18 ms 64 bytes from 216.58.219.228: icmp_seq=19 ttl=47 time=8.15 ms 64 bytes from 216.58.219.228: icmp_seq=20 ttl=47 time=8.12 ms ^C --- 216.58.219.228 ping statistics --- 20 packets transmitted, 18 received, 10% packet loss, time 19058ms rtt min/avg/max/mdev = 8.124/9.257/17.779/2.835 ms As to whether that’s rate limiting of icmp or not, that’s for google to know. :) I’m not seeing any issues getting to any google services, but none of them are resolving to that IP (or that IP block) either… Charles
Thanks, Adam
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://puck.nether.net/mailman/listinfo/outages>