Fastly·

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.

ResolvedEnded Jun 8, 2021
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: Confirmed

A 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 determination

Fastly describes "an undiscovered software bug" triggered by a valid customer change. Its summary does not mention an attack.[1]

How the failure happened

  1. 1TriggerSoftware deployment (May 12)
  2. 2FailureValid customer configuration change (Jun 8)
  3. 3Spread85% of the network returned errors
  4. AffectedFastly CDN edge network

Evidence for each step

  1. 1
    Software deployment (May 12). Introduced a bug a specific customer configuration could trigger[1]
    Starting point.
  2. 2
    Valid customer configuration change (Jun 8). Triggered the bug[1]
    Led from step 1: Stated in a provider report or official record.
  3. 3
    85% 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

  • Confirmed
    A bug introduced in a May 12 deployment was triggered by a valid customer configuration change.[1]
    Said by: Fastly · Evidence: Official
  • Confirmed
    85% of Fastly's network returned errors.[1]
    Said by: Fastly · Evidence: Official

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.

  1. First observedJun 8, 2021, 09:48 UTC
  2. AcknowledgedNot documented
  3. MitigationJun 8, 2021, 10:36 UTC
  4. RecoveryJun 8, 2021, 11:00 UTC
  5. ResolvedJun 8, 2021, 12:35 UTC
  6. Incident reportJun 8, 2021
Jun 8, 2021, 09:47 UTCJun 8, 2021, 17:25 UTC
  1. Software deployment introduces the latent bug.[1]
  2. Customer configuration change triggers the bug; global disruption begins.[1]
  3. First observed
    Fastly monitoring detects the disruption.[1]
  4. Fastly identifies the customer configuration that triggered the bug.[1]
  5. Mitigation
    Services begin to recover.[1]
  6. Recovery
    Most services recovered.[1]
  7. Resolved
    Incident mitigated.[1]
  8. After the incident ended
    Bug fix deployment begins.[1]
  9. Incident report
    Fastly publishes its summary of the outage.[1]
  10. Start to: Services began to recover49 min
  11. 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.

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. 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.