I forgot to say that DNS requests timeout randomly. I posted TR in case to help locate which Google DC gets this requests
On Wed, Aug 23, 2017 at 12:36 PM, cgm <999...@gmail.com> wrote: > Hi, > > Yes, is having random timeouts for us . TR to 8.8.8.8: > > 4. Google-level3-100G.LosAngeles1.Level3.net > 0.0% 2 9.9 9.9 9.9 > 9.9 0.0 > 5. 108.170.247.208 > 0.0% 2 10.0 10.0 10.0 10.1 0.0 > 6. 108.170.230.123 > 0.0% 2 17.1 17.1 17.1 17.1 0.0 > 7. 72.14.239.162 > 0.0% 2 39.0 38.8 38.7 39.0 0.2 > 8. 209.85.142.20 > 0.0% 2 38.6 38.8 38.6 38.9 0.2 > 9. ??? > > > > On Wed, Aug 23, 2017 at 12:30 PM, Mr. NPP via Outages <outages@outages.org > > wrote: > >> In los angeles, experiencing packet loss, slow resolution, and high ping >> times. it appears google's any cast dns is not working properly. >> >> --- 8.8.8.8 ping statistics --- >> 21 packets transmitted, 11 received, +1 errors, 47% packet loss, time >> 20229ms >> rtt min/avg/max/mdev = 44.635/151.432/258.331/76.230 ms >> >> from multiple providers. i would check over any2, but it appears my link >> to any2 is down (hopefully a separate issue) >> >> any confirm that they are seeing this issue? >> >> Thanks >> >> _______________________________________________ >> Outages mailing list >> Outages@outages.org >> https://puck.nether.net/mailman/listinfo/outages >> >> >
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages