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.

Final update

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.

1. Resolved · May 14, 21:03 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.
2. Monitoring · May 14, 20:51 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.
3. Identified · May 14, 20:42 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.
4. Investigating · May 14, 20:30 UTC
   A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters.