CHYP.ai · ORBIT // Cloudy_Day Security Suite

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

Network-control-plane configuration update dropped GCVE private traffic

Google Cloud resolved M7.5 Severe storm 2026-07-14

Google Cloud: Network-control-plane configuration update dropped GCVE private traffic. Scope: Two regions (stretched-cluster zones).

M7.5

Severe storm

How CHYP Magnitude works

  • 10h 40mDurationstart → resolved
  • 1Systems namedfrom the source
  • 2Places named2 on the map
  • 75Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Jul 14, 10 AMJul 14, 12 PMJul 14, 2 PMJul 14, 4 PMJul 14, 6 PMJul 14, 8 PM Official statusJul 14, 10:00 AM PT · Impact begins (vendor-stated)Jul 14, 8:40 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: Network-control-plane configuration update dropped GCVE private traffic. Scope: Two regions (stretched-cluster zones).

What broke

Google Cloud VMware Engine (Stretched Cluster).

Who was hit

75 catalogued services run on Google Cloud (inferred). Hit: Two regions (stretched-cluster zones).

How it recovered

Resolved after 10h 40m.

4Failure-mode fingerprint

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

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

5Evidence matrix

Official statusOfficial status · Jul 14, 4:00 AM PT: 0 itemsOfficial status · Jul 14, 4:41 AM PT: 0 itemsOfficial status · Jul 14, 5:23 AM PT: 0 itemsOfficial status · Jul 14, 6:05 AM PT: 0 itemsOfficial status · Jul 14, 6:46 AM PT: 0 itemsOfficial status · Jul 14, 7:28 AM PT: 0 itemsOfficial status · Jul 14, 8:10 AM PT: 0 itemsOfficial status · Jul 14, 8:51 AM PT: 0 itemsOfficial status · Jul 14, 9:33 AM PT: 1 itemOfficial status · Jul 14, 10:15 AM PT: 0 itemsOfficial status · Jul 14, 10:56 AM PT: 0 itemsOfficial status · Jul 14, 11:38 AM PT: 0 itemsOfficial status · Jul 14, 12:20 PM PT: 0 itemsOfficial status · Jul 14, 1:01 PM PT: 0 itemsOfficial status · Jul 14, 1:43 PM PT: 0 itemsOfficial status · Jul 14, 2:25 PM PT: 0 itemsOfficial status · Jul 14, 3:06 PM PT: 0 itemsOfficial status · Jul 14, 3:48 PM PT: 0 itemsOfficial status · Jul 14, 4:30 PM PT: 0 itemsOfficial status · Jul 14, 5:11 PM PT: 0 itemsOfficial status · Jul 14, 5:53 PM PT: 0 itemsOfficial status · Jul 14, 6:35 PM PT: 0 itemsOfficial status · Jul 14, 7:16 PM PT: 0 itemsOfficial status · Jul 14, 7:58 PM PT: 0 itemsNetwork & routingNetwork & routing · Jul 14, 4:00 AM PT: 0 itemsNetwork & routing · Jul 14, 4:41 AM PT: 0 itemsNetwork & routing · Jul 14, 5:23 AM PT: 0 itemsNetwork & routing · Jul 14, 6:05 AM PT: 0 itemsNetwork & routing · Jul 14, 6:46 AM PT: 0 itemsNetwork & routing · Jul 14, 7:28 AM PT: 0 itemsNetwork & routing · Jul 14, 8:10 AM PT: 0 itemsNetwork & routing · Jul 14, 8:51 AM PT: 0 itemsNetwork & routing · Jul 14, 9:33 AM PT: 0 itemsNetwork & routing · Jul 14, 10:15 AM PT: 0 itemsNetwork & routing · Jul 14, 10:56 AM PT: 0 itemsNetwork & routing · Jul 14, 11:38 AM PT: 0 itemsNetwork & routing · Jul 14, 12:20 PM PT: 0 itemsNetwork & routing · Jul 14, 1:01 PM PT: 0 itemsNetwork & routing · Jul 14, 1:43 PM PT: 0 itemsNetwork & routing · Jul 14, 2:25 PM PT: 0 itemsNetwork & routing · Jul 14, 3:06 PM PT: 0 itemsNetwork & routing · Jul 14, 3:48 PM PT: 0 itemsNetwork & routing · Jul 14, 4:30 PM PT: 0 itemsNetwork & routing · Jul 14, 5:11 PM PT: 0 itemsNetwork & routing · Jul 14, 5:53 PM PT: 0 itemsNetwork & routing · Jul 14, 6:35 PM PT: 0 itemsNetwork & routing · Jul 14, 7:16 PM PT: 0 itemsNetwork & routing · Jul 14, 7:58 PM PT: 0 itemsEarly signalsEarly signals · Jul 14, 4:00 AM PT: 0 itemsEarly signals · Jul 14, 4:41 AM PT: 0 itemsEarly signals · Jul 14, 5:23 AM PT: 0 itemsEarly signals · Jul 14, 6:05 AM PT: 0 itemsEarly signals · Jul 14, 6:46 AM PT: 0 itemsEarly signals · Jul 14, 7:28 AM PT: 0 itemsEarly signals · Jul 14, 8:10 AM PT: 0 itemsEarly signals · Jul 14, 8:51 AM PT: 0 itemsEarly signals · Jul 14, 9:33 AM PT: 0 itemsEarly signals · Jul 14, 10:15 AM PT: 0 itemsEarly signals · Jul 14, 10:56 AM PT: 0 itemsEarly signals · Jul 14, 11:38 AM PT: 0 itemsEarly signals · Jul 14, 12:20 PM PT: 0 itemsEarly signals · Jul 14, 1:01 PM PT: 0 itemsEarly signals · Jul 14, 1:43 PM PT: 0 itemsEarly signals · Jul 14, 2:25 PM PT: 0 itemsEarly signals · Jul 14, 3:06 PM PT: 0 itemsEarly signals · Jul 14, 3:48 PM PT: 0 itemsEarly signals · Jul 14, 4:30 PM PT: 0 itemsEarly signals · Jul 14, 5:11 PM PT: 0 itemsEarly signals · Jul 14, 5:53 PM PT: 0 itemsEarly signals · Jul 14, 6:35 PM PT: 0 itemsEarly signals · Jul 14, 7:16 PM PT: 0 itemsEarly signals · Jul 14, 7:58 PM PT: 0 itemsNews & chatterNews & chatter · Jul 14, 4:00 AM PT: 0 itemsNews & chatter · Jul 14, 4:41 AM PT: 0 itemsNews & chatter · Jul 14, 5:23 AM PT: 0 itemsNews & chatter · Jul 14, 6:05 AM PT: 0 itemsNews & chatter · Jul 14, 6:46 AM PT: 0 itemsNews & chatter · Jul 14, 7:28 AM PT: 0 itemsNews & chatter · Jul 14, 8:10 AM PT: 0 itemsNews & chatter · Jul 14, 8:51 AM PT: 0 itemsNews & chatter · Jul 14, 9:33 AM PT: 0 itemsNews & chatter · Jul 14, 10:15 AM PT: 0 itemsNews & chatter · Jul 14, 10:56 AM PT: 0 itemsNews & chatter · Jul 14, 11:38 AM PT: 0 itemsNews & chatter · Jul 14, 12:20 PM PT: 0 itemsNews & chatter · Jul 14, 1:01 PM PT: 0 itemsNews & chatter · Jul 14, 1:43 PM PT: 0 itemsNews & chatter · Jul 14, 2:25 PM PT: 0 itemsNews & chatter · Jul 14, 3:06 PM PT: 0 itemsNews & chatter · Jul 14, 3:48 PM PT: 0 itemsNews & chatter · Jul 14, 4:30 PM PT: 0 itemsNews & chatter · Jul 14, 5:11 PM PT: 0 itemsNews & chatter · Jul 14, 5:53 PM PT: 0 itemsNews & chatter · Jul 14, 6:35 PM PT: 0 itemsNews & chatter · Jul 14, 7:16 PM PT: 0 itemsNews & chatter · Jul 14, 7:58 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Jul 14, 4:00 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 4:41 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 5:23 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 6:05 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 6:46 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 7:28 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 8:10 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 8:51 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 9:33 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 10:15 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 10:56 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 11:38 AM PT: 0 itemsCoincidence (KEV) · Jul 14, 12:20 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 1:01 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 1:43 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 2:25 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 3:06 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 3:48 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 4:30 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 5:11 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 5:53 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 6:35 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 7:16 PM PT: 0 itemsCoincidence (KEV) · Jul 14, 7:58 PM PT: 0 itemsJul 14, 4:00 AM PTJul 14, 8:40 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

A network configuration update intended to prepare the cloud network infrastructure for new capabilities was deployed to the foundational network control plane. While the configuration payload itself was structurally valid, it exposed an implementation gap within the control plane's routing logic.

Official: Incident Start 14 July 2026 10:00 PT, Incident End 14 July 2026 20:40 PT, Duration 10 hours 40 minutes (US/Pacific), as stated in Google’s incident report.

Verbatim excerpt from Google Cloud Service Health — GCVE Stretched Cluster, 14 Jul 2026.

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

  • A change went wider, faster than its safety net. Staged rollouts and kill switches exist for exactly this.
  • 75 catalogued services lean on one provider. That's concentration risk, and it's the real headline.
  • Longer than 16 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-gcve-2026-07-14/"><img src="https://www.chyp.ai/dissect/m/gcp-gcve-2026-07-14/card.svg" alt="Network-control-plane configuration update dropped GCVE pri… · 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.