Service Health

This page provides status information on the services that are part of Google Cloud. 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 https://cloud.google.com/.

Incident affecting Traffic Director, Google Cloud DNS, Google Cloud Networking, Service Directory

Cloud DNS customers attempting to use new public ManagedZones are non-functional

Incident began at 2023-06-28 09:25 and ended at 2023-06-28 14:34 (all times are US/Pacific).

Previously affected location(s)

Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)Turin (europe-west12)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)Paris (europe-west9)Doha (me-central1)Tel Aviv (me-west1)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Dallas (us-south1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)

Date Time Description
28 Jun 2023 14:34 PDT

The issue with Google Cloud DNS, Service Directory, Traffic Director has been resolved for all affected users as of Wednesday, 2023-06-28 14:20 US/Pacific.

We thank you for your patience while we worked on resolving the issue.

28 Jun 2023 13:11 PDT

Summary: Cloud DNS customers attempting to use new public ManagedZones are non-functional

Description: Mitigation work is currently underway by our engineering team.

The mitigation is taking longer than expected.

We will provide more information by Wednesday, 2023-06-28 15:30 US/Pacific.

Diagnosis: Customers are able to create new public ManagedZones, but these zones are not served on our DNS nameservers. This manifests as DNS resolution failures for names in the newly created Managed Zones.

Workaround: None at this time.

28 Jun 2023 12:23 PDT

Summary: Cloud DNS customers attempting to use new public ManagedZones are non-functional

Description: Mitigation work is currently underway by our engineering team.

The mitigation is taking longer than expected.

We will provide more information by Wednesday, 2023-06-28 13:30 US/Pacific.

Diagnosis: Customers are able to create new public ManagedZones, but these zones are not served on our DNS nameservers. This manifests as DNS resolution failures for names in the newly created Managed Zones.

Workaround: None at this time.

28 Jun 2023 10:58 PDT

Summary: Cloud DNS customers attempting to use new public ManagedZones are non-functional

Description: Mitigation work is currently underway by our engineering team.

The mitigation is expected to complete by Wednesday, 2023-06-28 12:15 US/Pacific.

We will provide more information by Wednesday, 2023-06-28 12:30 US/Pacific.

Diagnosis: Customers are able to create new public ManagedZones, but these zones are not served on our DNS nameservers. This manifests as DNS resolution failures for names in the newly created Managed Zones.

Workaround: None at this time.

28 Jun 2023 09:44 PDT

Summary: Cloud DNS customers attempting to use new public ManagedZones are non-functional

Description: We are experiencing an issue with Google Cloud DNS, Service Directory, Traffic Director beginning at Wednesday, 2023-06-27 15:30 US/Pacific.

Our engineering team continues to investigate the issue.

We will provide an update by Wednesday, 2023-06-28 11:15 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: Customers are able to create new public ManagedZones, but these zones are not served on our DNS nameservers. This manifests as DNS resolution failures for names in the newly created Managed Zones.

Workaround: None at this time.