Live / PlanetScale / Incident
PlanetScale: AWS us-east-1 connectivity failures
PlanetScale · planetscale.comMajor incidentResolved2026-10-09 23:19 UTC
Public — what happened
Summary
PlanetScale reported a major incident on October 9, 2026, starting at 22:53 UTC, involving connection problems confined to one availability zone in its AWS us-east-1 region, which led to lagging replicas and trouble reaching databases. By 23:13 UTC the company said only a limited set of database branches in that region had been affected, attributing the problem to networking trouble between zones, and that the period of impact was over. PlanetScale asked customers still experiencing problems to contact its support team, and the incident was marked resolved at 23:19.
Timeline
- Started — 2026-10-09 22:53 UTC
- Investigating — 2026-10-09 22:53 UTC
- Monitoring — 2026-10-09 23:13 UTC
- Resolved — 2026-10-09 23:19 UTC · 26 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 PlanetScale 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 PlanetScale: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the PlanetScale report →
More from PlanetScale
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.