Is Google Cloud down? › Outage history › Aug 20, 2026

Google Cloud outage on Aug 20, 2026: what happened

On Aug 20, 2026, the Google Cloud status dashboard reported "We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.". About 3 hours 40 min: from Aug 20, 2026, 15:40 UTC to Aug 20, 2026, 19:20 UTC, by the official start and resolution times.

Google Cloud right now

At our last refresh (Oct 22, 2026, 12:35 UTC) Google Cloud was up: No open incidents on the Google Cloud status dashboard.

Is Google Cloud down right now? →
Started
Aug 20, 2026, 15:40 UTC
Resolved
Aug 20, 2026, 19:20 UTC
Duration
3 hours 40 min
Official impact
Service outage
Affected
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 Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Google Cloud Composer, Managed Service for Apache Kafka, Persistent Disk
Source
We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. on the Google Cloud status dashboard

The Google Cloud status dashboard rated it "Service outage", its highest impact level: an outage of the affected parts, not only slowness.

What caused the Google Cloud outage?

"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."

From the Google Cloud status dashboard, incident report, Aug 27, 2026, 21:45 UTC.

When was it fixed?

The Google Cloud status dashboard marked it resolved at Aug 20, 2026, 19:20 UTC, 3 hours 40 min after it started. Its resolution note: "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 ..."

Timeline of official updates

Every update the Google Cloud status dashboard posted, oldest first. Times are UTC.

  1. Aug 20, 2026, 16:44 UTC service outage

    Summary We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. Description We are experiencing an issue with multiple products, beginning on Thursday, 2026-08-20 08:40 PDT. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2026-08-20 10:30 PDT with details. We apologize to all who are affected by the disruption. Diagnosis / Customer Symptoms Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products. Workaround None at this time.

  2. Aug 20, 2026, 17:13 UTC service outage

    Summary We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. Description Mitigation actions are implemented by our engineering teams, recovery trends have been observed across infrastructure layers. Active efforts remain underway to bring impacted cloud services back to full operation. We will provide an update by Thursday, 2026-08-20 10:45 PDT with details. Diagnosis / Customer Symptoms Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products. Workaround We recommend customers to failover to other regions where feasible.

  3. Aug 20, 2026, 17:32 UTC service outage

    Summary We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. Description Mitigation actions are implemented by our engineering teams, recovery trends have been observed across infrastructure layers. Active efforts remain underway to bring impacted cloud services back to full operation. We will provide an update by Thursday, 2026-08-20 11:00 PDT with details. Diagnosis / Customer Symptoms Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products. Workaround We recommend customers to failover to other regions where feasible.

  4. Aug 20, 2026, 18:03 UTC service outage

    Summary The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products. Description Mitigation actions have been completed by our engineering teams and we are seeing recovery from multiple products. We are continuing to work to recover the remaining products. We will provide an update by Thursday, 2026-08-20 11:45 PDT with details. Diagnosis / Customer Symptoms Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products. Workaround No workarounds needed at this time.

  5. Aug 20, 2026, 18:53 UTC service outage

    Summary The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products. Description Mitigation actions have been completed by our engineering teams and we are seeing recovery from multiple products. We are continuing to work to recover the remaining products. We will provide an update by Thursday, 2026-08-20 12:30 PDT with details. Diagnosis / Customer Symptoms Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products. Workaround No workarounds needed at this time.

  6. Aug 20, 2026, 19:21 UTC service outage

    Summary The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products. Description Mitigation actions have been completed by our engineering teams and we are seeing recovery from multiple products. We are continuing to work to recover the remaining products. We will provide an update by Thursday, 2026-08-20 13:30 PDT with details. Diagnosis / Customer Symptoms Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products. Workaround No workarounds needed at this time.

  7. Aug 20, 2026, 19:37 UTC resolved

    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.

The official incident report

Published Aug 27, 2026, 21:45 UTC. The opening of the report; the full text is on the official page.

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 ...

Read the full report on the Google Cloud status dashboard

Google Cloud outage questions

What caused the Google Cloud outage on Aug 20, 2026?

In its incident report (Aug 27, 2026, 21:45 UTC), the Google Cloud status dashboard said: "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."

When was the Google Cloud outage on Aug 20, 2026 fixed?

The Google Cloud status dashboard marked it resolved at Aug 20, 2026, 19:20 UTC, 3 hours 40 min after it started. Its resolution note: "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 ..."

How long did the Google Cloud outage last?

About 3 hours 40 min: from Aug 20, 2026, 15:40 UTC to Aug 20, 2026, 19:20 UTC, by the official start and resolution times.

Was Google Cloud completely down?

The Google Cloud status dashboard rated it "Service outage", its highest impact level: an outage of the affected parts, not only slowness. The affected parts listed were: 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 Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Google Cloud Composer, Managed Service for Apache Kafka, Persistent Disk.

Which parts of Google Cloud were affected?

The Google Cloud status dashboard listed: 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 Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Google Cloud Composer, Managed Service for Apache Kafka, Persistent Disk.

Other recent Google Cloud incidents

Full Google Cloud outage history and biggest outages → · Recent outages across all services →

Quotes are the Google Cloud status dashboard's own words, from the official incident. Is It Up or Down is independent and not affiliated with Google Cloud. Times are UTC.