PlanetScale Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live PlanetScale status100.00% uptime history

Every Recorded PlanetScale Incident

PlanetScale incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 9, 2026AWS us-east-1 connectivity failuresAWS us-east-1 cross-zone networking has fully recovered.25 minResolved
Sep 28, 2026Branch creation delays in GCP europe-west-1We have resolved the branch creation issue and no further impact is expected at this time.2h 3mResolved
Sep 5, 2026Connectivity issues with Vitess databases in GCPWe'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…14 minResolved
Sep 2, 2026Dashboard and API 500 errors for postgres databasesThe 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.10 minResolved
Jul 24, 2026Insights metrics underreportingThe incident has been resolved.3h 0mResolved
Jul 20, 2026Insights metrics underreportingQuery Insights functionality is restored on all Postgres development branches.20h 49mResolved
Jul 18, 2026Connectivity issues in us-east-1Connection issues have been resolved. If you experience any further issues, please contact our support team.32 minResolved
Jul 17, 2026API and dashboard errorsAPI and dashboard service is restored.27 minResolved
Jul 16, 2026Single Sign On (SSO) unavailableThe issue is resolved. SSO is working fine again.1h 21mResolved
Jul 6, 2026Development branches with MySQL Vectors not servingAll 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…2h 26mResolved
May 14, 2026There 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.The 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…32 minResolved
May 13, 2026Database operations degraded in eu-west-2PlanetScale has remediated the issue and it is fully resolved.47 minResolved
May 8, 2026AWS use1-az4 thermal eventPlanetScale 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.16h 59mResolved
Apr 8, 2026Errors with database webhooksThe errors have been resolved.15 minResolved
Apr 2, 2026Currently experiencing issues with creating/updating/deleting Vitess credentialsSome percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.14 minResolved
Mar 11, 2026us-east-1 connection errorsThis incident has been resolved.15 minResolved
Feb 24, 2026Vitess branch creation unavailableVitess branch creation is available once again.1h 34mResolved
Feb 18, 2026Vitess database availability issues in GCP northamerica-northeast1Problem 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…42 minResolved
Jan 31, 2026Query insights outageQuery Insights is fully operational.2h 19mResolved
Jan 9, 2026API availability issuesThe issue has been resolved.16 minResolved
Jan 8, 2026Insights ingestion delayedInsights data ingestion encountered an error due to an unexpected data format. The issue was identified and fixed, and ingestion resumed.1h 44mResolved
Jan 6, 2026Errors with branch creation for GCP databasesThis incident is resolved.1h 13mResolved
Nov 17, 2025API and dashboard: 500 errorsWe've made a fix and the errors have resolved.-5725 minResolved
Oct 20, 2025Delays in Datadog metric publishingDatadog metrics are back up-to-date.27 minResolved
Oct 20, 2025Elevated error rates with Dashboard and API due to AWS us-east-1 outagePlanetScale 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.-17 minResolved
Oct 15, 2025some databases stuck in reparentingNo further disruption is expected, please contact support with any further issues.7h 23mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next PlanetScale incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This PlanetScale Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before PlanetScale acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single PlanetScale outage in this window ran 20h 49m, against a mean recovery of 2h 45m. If you depend on PlanetScale in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.