Amazon's Kiro coding agent linked to 13-hour AWS outage
The Financial Times, citing four people familiar with the matter, reported that engineers let Amazon's internal Kiro coding agent make changes, and it chose to delete and recreate an environment, triggering a roughly 13-hour interruption in mid-December 2025. Amazon says the event hit only AWS Cost Explorer in one region in mainland China. It attributes the event to a misconfigured role (user error), not to the AI, and has since required peer review for production access.
Damage
~13-hour interruption of AWS Cost Explorer in one region (per FT); Amazon reports no customer inquiries
Sources
Financial Times, second source. Evidence confidence: medium. Causation is disputed. Amazon calls it user error and says the engineer's role had broader permissions than intended. The FT reported a second AI-tool incident; Amazon says it did not affect AWS and happened elsewhere in Amazon. The FT piece ran about 19–20 Feb 2026, and Amazon published its rebuttal on 20 Feb. AIID dates the outage to about 15 Dec 2025.
Factor ratings and the score are this index’s judgments by a published formula; facts, dates and figures come from the linked sources. Where a lawsuit is pending, the summary reports allegations, not findings.
