PlanetScale status history
Current state: operational — “All Systems Operational” per https://www.planetscalestatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do PlanetScale incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-05 18:39 UTC | Connectivity issues with Vitess databases in GCP | resolved | major | 14 min |
| 2026-09-02 16:34 UTC | Dashboard and API 500 errors for postgres databases | resolved | major | 10 min |
| 2026-07-24 14:41 UTC | Insights metrics underreporting | resolved | major | 3 h 00 min |
| 2026-07-20 18:29 UTC | Insights metrics underreporting | resolved | minor | 20 h 49 min |
| 2026-07-18 20:32 UTC | Connectivity issues in us-east-1 | resolved | major | 32 min |
| 2026-07-17 16:41 UTC | API and dashboard errors | resolved | major | 27 min |
| 2026-07-16 09:30 UTC | Single Sign On (SSO) unavailable | resolved | minor | 1 h 21 min |
| 2026-07-06 19:18 UTC | Development branches with MySQL Vectors not serving | resolved | minor | 2 h 26 min |
| 2026-05-14 20:30 UTC | 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. | resolved | major | 32 min |
| 2026-05-13 17:17 UTC | Database operations degraded in eu-west-2 | resolved | minor | 47 min |
| 2026-05-08 02:22 UTC | AWS use1-az4 thermal event | resolved | none | 16 h 59 min |
| 2026-04-08 00:34 UTC | Errors with database webhooks | resolved | minor | 15 min |
| 2026-04-02 22:37 UTC | Currently experiencing issues with creating/updating/deleting Vitess credentials | resolved | minor | 14 min |
| 2026-03-11 13:04 UTC | us-east-1 connection errors | resolved | major | 15 min |
| 2026-02-24 10:26 UTC | Vitess branch creation unavailable | resolved | major | 1 h 34 min |
| 2026-02-18 20:23 UTC | Vitess database availability issues in GCP northamerica-northeast1 | resolved | major | 42 min |
| 2026-01-31 09:38 UTC | Query insights outage | resolved | critical | 2 h 19 min |
| 2026-01-09 01:29 UTC | API availability issues | resolved | major | 16 min |
| 2026-01-08 16:30 UTC | Insights ingestion delayed | resolved | minor | 1 h 44 min |
| 2026-01-06 16:27 UTC | Errors with branch creation for GCP databases | resolved | major | 1 h 13 min |
| 2025-11-17 18:10 UTC | API and dashboard: 500 errors | resolved | major | — |
| 2025-10-20 16:09 UTC | Delays in Datadog metric publishing | resolved | minor | 27 min |
| 2025-10-20 09:53 UTC | Elevated error rates with Dashboard and API due to AWS us-east-1 outage | resolved | minor | — |
| 2025-10-15 18:29 UTC | some databases stuck in reparenting | resolved | major | 7 h 23 min |
| 2025-10-07 22:04 UTC | SSO Authentication Errors | resolved | major | 1 h 07 min |
| 2025-10-01 15:10 UTC | We are investigating reports of connection issues with us-east-1 | resolved | minor | 4 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
}