What happened
Cloudflare: New DDoS rule exposed a latent rate-limiting bug. Scope: Global (1.4–2.1% of HTTP requests received an error page at the 30-minute peak).
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Cloudflare: New DDoS rule exposed a latent rate-limiting bug. Scope: Global (1.4–2.1% of HTTP requests received an error page at the 30-minute peak).
Severe storm
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: New DDoS rule exposed a latent rate-limiting bug. Scope: Global (1.4–2.1% of HTTP requests received an error page at the 30-minute peak).
Cloudflare CDN / HTTP.
14 catalogued services run on Cloudflare (inferred). Hit: Global (1.4–2.1% of HTTP requests received an error page at the 30-minute peak).
Resolved after 1h 54m (vendor wording: 114m).
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.
As part of routine updates to our protection mechanisms, we created a new DDoS rule to prevent a specific type of abuse that we observed on our infrastructure. This DDoS rule worked as expected, however in a specific suspect traffic case it exposed a latent bug in our existing rate-limiting component.
Official total impact 114 minutes, from two independent events (this rule/bug and a backbone congestion event). Clock-time start was not taken from a single official ISO timestamp beyond that duration.
Verbatim excerpt from Cloudflare incident on June 20, 2024.
100% similar · same provider
WAF change for a React vulnerability hit a latent Lua bug
Config push
90% similar · same provider
Network configuration change took 19 data centers offline
Config push
70% similar · same provider
Bot Management feature file doubled and crashed traffic-routing software
Config pushCapacityCascade
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-ratelimit-2024-06-20/"><img src="https://www.chyp.ai/dissect/m/cf-ratelimit-2024-06-20/card.svg" alt="New DDoS rule exposed a latent rate-limiting bug · ORBIT Outage Dissector" width="600"></a>