Description: Sometime in mid-December 2025, AWS Cost Explorer in one mainland China region reportedly experienced an approximately 13-hour interruption after Amazon engineers allegedly allowed Kiro, an internal AI coding tool, to make changes and it reportedly deleted and recreated part of the working environment. Amazon reportedly disputed that account, saying the interruption was an extremely limited event caused by user error and misconfigured access controls, not AI.
Editor Notes: Timeline notes: 12/15/2025 is an approximate date. Reporting appears only to state sometime in mid-December 2025. The incident ID was created 04/05/2026.
Entities
View all entitiesAlleged: Amazon Web Services (AWS) , Kiro and AWS Cost Explorer developed and deployed an AI system, which harmed Amazon Web Services (AWS) customers.
Alleged implicated AI systems: Kiro and AWS Cost Explorer
Incident Stats
Risk Subdomain
A further 23 subdomains create an accessible and understandable classification of hazards and harms associated with AI
7.3. Lack of capability or robustness
Risk Domain
The Domain Taxonomy of AI Risks classifies risks into seven AI risk domains: (1) Discrimination & toxicity, (2) Privacy & security, (3) Misinformation, (4) Malicious actors & misuse, (5) Human-computer interaction, (6) Socioeconomic & environmental harms, and (7) AI system safety, failures & limitations.
- AI system safety, failures, and limitations
Entity
Which, if any, entity is presented as the main cause of the risk
AI
Timing
The stage in the AI lifecycle at which the risk is presented as occurring
Post-deployment
Intent
Whether the risk is presented as occurring as an expected or unexpected outcome from pursuing a goal
Unintentional
Incident Reports
Reports Timeline
Loading...
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…
Variants
A "variant" is an AI incident similar to a known case—it has the same causes, harms, and AI system. Instead of listing it separately, we group it under the first reported incident. Unlike other incidents, variants do not need to have been reported outside the AIID. Learn more from the research paper.
Seen something similar?
Similar Incidents
Did our AI mess up? Flag the unrelated incidents
Similar Incidents
Did our AI mess up? Flag the unrelated incidents