Service Health
Incident affecting Google Cloud Networking
Some customer VMs may be unreachable in us-central1-b.
Incident began at 2022-05-23 01:26 and ended at 2022-05-23 09:30 (all times are US/Pacific).
Previously affected location(s)
Iowa (us-central1)
Date | Time | Description | |
---|---|---|---|
| 23 May 2022 | 14:55 PDT | We apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Support by opening a case using https://cloud.google.com/support or help article https://support.google.com/a/answer/1047213. (All Times US/Pacific) Incident Start: 23 May 2021 01:26 Incident End: 23 May 2021 09:30 Duration: 8 hours, 4 minutes Affected Services and Features: Google Cloud Networking Regions/Zones: us-central1-b Description: Google Cloud Networking experienced issues causing Google Compute Engine instances to be unreachable in us-central1-b for a duration of 8 hours, 4 minutes. From preliminary analysis, the root cause is a roll out in us-central1-b. The issue was mitigated by rolling back the changes. Customer Impact: Affected customers would have experienced issues with network traffic between Google Compute Engine instances within us-central1-b of the same VPC. |
| 23 May 2022 | 09:35 PDT | The issue with Google Cloud Networking has been resolved for all affected users as of Monday, 2022-05-23 09:29 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 23 May 2022 | 09:05 PDT | Summary: Some customer VMs may be unreachable in us-central1-b. Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Monday, 2022-05-23 10:00 US/Pacific. We will provide more information by Monday, 2022-05-23 10:30 US/Pacific. Diagnosis: VMs may be unreachable in us-central1-b. Workaround: Customer can try migrating VMs to another cluster in us-central1-b. |
| 23 May 2022 | 09:01 PDT | Summary: Some customer VMs may be unreachable in us-central1-b. Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Monday, 2022-05-23 10:00 US/Pacific. We will provide more information by Monday, 2022-05-23 10:00 US/Pacific. Diagnosis: VMs may be unreachable in us-central1-b. Workaround: Customer can try migrating VMs to another cluster in us-central1-b. |
- All times are US/Pacific