The incident response lifecycle turned into a runbook a small team can follow under pressure: preparation, detection and analysis, containment, eradication, recovery and the post-incident review, with roles, evidence handling and communication templates.
A summary of Cloudflare's official postmortem for the November 18, 2025 outage: a database permission change doubled a generated feature file, which crossed a hard limit and crashed the proxy. Plus the lessons we are applying to our own config pipelines.
A practitioner's reading of AWS's official summary of the October 19-20, 2025 us-east-1 disruption: a race in DynamoDB's DNS automation left an empty record, and recovery cascaded through EC2, NLB and Lambda. What happened per the report, and what we changed.
A narrative of one on-call night on a subscription payments platform: the 01:40 page, a settlement job stuck on a lock, a provider returning timeouts that were actually successes, the decisions under pressure, and the blameless review that followed. Details changed, mistakes and lessons real.
A practical guide to blameless postmortems: how to build a timeline, measure impact, find contributing factors instead of a culprit, write action items that get done, and run the review meeting so people tell the truth.
A practitioner's summary of CrowdStrike's official root cause analysis for the July 19, 2024 Windows crashes: a 21-field template read with 20 inputs, an out-of-bounds read in a kernel driver, and fleets stuck in boot loops. What the RCA says, and what we changed in our own releases.