Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, last 374 daysPlaces named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
3 places · 5 not pinned
Virginia (us-east-1): 3 incidents · PlanetScaleIowa (us-central1): 1 incident · PlanetScaleMontréal (northamerica-northeast1): 1 incident · PlanetScale
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 87 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Mon, Oct 261 incident

21:53SEV 2PlanetScale · Problems with Vitess connectivity and credential changes · source1h 38m

Fri, Oct 91 incident

22:53SEV 2PlanetScale · AWS us-east-1 connectivity failures · source26m

Sat, Sep 51 incident

18:39SEV 2PlanetScale · Connectivity issues with Vitess databases in GCP · source14m

Sat, Jul 181 incident

20:32SEV 2PlanetScale · Connectivity issues in us-east-1 · source33m

Fri, Jul 171 incident

16:41SEV 2PlanetScale · API and dashboard errors · source28m

Mon, Jul 61 incident

19:18SEV 2PlanetScale · Development branches with MySQL Vectors not serving · source2h 27m

Thu, May 141 incident

20:30SEV 2PlanetScale · 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. · source32m

Wed, Mar 111 incident

13:04SEV 2PlanetScale · us-east-1 connection errors · source15m

Wed, Feb 181 incident

20:23SEV 2PlanetScale · Vitess database availability issues in GCP northamerica-northeast1 · source43m

Fri, Jan 91 incident

01:29SEV 2PlanetScale · API availability issues · source17m