https://approjects-vendor-status-watch.static.hf.space/v/planetscale.htmlIncidents from PlanetScale's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://www.planetscalestatus.complanetscale:2026-09-05T18:39:42ZSat, 05 Sep 2026 18:39:42 +0000We've identified an issue with database connectivity for Vitess databases in GCP. We've taken steps to resolve the issue and are making immediate improvements to address root-causes and detection. Databases connectivity is now restored.https://www.planetscalestatus.complanetscale:2026-09-02T16:34:16ZWed, 02 Sep 2026 16:34:16 +0000The incident has been resolved. Between 12:17 and 12:24 UTC, the dashboard and API were returning 500 errors for postgres database management pages and API endpoints.https://www.planetscalestatus.complanetscale:2026-07-24T14:41:44ZFri, 24 Jul 2026 14:41:44 +0000The incident has been resolved.https://www.planetscalestatus.complanetscale:2026-07-20T18:29:38ZMon, 20 Jul 2026 18:29:38 +0000Query Insights functionality is restored on all Postgres development branches. https://www.planetscalestatus.complanetscale:2026-07-18T20:32:44ZSat, 18 Jul 2026 20:32:44 +0000Connection issues have been resolved. If you experience any further issues, please contact our support team.https://www.planetscalestatus.complanetscale:2026-07-17T16:41:49ZFri, 17 Jul 2026 16:41:49 +0000API and dashboard service is restored.https://www.planetscalestatus.complanetscale:2026-07-16T09:30:45ZThu, 16 Jul 2026 09:30:45 +0000The issue is resolved. SSO is working fine again.https://www.planetscalestatus.complanetscale:2026-07-06T19:18:34ZMon, 06 Jul 2026 19:18:34 +0000All impacted branches are recovered. PlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. A bug in the 8.4.x version of our Vectors builds resulted in the upgrade immediately failing on startup. Because Vitess development branches only have one instance - the primary - impacted development branches did not have a primary during the impact window. The incident was resolved by reverting impacted branches to their previous MySQL version. PlanetScale will fix the bug in the MySQL Vectors 8.4.x build before re-attempting the upgrade at a later date.https://www.planetscalestatus.complanetscale:2026-05-14T20:30:55ZThu, 14 May 2026 20:30:55 +0000The 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. https://www.planetscalestatus.complanetscale:2026-05-13T17:17:04ZWed, 13 May 2026 17:17:04 +0000PlanetScale has remediated the issue and it is fully resolved.https://www.planetscalestatus.complanetscale:2026-05-08T02:22:38ZFri, 08 May 2026 02:22:38 +0000PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.https://www.planetscalestatus.complanetscale:2026-04-08T00:34:35ZWed, 08 Apr 2026 00:34:35 +0000The errors have been resolved.https://www.planetscalestatus.complanetscale:2026-04-02T22:37:39ZThu, 02 Apr 2026 22:37:39 +0000Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.https://www.planetscalestatus.complanetscale:2026-03-11T13:04:02ZWed, 11 Mar 2026 13:04:02 +0000This incident has been resolved.https://www.planetscalestatus.complanetscale:2026-02-24T10:26:20ZTue, 24 Feb 2026 10:26:20 +0000Vitess branch creation is available once again.https://www.planetscalestatus.complanetscale:2026-02-18T20:23:32ZWed, 18 Feb 2026 20:23:32 +0000Problem has been resolved. We saw three nodes fail across three availability zones simultaneously. Impacting databases hosted on those nodes. All databases have been moved to healthy nodes and we're investigating how we can further reduce impact from similar events in the future.https://www.planetscalestatus.complanetscale:2026-01-31T09:38:50ZSat, 31 Jan 2026 09:38:50 +0000Query Insights is fully operational.https://www.planetscalestatus.complanetscale:2026-01-09T01:29:20ZFri, 09 Jan 2026 01:29:20 +0000The issue has been resolved.https://www.planetscalestatus.complanetscale:2026-01-08T16:30:19ZThu, 08 Jan 2026 16:30:19 +0000Insights data ingestion encountered an error due to an unexpected data format. The issue was identified and fixed, and ingestion resumed.https://www.planetscalestatus.complanetscale:2026-01-06T16:27:46ZTue, 06 Jan 2026 16:27:46 +0000This incident is resolved.https://www.planetscalestatus.complanetscale:2025-11-17T18:10:21ZMon, 17 Nov 2025 18:10:21 +0000We've made a fix and the errors have resolved.https://www.planetscalestatus.complanetscale:2025-10-20T16:09:10ZMon, 20 Oct 2025 16:09:10 +0000Datadog metrics are back up-to-date.https://www.planetscalestatus.complanetscale:2025-10-20T09:53:18ZMon, 20 Oct 2025 09:53:18 +0000PlanetScale is continuing to monitor the condition of AWS us-east-1. At this point we do not see any further impact, and have re-enabled database and branch creation in the region. https://www.planetscalestatus.complanetscale:2025-10-15T18:29:33ZWed, 15 Oct 2025 18:29:33 +0000No further disruption is expected, please contact support with any further issues.https://www.planetscalestatus.complanetscale:2025-10-07T22:04:12ZTue, 07 Oct 2025 22:04:12 +0000We've resolved the issue. SSO/SAML is working again.https://www.planetscalestatus.complanetscale:2025-10-01T15:10:50ZWed, 01 Oct 2025 15:10:50 +0000All systems operating normally