AWS Q Developer outage part of late-2025 AI outages; no customer impact on AWS services
Two AI-related AWS outages were reported in late 2025, including the Q Developer incident; AWS said it did not affect customer-facing AWS services, with public details limited. Public reporting emerged in February 2026 via FT and The Verge.
An AI coding agent error caused a small but entirely foreseeable AWS Q Developer outage.
Key facts
- What
- Two AI-related AWS outages were reported in late 2025, including the Q Developer incident; AWS said it did not affect customer-facing AWS services, with public details limited.
- Incident date
- Dec 1, 2025
- Who
- Amazon Web Services (AWS)
- Failure mode
- Agentic Action Error
- AI surface
- Chatbot
- Severity
- Low
What happened
Public reporting describes a late-2025 AWS production outage linked to the Q Developer AI tool. It was reported as the second AI-related AWS production outage in a short period, with the other outage tied to the Kiro AI tool in December 2025. AWS stated the Q Developer incident did not affect any customer-facing AWS services, and public technical details remain limited.
What broke inside the model
- 01 · TriggerAn agent plans a multi-step task.
- 02 · Model stepIt chooses a wrong or destructive action.
- 03 · Control gapNo confirmation gate guards the write.
- 04 · FailureThe action commits to a system of record.
- 05 · ConsequenceData is changed or destroyed irreversibly.
A wrong action commits, and the step is written before anything can stop it.
The mechanism is described as an AI coding agent error tied to Q Developer causing a production outage. Public accounts describe the outages as small and foreseeable, and AWS stated the incident did not affect customer-facing services.
What it cost
Sources
- PressAmazon blames human employees for an AI coding agents mistaketheverge.com
- PressFT: Two AWS outages linked to AI tools, including Q Developerft.com
- PressAI Incident Database: AWS Q Developer outage reportincidentdatabase.ai
Cite this entry
https://failureindex.ai/failures/aws-developer-outage-part-late-2025AI Failure Index. "AWS Q Developer outage part of late-2025 AI outages; no customer impact on AWS services" (FI-0228). Realm Labs. https://failureindex.ai/failures/aws-developer-outage-part-late-2025 (indexed Jun 5, 2026).Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0228. Full dataset at /data.
Note from Realm Labs, the Index steward
How Realm would have caught this
- Prism
- OmniGuard
- AgentRealm
Realm can sit inline on the agent's action path and require that a destructive or high-consequence action clears a real check before it executes, so 'delete and recreate' or a wrong write is stopped at the moment of intent, not explained in the post-mortem.