- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 17h it lasted.
Anything that failed between 2026-05-08 02:22 UTC and 2026-05-08 19:22 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 2
- monitoring
PlanetScale is aware of the AWS use1-az4 thermal event. We expect databases to be unaffected. Please contact support if you have any questions or notice any disruption.
provider
- resolved
PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.
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-f6e39a9099
Is PlanetScale still down?
No, this incident was resolved 2026-05-08 19:22 UTC. For PlanetScale's live state, see https://down.guide/planetscale.
How long did it last?
17h, from 2026-05-08 02:22 UTC to 2026-05-08 19:22 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.