Kiro AI Coding Tool Was Reportedly Implicated in 13-Hour AWS Cost Explorer Outage in Mainland China

December 15, 2025

The incident has raised questions about the accountability of internal AI tools in large-scale infrastructure disruptions, and the need for clear lines of responsibility in such situations is now a pressing concern. As Amazon continues to navigate this mystery, it is crucial that they conduct a thorough investigation into what really went wrong and how to prevent similar incidents in the future. We will continue to monitor this story and provide updates as more information becomes available; you can join us on this journey of discovery by clicking here JOIN US.

Matched TAIM controls

Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls

Alleged deployer
Amazon Web Services (AWS)
Alleged developer
Amazon Web Services (AWS)
Alleged harmed parties
Amazon Web Services (AWS) customers

AI governance case studies

For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.

Source

Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/1442

Data source

Incident data is from the AI Incident Database (AIID).

When citing the database as a whole, please use:

McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.

Pre-print on arXiv · Database snapshots & citation guide

We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.