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
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... On Sun, Jun 18, 2017 at 6:46 PM, Tanner Ryan via Outages < outages@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@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Nick Kephart ThousandEyes Sr. Director of Product Management m: 415-728-7415
$150 / month for KYIH basically... https://www.thousandeyes.com/pricing Aryn H. K. Nakaoka anakaoka@trinet-hi.com Direct: 808.356.2901 Fax: 808.356.2919 Tri-net Solutions 518 Holokahana Lane Suite #200 Honolulu, HI 96817 http://www.trinet-hi.com https://twitter.com/AlohaTone Aloha Tone PBX https://www.youtube.com/watch?v=96YWPY9wCeU Aloha Tone (HA) High Availability http://youtu.be/rJsr4k0RBH8 A Better Solution https://www.trinet-hi.com/abettersolution.pdf <https://www.trinet-hi.com/abettersolution.pdf> CONFIDENTIALITY NOTICE: The information contained in this email and any attachments may be privileged, confidential and protected from disclosure. Any disclosure, distribution or copying of this email or any attachments by persons or entities other than the intended recipient is prohibited. If you have received this email in error, please notify the sender immediately by replying to the message and deleting this email and any attachments from your system. Thank you for your cooperation. ____________________________________________________________________ We took some time and made a fun demo for users to test the voicemail transcription. Handsfree tweeting. 1. Call 808-792-CARS (2277) and leave a voicemail 2. Check https://twitter.com/808792cars for the transcription On Mon, Jun 19, 2017 at 6:35 AM, Nick Kephart via Outages < outages@outages.org> wrote:
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@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@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Nick Kephart ThousandEyes Sr. Director of Product Management m: 415-728-7415 <(415)%20728-7415>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
https://www.thousandeyes.com/solutions/enterprise-it Aryn H. K. Nakaoka anakaoka@trinet-hi.com Direct: 808.356.2901 Fax: 808.356.2919 Tri-net Solutions 518 Holokahana Lane Suite #200 Honolulu, HI 96817 http://www.trinet-hi.com https://twitter.com/AlohaTone Aloha Tone PBX https://www.youtube.com/watch?v=96YWPY9wCeU Aloha Tone (HA) High Availability http://youtu.be/rJsr4k0RBH8 A Better Solution https://www.trinet-hi.com/abettersolution.pdf <https://www.trinet-hi.com/abettersolution.pdf> CONFIDENTIALITY NOTICE: The information contained in this email and any attachments may be privileged, confidential and protected from disclosure. Any disclosure, distribution or copying of this email or any attachments by persons or entities other than the intended recipient is prohibited. If you have received this email in error, please notify the sender immediately by replying to the message and deleting this email and any attachments from your system. Thank you for your cooperation. ____________________________________________________________________ We took some time and made a fun demo for users to test the voicemail transcription. Handsfree tweeting. 1. Call 808-792-CARS (2277) and leave a voicemail 2. Check https://twitter.com/808792cars for the transcription On Mon, Jun 19, 2017 at 6:53 AM, Aryn Nakaoka 808.356.2901 < anakaoka@trinet-hi.com> wrote:
$150 / month for KYIH basically...
https://www.thousandeyes.com/pricing
Aryn H. K. Nakaoka anakaoka@trinet-hi.com
Direct: 808.356.2901 <(808)%20356-2901> Fax: 808.356.2919 <(808)%20356-2919>
Tri-net Solutions 518 Holokahana Lane Suite #200 Honolulu, HI 96817 http://www.trinet-hi.com
Aloha Tone PBX https://www.youtube.com/watch?v=96YWPY9wCeU
Aloha Tone (HA) High Availability http://youtu.be/rJsr4k0RBH8
A Better Solution https://www.trinet-hi.com/abettersolution.pdf <https://www.trinet-hi.com/abettersolution.pdf> CONFIDENTIALITY NOTICE: The information contained in this email and any attachments may be privileged, confidential and protected from disclosure. Any disclosure, distribution or copying of this email or any attachments by persons or entities other than the intended recipient is prohibited. If you have received this email in error, please notify the sender immediately by replying to the message and deleting this email and any attachments from your system. Thank you for your cooperation.
____________________________________________________________________
We took some time and made a fun demo for users to test the voicemail transcription.
Handsfree tweeting. 1. Call 808-792-CARS (2277) and leave a voicemail 2. Check https://twitter.com/808792cars for the transcription
On Mon, Jun 19, 2017 at 6:35 AM, Nick Kephart via Outages < outages@outages.org> wrote:
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@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@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Nick Kephart ThousandEyes Sr. Director of Product Management m: 415-728-7415 <(415)%20728-7415>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
outages> $150 / month for KYIH basically... outages> [[https://www.thousandeyes.com/pricing]] Please keep commercials and marketing off this list. Have also reported this to the list moderators.
It's worth setting your on-site monitoring system to measure and record DNS lookup times to Google's resolvers. I also record the time to do "wget -p www.google.com". This gives me some insight into whether there's upstream problems.
Not Google, but Dyn’s DNS services have not been propagating zone updates at all for the past 36+ hours. It’s getting kind of annoying. -K From: Outages <outages-bounces@outages.org> on behalf of Tanner Ryan via Outages <outages@outages.org> Reply-To: Tanner Ryan <canadatechguy@gmail.com> Date: Sunday, June 18, 2017 at 8:46 PM To: "outages@outages.org" <outages@outages.org> Subject: [outages] Abnormal Google Public DNS Routing 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 ________________________________ This message and any attached files contain confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or without error as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
participants (6)
-
Aryn Nakaoka 808.356.2901 -
Karl Katzke -
Nick Kephart -
P E -
Paul M - outages -
Tanner Ryan