STUPID-2026-0054
Two AI agents ping-ponged for 11 days and ran up a $47,000 bill — neither noticed anything wrong
Instruction given
Run a research pipeline with an Analyzer agent and a Verifier agent.
Expected behavior
Detect when the pipeline is stuck and halt; cap spend.
Actual behavior
An Analyzer and a Verifier agent ping-ponged requests at each other for 11 days straight, generating a $47,000 bill. Because neither agent saw an error from its own perspective, no error was ever flagged and nothing stopped the loop.
Damage
$47,000 in irrecoverable API/compute spend from an 11-day loop that no component recognized as broken — a pure agentic runaway with no human-visible failure until the invoice arrived.
Classification
- Agent
- Multiple Agents
- Failure mode
- Infinite Loop
- Root cause
- Confidence Miscalibration
- Domain
- Infra
- Source
- News Report
Related incidents
Get told when an agent breaks something
We document AI agent failures daily, severity-scored against a published scale. When one lands at 7.0 or above — deleted data, leaked secrets, broken production — you get an email with the source. When nothing does, you get nothing.
This database is callable over MCP — query it from inside your agent.