Gemini Partial Outage - September 1, 2026

<p> Incident began at <strong>2026-09-01 07:44</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Multiple products in us-central1-b are experiencing network service degradation.</p> <p><strong>Description</strong></p> <p>The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected.</p> <p>Following network-level mitigation efforts, the underlying network infrastructure has fully recovered. Product engineering teams across Cloud are currently validating the recovery status of individual services.</p> <p>We will provide more information by Tuesday, 2026-09-01 10:00 US/Pacific with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Customers are experiencing elevated packet loss and errors.</p> <ul> <li>BigQuery</li> <li>Cloud Dataflow</li> <li>Cloud SQL</li> <li>App Engine</li> <li>Cloud Run</li> <li>AlloyDB</li> <li>Cloud Bigtable</li> <li>Cloud Spanner</li> <li>Compute Engine</li> <li>Cloud VPN</li> <li>Cloud Interconnect</li> <li>Cloud NAT</li> <li>Cloud Filestore</li> <li>Cloud Hybrid Connectivity</li> <li>Virtual Private Cloud</li> <li>Google Kubernetes Engine</li> <li>Looker (Google Cloud core)</li> <li>Apigee</li> <li>Google SecOps SOAR</li> </ul> <p><strong>Workaround</strong></p> <ul> <li>Customers with service layer retries may see successful completions as only a portion of the zone is affected.</li> <li>Customers that are severely affected and have services available in alternate zones can failover to alternate zones.</li> </ul> </div><hr><p>Affected products: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC)</p><p>Affected locations: Iowa (us-central1)</p>

<p> Incident began at <strong>2026-09-01 07:44</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Multiple products in us-central1-b are experiencing network service degradation.</p> <p><strong>Description</strong></p> <p>The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected.</p> <p>Most of the products have recovered and the engineering team is still validating a few remaining product impacts.</p> <p>We will provide more information by Tuesday, 2026-09-01 11:00 US/Pacific with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Customers are experiencing elevated packet loss and errors.</p> <ul> <li>Cloud Run</li> <li>App Engine</li> </ul> <p>Following products have recovered</p> <ul> <li>BigQuery</li> <li>Cloud Dataflow</li> <li>Cloud Bigtable</li> <li>Compute Engine</li> <li>Cloud Hybrid Connectivity</li> <li>Cloud Filestore</li> <li>Virtual Private Cloud</li> <li>Cloud Spanner</li> <li>Google Kubernetes Engine</li> <li>Cloud SQL</li> <li>AlloyDBCloud VPN</li> <li>Apigee</li> <li>Cloud Interconnect</li> <li>Cloud NAT</li> <li>Looker (Google Cloud core)</li> <li>Google SecOps SOAR</li> <li>Cloud Firestore</li> </ul> <p><strong>Workaround</strong></p> <ul> <li>Customers with service layer retries may see successful completions as only a portion of the zone is affected.</li> <li>Customers that are severely affected and have services available in alternate zones can failover to alternate zones.</li> </ul> </div><hr><p>Affected products: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC)</p><p>Affected locations: Iowa (us-central1)</p>

<p> Incident began at <strong>2026-09-01 07:44</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Multiple products in us-central1-b are experiencing network service degradation.</p> <p><strong>Description</strong></p> <p>The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected.</p> <p>Most of the products have recovered and the engineering team is still validating a few remaining product impacts.</p> <p>Routine network maintenance triggered issues in us-central1-b. We have recovered the network capacity that was impacted and restored all zonal and regional services. Maintenance in the region has been halted while proactive audits are carried out.</p> <p>We will provide more information by Tuesday, 2026-09-01 12:30 US/Pacific with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Customers are experiencing elevated packet loss and errors.</p> <ul> <li>Cloud Run</li> <li>App Engine</li> </ul> <p>Following products have recovered</p> <ul> <li>BigQuery</li> <li>Cloud Dataflow</li> <li>Cloud Bigtable</li> <li>Compute Engine</li> <li>Cloud Hybrid Connectivity</li> <li>Cloud Filestore</li> <li>Virtual Private Cloud</li> <li>Cloud Spanner</li> <li>Google Kubernetes Engine</li> <li>Cloud SQL</li> <li>AlloyDBCloud VPN</li> <li>Apigee</li> <li>Cloud Interconnect</li> <li>Cloud NAT</li> <li>Looker (Google Cloud core)</li> <li>Google SecOps SOAR</li> <li>Cloud Firestore</li> </ul> <p><strong>Workaround</strong></p> <ul> <li>Customers with service layer retries may see successful completions as only a portion of the zone is affected.</li> </ul> </div><hr><p>Affected products: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC)</p><p>Affected locations: Iowa (us-central1)</p>

<p> Incident began at <strong>2026-09-01 07:44</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Multiple products in us-central1-b are experiencing network service degradation.</p> <p><strong>Description</strong></p> <p>The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected.</p> <p>Most of the products have recovered. The impacted products Cloud Run and App Engine are also seeing recovery and the errors have lowered pre-incident levels. Engineering continues to monitor and validate.</p> <p>Routine network fabric path maintenance triggered unexpected issues in two clusters in us-central1-b. We have recovered the network capacity that was impacted and restored all zonal and regional services. Maintenance in the region has been halted while proactive audits are carried out.</p> <p>We will provide more information by Tuesday, 2026-09-01 12:30 US/Pacific with current details.</p> <p><strong>Customer Symptoms</strong></p> <p>Customers are experiencing elevated packet loss and errors.</p> <ul> <li>Cloud Run</li> <li>App Engine</li> </ul> <p>Following products have recovered</p> <ul> <li>BigQuery</li> <li>Cloud Dataflow</li> <li>Cloud Bigtable</li> <li>Compute Engine</li> <li>Cloud Hybrid Connectivity</li> <li>Cloud Filestore</li> <li>Virtual Private Cloud</li> <li>Cloud Spanner</li> <li>Google Kubernetes Engine</li> <li>Cloud SQL</li> <li>AlloyDBCloud VPN</li> <li>Apigee</li> <li>Cloud Interconnect</li> <li>Cloud NAT</li> <li>Looker (Google Cloud core)</li> <li>Google SecOps SOAR</li> <li>Cloud Firestore</li> </ul> <p><strong>Workaround</strong></p> <ul> <li>Customers with service layer retries may see successful completions as only a portion of the zone is affected.</li> </ul> </div><hr><p>Affected products: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC)</p><p>Affected locations: Iowa (us-central1)</p>

<p> Incident began at <strong>2026-09-01 07:44</strong> and ended at <strong>2026-09-01 11:52</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p><strong>Summary</strong></p> <p>Multiple products in us-central1-b experienced network service degradation.</p> <p><strong>Description</strong></p> <p>The issue was affecting a portion of the us-central1-b zone. The remaining zones in the region were unaffected.</p> <p>All the impacted products have recovered.</p> <p>From preliminary analysis, routine network fabric path maintenance triggered unexpected issues in one cluster in us-central1-b. We have recovered the network capacity that was impacted and restored all zonal and regional services. Maintenance in the region has been halted while proactive audits are carried out.</p> <p>We thank you for your patience while we worked on resolving the issue.</p> <p><strong>Customer Symptoms</strong></p> <p>Customers experienced elevated packet loss and errors.</p> <p><strong>Workaround</strong></p> <p>The issue has been mitigated.</p> </div><hr><p>Affected products: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC)</p><p>Affected locations: Iowa (us-central1)</p>