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. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit cloud.google.com.
Google Cloud Storage Incident #20007
We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific.
Incident began at 2020-10-27 13:21 and ended at 2020-10-27 14:09 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Oct 27, 2020 | 14:09 | The issue with Google Cloud Storage buckets in us-central1 seeing higher latency and timeout errors has been resolved for all affected projects as of Tuesday, 2020-10-27 13:30 US/Pacific. |
|
The issue with Google Cloud Storage buckets in us-central1 seeing higher latency and timeout errors has been resolved for all affected projects as of Tuesday, 2020-10-27 13:30 US/Pacific. |
|||
| Oct 27, 2020 | 13:53 | Description: We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Mitigation has been effective and we believe the issue should be resolved as of Tuesday, 2020-10-27 13:30 US/Pacific. We are continuing to monitor the situation for any changes. We will provide more information by Tuesday, 2020-10-27 14:15 US/Pacific. Diagnosis: Affected customers may experience request timeout errors. Downstream services may include Google Container Registry with images being stored in us-central1. This may cause GKE workloads to have trouble pulling new images in us-central1. Workaround: None at this time. |
|
Description: We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Mitigation has been effective and we believe the issue should be resolved as of Tuesday, 2020-10-27 13:30 US/Pacific. We are continuing to monitor the situation for any changes. We will provide more information by Tuesday, 2020-10-27 14:15 US/Pacific. Diagnosis: Affected customers may experience request timeout errors. Downstream services may include Google Container Registry with images being stored in us-central1. This may cause GKE workloads to have trouble pulling new images in us-central1. Workaround: None at this time. |
|||
| Oct 27, 2020 | 13:38 | Description: We are experiencing an issue with Google Cloud Storage requests timing out as of Tuesday, 2020-10-27 11:00 US/Pacific. Google Container Registry is also experiencing timeout errors as a result of the Google Cloud Storage issues. Our engineers are currently investigating the root cause and working to mitigate the issue. We will provide more information by Tuesday, 2020-10-27 14:15 US/Pacific. Location: us-central1 Diagnosis: Affected customers may experience request timeout errors. Workaround: None at this time. |
|
Description: We are experiencing an issue with Google Cloud Storage requests timing out as of Tuesday, 2020-10-27 11:00 US/Pacific. Google Container Registry is also experiencing timeout errors as a result of the Google Cloud Storage issues. Our engineers are currently investigating the root cause and working to mitigate the issue. We will provide more information by Tuesday, 2020-10-27 14:15 US/Pacific. Location: us-central1 Diagnosis: Affected customers may experience request timeout errors. Workaround: None at this time. |
|||
| Oct 27, 2020 | 13:24 | Description: We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Our engineers are currently investigating the root cause. We will provide more information by Tuesday, 2020-10-27 14:00 US/Pacific. Location: us-central1 Diagnosis: Affected customers may experience request timeout errors. Workaround: None at this time. |
|
Description: We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Our engineers are currently investigating the root cause. We will provide more information by Tuesday, 2020-10-27 14:00 US/Pacific. Location: us-central1 Diagnosis: Affected customers may experience request timeout errors. Workaround: None at this time. |
|||