Live / Amp / Incident
Amp: Thread creation and agent failures
Amp · ampcode.comMajor incidentResolved2026-10-21 22:52 UTC
Public — what happened
Summary
Amp reported a major incident beginning at 22:35 UTC on 2026-10-21, in which some agents and threads could not connect. By 22:41 UTC the company said agents were connecting but taking roughly 5 to 20 seconds to do so. Amp's posted updates did not name a cause, and the incident was marked resolved at 22:52 UTC.
Timeline
- Started — 2026-10-21 22:35 UTC
- Investigating — 2026-10-21 22:35 UTC (2 updates)
- Resolved — 2026-10-21 22:52 UTC · 17 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.