PlanetScale reported this major-impact incident on its official status page on May 14, 2026, 20:30 UTC. It was resolved after 32 min.
Right now PlanetScale is operational. Live PlanetScale status →
The changes we applied are effectively preventing further unexpected restarts to the high availability component shared by Postgres clusters. We have not seen further restarts to this component nor unplanned failovers in Postgres clusters since applying these changes.
We applied changes to prevent unexpected restarts of the high availability component shared by Postgres clusters. We have not seen further restarts of this component nor unplanned Postgres failovers since applying these changes. We are actively monitoring the situation.
We have identified the likely cause of unexpected restarts to the high availability component used by Postgres clusters, and are applying changes to prevent recurrences.
A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters.
Our 5-minute checks didn't record a change in PlanetScale's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
PlanetScale reported 9 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 21m. See PlanetScale's uptime and incident history