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.

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

3 results · filtered
topic: ebs
id
incident
org
date
duration
severity
tags
FM-018
The Overheated AWS ZoneA thermal event in one US-EAST-1 data center impaired EC2 instances and EBS volumes in use1-az4, disrupting workloads that depended on resources pinned to the affected Availability Zone.
AWS
2026-05-08
20h 30m
SEV-2
us-east-1use1-az4thermal-event
FM-012
When Heroku's Whole Platform Shared One AWS Failure DomainWhen AWS's US-East EBS storage entered a re-mirroring storm, Heroku's dynos, Heroku Postgres databases, and management API all failed together. The platform had no other region to run in and no path to recover without AWS.
Heroku
2011-04-21
~3 days
SEV-1
awsebsus-east
FM-013
The EBS Self-Repair Storm That Couldn't Stop ItselfA network change in US-East shifted traffic to a low-capacity path. EBS nodes that lost their replication connection began re-mirroring at the same time, exhausting free capacity and stranding volumes in a loop the cluster could not exit on its own.
AWS
2011-04-21
~4 days
SEV-1
ebsrdsus-east