There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information.

What to do

• Check whether you use PlanetScale in us, us-central1. 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 32m it lasted.

  Anything that failed between 2026-05-14 20:30 UTC and 2026-05-14 21:03 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

1. investigatingMay 14, 2026, 8:30 PM UTC

   A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters.

   provider

2. identifiedMay 14, 2026, 8:42 PM UTC

   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.

   provider

3. monitoringMay 14, 2026, 8:51 PM UTC

   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.

   provider

4. resolvedMay 14, 2026, 9:03 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.