Service Health
Incident affecting Google Distributed Cloud Edge
Cluster creation and update operations may fail in Google Distributed Cloud Edge
Incident began at 2024-08-15 16:38 and ended at 2024-08-15 17:51 (all times are US/Pacific).
Previously affected location(s)
Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Warsaw (europe-central2)Finland (europe-north1)Belgium (europe-west1)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)Columbus (us-east5)Dallas (us-south1)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)
Date | Time | Description | |
---|---|---|---|
| 15 Aug 2024 | 17:51 PDT | The issue with Google Distributed Cloud Edge has been resolved for all affected users as of Thursday, 2024-08-15 17:46 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 15 Aug 2024 | 17:01 PDT | Summary: Cluster creation and update operations may fail in Google Distributed Cloud Edge Description: We are experiencing an issue with Google Distributed Cloud Edge beginning at Thursday, 2024-08-15 10:45 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2024-08-15 18:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers will be unable to perform any cluster mutation operations like (cluster creation, upgrade, nodepool creation, cluster deletion, etc) Workaround: None at this time. |
- All times are US/Pacific