Fixed
Status Update
Comments
do...@webrepublic.ch <do...@webrepublic.ch> #2
Correction: the AWS region affected is eu-west-1 (Ireland), not eu-central-1 (Frankfurt) as I mistakenly wrote.
ek...@google.com <ek...@google.com> #3
I believe this was a temporary issue that has since been resolved. Closing this bug report.
Description
For hosts in the eu-central Amazon Webservices zone, Google nameservers seem to always resolve
This might be the underlying issue of our observation that since around March 7th, a significant share of our calls to
** What steps will reproduce the problem? **
1. Resolve
** What is the expected output? What do you see instead? If you see error messages, please provide them. **
Expected output would be similar to other regions, e.g:
$ dig
172.217.16.138
172.217.22.74
172.217.16.202
172.217.18.106
172.217.21.202
216.58.205.234
172.217.21.234
172.217.22.10
172.217.18.170
216.58.206.10
216.58.207.74
Actual output is:
$ dig
74.125.193.95
** Please provide any additional information below. **
Note that this issue is not specific to the Sheets API — we've experienced it for all Google APIs that have their end points on
We first assumed a networking/connectivity issue on Amazon's end. Their support confirmed the issue, but suggested that the discrepancy in the DNS resolving results are the root cause.