🟢 Operational
RESOLVED: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.
Resolved
- Started
- 2026-08-20 19:37 UTC
32 days ago - Last update
- 2026-08-27 21:45 UTC
25 days ago - Duration
- 0s
Timeline
-
27 Aug · 21:45 UTC
🟠 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business operations. Recognizing your reliance on Google Cloud, we express our sincere regrets for any operational impact experienced. Our engineering teams are actively addressing the underlying root cause to prevent future recurrences.
Please note that the information provided herein reflects our current understanding as of the time of publication and remains subject to revision as the investigation progresses. A comprehensive Incident Report detailing preventive measures will be issued upon conclusion of our inquiry.
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: 20 August 2026 08:00
Incident End: 20 August 2026 10:22
Duration: 2 hours, 22 minutes
Summary
On Thursday, 20 August 2026, multiple Google Cloud services encountered elevated latency, provisioning failures, increased error rates, and service degradations lasting for a duration of 2 hours and 22 minutes.
Preliminary Root Cause
The disruption originated during scheduled fiber optic maintenance, which unexpectedly compromised network capacity between data centers within the us-west1 region. Automated rerouting mechanisms failed to properly redistribute traffic to alternate capacity, resulting in network congestion as volumes exceeded available bandwidth in the affected area.
This underlying network degradation subsequently impacted higher-level service components through request throttling, increased latency, and cascading retries. Consequently, both control plane operations and data plane requests failed to execute successfully across several dependent Google Cloud services, producing the observed latency and elevated error rates.
Remediation
Internal m -
27 Aug · 21:45 UTC
🔴 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Incident Report
Summary
On Thursday, 20 August 2026, from 08:00 to 10:22 US/Pacific (15:00 to 17:22 UTC), multiple Google Cloud services in the us-west1 region experienced elevated latency, provisioning failures, increased error rates, and widespread service degradations for a total duration of 2 hours and 22 minutes. The incident impacted a wide range of core services — including Persistent Disk, Google Kubernetes Engine, Google Compute Engine, Cloud Run, Google Cloud Bigtable, Cloud Storage, and Identity and Access Management — across both control plane operations and data plane requests.
We sincerely apologize for the disruption this incident caused to your business operations and critical workloads. We recognize the vital role Google Cloud plays in supporting your organization, and we deeply regret the impact on your business operations and critical workloads. Engineering and infrastructure teams are actively implementing measures to address the root causes and strengthen network resiliency to prevent recurrences in the future. Specifically, teams are monitoring recovery progress, refining safety checks for planned optical maintenance, and optimizing regional traffic routing mechanisms to safeguard against unexpected capacity constraints.
Root Cause
The disruption originated during scheduled fiber optic maintenance, which unexpectedly compromised network capacity between data centers within the us-west1 region. Automated rerouting mechanisms failed to properly redistribute traffic to alternate capacity, resulting in network congestion as volumes exceeded available bandwidth in the affected area.
This underlying network degradation subsequently impacted higher-level service components through severe packet loss, request throttling, and increased latency across inter-campus dependencies. Core infrastructure services, including Spanner Paxos consensus and the Unified Me -
25 Aug · 06:20 UTC
🟠 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Preliminary Incident Report
We sincerely apologize for the disruption this incident caused to your business operations. Recognizing your reliance on Google Cloud, we express our sincere regrets for any operational impact experienced. Our engineering teams are actively addressing the underlying root cause to prevent future recurrences.
Please note that the information provided herein reflects our current understanding as of the time of publication and remains subject to revision as the investigation progresses. A comprehensive Incident Report detailing preventive measures will be issued upon conclusion of our inquiry.
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: 20 August 2026 08:00
Incident End: 20 August 2026 10:22
Duration: 2 hours, 22 minutes
Summary
On Thursday, 20 August 2026, multiple Google Cloud services encountered elevated latency, provisioning failures, increased error rates, and service degradations lasting for a duration of 2 hours and 22 minutes.
Preliminary Root Cause
The disruption originated during scheduled fiber optic maintenance, which unexpectedly compromised network capacity between data centers within the us-west1 region. Automated rerouting mechanisms failed to properly redistribute traffic to alternate capacity, resulting in network congestion as volumes exceeded available bandwidth in the affected area.
This underlying network degradation subsequently impacted higher-level service components through request throttling, increased latency, and cascading retries. Consequently, both control plane operations and data plane requests failed to execute successfully across several dependent Google Cloud services, producing the observed latency and elevated error rates.
Remediation
Internal m -
25 Aug · 06:20 UTC
🟡 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Summary
The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated.
Description
We have mitigated the issue impacting multiple products in our us-west1 region as of Thursday, 2026-08-20 10:22 PDT.
Our engineering teams have restored capacity on a planned optical maintenance that caused unexpected congestion in Dalles, Oregon metro /us-west1 region. Our systems stabilized and services have recovered once capacity was restored. Our teams are continuing to monitor for any residual impact.
We will publish an analysis of this incident once we have completed our internal investigation.
We thank you for your patience while we worked on resolving the issue.
Diagnosis / Customer Symptoms
Customers in us-west1 may have experienced timeouts, service degradations, errors, and elevated latencies across multiple products.
Workaround
This issue is now mitigated.
Affected products: AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Data Fusion, Cloud Filestore, Cloud Key Management Service, Cloud Monitoring, Cloud Run, Contact Center AI Platform, Dataproc Metastore, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Managed Service for Apache Kafka, Persistent Disk
Affected locations: Global, Oregon (us-west1) -
20 Aug · 19:37 UTC
🟡 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Summary
The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated.
Description
We have mitigated the issue impacting multiple products in our us-west1 region as of Thursday, 2026-08-20 10:22 PDT.
Our engineering teams have restored capacity on a planned optical maintenance that caused unexpected congestion in Dalles, Oregon metro /us-west1 region. Our systems stabilized and services have recovered once capacity was restored. Our teams are continuing to monitor for any residual impact.
We will publish an analysis of this incident once we have completed our internal investigation.
We thank you for your patience while we worked on resolving the issue.
Diagnosis / Customer Symptoms
Customers in us-west1 may have experienced timeouts, service degradations, errors, and elevated latencies across multiple products.
Workaround
This issue is now mitigated.
Affected products: AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Data Fusion, Cloud Filestore, Cloud Key Management Service, Cloud Monitoring, Cloud Run, Contact Center AI Platform, Dataproc Metastore, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Managed Service for Apache Kafka, Persistent Disk
Affected locations: Global, Oregon (us-west1) -
20 Aug · 19:37 UTC
🟡 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Summary
The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated.
Description
We have mitigated the issue impacting multiple products in our us-west1 region as of Thursday, 2026-08-20 10:22 PDT.
Our engineering teams have restored capacity on a planned optical maintenance that caused unexpected congestion in Dalles, Oregon metro /us-west1 region. Our systems stabilized and services have recovered once capacity was restored. Our teams are continuing to monitor for any residual impact.
We will publish an analysis of this incident once we have completed our internal investigation.
We thank you for your patience while we worked on resolving the issue.
Diagnosis / Customer Symptoms
Customers in us-west1 may have experienced timeouts, service degradations, errors, and elevated latencies across multiple products.
Workaround
This issue is now mitigated.
Affected products: AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Data Fusion, Cloud Filestore, Cloud Key Management Service, Cloud Monitoring, Cloud Run, Contact Center AI Platform, Dataproc Metastore, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Managed Service for Apache Kafka, Persistent Disk
Affected locations: Global, Oregon (us-west1) -
20 Aug · 19:37 UTC
🟡 Resolved
atom
Incident began at 2026-08-20 08:40 and ended at 2026-08-20 12:20 (all times are US/Pacific).
Summary
The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated.
Description
We have mitigated the issue impacting multiple products in our us-west1 region as of Thursday, 2026-08-20 10:22 PDT.
Our engineering teams have restored capacity on a planned optical maintenance that caused unexpected congestion in Dalles, Oregon metro /us-west1 region. Our systems stabilized and services have recovered once capacity was restored. Our teams are continuing to monitor for any residual impact.
We will publish an analysis of this incident once we have completed our internal investigation.
We thank you for your patience while we worked on resolving the issue.
Diagnosis / Customer Symptoms
Customers in us-west1 may have experienced timeouts, service degradations, errors, and elevated latencies across multiple products.
Workaround
This issue is now mitigated.
Affected products: AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Data Fusion, Cloud Filestore, Cloud Key Management Service, Cloud Monitoring, Cloud Run, Contact Center AI Platform, Dataproc Metastore, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Managed Service for Apache Kafka, Persistent Disk
Affected locations: Global, Oregon (us-west1)
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.