Live / Amp / Incident
Amp: Thread creation and agent failures
Amp · ampcode.comCritical outageResolved2026-10-21 12:29 UTC
Public — what happened
Summary
Amp reported a critical incident in which users could not start new threads, and sending messages within threads returned errors. The company said it began investigating at 12:07 UTC on 2026-10-21. Six minutes later, at 12:13 UTC, Amp said it had found the problem and was rolling out a fix. The incident was marked resolved at 12:29 UTC.
Timeline
- Started — 2026-10-21 12:07 UTC
- Investigating — 2026-10-21 12:07 UTC
- Identified — 2026-10-21 12:13 UTC
- Resolved — 2026-10-21 12:29 UTC · 23 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Amp against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Amp: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Amp report →
More from Amp
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.