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 Kubernetes Engine Incident #21001
GKE cluster operations may fail in various regions.
Incident began at 2021-02-01 17:17 and ended at 2021-02-01 18:20 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Feb 01, 2021 | 18:20 | The issue with Google Kubernetes Engine has been resolved for all affected projects as of Monday, 2021-02-01 18:19 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|
The issue with Google Kubernetes Engine has been resolved for all affected projects as of Monday, 2021-02-01 18:19 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
|||
| Feb 01, 2021 | 17:48 | Description: We are experiencing an intermittent issue with Google Kubernetes Engine. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2021-02-01 18:32 US/Pacific with current details. Locations: * asia-east2 * asia-northeast2 * asia-northeast3 * asia-southeast2 * europe-north1 * us-central1 We apologize to all who are affected by the disruption. Diagnosis: Clusters and node-pool creation operation may ended up with an error. Workaround: None at this time. |
|
Description: We are experiencing an intermittent issue with Google Kubernetes Engine. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2021-02-01 18:32 US/Pacific with current details. Locations: * asia-east2 * asia-northeast2 * asia-northeast3 * asia-southeast2 * europe-north1 * us-central1 We apologize to all who are affected by the disruption. Diagnosis: Clusters and node-pool creation operation may ended up with an error. Workaround: None at this time. |
|||