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.

Summary

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.

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.

• Started

  May 14, 2026 · 8:30 PM

• Resolved

  May 14, 2026 · 9:03 PM

• Duration

  32m

• Severity

  Major

• ◐

  Investigating

  May 14 · 8:30 PM PlanetScale

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

• ◆

  Identified

  May 14 · 8:42 PM PlanetScale

  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.

• ◉

  Monitoring

  May 14 · 8:51 PM PlanetScale

  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.

• ✓

  Resolved

  May 14 · 9:03 PM PlanetScale

  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.