Inside Amazon S Ai Outage Crisis What The Emergency Meeting Signals For Enterprise Engineering

Originally published on CoreProse KB-incidents Amazon’s latest reliability scare was not a single bad deploy but a pattern. After four Sev1 incidents in one week, Amazon’s retail tech leadership turned its routine “This Week in Stores Tech” (TWiST) meeting into a mandatory deep dive on outages and root causes. Senior vice president Dave Treadwell admitted that site availability “has not been good recently.”[5][7] Internal documents pointed to a “trend of incidents” since Q3 2025, with several disruptions tied to generative AI–assisted changes and coding tools like Q and Kiro.[2][9] One outage left customers unable to see prices or complete checkouts for roughly six hours, traced to an erroneous software deployment.[5] For engineering leaders, this is a case study in what happens when generative AI scales faster than your guardrails. 1. What Triggered Amazon’s Emergency AI Outage Meeting Amazon’s retail tech organization convened a special TWiST session to dissect recent outages and def