Re:Google Cloud Platform network outage in us-east1-c/d
by kessiler on Monday June 29, 2020 @01:12PM
(#23679554)
We are experiencing an issue with Cloud Networking in us-east1-c and us-east1-d, beginning on Monday, 2020-06-29 07:54 US/Pacific, affecting multiple Google Cloud Services.
Services in us-east1-d have been restored. Services in us-east1-c are still being restored. No ETA as of now.
Impact is due to power failure. A more detailed analysis will be available at a later time.
Our engineering team is working on recovery of impacted services.
We will provide an update by Monday, 2020-06-29 10:30 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones.
Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.
Services in us-east1-d have been restored. Services in us-east1-c are still being restored. No ETA as of now.
Impact is due to power failure. A more detailed analysis will be available at a later time.
Our engineering team is working on recovery of impacted services.
We will provide an update by Monday, 2020-06-29 10:30 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: Some services in us-east1-c and us-east1-d are failing, customers impacted by this incident would likely experience a total unavailability of zonal services hosted in us-east1-c or us-east1-d. It is possible for customers to experience service interruption in none, one, or both zones.
Workaround: Other zones in the region are not impacted. If possible, migrating workloads would mitigate impact. If workloads are unable to be migrated, there is no workaround at this time.