1/ The "cloud is always up" assumption took three hits in five weeks last fall. The dates, the causes, the blast radius — then one question for your ops team:
2/ Oct 19–20, 2025: AWS US-East-1 goes down. Cause: a DynamoDB DNS race condition. Recovered ~6 p.m. ET Oct 20.
3/ Oct 29, 2025: Azure, 8 hours. Cause: a faulty tenant configuration deployment. Alaska Airlines reported key systems affected.
4/ Nov 18, 2025: Cloudflare. Blast radius: ~40M live sites, 19M in the U.S.
5/ Different providers, different causes, same lesson: one region or one config push can be one point of failure. The question isn't if it recurs — it's what your team does in hour one. What's your plan?
CTA — Reply prompt: "What's your hour-one plan?"