Google Cloud incident
Incident affecting AlloyDB for PostgreSQL, Apigee Edge Public Cloud and Apigee X
Google Cloud experienced a critical incident on August 20, 2026 affecting AlloyDB for PostgreSQL and Apigee Edge Public Cloud and 1 more component, lasting 3h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 20, 2026, 04:44 PM UTC
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.
- investigating Aug 20, 2026, 05:13 PM UTC
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: 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. Workaround: We recommend customers to failover to other regions where feasible.
- investigating Aug 20, 2026, 05:32 PM UTC
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.
- investigating Aug 20, 2026, 06:03 PM UTC
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.
- investigating Aug 20, 2026, 06:53 PM UTC
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.
- investigating Aug 20, 2026, 07:21 PM UTC
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.
- resolved Aug 20, 2026, 07:37 PM UTC
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.