Engineering postmortems, with sources
Follow the timeline of real engineering failures: what broke, how teams detected it, how they recovered, and what they changed afterward. Timeline claims link to their sources.
AWS Middle East (Bahrain) Region (ME-SOUTH-1) · 6 timeline events
A facility in AWS’s Bahrain region suffered physical impact and power disruption. AWS later said the region was unavailable and it could not restore resources and data that had not been migrated.
Read the timeline →AWS Middle East (UAE) Region (ME-CENTRAL-1) · 10 timeline events
Physical damage and power loss impaired two availability zones in AWS’s UAE region. AWS reported cascading errors in services including S3, DynamoDB, EC2, Lambda, and RDS; recovery remains incomplete.
Read the timeline →GitHub.com · 6 timeline events
A network partition triggered cross-region database failover, leaving clusters with divergent writes and causing more than a day of degraded service while GitHub restored consistency.
Read the timeline →Cloudflare WAF and global network · 6 timeline events
A globally deployed WAF rule contained a regular expression with excessive backtracking, exhausting CPU on Cloudflare’s HTTP/HTTPS serving path.
Read the timeline →Amazon S3 (AWS US-EAST-1) · 4 timeline events
An incorrectly entered operational command removed more S3 subsystem capacity than intended, affecting S3 and dependent AWS services in Northern Virginia.
Read the timeline →