Tools
Entities
View all entitiesIncident Stats
Risk Subdomain
7.3. Lack of capability or robustness
Risk Domain
- AI system safety, failures, and limitations
Entity
AI
Timing
Post-deployment
Intent
Unintentional
Incident Reports
Reports Timeline
Amazon Web Services suffered a 13-hour outage to one system in December as a result of its AI coding assistant Kiro's actions, according to the Financial Times. Numerous unnamed Amazon employees told the *FT *that AI agent Kiro was responsi…

A recent Amazon Web Services (AWS) outage that lasted 13 hours was reportedly caused by one of its own AI tools, according to reporting by Financial Times. This happened in December after engineers deployed the Kiro AI coding tool to make c…
When Amazon Web Services got hit by a 13-hour outage in December, it wasn't because a person tripped over a cord. According to a report from the Financial Times, several anonymous Amazon employees said that the outage was the fault of Kiro,…
We want to address the inaccuracies in the Financial Times' reporting yesterday. The brief service interruption they reported on was the result of user error---specifically misconfigured access controls---not AI as the story claims.
The dis…
In December 2025, Amazon Web Services experienced a 13-hour outage that started with an AI bot making a decision. Not a human engineer. An AI coding tool called Kiro decided the best way to fix a problem was to delete and recreate a product…
Variants
Similar Incidents
Did our AI mess up? Flag the unrelated incidents
Similar Incidents
Did our AI mess up? Flag the unrelated incidents


