New Multi-region uptime checks and custom-domain status pages

PlanetScale Outage History

Daily provider-status observations and published incident history for PlanetScale.

Operational

PlanetScale is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow PlanetScale for future changes.

96.6% of 58 verified observed days had no reported provider issue

90-Day Trend

Jul 24Oct 21

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 96.7% 30 1

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

11 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

July 2026
Insights metrics underreporting
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Mitigations are in place and we're seeing signs of recovery. We continue to monitor the health of the system.
identified
Insights metrics are underreporting for Postgres and Vitess databases. Database traffic and connectivity are unaffected. We are actively investigating the issue and are deploying mitigations.
Insights metrics underreporting
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Query Insights is gradually recovering across all Postgres development branches.
identified
Query Insights is recovered across all branches except for Postgres development branches, where recovery is happening gradually. We are working to accelerate recovery of Query Insights Postgres development branches.
identified
We are seeing recovery of Query Insights across all branches, except for Postgres development branches which where we disabled Query Insights to relieve pressure on an overloaded component. We are working to restore Query Insights to development branches as quickly as possible.
identified
We have temporarily disabled Query Insights in Postgres development branches to relieve an overloaded component in the Query Insights processing pipeline. We are working to restore Query Insights to all branches as quickly as possible.
identified
We are continuing to work towards remediation.
identified
We have identified the cause of reduced Query Insights metrics reporting and are working on remediations.
investigating
Insights metrics are underreporting for Postgres and Vitess databases. Database traffic and connectivity are unaffected. We are actively investigating the Insights issue.
Connectivity issues in us-east-1
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We remediated the issue, and clients can now connect to their database branches in us-east-1 normally. We will continue monitoring the situation.
investigating
We are observing connectivity issues on Postgres in the us-east-1 region. We are remediating.
API and dashboard errors
major Source not attested
Last archived state: resolved
View archived record details
monitoring
We have increased the memory available to the API and are monitoring the performance and stability of the API and dashboard to confirm service is restored.
identified
We have identified the cause of the errors - a pattern of requests causing the application to run out of memory and crash - and are working to better handle this traffic pattern now.
investigating
We are aware that both our API and dashboard are returning errors. We are investigating the cause and will restore service as soon as possible.
Single Sign On (SSO) unavailable
minor Source not attested
Last archived state: resolved
View archived record details
investigating
SSO login to the PlanetScale website and API is unavailable. We are investigating. Database operations are unaffected.
Development branches with MySQL Vectors not serving
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Branches are recovering and we are monitoring the situation.
identified
We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.
investigating
PlanetScale initiated a system wide upgrade of branches with Vectors enabled and running on MySQL 8.0 to MySQL 8.4. A number of development branches were disrupted and have not yet recovered. We are investigating and remediating.
May 2026
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.
major Source not attested
Last archived state: resolved
View archived record details
monitoring
identified
investigating
Database operations degraded in eu-west-2
major Source not attested
Last archived state: resolved
View archived record details
monitoring
investigating
AWS use1-az4 thermal event
Source not attested
Last archived state: resolved
View archived record details
monitoring
April 2026
Errors with database webhooks
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
investigating