Fastly outage: one customer's valid setting triggers a hidden bug
A latent bug in Fastly's edge software made 85% of its network return errors, taking down many major websites for about an hour.
- Security:
- No determination
- Started
- Jun 8, 2021, 09:47 UTC
- Incident mitigated
- Jun 8, 2021, 12:35 UTC
- Duration
- 49 minto: Services began to recover2 h 48 min to: Incident mitigated
- Full recovery
- Complete
- Geographic scope
- Global
- Last verified
- 1 source
What happened
- Systems and services affected
- Fastly CDN edge network
- Kind of failure
- Software defect
- Sector
- Internet infrastructure
- Provider report
- Published
- Status and recovery
- Resolved. Most services recovered by 11:00 UTC; Fastly marked the incident mitigated at 12:35 UTC and began deploying the permanent fix at 17:25 UTC.[1]
95% of the network was operating normally within 49 minutes; Fastly marked the incident mitigated at 12:35 UTC.
What caused it?
Root cause: ConfirmedA software deployment that began May 12 introduced a bug that a specific customer configuration could trigger. On June 8 a customer pushed a valid configuration change that did.[1]
Provider report: Published. Fastly published a summary on June 8, 2021.[1]
Was it malicious?
No determinationFastly describes "an undiscovered software bug" triggered by a valid customer change. Its summary does not mention an attack.[1]
How the failure happened
- 1TriggerSoftware deployment (May 12)
- 2FailureValid customer configuration change (Jun 8)
- 3Spread85% of the network returned errors
- AffectedFastly CDN edge network
Evidence for each step
- 1Software deployment (May 12). Introduced a bug a specific customer configuration could trigger[1]Starting point.
- 2Valid customer configuration change (Jun 8). Triggered the bug[1]Led from step 1: Stated in a provider report or official record.
- 385% of the network returned errors[1]Led from step 2: Stated in a provider report or official record.
Only steps the sources state are drawn. Affected services are listed under What happened.
Explanation
Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.
Plain language: what happened and why people were affected.
On June 8, 2021, many big websites showed error messages for about an hour. They all used Fastly, a company that delivers web pages from servers around the world.
A software update weeks earlier had a hidden flaw. When one customer made a normal change to their settings, it set off the flaw and most of Fastly's network started failing.
Fastly spotted it within a minute and had most sites back within an hour.
Confirmed and unknown
Confirmed
Still unknown
No open questions: the provider has published a full account.
Timeline
Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.
- First observedJun 8, 2021, 09:48 UTC
- AcknowledgedNot documented
- MitigationJun 8, 2021, 10:36 UTC
- RecoveryJun 8, 2021, 11:00 UTC
- ResolvedJun 8, 2021, 12:35 UTC
- Incident reportJun 8, 2021
- Software deployment introduces the latent bug.[1]
- Customer configuration change triggers the bug; global disruption begins.[1]
- First observedFastly monitoring detects the disruption.[1]
- Fastly identifies the customer configuration that triggered the bug.[1]
- MitigationServices begin to recover.[1]
- RecoveryMost services recovered.[1]
- ResolvedIncident mitigated.[1]
- After the incident endedBug fix deployment begins.[1]
- Incident reportFastly publishes its summary of the outage.[1]
- Start to: Services began to recover49 min
- Start to: Incident mitigated2 h 48 min
Related incidents
Links stated by providers or officials carry their evidence label. “Similar failure” is a comparison of documented causes, not a causal link.
- Similar failure (comparison)
A valid input reached a latent flaw in a CDN's edge software.[1]
Evidence and sources
Grouped by type of evidence. Numbers match the citations above.
Primary: provider and official sources
Published by the provider or agency itself: incident reports, status records, advisories, statements.
- 1.Summary of June 8 outage (opens in a new tab)Fastly · Provider report · Published · Accessed
Last verified against these sources on Nov 14, 2026.