Service Health
Incident affecting Google Compute Engine
We are experiencing an issue with Google Compute Engine in us-east1-c and us-east1-d
Incident began at 2020-06-29 08:30 and ended at 2020-06-29 09:56 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 29 Jun 2020 | 10:00 PDT | The issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific has been resolved for all affected users as of Monday, 2020-06-29 09:45 US/Pacific. The impact to us-east1-d has been mitigated by Monday, 2020-06-29 08:45 US/Pacific. The impact to us-east1-c has been mitigated by Monday, 2020-06-29 09:45 US/Pacific. For additional information on the broader outage and any follow up reports, please see https://status.cloud.google.com/incident/cloud-networking/20005 We thank you for your patience while we're working on resolving the issue. |
| 29 Jun 2020 | 09:56 PDT | The issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific has been resolved for all affected users as of Monday, 2020-06-29 09:45 US/Pacific. We are experiencing an issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific. The impact to us-east1-d has been mitigated by Monday, 2020-06-29 08:45 US/Pacific. The impact to us-east1-c has been mitigated by Monday, 2020-06-29 09:45 US/Pacific. We thank you for your patience while we're working on resolving the issue. |
| 29 Jun 2020 | 09:52 PDT | Description: We are experiencing an issue with Google Compute Engine in zones us-east1-c and us-east1-d where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:20 US/Pacific. The impact to us-east1-d has been mitigated by Monday, 2020-06-29 08:45 US/Pacific. The impact to us-east1-c is ongoing. Symptoms: Existing VMs may appear as unavailable and may be unreachable. New VM creation may fail. Our engineering team continues to investigate the issue. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 10:00 US/Pacific. |
| 29 Jun 2020 | 09:18 PDT | Description: We are experiencing an issue with Google Compute Engine affecting all zones in region us-east1 where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:15 US/Pacific. Symptoms: Existing VMs may appear as unavailable and may be unreachable. New VM creation may fail. Our engineering team continues to investigate the issue. For regular status updates, please follow: https://status.cloud.google.com/incident/cloud-networking/20005 where we will provide the next update by Monday, 2020-06-29 10:10 US/Pacific. |
| 29 Jun 2020 | 08:56 PDT | Description: We are experiencing an issue with Google Compute Engine in all zones in us-east1 where existing VMs may be unavailable or unreachable, and new VM creation may fail beginning on Monday, 2020-06-29 08:15 US/Pacific. Symptoms: Existing VMs may appear as unavailable and may be unreachable. New VM creation may fail. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2020-06-29 09:52 US/Pacific with current details. We apologize to all who are affected by the disruption. |
- All times are US/Pacific