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 certain changes, say four people familiar with the matter.
Kiro is an agentic tool, meaning it can take autonomous actions on behalf of users. In this case, the bot reportedly determined that it needed to “delete and recreate the environment.” This is what allegedly led to the lengthy outage that primarily impacted China.
Amazon says it was merely a “coincidence that AI tools were involved” and that “the same issue could occur with any developer tool or manual action.” The company blamed the outage on “user error, not AI error.” It said that by default the Kiro tool “requests authorization before taking any action” but that the staffer involved in the December incident had “broader permissions than expected — a user access control issue, not an AI autonomy issue.”
Multiple Amazon employees spoke to Financial Times and noted that this was “at least” the second occasion in recent months in which the company’s AI tools were at the center of a service disruption. “The outages were small but entirely foreseeable,” said one senior AWS employee.
A builder shares why their workflow finally clicked.
Instead of jumping straight to code, the IDE pushed them to start with specs.
✔️ Clear requirements.
✔️ Acceptance criteria.
✔️ Traceable tasks.
Their takeaway:
Think first. Code later.
Get the full breakdown here 👉… pic.twitter.com/eD7ZrEdEn5
— Kiro (@kirodotdev) January 14, 2026
The company launched Kiro in July and has since pushed employees into using the tool. Leadership set an 80 percent weekly use goal and has been closely tracking adoption rates. Amazon also sells access to the agentic tool for a monthly subscription fee.
These recent outages follow a more serious event from October, in which a 15-hour AWS outage disrupted services like Alexa, Snapchat, Fortnite and Venmo, among others. The company blamed a bug in its automation software for that one.
This article originally appeared on Engadget at https://www.engadget.com/ai/13-hour-aws-outage-reportedly-caused-by-amazons-own-ai-tools-170930190.html?src=rss