Console

Service Health

This page provides status information on the services that are part of Google Cloud. 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 https://cloud.google.com/.

Incident affecting Google Cloud Storage

Google Cloud Storage elevated error rates

Incident began at 2017-06-27 07:30 and ended at 2017-06-30 01:45 (all times are US/Pacific).

Date Time Description
30 Jun 2017 01:47 PDT

The issue with degraded availability for some Google Cloud Storage objects has been resolved for all affected projects. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

We will provide a more detailed analysis of this incident once we have completed our internal investigation.
29 Jun 2017 16:12 PDT

Google engineers continue to work to restore the service. At this point, the error rate remains low. If your service or application is affected, we apologize.

We will provide another status update by June 30, 04:00 US/Pacific.
29 Jun 2017 07:07 PDT

Google engineers are continuing to restore the service. Error rates are continuing to decrease.

We will provide another status update by 15:00 June 29 US/Pacific.
28 Jun 2017 17:18 PDT

Starting at Tuesday 27 June 2017 07:30 PST, Google Cloud Storage started experiencing degraded availability for some objects based in us-central1 buckets (Regional, Nearline, Coldline, Durable Reduced Availability) and US multi-region buckets. Between 08:00 and 18:00 PST error rate was ~3.5%, error rates have since decreased to 0.5%. Errors are expected to be consistent for objects.

Customers do not need to make any changes at this time. Google engineers have identified the root cause and are working to restore the service. If your service or application is affected, we apologize.

We will provide another status update by 05:00 June 29 US/Pacific.