Vendor Status Watch

← all vendors

PlanetScale status history

Current state: operational — “All Systems Operational” per https://www.planetscalestatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
8incidents, last 90 days
26incidents on record
Incidents per week, last 12 weeks:

How long do PlanetScale incidents last?

44 minmedian incident duration24 measured
7.4 h90th percentile1 in 10 ran longer
37 minmedian, major/critical only14 incidents

From 24 incidents with a vendor-posted start and resolve time. Longest on record: Insights metrics underreporting — 20.8 h (2026-07-20 18:29 UTC). Excluded, never estimated: 2 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (26)

StartedIncidentStatusImpactDuration
2026-09-05 18:39 UTCConnectivity issues with Vitess databases in GCPresolvedmajor14 min
2026-09-02 16:34 UTCDashboard and API 500 errors for postgres databasesresolvedmajor10 min
2026-07-24 14:41 UTCInsights metrics underreportingresolvedmajor3 h 00 min
2026-07-20 18:29 UTCInsights metrics underreportingresolvedminor20 h 49 min
2026-07-18 20:32 UTCConnectivity issues in us-east-1resolvedmajor32 min
2026-07-17 16:41 UTCAPI and dashboard errorsresolvedmajor27 min
2026-07-16 09:30 UTCSingle Sign On (SSO) unavailableresolvedminor1 h 21 min
2026-07-06 19:18 UTCDevelopment branches with MySQL Vectors not servingresolvedminor2 h 26 min
2026-05-14 20:30 UTCThere 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.resolvedmajor32 min
2026-05-13 17:17 UTCDatabase operations degraded in eu-west-2resolvedminor47 min
2026-05-08 02:22 UTCAWS use1-az4 thermal eventresolvednone16 h 59 min
2026-04-08 00:34 UTCErrors with database webhooksresolvedminor15 min
2026-04-02 22:37 UTCCurrently experiencing issues with creating/updating/deleting Vitess credentialsresolvedminor14 min
2026-03-11 13:04 UTCus-east-1 connection errorsresolvedmajor15 min
2026-02-24 10:26 UTCVitess branch creation unavailableresolvedmajor1 h 34 min
2026-02-18 20:23 UTCVitess database availability issues in GCP northamerica-northeast1resolvedmajor42 min
2026-01-31 09:38 UTCQuery insights outageresolvedcritical2 h 19 min
2026-01-09 01:29 UTCAPI availability issuesresolvedmajor16 min
2026-01-08 16:30 UTCInsights ingestion delayedresolvedminor1 h 44 min
2026-01-06 16:27 UTCErrors with branch creation for GCP databasesresolvedmajor1 h 13 min
2025-11-17 18:10 UTCAPI and dashboard: 500 errorsresolvedmajor
2025-10-20 16:09 UTCDelays in Datadog metric publishingresolvedminor27 min
2025-10-20 09:53 UTCElevated error rates with Dashboard and API due to AWS us-east-1 outageresolvedminor
2025-10-15 18:29 UTCsome databases stuck in reparentingresolvedmajor7 h 23 min
2025-10-07 22:04 UTCSSO Authentication Errorsresolvedmajor1 h 07 min
2025-10-01 15:10 UTCWe are investigating reports of connection issues with us-east-1resolvedminor4 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch PlanetScale with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "planetscale"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}