What happened
Cloudflare: Network configuration change took 19 data centers offline. Scope: 19 of Cloudflare’s busiest data centers.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Cloudflare: Network configuration change took 19 data centers offline. Scope: 19 of Cloudflare’s busiest data centers.
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Cloudflare: Network configuration change took 19 data centers offline. Scope: 19 of Cloudflare’s busiest data centers.
Cloudflare network / CDN (19 Multi-Colo PoPs).
14 catalogued services run on Cloudflare (inferred). Hit: 19 of Cloudflare’s busiest data centers.
Resolved after 1h 15m (vendor wording: 75m).
Center: Cloudflare. 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.
Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.
Failure modes as stated in the vendor's own post-incident report (Meltdown Index).
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.
This outage was caused by a change that was part of a long-running project to increase resilience in our busiest locations. A change to the network configuration in those locations caused an outage which started at 06:27 UTC. At 06:58 UTC the first data center was brought back online and by 07:42 UTC all data centers were online and working correctly.
Official window 06:27–07:42 UTC (75 minutes). These 19 locations handle a significant proportion of Cloudflare’s global traffic.
Verbatim excerpt from Cloudflare outage on June 21, 2022.
90% similar · same provider
WAF change for a React vulnerability hit a latent Lua bug
Config push
90% similar · same provider
New DDoS rule exposed a latent rate-limiting bug
Config push
77% similar · same provider
Backbone router configuration error overwhelmed Atlanta
Config pushCapacity
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.
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 Cloudflare.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Cloudflare in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/cf-mcp-bgp-2022-06-21/"><img src="https://www.chyp.ai/dissect/m/cf-mcp-bgp-2022-06-21/card.svg" alt="Network configuration change took 19 data centers offline · ORBIT Outage Dissector" width="600"></a>