CHYP.ai · ORBIT // Cloudy_Day Security Suite

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

Valid customer configuration triggered a latent global bug

Fastly resolved M6.9 Storm 2021-06-08

Fastly: Valid customer configuration triggered a latent global bug. Scope: Global (85% of the network returned errors).

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

1Scrub the outage

full window
Severityofficial state Jun 8, 2 AMJun 8, 3 AMJun 8, 3 AMJun 8, 4 AMJun 8, 5 AMJun 8, 5 AM Official statusJun 8, 2:47 AM PT · Impact begins (vendor-stated)Jun 8, 5:35 AM 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

Fastly: Valid customer configuration triggered a latent global bug. Scope: Global (85% of the network returned errors).

What broke

Fastly CDN (global).

Who was hit

2 catalogued services run on Fastly (inferred). Hit: Global (85% of the network returned errors).

How it recovered

Resolved after 2h 48m.

2Blast radius

PyPI · OperationalPyPIReddit · OperationalRedditFastly2 dependents

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.

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
  • Config propagationvendor post-incident report (Meltdown Index)
  • Retry amplificationno sign
  • Control-plane couplingno 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 · Jun 7, 8:47 PM PT: 0 itemsOfficial status · Jun 7, 9:09 PM PT: 0 itemsOfficial status · Jun 7, 9:31 PM PT: 0 itemsOfficial status · Jun 7, 9:53 PM PT: 0 itemsOfficial status · Jun 7, 10:15 PM PT: 0 itemsOfficial status · Jun 7, 10:37 PM PT: 0 itemsOfficial status · Jun 7, 10:59 PM PT: 0 itemsOfficial status · Jun 7, 11:21 PM PT: 0 itemsOfficial status · Jun 7, 11:43 PM PT: 0 itemsOfficial status · Jun 8, 12:05 AM PT: 0 itemsOfficial status · Jun 8, 12:27 AM PT: 0 itemsOfficial status · Jun 8, 12:49 AM PT: 0 itemsOfficial status · Jun 8, 1:11 AM PT: 0 itemsOfficial status · Jun 8, 1:33 AM PT: 0 itemsOfficial status · Jun 8, 1:55 AM PT: 0 itemsOfficial status · Jun 8, 2:17 AM PT: 0 itemsOfficial status · Jun 8, 2:39 AM PT: 1 itemOfficial status · Jun 8, 3:01 AM PT: 0 itemsOfficial status · Jun 8, 3:23 AM PT: 0 itemsOfficial status · Jun 8, 3:45 AM PT: 0 itemsOfficial status · Jun 8, 4:07 AM PT: 0 itemsOfficial status · Jun 8, 4:29 AM PT: 0 itemsOfficial status · Jun 8, 4:51 AM PT: 0 itemsOfficial status · Jun 8, 5:13 AM PT: 0 itemsNetwork & routingNetwork & routing · Jun 7, 8:47 PM PT: 0 itemsNetwork & routing · Jun 7, 9:09 PM PT: 0 itemsNetwork & routing · Jun 7, 9:31 PM PT: 0 itemsNetwork & routing · Jun 7, 9:53 PM PT: 0 itemsNetwork & routing · Jun 7, 10:15 PM PT: 0 itemsNetwork & routing · Jun 7, 10:37 PM PT: 0 itemsNetwork & routing · Jun 7, 10:59 PM PT: 0 itemsNetwork & routing · Jun 7, 11:21 PM PT: 0 itemsNetwork & routing · Jun 7, 11:43 PM PT: 0 itemsNetwork & routing · Jun 8, 12:05 AM PT: 0 itemsNetwork & routing · Jun 8, 12:27 AM PT: 0 itemsNetwork & routing · Jun 8, 12:49 AM PT: 0 itemsNetwork & routing · Jun 8, 1:11 AM PT: 0 itemsNetwork & routing · Jun 8, 1:33 AM PT: 0 itemsNetwork & routing · Jun 8, 1:55 AM PT: 0 itemsNetwork & routing · Jun 8, 2:17 AM PT: 0 itemsNetwork & routing · Jun 8, 2:39 AM PT: 0 itemsNetwork & routing · Jun 8, 3:01 AM PT: 0 itemsNetwork & routing · Jun 8, 3:23 AM PT: 0 itemsNetwork & routing · Jun 8, 3:45 AM PT: 0 itemsNetwork & routing · Jun 8, 4:07 AM PT: 0 itemsNetwork & routing · Jun 8, 4:29 AM PT: 0 itemsNetwork & routing · Jun 8, 4:51 AM PT: 0 itemsNetwork & routing · Jun 8, 5:13 AM PT: 0 itemsEarly signalsEarly signals · Jun 7, 8:47 PM PT: 0 itemsEarly signals · Jun 7, 9:09 PM PT: 0 itemsEarly signals · Jun 7, 9:31 PM PT: 0 itemsEarly signals · Jun 7, 9:53 PM PT: 0 itemsEarly signals · Jun 7, 10:15 PM PT: 0 itemsEarly signals · Jun 7, 10:37 PM PT: 0 itemsEarly signals · Jun 7, 10:59 PM PT: 0 itemsEarly signals · Jun 7, 11:21 PM PT: 0 itemsEarly signals · Jun 7, 11:43 PM PT: 0 itemsEarly signals · Jun 8, 12:05 AM PT: 0 itemsEarly signals · Jun 8, 12:27 AM PT: 0 itemsEarly signals · Jun 8, 12:49 AM PT: 0 itemsEarly signals · Jun 8, 1:11 AM PT: 0 itemsEarly signals · Jun 8, 1:33 AM PT: 0 itemsEarly signals · Jun 8, 1:55 AM PT: 0 itemsEarly signals · Jun 8, 2:17 AM PT: 0 itemsEarly signals · Jun 8, 2:39 AM PT: 0 itemsEarly signals · Jun 8, 3:01 AM PT: 0 itemsEarly signals · Jun 8, 3:23 AM PT: 0 itemsEarly signals · Jun 8, 3:45 AM PT: 0 itemsEarly signals · Jun 8, 4:07 AM PT: 0 itemsEarly signals · Jun 8, 4:29 AM PT: 0 itemsEarly signals · Jun 8, 4:51 AM PT: 0 itemsEarly signals · Jun 8, 5:13 AM PT: 0 itemsNews & chatterNews & chatter · Jun 7, 8:47 PM PT: 0 itemsNews & chatter · Jun 7, 9:09 PM PT: 0 itemsNews & chatter · Jun 7, 9:31 PM PT: 0 itemsNews & chatter · Jun 7, 9:53 PM PT: 0 itemsNews & chatter · Jun 7, 10:15 PM PT: 0 itemsNews & chatter · Jun 7, 10:37 PM PT: 0 itemsNews & chatter · Jun 7, 10:59 PM PT: 0 itemsNews & chatter · Jun 7, 11:21 PM PT: 0 itemsNews & chatter · Jun 7, 11:43 PM PT: 0 itemsNews & chatter · Jun 8, 12:05 AM PT: 0 itemsNews & chatter · Jun 8, 12:27 AM PT: 0 itemsNews & chatter · Jun 8, 12:49 AM PT: 0 itemsNews & chatter · Jun 8, 1:11 AM PT: 0 itemsNews & chatter · Jun 8, 1:33 AM PT: 0 itemsNews & chatter · Jun 8, 1:55 AM PT: 0 itemsNews & chatter · Jun 8, 2:17 AM PT: 0 itemsNews & chatter · Jun 8, 2:39 AM PT: 0 itemsNews & chatter · Jun 8, 3:01 AM PT: 0 itemsNews & chatter · Jun 8, 3:23 AM PT: 0 itemsNews & chatter · Jun 8, 3:45 AM PT: 0 itemsNews & chatter · Jun 8, 4:07 AM PT: 0 itemsNews & chatter · Jun 8, 4:29 AM PT: 0 itemsNews & chatter · Jun 8, 4:51 AM PT: 0 itemsNews & chatter · Jun 8, 5:13 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Jun 7, 8:47 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 9:09 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 9:31 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 9:53 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 10:15 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 10:37 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 10:59 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 11:21 PM PT: 0 itemsCoincidence (KEV) · Jun 7, 11:43 PM PT: 0 itemsCoincidence (KEV) · Jun 8, 12:05 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 12:27 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 12:49 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 1:11 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 1:33 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 1:55 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 2:17 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 2:39 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 3:01 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 3:23 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 3:45 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 4:07 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 4:29 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 4:51 AM PT: 0 itemsCoincidence (KEV) · Jun 8, 5:13 AM PT: 0 itemsJun 7, 8:47 PM PTJun 8, 5:35 AM 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

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.

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.
  • Longer than 8 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 Fastly.

8Dissection capsule

Share card for this dissection

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

JSON capsuleMarkdownShare card (SVG)

Open Fastly in the War Room →Status page →

Embed this card
<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>

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.