Skip to content
Submit incident
AII-1001-11477
Well documentedThree or more independent publishers report the core facts.

AWS outage caused by autonomous AI coding tool Kiro

Amazon AWS experienced at least one significant outage in December lasting 13 hours when its autonomous AI coding tool Kiro was allowed to delete and recreate an environment. The incident disrupted a cost management resource affecting customers in one of AWS's 39 regions. Amazon disputed reports of two separate AI-caused outages, attributing the incident to user error rather than AI malfunction.

December 2025 Β· Amazon Β· Safety and wellbeing
December 2025
AII-1001-114778 sources ↓
Quick facts
Category
Safety and wellbeing
Country
United States
Source
The Times of India
Date
December 2025
Drafted by
Raidu Incident Detection

What happened

A 13-hour interruption to AWS operations in December was caused by the AI agent Kiro autonomously choosing to delete and then recreate a part of its environment, according to reporting by the Financial Times.

The incident affected a cost management resource used by customers to monitor usage costs in one of AWS's 39 regions, reportedly in one of two regions in mainland China.

Reported impact

The outage disrupted the AWS cost management service, preventing customers in the affected region from monitoring their usage costs during the 13-hour period.

AWS provides vital infrastructure for much of the internet, and the outage affected a customer-facing service.

Index analysis

A security researcher, Jamieson O'Reilly, noted that AI-caused mishaps differ from human errors because AI agents typically have less opportunity to self-correct during autonomous actions compared to manual human input, where errors can be caught during typing.

Financial Times reporting cited sources familiar with the matter stating that AWS suffered two interruptions in December due to errors involving its own AI tools, though Amazon disputed this characterization and said there was only one incident affecting customers.

Governance controls

Amazon attributed the outage to user error rather than AI error, stating in a response to the Financial Times that engineers had allowed the Kiro tool to perform certain changes.

Amazon said there was no evidence that AI tools led to more errors than human engineers, characterizing the incident as extremely limited and coincidental in nature.

Classification

Category
Safety and wellbeing
Industry
IT infrastructure and hosting
Country
United States
Harm status
Actual harm
Intent
Unintentional
Timing
Post-deployment
Harm types
Economic or property, Public interest
Harmed
Consumers, Business
Failure modes
Unsafe autonomous behaviour, Agent misaction
AI systems
Kiro

Sources and evidence

This record was researched and written by the Index, based on the following original reporting.

The Times of India
AWS reported outage: Amazon claims it was 'coincidence' that AI tools were involved and that the ... - The Times of India
20 February 2026
The Guardian
Amazon's cloud 'hit by two outages caused by AI tools last year'
20 February 2026
The Hindu
Amazon's cloud unit hit was hit by least two outages involving AI tools in December: Report
20 February 2026
The Verge
Amazon blames human employees for an AI coding agent's mistake
20 February 2026
Economic Times
Amazon's cloud unit hit by outage involving AI tools in December
20 February 2026
TechRadar
Recent AWS outages blamed on AI tools - at least two incidents took down Amazon services
20 February 2026
Tom's Guide
AWS suffered 'at least two outages' caused by AI tools, and now I'm convinced we're living inside a 'Silicon Valley' episode
20 February 2026
uol.com.br
Unidade de computaΓ§Γ£o em nuvem da Amazon sofreu em dezembro interrupΓ§Γ£o envolvendo ferramentas de IA
20 February 2026