- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 26of 100
What to do
Check whether your product depends on PlanetScale. 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 28m it lasted.
Anything that failed between 2026-07-17 16:41 UTC and 2026-07-17 17:09 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 4
- investigating
We are aware that both our API and dashboard are returning errors. We are investigating the cause and will restore service as soon as possible.
provider
- identified
We have identified the cause of the errors - a pattern of requests causing the application to run out of memory and crash - and are working to better handle this traffic pattern now.
provider
- monitoring
We have increased the memory available to the API and are monitoring the performance and stability of the API and dashboard to confirm service is restored.
provider
- resolved
API and dashboard service is restored.
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-b2a821f71c
Is PlanetScale still down?
No, this incident was resolved 2026-07-17 17:09 UTC. For PlanetScale's live state, see https://down.guide/planetscale.
How long did it last?
28m, from 2026-07-17 16:41 UTC to 2026-07-17 17:09 UTC, by the times PlanetScale posted.
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.