[outages] Abnormal Google Public DNS Routing

[Nick Kephart]

Tanner,

Google has definitely been modifying their internal Google Public DNS
routes over the past month. We've seen this is various cities across the
Americas (US, Canada, Brazil, Colombia). In all cases it has dramatically
increased number of hops in the Google network and the latency of the
connection (20-100ms depending on the location).

Toronto's routing changed Fri June 9th 16:45 UTC:
https://tdmjwoq.share.thousandeyes.com

Other locations (Los Angeles, Rio, Montreal, Bogota, Dallas) have changed
to this new routing via Google data centers over the past month. You can
see the timing here:
https://app.thousandeyes.com/share/reports/snapshots/70941004-e312-4c41-9ddc-d30fae08358d

On Sun, Jun 18, 2017 at 6:46 PM, Tanner Ryan via Outages <
outages at outages.org> wrote:

> Hello,
>
> Has anyone experienced any issues with Google Public DNS in the past 5
> days or so?
>
> My connection to the public resolver usually enters Google at the Toronto
> Internet Exchange (TORIX), and terminates at Google's caching node in
> Toronto. For the past few days, the connection is still entering in at
> TORIX, but is routing much further into Google's network to terminate.
>
> Before DNS resolutions were getting resolved in Toronto, but now are
> getting passed to the Council Bluffs (Iowa) data center. This not only
> causes DNS resolution times to increase, but I am also noticing some
> resolution timeouts every once in a while.
>
> I also know that there has been a lot of issues with Google Public DNS in
> Brazil for the past few days. I've seen this abnormal routing start around
> the same time that the issues in Brazil started.
>
> Is anyone else also seeing this abnormal routing or experiencing these
> issues?
>
>
> ~Tanner
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>


-- 
Nick Kephart
ThousandEyes
Sr. Director of Product Management
m: 415-728-7415
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20170619/71c6d9d7/attachment.htm>