Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations.
Google Cloud · Último estado guardado del proveedor: resolved
El texto de la fuente oficial se muestra en su idioma original.
El último estado guardado de un evento no es el estado actual del servicio. Las listas de fuentes pueden ser incompletas, y desaparecer de una fuente no confirma recuperación. Abre el informe actual o la fuente oficial para obtener evidencia más reciente.
Detalles de evento guardados
- Estado del proveedor
- resolved
- Impacto del proveedor
- SERVICE DISRUPTION
- Registro del proveedor creado
- 08 Oct 2026, 18:24:18 UTC
- Registro del proveedor actualizado
- 09 Oct 2026, 16:50:52 UTC
- Inicio explícito del proveedor
- 08 Oct 2026, 12:19:00 UTC
- Fin explícito del proveedor
- 08 Oct 2026, 23:30:00 UTC
Componentes afectados reportados por el proveedor
- Google Cloud Storage
UwaYoXQ5bHYHG6EdiPB8
Estas asociaciones describen el alcance reportado del evento. No establecen disponibilidad actual de componentes ni dependencias verificadas.
La hora de creación de un registro no es necesariamente el inicio de una interrupción. Las horas no reportadas siguen sin estar disponibles. No calculamos el tiempo de inactividad a partir de las horas de recopilación.
Flujo público de incidentes de Google Cloud, validado con su catálogo. No es Personalized Service Health, estado de un proyecto particular, estado de aplicación Gemini ni Gemini API / AI Studio. Sin incidentes reportados no se confirma independientemente disponibilidad. La información de producto y ubicación del proveedor se conserva en actualizaciones; no se derivan resultados regionales de sondas.
Actualizaciones del proveedor en revisiones guardadas
Más recientes primero. Mostramos hasta 100 actualizaciones distintas de las últimas 20 revisiones de contenido guardadas. Las modificaciones de redacción a la misma hora del proveedor se conservan por separado.
- AVAILABLE
Reported products: Google Cloud Storage. No affected locations listed in this update. ## 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](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 database service contributed to additional metadata processing errors during a portion of the incident window. Google engineers have begun a full root cause analysis (RCA) and will provide additional information once it is available. ## Remediation The issue was initially detected by Google engineering teams actively monitoring system telemetry early in the incident window. To mitigate the issue, Google engineers executed the following step-by-step strategy: * Engineers initially attempted to dynamically allocate additional emergency capacity to the affected region, but this was blocked by systemic regional capacity limits. * To relieve immediate pressure, engineers selectively drained traffic from the most overloaded backend storage nodes. * A configuration change was deployed to disable the traffic sorting optimization, significantly reducing resource overhead on the storage backend. * For the concurrent metadata issue, engineers rolled back a recent update to the underlying metadata database service. Once traffic levels stabilized and resource utilization returned to normal baseline levels, the previously drained nodes were restored to active service, successfully restoring normal operations. ## Description of Impact On 08 October, 2026, from 04:00 to 16:30 US/Pacific, customers utilizing the us-central1 region experienced elevated latency and error rates during Cloud Storage upload and write operations. * Customers primarily observed HTTP 503 UNAVAILABLE errors on WriteObject operations and client-side timeouts. * A minor impact was also observed on read operations during this timeframe. * Cloud Storage operations in all other regions, as well as all other Google Cloud services, remained unaffected by this specific event.
Visto en una revisión guardada a las 09 Oct 2026, 16:52:37 UTC - AVAILABLE
Reported products: Google Cloud Storage. No affected locations listed in this update. ## \# 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](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 database service contributed to additional metadata processing errors during a portion of the incident window. Google engineers have begun a full root cause analysis (RCA) and will provide additional information once it is available. ## \#\# Remediation The issue was initially detected by Google engineering teams actively monitoring system telemetry early in the incident window. To mitigate the issue, Google engineers executed the following step-by-step strategy: * Engineers initially attempted to dynamically allocate additional emergency capacity to the affected region, but this was blocked by systemic regional capacity limits. * To relieve immediate pressure, engineers selectively drained traffic from the most overloaded backend storage nodes. * A configuration change was deployed to disable the traffic sorting optimization, significantly reducing resource overhead on the storage backend. * For the concurrent metadata issue, engineers rolled back a recent update to the underlying metadata database service. Once traffic levels stabilized and resource utilization returned to normal baseline levels, the previously drained nodes were restored to active service, successfully restoring normal operations. ## \#\# Description of Impact On 08 October, 2026, from 04:00 to 16:30 US/Pacific, customers utilizing the us-central1 region experienced elevated latency and error rates during Cloud Storage upload and write operations. * Customers primarily observed HTTP 503 UNAVAILABLE errors on WriteObject operations and client-side timeouts. * A minor impact was also observed on read operations during this timeframe. * Cloud Storage operations in all other regions, as well as all other Google Cloud services, remained unaffected by this specific event.
Visto en una revisión guardada a las 09 Oct 2026, 16:48:23 UTC - AVAILABLE
Reported products: Google Cloud Storage. No affected locations listed in this update. ## \# 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](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 database service contributed to additional metadata processing errors during a portion of the incident window. Google engineers have begun a full root cause analysis (RCA) and will provide additional information once it is available. ## \#\# Remediation The issue was initially detected by Google engineering teams actively monitoring system telemetry early in the incident window. To mitigate the issue, Google engineers executed the following step-by-step strategy: * Engineers initially attempted to dynamically allocate additional emergency capacity to the affected region, but this was blocked by systemic regional capacity limits. * To relieve immediate pressure, engineers selectively drained traffic from the most overloaded backend storage nodes. * A configuration change was deployed to disable the traffic sorting optimization, significantly reducing resource overhead on the storage backend. * For the concurrent metadata issue, engineers rolled back a recent update to the underlying metadata database service. Once traffic levels stabilized and resource utilization returned to normal baseline levels, the previously drained nodes were restored to active service, successfully restoring normal operations. ## \#\# Description of Impact On 08 October, 2026, from 04:00 to 16:30 US/Pacific, customers utilizing the us-central1 region experienced elevated latency and error rates during Cloud Storage upload and write operations. * Customers primarily observed HTTP 503 UNAVAILABLE errors on WriteObject operations and client-side timeouts. * A minor impact was also observed on read operations during this timeframe. * Cloud Storage operations in all other regions, as well as all other Google Cloud services, remained unaffected by this specific event.
Visto en una revisión guardada a las 09 Oct 2026, 16:46:22 UTC - SERVICE DISRUPTION
Reported products: Google Cloud Storage. Reported locations: Iowa (us-central1) (us-central1). **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.
Visto en una revisión guardada a las 09 Oct 2026, 16:52:37 UTC - AVAILABLE
Reported products: Google Cloud Storage. No affected locations listed in this update. **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.
Visto en una revisión guardada a las 09 Oct 2026, 00:16:16 UTC - SERVICE DISRUPTION
Reported products: Google Cloud Storage. Reported locations: Iowa (us-central1) (us-central1). **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.
Visto en una revisión guardada a las 09 Oct 2026, 16:52:37 UTC - SERVICE DISRUPTION
Reported products: Google Cloud Storage. Reported locations: Iowa (us-central1) (us-central1). **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.
Visto en una revisión guardada a las 09 Oct 2026, 16:52:37 UTC - SERVICE DISRUPTION
Reported products: Google Cloud Storage. Reported locations: Iowa (us-central1) (us-central1). **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.
Visto en una revisión guardada a las 09 Oct 2026, 16:52:37 UTC - SERVICE DISRUPTION
Reported products: Google Cloud Storage. Reported locations: Iowa (us-central1) (us-central1). **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.
Visto en una revisión guardada a las 09 Oct 2026, 16:52:37 UTC