Outage report · Partial outage

Google Cloud Run outage on Sep 1, 2026

Multiple products in us-central1-b are experiencing network service degradation.

SeverityPartial outage

StartedSep 1, 2026, 14:42UTC

ResolvedSep 1, 2026, 18:52UTC

Duration4h 10m

What happened

Google Cloud Run reported a partial outage starting Sep 1, 2026, 14:42 UTC, affecting AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Firestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery and 8 more. It was marked resolved at Sep 1, 2026, 18:52 UTC.

The incident lasted 4h 10m from first report to resolution.
It was the 2nd longest of 3 significant outages Google Cloud Run reported in the 12 months up to it.
Google Cloud Run had reported 1 other partial or major outage in the 90 days before it.
12 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Google Cloud Run

## Addendum to Incident Report This addendum extends the Detailed Description of Impact from the previous message. Though only two clusters in a datacenter in us-central1-b and us-central1-f experienced network isolation, a few regional products with a dependency on the affected datacenter were also affected. Between 07:41 and 11:52 US/Pacific on Tuesday, September 1, 2026, the following products were affected: - **Compute Engine VMs**: VMs running in the affected data center lost network connectivity to resources located outside of their datacenter. From a Compute Engine perspective, this incident only affected a subset of VMs in us-central1-b and us-central1-f. - **Zonal and Regional Products Based on Compute Engine** Products with dependencies on VMs in the affected datacenter experienced symptoms like connection timeouts or service unavailability because the underlying VMs lost network connectivity. Examples of products that are based on Compute Engine VMs include: Apigee, Cloud SQ

Read Google Cloud Run's official incident report ↗