The library. Every incident, structured.
A growing archive of public postmortems, broken down into a consistent shape: what broke, why it cascaded, and what to take from it. New incidents added regularly.
28+
incidents
11+
years
13
organizations
/
sort
1 result · filtered
topic: latent-bug
id
incident
org
date
duration
severity
tags
FM-005
The Valid Config Change That Broke 85% of FastlyA software release shipped 27 days earlier left a latent bug in Fastly's edge platform. A routine, valid customer configuration change triggered it and 85% of Fastly's network began returning errors within seconds.
Fastly
2021-06-08
~1h
SEV-1
cdnedge-networkconfig