Gemini Partial Outage - August 20, 2026

<p> Incident began at <strong>2026-08-20 08:40</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.</p> <p><strong>Description</strong></p> <p>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.</p> <p>We will provide an update by Thursday, 2026-08-20 10:45 PDT with details.</p> <p><strong>Diagnosis / Customer Symptoms</strong></p> <p>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.</p> <p>We will provide an update by Thursday, 2026-08-20 10:45 PDT with details.</p> <p><strong>Workaround</strong></p> <p>We recommend customers to failover to other regions where feasible.</p> </div><hr><p>Affected products: Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Key Management Service, Cloud Run, Contact Center AI Platform, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Composer, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Managed Service for Apache Kafka, Persistent Disk</p><p>Affected locations: Global, Oregon (us-west1)</p>

<p> Incident began at <strong>2026-08-20 08:40</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.</p> <p><strong>Description</strong></p> <p>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.</p> <p>We will provide an update by Thursday, 2026-08-20 11:00 PDT with details.</p> <p><strong>Diagnosis / Customer Symptoms</strong></p> <p>Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products.</p> <p><strong>Workaround</strong></p> <p>We recommend customers to failover to other regions where feasible.</p> </div><hr><p>Affected products: Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Data Fusion, Cloud Filestore, Cloud Key Management Service, Cloud Run, Contact Center AI Platform, 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</p><p>Affected locations: Global, Oregon (us-west1)</p>

<p> Incident began at <strong>2026-08-20 08:40</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products.</p> <p><strong>Description</strong></p> <p>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.</p> <p>We will provide an update by Thursday, 2026-08-20 11:45 PDT with details.</p> <p><strong>Diagnosis / Customer Symptoms</strong></p> <p>Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products.</p> <p><strong>Workaround</strong></p> <p>No workarounds needed at this time.</p> </div><hr><p>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</p><p>Affected locations: Global, Oregon (us-west1)</p>

<p> Incident began at <strong>2026-08-20 08:40</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products.</p> <p><strong>Description</strong></p> <p>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.</p> <p>We will provide an update by Thursday, 2026-08-20 12:30 PDT with details.</p> <p><strong>Diagnosis / Customer Symptoms</strong></p> <p>Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products.</p> <p><strong>Workaround</strong></p> <p>No workarounds needed at this time.</p> </div><hr><p>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</p><p>Affected locations: Global, Oregon (us-west1)</p>

<p> Incident began at <strong>2026-08-20 08:40</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products.</p> <p><strong>Description</strong></p> <p>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.</p> <p>We will provide an update by Thursday, 2026-08-20 13:30 PDT with details.</p> <p><strong>Diagnosis / Customer Symptoms</strong></p> <p>Customers in us-west1 may experience timeouts, service degradations, errors, and elevated latencies across multiple products.</p> <p><strong>Workaround</strong></p> <p>No workarounds needed at this time.</p> </div><hr><p>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</p><p>Affected locations: Global, Oregon (us-west1)</p>

<p> Incident began at <strong>2026-08-20 08:40</strong> and ended at <strong>2026-08-20 12:20</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated.</p> <p><strong>Description</strong></p> <p>We have mitigated the issue impacting multiple products in our us-west1 region as of Thursday, 2026-08-20 10:22 PDT.</p> <p>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.</p> <p>We will publish an analysis of this incident once we have completed our internal investigation.</p> <p>We thank you for your patience while we worked on resolving the issue.</p> <p><strong>Diagnosis / Customer Symptoms</strong></p> <p>Customers in us-west1 may have experienced timeouts, service degradations, errors, and elevated latencies across multiple products.</p> <p><strong>Workaround</strong></p> <p>This issue is now mitigated.</p> </div><hr><p>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</p><p>Affected locations: Global, Oregon (us-west1)</p>