Vendor reports: partial outageResolved · vendor status “resolved”Official status API

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.

Reported by PlanetScale · Databases · source last read 5 min ago

Vendor start
May 14, 2026, 20:30 UTC
Vendor's clock
Resolved
May 14, 2026, 21:03 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
32 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • PlanetScale reports partial outage: "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.".[E1, E2]
  • The vendor marked it resolved at 2026-05-14 21:03 UTC.[E3, E7]

Affected products and regions

  • Regions: us-central1 (read from the title, so inferred).[E5]

What is unknown

  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-05-14 21:03 UTC · summary s1, evidence ba9459f0ab1a298f

Evidence (7)
  1. E1PlanetScale reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "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.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-05-14 20:30 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-central1. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-05-14 21:03 UTC. (vendor)

Affected scope

us-central1

Components: not stated by the vendor

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

PlanetScale is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. May 14, 2026, 20:30 UTCVendor-reported startVendor time
  2. May 14, 2026, 21:03 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.