🟢 Operational

RESOLVED: Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.

Resolved

Started: 2026-10-08 18:24 UTC
29 days ago
Last update: 2026-10-14 07:17 UTC
23 days ago
Duration: 22h 22m

Timeline

14 Oct · 07:17 UTC 🟡 Resolved atom
Incident began at 2026-10-08 04:00 and ended at 2026-10-09 09:46 (all times are US/Pacific).

Incident Report
Date/Time of the Issue (All time US/Pacific)
Incident First Occurrence

Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Incident Recurrence

Recurrence Start: 09 October 2026 04:05

Recurrence End: 09 October 2026 09:46

Duration: 5 hours, 41 minutes

Total Duration: 18 hours, 11 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates while performing upload or write operations in the us-central1 region for a duration of 12 hours, 30 minutes. This was followed by a recurrence on Friday, 09 October 2026 in the us-central1-b zone for a duration of 5 hours, 41 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall due to increased traffic.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization configuration update to the Google Cloud Storage load balancing layer intended to address localized capacity constraints caused severe resource exhaustion on specific storage backend nodes in the affected region by inadvertently bypassing the standard capacity-aware routing logic, resulting in a severe load imbalance.
Consequently, a small fraction of storage backend nodes in the us-central1 region received an overwhelming proportion of incoming write traffic despite having low available serving capacity. This concentration of traffic led to resource exhaustion on the affected backend servers causing backend services handling object data ingestion to begin timing out.
Because the underlying instances could not process the high volume
14 Oct · 07:17 UTC 🟡 Resolved atom
Incident began at 2026-10-08 04:00 and ended at 2026-10-09 09:46 (all times are US/Pacific).

Incident Report
Date/Time of the Issue (All time US/Pacific)
Incident First Occurrence

Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Incident Recurrence

Recurrence Start: 09 October 2026 04:05

Recurrence End: 09 October 2026 09:46

Duration: 5 hours, 41 minutes

Total Duration: 18 hours, 11 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates while performing upload or write operations in the us-central1 region for a duration of 12 hours, 30 minutes. This was followed by a recurrence on Friday, 09 October 2026 in the us-central1-b zone for a duration of 5 hours, 41 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall due to increased traffic.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization configuration update to the Google Cloud Storage load balancing layer intended to address localized capacity constraints caused severe resource exhaustion on specific storage backend nodes in the affected region by inadvertently bypassing the standard capacity-aware routing logic, resulting in a severe load imbalance.
Consequently, a small fraction of storage backend nodes in the us-central1 region received an overwhelming proportion of incoming write traffic despite having low available serving capacity. This concentration of traffic led to resource exhaustion on the affected backend servers causing backend services handling object data ingestion to begin timing out.
Because the underlying instances could not process the high volume
14 Oct · 07:15 UTC 🟡 Resolved atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Incident Report
Date/Time of the Issue (All time US/Pacific)
Incident First Occurrence

Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Incident Recurrence

Recurrence Start: 09 October 2026 04:05

Recurrence End: 09 October 2026 09:46

Duration: 5 hours, 41 minutes

Total Duration: 18 hours, 11 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates while performing upload or write operations in the us-central1 region for a duration of 12 hours, 30 minutes. This was followed by a recurrence on Friday, 09 October 2026 in the us-central1-b zone for a duration of 5 hours, 41 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall due to increased traffic.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization configuration update to the Google Cloud Storage load balancing layer intended to address localized capacity constraints caused severe resource exhaustion on specific storage backend nodes in the affected region by inadvertently bypassing the standard capacity-aware routing logic, resulting in a severe load imbalance.
Consequently, a small fraction of storage backend nodes in the us-central1 region received an overwhelming proportion of incoming write traffic despite having low available serving capacity. This concentration of traffic led to resource exhaustion on the affected backend servers causing backend services handling object data ingestion to begin timing out.
Because the underlying instances could not process the high volume
14 Oct · 07:15 UTC 🟠 Resolved atom
Incident began at 2026-10-08 04:00 and ended at 2026-10-09 09:46 (all times are US/Pacific).

Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.

If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support

Date/Time of the Issue (All time US/Pacific)
Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates in the us-central1 region for a duration of 12 hours, 30 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Preliminary Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization intended to address localized capacity constraints caused severe resource exhaustion on specific backend storage nodes in the affected region.
This resource exhaustion caused backend services handling object data ingestion to begin timing out.
As a result, incoming upload and write requests routed to these nodes experienced elevated latency and failed to complete, resulting in errors surfaced to customers.
Concurrently, a separate issue with the underlying da
14 Oct · 07:15 UTC 🟠 Resolved atom
Incident began at 2026-10-08 04:00 and ended at 2026-10-09 09:46 (all times are US/Pacific).

Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.

If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support

Date/Time of the Issue (All time US/Pacific)
Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates in the us-central1 region for a duration of 12 hours, 30 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Preliminary Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization intended to address localized capacity constraints caused severe resource exhaustion on specific backend storage nodes in the affected region.
This resource exhaustion caused backend services handling object data ingestion to begin timing out.
As a result, incoming upload and write requests routed to these nodes experienced elevated latency and failed to complete, resulting in errors surfaced to customers.
Concurrently, a separate issue with the underlying da
14 Oct · 07:15 UTC 🟠 Resolved atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.

If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support

Date/Time of the Issue (All time US/Pacific)
Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates in the us-central1 region for a duration of 12 hours, 30 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Preliminary Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization intended to address localized capacity constraints caused severe resource exhaustion on specific backend storage nodes in the affected region.
This resource exhaustion caused backend services handling object data ingestion to begin timing out.
As a result, incoming upload and write requests routed to these nodes experienced elevated latency and failed to complete, resulting in errors surfaced to customers.
Concurrently, a separate issue with the underlying da
09 Oct · 16:50 UTC 🟠 Resolved atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.

If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support

Date/Time of the Issue (All time US/Pacific)
Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates in the us-central1 region for a duration of 12 hours, 30 minutes. We are taking immediate steps to ensure this doesn’t happen again.

Preliminary Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization intended to address localized capacity constraints caused severe resource exhaustion on specific backend storage nodes in the affected region.
This resource exhaustion caused backend services handling object data ingestion to begin timing out.
As a result, incoming upload and write requests routed to these nodes experienced elevated latency and failed to complete, resulting in errors surfaced to customers.
Concurrently, a separate issue with the underlying da
09 Oct · 16:46 UTC 🟠 Resolved atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

# Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.

If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support

Date/Time of the Issue (All time US/Pacific)
Incident Start: 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

## Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates in the us-central1 region for a duration of 12 hours, 30 minutes. We are taking immediate steps to ensure this doesn’t happen again.

## Preliminary Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization intended to address localized capacity constraints caused severe resource exhaustion on specific backend storage nodes in the affected region.
This resource exhaustion caused backend services handling object data ingestion to begin timing out.
As a result, incoming upload and write requests routed to these nodes experienced elevated latency and failed to complete, resulting in errors surfaced to customers.
Concurrently, a separate issue with the u
09 Oct · 16:44 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday, 2026-10-08 05:19 PDT.

The initial mitigations applied by our engineering team continue to show observable improvements in error rates.

Our engineering team is actively monitoring the environment and rolling out further mitigations to fully stabilize the service.

We will provide an update by Thursday, 2026-10-08 16:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
09 Oct · 16:44 UTC 🟠 Resolved atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

# Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete.

If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support

Date/Time of the Issue (All time US/Pacific)
Incident Start*:* 08 October 2026 04:00

Incident End: 08 October 2026 16:30

Duration: 12 hours, 30 minutes

## Summary
On Thursday, 08 October 2026, Google Cloud Storage experienced elevated write latency and write error rates in the us-central1 region for a duration of 12 hours, 30 minutes. We are taking immediate steps to ensure this doesn’t happen again.

## Preliminary Root Cause
Google Cloud Storage relies on a highly distributed backend architecture to process and store incoming data. During the incident window, specific storage backend nodes within the us-central1 region experienced a localized capacity shortfall.

The sequence of events leading to customer impact was as follows:

A traffic sorting optimization intended to address localized capacity constraints caused severe resource exhaustion on specific backend storage nodes in the affected region.
This resource exhaustion caused backend services handling object data ingestion to begin timing out.
As a result, incoming upload and write requests routed to these nodes experienced elevated latency and failed to complete, resulting in errors surfaced to customers.
Concurrently, a separate issue with the
09 Oct · 00:13 UTC 🟡 Resolved atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday, 2026-10-08 05:19 PDT.

The initial mitigations applied by our engineering team continue to show observable improvements in error rates.

Our engineering team is actively monitoring the environment and rolling out further mitigations to fully stabilize the service.

We will provide an update by Thursday, 2026-10-08 16:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 20:48 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday, 2026-10-08 05:19 PDT.

The initial mitigations applied by our engineering team continue to show observable improvements in error rates.

Our engineering team is actively monitoring the environment and rolling out further mitigations to fully stabilize the service.

We will provide an update by Thursday, 2026-10-08 16:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 20:48 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday, 2026-10-08 05:19 PDT.

The initial mitigations applied by our engineering team continue to show observable improvements in error rates. Our engineering team is actively monitoring the environment and rolling out further mitigations to fully stabilize the service.

We will provide an update by Thursday, 2026-10-08 14:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 20:48 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday, 2026-10-08 05:19 PDT.

The initial mitigations applied by our engineering team continue to show observable improvements in error rates. Our engineering team is actively monitoring the environment and rolling out further mitigations to fully stabilize the service.

We will provide an update by Thursday, 2026-10-08 14:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 19:38 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Initial mitigations applied by our engineering team leading to observable improvements in error rates in our internal monitoring beginning 10:57 PDT. Work remains underway to roll out further mitigations.

We will provide an update by Thursday, 2026-10-08 12:45 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 19:38 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Initial mitigations applied by our engineering team leading to observable improvements in error rates in our internal monitoring beginning 10:57 PDT. Work remains underway to roll out further mitigations.

We will provide an update by Thursday, 2026-10-08 12:45 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 19:38 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday, 2026-10-08 05:19 PDT.

The initial mitigations applied by our engineering team continue to show observable improvements in error rates. Our engineering team is actively monitoring the environment and rolling out further mitigations to fully stabilize the service.

We will provide an update by Thursday, 2026-10-08 14:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:55 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Initial mitigations applied by our engineering team leading to observable improvements in error rates in our internal monitoring beginning 10:57 PDT. Work remains underway to roll out further mitigations.

We will provide an update by Thursday, 2026-10-08 12:45 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:55 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Initial mitigations applied by our engineering team leading to observable improvements in error rates in our internal monitoring. Work remains underway to roll out further mitigations.

We will provide an update by Thursday, 2026-10-08 12:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:55 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Initial mitigations applied by our engineering team leading to observable improvements in error rates in our internal monitoring. Work remains underway to roll out further mitigations.

We will provide an update by Thursday, 2026-10-08 12:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:34 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 and ended at 2026-10-08 16:30 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2026-10-08 11:50 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:34 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2026-10-08 11:50 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:34 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Initial mitigations applied by our engineering team leading to observable improvements in error rates in our internal monitoring. Work remains underway to roll out further mitigations.

We will provide an update by Thursday, 2026-10-08 12:00 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)
08 Oct · 18:24 UTC 🟡 Investigating atom
Incident began at 2026-10-08 05:19 (all times are US/Pacific).

Summary

Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations

Description

We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2026-10-08 11:50 PDT with current details.

Customer Symptoms

Customers are experiencing elevated latencies and error rates when performing upload or write operations.
A smaller subset of read operations may also experience increased latency and errors

Workaround

None at this time.

Affected products: Google Cloud Storage

Affected locations: Iowa (us-central1)

Source

Official Google Cloud status — view original incident ↗

IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.