The October 8, 2026 Google Cloud Storage Outage
Introduction
Google Cloud Storage in us-central1 (Iowa) had elevated latency and error rates on upload and write operations on October 8, 2026, and a smaller subset of reads was also affected, according to Google's incident page. Google records the start at 11:00 UTC and the end at 23:30 UTC the same day - 12 hours 30 minutes. The outage report - fetched on October 12, 2026 - includes a preliminary incident report as of this writing. Google attributes the impact to a traffic sorting optimization that caused severe resource exhaustion on specific backend storage nodes in us-central1, and to a separate issue in the underlying database service that added metadata processing errors for part of the window. Google says the report is preliminary and a full root cause analysis is still underway.
- Introduction
- Methodology and Coverage
- Timeline of the Outage
- Impact and Root Cause
- Earlier Google Cloud Outages
- Conclusion
- FAQ
Methodology and Coverage
The sources below were fetched on October 12, 2026.
- Google's incident report page.
- Google's JSON incident history, entry
mSFVt6PiP557bjRyYsut.
Timeline of the Outage
Rows are from Google's own outage report.
| UTC | Event |
|---|---|
| Oct 8 11:00 | Incident start time according to the final update as of this writing. Note that the first outage update stated the start time as 12:19 UTC (05:19 PDT) |
| 17:57 | Google later said mitigations showed improvement in internal monitoring from this time (10:57 PDT). |
| 18:24 | Engineers continue to investigate. First update from Google. |
| 18:34 | Initial mitigations applied, improvement seen. |
| 18:55 | Same update, and it adds the 10:57 PDT improvement start. |
| 19:38 | "Continuing to mitigate". First update text naming us-central1. |
| 20:48 | Initial mitigations show improvements. |
| 23:30 | Incident end time recorded. |
| Oct 9 16:50 | Preliminary incident report (last update as of this writing). |
Impact window: 11:00 UTC to 23:30 UTC on October 8, 2026, 12 h 30 m from Google's stated start to the recorded end.
The thing to note here is that the first status page update happened after more than 7 hours of the outage starting.
Impact and Root Cause
Google's preliminary incident report, fetched on October 12, 2026, gives a summary of the root cause. Google says the text is its best knowledge at posting and is subject to change, and that a full root cause analysis is still underway.
Specific storage backend nodes in us-central1 had a capacity shortfall but it was localized (specific to one area). A traffic sorting optimization, intended to address localized capacity constraints, caused severe resource exhaustion on those nodes. Backend services that handle object data ingestion began timing out, and upload and write requests routed to those nodes saw elevated latency and failed. Concurrently, a separate issue with the underlying database service contributed to additional metadata processing errors during a portion of the window.
What Customers Experienced
Users of Google Cloud Storage might have experienced "elevated write latency and write error rates in the us-central1 region". Some reads were also slow or failing. The workaround field in every update before the preliminary report is "None at this time". The only region listed is Iowa (us-central1).
Services Affected
- Upload and write operations for Google Cloud Storage in us-central1, which had elevated latency and error rates.
- A smaller subset of reads in that region, which were also affected.
Severity
Google labeled the severity of this outage as "medium", with an impact of "SERVICE_DISRUPTION".
Confirmed Downstream Impacts
IncidentHub recorded 4 downstream outages which named the Google Cloud Storage outage as a cause.
| Affected Service | Impact (as stated in their outage report) |
|---|---|
| Torq | "a small number of accelerated steps in our US region have failed with a timeout error." |
| Temporal | "We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions" |
| Elastic Cloud | "Customers may experience delayed or unavailable project operations." |
| Mixpanel | "experiencing delays in our data ingestion pipeline, which is affecting real-time data for projects enrolled in the US projects, resulting in delays for a subset of projects" |
Earlier Google Cloud Outages
Google Cloud Platform experienced a total of 7 outages between October 13, 2025 and October 12, 2026.
Out of those, 2 outages affected Google Cloud Storage (including this one).
Two specific examples of Google Cloud Storage outages from previous years:
March 12, 2019 - Google Cloud Storage Incident #19002
Cloud Storage Incident #19002 was specific to Cloud Storage and lasted 4 hours 10 minutes, across all regions. Google's report says the internal blob storage service averaged 20% errors, with a peak of 31%, and Cloud Storage saw 4.8% average errors, across all bucket locations and storage classes. The cause according to that report was a config change that overloaded the system that looks up blob locations, leading to a cascading failure. The same report says Gmail, Google Photos and Google Drive also saw elevated errors.
June 12, 2025 - Multi-Product Google Cloud Outage
On June 12, 2025, a policy change with blank fields crashed Service Control, the API management layer, globally. The incident lasted about 7 hours 27 minutes, and us-central1 took the longest to recover, about 2 hours 40 minutes, according to Google's incident report. Cloud Storage is in Google's list of affected products for that incident. It was not a Cloud Storage-only outage.
Conclusion
Google Cloud Storage uploads and writes in us-central1 experienced elevated latency and errors from 11:00 UTC to 23:30 UTC on October 8, 2026, 12 hours 30 minutes based on Google's own outage report, and a smaller subset of reads was affected too. Google's preliminary report attributes the write failures to resource exhaustion on specific backend storage nodes in us-central1 after a traffic sorting optimization, and it names a separate database issue that added metadata errors for part of the window.
FAQ
How long did the October 8, 2026 Google Cloud Storage outage last?
12 hours 30 minutes. Google's own outage report records a start of 11:00 UTC and an end of 23:30 UTC on October 8, 2026.
What caused it?
A traffic sorting optimization, according to Google's preliminary report. That report says the change was meant to address localized capacity constraints and instead caused severe resource exhaustion on specific backend storage nodes in us-central1, so services handling data ingestion into Google Cloud Storage timed out and uploads and writes to those nodes failed. It also says a separate issue in the underlying database service added metadata processing errors for part of the window.
Which region was listed?
us-central1 (Iowa). That is the only region named in Google's updates.
Was there a workaround?
No. Every status update before the preliminary report says "None at this time".
Did other companies report impact from this incident?
IncidentHub recorded 4 confirmed downstream outages which named the Google Cloud Storage outage as a cause.
IncidentHub is not affiliated with any of the services and vendors mentioned in this article. All logos and company names are trademarks or registered trademarks of their respective holders. This summary is independent and not affiliated with or endorsed by Google or any of the services and vendors mentioned in this article.
This article was first published on the IncidentHub blog.
You might also like: