PlanetScale incident

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.

Minor Resolved View vendor source →

PlanetScale experienced a minor incident on May 14, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 14, 2026, 09:03 PM UTC
Resolved
May 14, 2026, 09:03 PM UTC
Duration
Detected by Pingoru
May 14, 2026, 09:03 PM UTC

Update timeline

  1. investigating May 14, 2026, 08:30 PM UTC

    Status: Investigating A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters. Affected components us-central1 (Iowa) (Partial outage)

  2. identified May 14, 2026, 08:42 PM UTC

    Status: Identified 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. Affected components us-central1 (Iowa) (Partial outage)

  3. monitoring May 14, 2026, 08:51 PM UTC

    Status: Monitoring 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. Affected components us-central1 (Iowa) (Partial outage)

  4. resolved May 14, 2026, 09:03 PM UTC

    Status: Resolved 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. Affected components us-central1 (Iowa) (Operational)