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. For additional information on these services, please visit cloud.google.com.
Google Compute Engine Incident #16008
We are investigating a problem with GCE Instances that were created before mid-February in Zones us-central1-b, europe-west1-c and asia-east1-b
Incident began at 2016-04-21 15:18 and ended at 2016-04-22 02:55 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Apr 22, 2016 | 01:55 | An issue is ongoing with a very small number of Google Compute Engine instances hanging during startup. The root cause has been established and mitigation is in progress. Affected instances can be recovered by manually stopping them and starting them again. We were able to identify affected projects and will notify appropriate project contacts within the next 60 minutes. Current data indicates that less than 0.001% of projects were affected by the issue. No further public communications will be made on this issue. |
|
An issue is ongoing with a very small number of Google Compute Engine instances hanging during startup. The root cause has been established and mitigation is in progress. Affected instances can be recovered by manually stopping them and starting them again. We were able to identify affected projects and will notify appropriate project contacts within the next 60 minutes. Current data indicates that less than 0.001% of projects were affected by the issue. No further public communications will be made on this issue. |
|||
| Apr 21, 2016 | 23:00 | We are still investigating the issue with Google Compute Engine. We will provide another status update by 03:00 US/Pacific with current details. |
|
We are still investigating the issue with Google Compute Engine. We will provide another status update by 03:00 US/Pacific with current details. |
|||
| Apr 21, 2016 | 21:00 | We are still investigating the issue with Google Compute Engine. We will provide another status update by 23:00 US/Pacific with current details. |
|
We are still investigating the issue with Google Compute Engine. We will provide another status update by 23:00 US/Pacific with current details. |
|||
| Apr 21, 2016 | 19:16 | We are still investigating the issue with Google Compute Engine. We will provide another status update by 21:00 US/Pacific with current details. Affected zones correction: Zone [asia-east1-b] is currently affected but zone [asia-east1-a] is not affected. |
|
We are still investigating the issue with Google Compute Engine. We will provide another status update by 21:00 US/Pacific with current details. Affected zones correction: Zone [asia-east1-b] is currently affected but zone [asia-east1-a] is not affected. |
|||
| Apr 21, 2016 | 18:00 | We are still investigating this problem and we'll provide a new update at 7:00 pm PT |
|
We are still investigating this problem and we'll provide a new update at 7:00 pm PT |
|||
| Apr 21, 2016 | 17:00 | We Continue investigating this problem and we'll provide a new update at 6:00 pm PT |
|
We Continue investigating this problem and we'll provide a new update at 6:00 pm PT |
|||
| Apr 21, 2016 | 16:13 | We are currently investigating a problem with GCE instances created before mid-February in regions us-central1-b, europe-west1-c and asia-east1-a where instance restarts will render them unavailable. |
|
We are currently investigating a problem with GCE instances created before mid-February in regions us-central1-b, europe-west1-c and asia-east1-a where instance restarts will render them unavailable. |
|||