What happened
Fastly: Valid customer configuration triggered a latent global bug. Scope: Global (85% of the network returned errors).
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Fastly: Valid customer configuration triggered a latent global bug. Scope: Global (85% of the network returned errors).
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Fastly: Valid customer configuration triggered a latent global bug. Scope: Global (85% of the network returned errors).
Fastly CDN (global).
2 catalogued services run on Fastly (inferred). Hit: Global (85% of the network returned errors).
Resolved after 2h 48m.
Center: Fastly. 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.
We experienced a global outage due to an undiscovered software bug that surfaced on June 8 when it was triggered by a valid customer configuration change. We detected the disruption within one minute, then identified and isolated the cause, and disabled the configuration. Within 49 minutes, 95% of our network was operating as normal.
Timeline (UTC): onset 09:47; 95% operating as normal within 49 minutes; incident mitigated 12:35. Duration_minutes records the official 49-minute recovery to 95%.
Verbatim excerpt from Summary of June 8 outage | Fastly.
65% similar
WAF change for a React vulnerability hit a latent Lua bug
Config push
65% similar
Sensor content-configuration update caused a widespread Windows outage
Config push
65% similar
New DDoS rule exposed a latent rate-limiting bug
Config push
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 Fastly.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Fastly in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/fastly-cdn-2021-06-08/"><img src="https://www.chyp.ai/dissect/m/fastly-cdn-2021-06-08/card.svg" alt="Valid customer configuration triggered a latent global bug · ORBIT Outage Dissector" width="600"></a>