- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 2h 27m it lasted.
Anything that failed between 2026-07-06 19:18 UTC and 2026-07-06 21:45 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
PlanetScale initiated a system wide upgrade of branches with Vectors enabled and running on MySQL 8.0 to MySQL 8.4. A number of development branches were disrupted and have not yet recovered. We are investigating and remediating.
provider
- identified
We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.
provider
- monitoring
Branches are recovering and we are monitoring the situation.
provider
- resolved
All impacted branches are recovered. PlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. A bug in the 8.4.x version of our Vectors builds resulted in the upgrade immediately failing on startup. Because Vitess development branches only have one instance - the primary - impacted development branches did not have a primary during the impact window. The incident was resolved by reverting impacted branches to their previous MySQL version. PlanetScale will fix the bug in the MySQL Vectors 8.4.x build before re-attempting the upgrade at a later date.
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-1a5ab754d7
Is PlanetScale still down?
No, this incident was resolved 2026-07-06 21:45 UTC. For PlanetScale's live state, see https://down.guide/planetscale.
How long did it last?
2h 27m, from 2026-07-06 19:18 UTC to 2026-07-06 21:45 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.