Live  /  Amp  /  Incident

Amp: Thread creation and connection failures

Amp · ampcode.comMajor incidentResolved2026-09-06 22:32 UTC
Public — what happened

Summary

Amp reported a major incident in which users had trouble creating threads and connecting, beginning at 16:22 UTC on September 6, 2026. The company did not say what caused the problem. In its final update, Amp said it had seen no errors for three hours, would keep watching, and planned further fixes to prevent a repeat. The incident was marked resolved at 22:32 that same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 37, 2026, our weekly internet health report.

The full archive is on the Amp status & history page.

Related: Amp status & history. SquidGrid is not affiliated with Amp.