Google Cloud outage, 12 June 2025

Google Cloud global Service Control outage (12 June 2025). The disruption lasted about 7 hours 27 minutes, according to Google Cloud’s own timeline. It began at 17:51 UTC and was resolved at 01:18 UTC the next day. A new quota-policy feature added to Service Control on May 29 had no error handling and wasn’t behind a feature flag.

What happened next. On June 12 a policy change with blank fields replicated globally within seconds, hit the untested code path, and a null pointer crashed Service Control binaries in every region, returning 503s for API requests.

What changes. Google will modularize Service Control so it fails open, require feature flags on critical binary changes, propagate globally replicated data incrementally, and use randomized exponential backoff.

Questions

What caused the Google Cloud outage in June 2025?

A new quota-policy feature added to Service Control on May 29 had no error handling and wasn’t behind a feature flag.

Which services were affected?

Google Cloud APIs (IAM, Compute Engine, BigQuery, Cloud Storage, Cloud SQL, Spanner, Pub/Sub, Cloud Console and many more), Google Workspace, Google Security Operations.

Read how shared dependencies spread a failure in why one cloud outage can break unrelated apps, or browse the outage archive.