Skip to content
Google Cloud ยท Cloud and hostingJun 12, 2025, 17:49 UTC

Service Control crash loop returns 503s across Google Cloud

CriticalConfig changeUpdated 20h ago
Jun 12, 17:49 UTCJun 12, 20:49 UTC
Duration
3h
Impact
Critical
Root cause
Config change
Google Cloud, 90 days
4 incidents
Affected
Service ControlCompute EngineBigQueryCloud StorageWorkspaceGlobal

Lesson: New code paths belong behind feature flags, and globally replicated policy data needs staged propagation like any binary.

What happened

A policy change inserted into the regional Spanner tables that Service Control reads hit an unguarded code path with a null pointer, crashing Service Control binaries worldwide. External API requests returned 503 errors; us-central1 recovered last.

More from Google Cloud

Full history

Also caused by configuration change

All
StartedIncidentDuration
Sep 2218:20 UTCPhone Number APIs and Console Were Returning Incorrect 404 ResponsesTwilio0m
Sep 1622:30 UTCHyperdrive Elevated Origin Connection Failure RatesCloudflare0m
Sep 1211:04 UTCSome customers experiencing blurry image previews and download issuesSlack8h 56m
Sep 1107:18 UTCINC20000213Snowflake6h 1m
Sep 407:34 UTCINC20000199Snowflake2h 36m
Sep 109:58 UTCINC20000190Snowflake3h 52m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.