Service Control crash loop returns 503s across Google Cloud
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 historyAlso caused by configuration change
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 2218:20 UTC | Phone Number APIs and Console Were Returning Incorrect 404 Responses | none | 0m | |
| Sep 1622:30 UTC | Hyperdrive Elevated Origin Connection Failure Rates | none | 0m | |
| Sep 1211:04 UTC | Some customers experiencing blurry image previews and download issues | minor | 8h 56m | |
| Sep 1107:18 UTC | INC20000213 | critical | 6h 1m | |
| Sep 407:34 UTC | INC20000199 | critical | 2h 36m | |
| Sep 109:58 UTC | INC20000190 | major | 3h 52m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.