Live / Amp / Incident
Amp: Some threads are stuck in reconnecting
Amp · ampcode.comMajor incidentResolved2026-10-23 19:11 UTC
Public — what happened
Summary
Amp said that some of its threads were stuck in a reconnecting state or failed to start, and it rated the incident as major. The company began investigating at 19:02 UTC on 2026-10-23. Amp marked the incident resolved at 19:11 UTC, about nine minutes later, and its status text did not name a cause.
Timeline
- Started — 2026-10-23 19:02 UTC
- Investigating — 2026-10-23 19:02 UTC
- Resolved — 2026-10-23 19:11 UTC · 9 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.