Live / Amp / Incident
Amp: Slowness on ampcode.com and clients
Amp · ampcode.comMinor incidentResolved2026-10-22 17:16 UTC
Public — what happened
Summary
Amp said some users saw intermittent slowness on ampcode.com and on its macOS, iOS and terminal clients, starting around 15:26 UTC on 2026-10-22. The company said it attributed the problem to its database hitting resource limits under heavier load, and later said a poorly performing query and a user's plugin were adding to the strain. Amp said it reduced the load, reverted the query and optimized others, and by 16:37 UTC reported database performance was back to normal. The incident was marked resolved at 17:16 UTC.
Timeline
- Started — 2026-10-22 15:26 UTC
- Identified — 2026-10-22 15:26 UTC (3 updates)
- Monitoring — 2026-10-22 16:37 UTC
- Resolved — 2026-10-22 17:16 UTC · 1h 51m 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.