Service Health
Incident affecting Google Compute Engine, Google Kubernetes Engine
Google Compute Engine and Google Kubernetes Engine are experiencing issues with some instance, node, cluster operations
Incident began at 2023-06-08 16:44 and ended at 2023-06-08 17:57 (all times are US/Pacific).
Previously affected location(s)
Las Vegas (us-west4)
Date | Time | Description | |
---|---|---|---|
| 8 Jun 2023 | 17:57 PDT | The issue with Google Compute Engine, Google Kubernetes Engine has been resolved for all affected projects as of Thursday, 2023-06-08 17:57 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 8 Jun 2023 | 17:39 PDT | Summary: Google Compute Engine and Google Kubernetes Engine are experiencing issues with some instance, node, cluster operations Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2023-06-08 18:30 US/Pacific. Diagnosis: Google Compute Engine (GCE):
Google Kubernetes Engine (GKE):
Workaround: Customers can use other zones and regions where feasible |
| 8 Jun 2023 | 17:29 PDT | Summary: Google Compute Engine is experiencing issues with instance create, delete, suspend, and resume operations in us-west4-b Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2023-06-08 18:30 US/Pacific. Diagnosis:
Workaround: Customers can use other zones and regions where feasible |
| 8 Jun 2023 | 17:00 PDT | Summary: Google Compute Engine is experiencing issues with instance create, delete, suspend, and resume operations in us-west4-b Description: We are experiencing an issue with Google Compute Engine beginning at Thursday, 2023-06-08 16:22 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-06-08 17:45 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis:
Workaround: Customers can use other zones and regions where feasible |
- All times are US/Pacific