- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 34of 100
What to do
Check whether you use PlanetScale in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 26m it lasted.
Anything that failed between 2026-10-09 22:53 UTC and 2026-10-09 23:19 UTC may need a replay.Subscribe to PlanetScale's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=planetscale works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from PlanetScale 3
- investigating
We are investigating reports of connectivity failures scoped to a single AZ in AWS us-east-1 causing replica delay and connectivity issues.
provider
- monitoring
A small number of database branches in AWS us-east-1 were impacted by cross-zone networking issues, for which the impact window has ended. If you continue to see impact, please reach out to PlanetScale support.
provider
- resolved
AWS us-east-1 cross-zone networking has fully recovered.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-23be5a48d0
Is PlanetScale still down?
No, this incident was resolved 2026-10-09 23:19 UTC. For PlanetScale's live state, see https://down.guide/planetscale.
How long did it last?
26m, from 2026-10-09 22:53 UTC to 2026-10-09 23:19 UTC, by the times PlanetScale posted.
What was affected?
PlanetScale named in us, us-east-1.
What caused it?
PlanetScale hasn't published a root cause. If it does, it shows here.
Where does this come from?
PlanetScale's official status page, https://www.planetscalestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.