Live  /  Amp  /  Incident

Amp: Slow to connect to threads

Amp · ampcode.comMinor incidentResolved2026-09-05 17:55 UTC
Public — what happened

Summary

Amp reported a minor issue on September 5, 2026, beginning at 17:24 UTC, in which users were slow to connect to threads and some threads failed. The company said several deploys happening together led its load balancers to behave incorrectly and put too much load on some servers. Amp said it changed how traffic was being distributed, and the incident was marked resolved at 17:55.

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.