Google Cloud Status Dashboard
This page provides status information on the services that are part of Google Cloud Platform. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit cloud.google.com.
Google Cloud DNS Incident #21001
We are experiencing an issue with Cloud DNS CNAME chasing in multiple zones.
Incident began at 2021-01-21 15:55 and ended at 2021-01-21 19:17 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Jan 21, 2021 | 19:17 | The issue with Cloud DNS has been resolved for all affected projects as of Thursday, 2021-01-21 19:17 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|
The issue with Cloud DNS has been resolved for all affected projects as of Thursday, 2021-01-21 19:17 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|||
| Jan 21, 2021 | 18:48 | Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. The following zones are known to be impacted currently: us-east1-d Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-01-21 19:15 US/Pacific. We will provide more information by Thursday, 2021-01-21 19:15 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|
Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. The following zones are known to be impacted currently: us-east1-d Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-01-21 19:15 US/Pacific. We will provide more information by Thursday, 2021-01-21 19:15 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|||
| Jan 21, 2021 | 18:16 | Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. The following zones are known to be impacted currently: europe-west1-c Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-01-21 18:45 US/Pacific. We will provide more information by Thursday, 2021-01-21 18:45 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|
Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. The following zones are known to be impacted currently: europe-west1-c Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-01-21 18:45 US/Pacific. We will provide more information by Thursday, 2021-01-21 18:45 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|||
| Jan 21, 2021 | 17:39 | Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. The following zones are known to be impacted currently: asia-east1-a australia-southeast1-a europe-west1-c europe-west2-a us-east1-d us-west1-a Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-01-21 18:30 US/Pacific. We will provide more information by Thursday, 2021-01-21 18:15 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|
Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. The following zones are known to be impacted currently: asia-east1-a australia-southeast1-a europe-west1-c europe-west2-a us-east1-d us-west1-a Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-01-21 18:30 US/Pacific. We will provide more information by Thursday, 2021-01-21 18:15 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|||
| Jan 21, 2021 | 17:31 | Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. Mitigation work is currently underway by our engineering team. The following zones are known to be impacted: asia-east1-a asia-east2-c asia-northeast1-a asia-northeast2-c asia-northeast3-c asia-south1-a asia-southeast1-a asia-southeast2-c australia-southeast1-a europe-west1-c europe-west2-a europe-west3-a europe-west6-c southamerica-east1-a us-central1-d us-east1-d us-west1-a us-west2-c us-west3-c us-west4-c We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2021-01-21 18:00 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|
Description: Customers using CNAME chasing may experience an issue with Cloud DNS. Querying for a record defined in one private zone that points to a record in another private zone does not return the final answer. See https://cloud.google.com/dns/docs/cnamechasing for more details about CNAME chasing. Mitigation work is currently underway by our engineering team. The following zones are known to be impacted: asia-east1-a asia-east2-c asia-northeast1-a asia-northeast2-c asia-northeast3-c asia-south1-a asia-southeast1-a asia-southeast2-c australia-southeast1-a europe-west1-c europe-west2-a europe-west3-a europe-west6-c southamerica-east1-a us-central1-d us-east1-d us-west1-a us-west2-c us-west3-c us-west4-c We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2021-01-21 18:00 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|||
| Jan 21, 2021 | 16:26 | Description: Mitigation work is currently underway by our engineering team. The following zones are known to be impacted: asia-east1-a We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2021-01-21 17:30 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|
Description: Mitigation work is currently underway by our engineering team. The following zones are known to be impacted: asia-east1-a We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2021-01-21 17:30 US/Pacific. Diagnosis: CNAME chasing between private zone to private zone is not working. Workaround: None at this time. |
|||