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

newsletter

Get the next incident.

One production failure case study every week. Read the pattern before it shows up in your own system.

1 result · filtered
topic: s3
id
incident
org
date
duration
severity
tags
FM-003
The S3 Command That Took Out us-east-1A maintenance command with the wrong scope argument removed too much S3 subsystem capacity in us-east-1, forcing the index and placement subsystems through full restarts.
AWS
2017-02-28
4h 17m
SEV-1
s3us-east-1storage