CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report

Service Control crash loop after a blank quota-policy field went global

Google Cloud resolved M8.8 Meltdown 2025-06-12

Google Cloud: Service Control crash loop after a blank quota-policy field went global. Scope: Global.

  • 7h 27mDurationstart → resolved
  • 4Systems namedfrom the source
  • 7Places named7 on the map
  • 75Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Jun 12, 11 AMJun 12, 12 PMJun 12, 1 PMJun 12, 3 PMJun 12, 4 PMJun 12, 6 PM Official statusJun 12, 10:51 AM PT · Impact begins (vendor-stated)Jun 12, 6:18 PM PT · Mitigated (vendor-stated)Network & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startresolved ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Google Cloud: Service Control crash loop after a blank quota-policy field went global. Scope: Global.

What broke

Google Cloud APIs, Google Workspace, Google Security Operations, Cloud IAM / Service Control.

Who was hit

75 catalogued services run on Google Cloud (inferred). Hit: Global.

How it recovered

Resolved after 7h 27m.

2Blast radius

Elastic Cloud · Degraded / minor incidentJFrog · MaintenanceAiven · OperationalAnthropic (Claude) · OperationalBigCommerce · OperationalBox · OperationalCalendly · OperationalCircleCI · OperationalClerk · OperationalCloudinary · OperationalCockroachDB Cloud · OperationalCodecov · OperationalCohere · OperationalDiscord · OperationalElevenLabs · OperationalExpo · OperationalFirebase · OperationalGmail · OperationalGoogle Drive · OperationalGoogle Meet · OperationalGoogle Workspace · OperationalGrafana Cloud · OperationalHubSpot · Operationalimgix · Operationalincident.io · OperationalJumpCloud · OperationalKinsta · OperationalLinear · OperationalMixpanel · OperationalMongoDB Atlas · OperationalMux · OperationalNetlify · OperationalPinecone · OperationalPlanetScale · OperationalRender · OperationalReplit · OperationalGoogle Cloud75 dependents +39 more catalogued dependents not drawn

Center: Google Cloud. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.

3Blast map

North America · vendor-stated scope: globalSouth America · vendor-stated scope: globalEurope · vendor-stated scope: globalAfrica · vendor-stated scope: globalMiddle East · vendor-stated scope: globalAsia · vendor-stated scope: globalOceania · vendor-stated scope: global
  1. North America
  2. South America
  3. Europe
  4. Africa
  5. Middle East
  6. Asia
  7. Oceania

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Control-plane couplingvendor post-incident report (Meltdown Index)
  • Config propagationvendor post-incident report (Meltdown Index)
  • Capacity exhaustionvendor post-incident report (Meltdown Index)
  • Retry amplificationno sign
  • Dependency cascadeno sign

Failure modes as stated in the vendor's own post-incident report (Meltdown Index).

5Evidence matrix

Official statusOfficial status · Jun 12, 4:51 AM PT: 0 itemsOfficial status · Jun 12, 5:24 AM PT: 0 itemsOfficial status · Jun 12, 5:58 AM PT: 0 itemsOfficial status · Jun 12, 6:31 AM PT: 0 itemsOfficial status · Jun 12, 7:05 AM PT: 0 itemsOfficial status · Jun 12, 7:39 AM PT: 0 itemsOfficial status · Jun 12, 8:12 AM PT: 0 itemsOfficial status · Jun 12, 8:46 AM PT: 0 itemsOfficial status · Jun 12, 9:20 AM PT: 0 itemsOfficial status · Jun 12, 9:53 AM PT: 0 itemsOfficial status · Jun 12, 10:27 AM PT: 1 itemOfficial status · Jun 12, 11:00 AM PT: 0 itemsOfficial status · Jun 12, 11:34 AM PT: 0 itemsOfficial status · Jun 12, 12:08 PM PT: 0 itemsOfficial status · Jun 12, 12:41 PM PT: 0 itemsOfficial status · Jun 12, 1:15 PM PT: 0 itemsOfficial status · Jun 12, 1:49 PM PT: 0 itemsOfficial status · Jun 12, 2:22 PM PT: 0 itemsOfficial status · Jun 12, 2:56 PM PT: 0 itemsOfficial status · Jun 12, 3:29 PM PT: 0 itemsOfficial status · Jun 12, 4:03 PM PT: 0 itemsOfficial status · Jun 12, 4:37 PM PT: 0 itemsOfficial status · Jun 12, 5:10 PM PT: 0 itemsOfficial status · Jun 12, 5:44 PM PT: 0 itemsNetwork & routingNetwork & routing · Jun 12, 4:51 AM PT: 0 itemsNetwork & routing · Jun 12, 5:24 AM PT: 0 itemsNetwork & routing · Jun 12, 5:58 AM PT: 0 itemsNetwork & routing · Jun 12, 6:31 AM PT: 0 itemsNetwork & routing · Jun 12, 7:05 AM PT: 0 itemsNetwork & routing · Jun 12, 7:39 AM PT: 0 itemsNetwork & routing · Jun 12, 8:12 AM PT: 0 itemsNetwork & routing · Jun 12, 8:46 AM PT: 0 itemsNetwork & routing · Jun 12, 9:20 AM PT: 0 itemsNetwork & routing · Jun 12, 9:53 AM PT: 0 itemsNetwork & routing · Jun 12, 10:27 AM PT: 0 itemsNetwork & routing · Jun 12, 11:00 AM PT: 0 itemsNetwork & routing · Jun 12, 11:34 AM PT: 0 itemsNetwork & routing · Jun 12, 12:08 PM PT: 0 itemsNetwork & routing · Jun 12, 12:41 PM PT: 0 itemsNetwork & routing · Jun 12, 1:15 PM PT: 0 itemsNetwork & routing · Jun 12, 1:49 PM PT: 0 itemsNetwork & routing · Jun 12, 2:22 PM PT: 0 itemsNetwork & routing · Jun 12, 2:56 PM PT: 0 itemsNetwork & routing · Jun 12, 3:29 PM PT: 0 itemsNetwork & routing · Jun 12, 4:03 PM PT: 0 itemsNetwork & routing · Jun 12, 4:37 PM PT: 0 itemsNetwork & routing · Jun 12, 5:10 PM PT: 0 itemsNetwork & routing · Jun 12, 5:44 PM PT: 0 itemsEarly signalsEarly signals · Jun 12, 4:51 AM PT: 0 itemsEarly signals · Jun 12, 5:24 AM PT: 0 itemsEarly signals · Jun 12, 5:58 AM PT: 0 itemsEarly signals · Jun 12, 6:31 AM PT: 0 itemsEarly signals · Jun 12, 7:05 AM PT: 0 itemsEarly signals · Jun 12, 7:39 AM PT: 0 itemsEarly signals · Jun 12, 8:12 AM PT: 0 itemsEarly signals · Jun 12, 8:46 AM PT: 0 itemsEarly signals · Jun 12, 9:20 AM PT: 0 itemsEarly signals · Jun 12, 9:53 AM PT: 0 itemsEarly signals · Jun 12, 10:27 AM PT: 0 itemsEarly signals · Jun 12, 11:00 AM PT: 0 itemsEarly signals · Jun 12, 11:34 AM PT: 0 itemsEarly signals · Jun 12, 12:08 PM PT: 0 itemsEarly signals · Jun 12, 12:41 PM PT: 0 itemsEarly signals · Jun 12, 1:15 PM PT: 0 itemsEarly signals · Jun 12, 1:49 PM PT: 0 itemsEarly signals · Jun 12, 2:22 PM PT: 0 itemsEarly signals · Jun 12, 2:56 PM PT: 0 itemsEarly signals · Jun 12, 3:29 PM PT: 0 itemsEarly signals · Jun 12, 4:03 PM PT: 0 itemsEarly signals · Jun 12, 4:37 PM PT: 0 itemsEarly signals · Jun 12, 5:10 PM PT: 0 itemsEarly signals · Jun 12, 5:44 PM PT: 0 itemsNews & chatterNews & chatter · Jun 12, 4:51 AM PT: 0 itemsNews & chatter · Jun 12, 5:24 AM PT: 0 itemsNews & chatter · Jun 12, 5:58 AM PT: 0 itemsNews & chatter · Jun 12, 6:31 AM PT: 0 itemsNews & chatter · Jun 12, 7:05 AM PT: 0 itemsNews & chatter · Jun 12, 7:39 AM PT: 0 itemsNews & chatter · Jun 12, 8:12 AM PT: 0 itemsNews & chatter · Jun 12, 8:46 AM PT: 0 itemsNews & chatter · Jun 12, 9:20 AM PT: 0 itemsNews & chatter · Jun 12, 9:53 AM PT: 0 itemsNews & chatter · Jun 12, 10:27 AM PT: 0 itemsNews & chatter · Jun 12, 11:00 AM PT: 0 itemsNews & chatter · Jun 12, 11:34 AM PT: 0 itemsNews & chatter · Jun 12, 12:08 PM PT: 0 itemsNews & chatter · Jun 12, 12:41 PM PT: 0 itemsNews & chatter · Jun 12, 1:15 PM PT: 0 itemsNews & chatter · Jun 12, 1:49 PM PT: 0 itemsNews & chatter · Jun 12, 2:22 PM PT: 0 itemsNews & chatter · Jun 12, 2:56 PM PT: 0 itemsNews & chatter · Jun 12, 3:29 PM PT: 0 itemsNews & chatter · Jun 12, 4:03 PM PT: 0 itemsNews & chatter · Jun 12, 4:37 PM PT: 0 itemsNews & chatter · Jun 12, 5:10 PM PT: 0 itemsNews & chatter · Jun 12, 5:44 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Jun 12, 4:51 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 5:24 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 5:58 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 6:31 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 7:05 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 7:39 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 8:12 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 8:46 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 9:20 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 9:53 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 10:27 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 11:00 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 11:34 AM PT: 0 itemsCoincidence (KEV) · Jun 12, 12:08 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 12:41 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 1:15 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 1:49 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 2:22 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 2:56 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 3:29 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 4:03 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 4:37 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 5:10 PM PT: 0 itemsCoincidence (KEV) · Jun 12, 5:44 PM PT: 0 itemsJun 12, 4:51 AM PTJun 12, 6:18 PM PT

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6In the vendor's words

On June 12, 2025 at ~10:45am PDT, a policy change was inserted into the regional Spanner tables that Service Control uses for policies. Given the global nature of quota management, this metadata was replicated globally within seconds. This policy data contained unintended blank fields. Service Control, then regionally exercised quota checks on policies in each regional datastore. This pulled in blank fields for this respective policy change and exercised the code path that hit the null pointer causing the binaries to go into a crash loop.

Official incident window: began 2025-06-12 10:51 and ended 2025-06-12 18:18 US/Pacific (7h 27m). The policy insertion is described at approximately 10:45am PDT.

Verbatim excerpt from Google Cloud Service Health — Service Control, 12 Jun 2025.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • Control plane on the critical path again. When the management layer sneezes, the data plane shouldn't catch a cold.
  • 75 catalogued services lean on one provider. That's concentration risk, and it's the real headline.
  • Longer than 12 of 19 indexed control-plane meltdowns with a stated duration.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Google Cloud.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Google Cloud in the War Room →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/m/gcp-service-control-2025-06-12/"><img src="https://www.chyp.ai/dissect/m/gcp-service-control-2025-06-12/card.svg" alt="Service Control crash loop after a blank quota-policy field… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Taken from the vendor's own post-incident report; quotes are verbatim excerpts.
  • Dependents are today's inferred catalogue, not who was affected on the day.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.