All Providers

PlanetScale

Operational

25components tracked.· Official status page

us-east-1 (Northern Virginia) Operational
oldest now
us-east-2 (Ohio) Operational
oldest now
us-west-2 (Oregon) Operational
oldest now
ap-northeast-1 (Tokyo) Operational
oldest now
ap-south-1 (Mumbai) Operational
oldest now
ap-southeast-1 (Singapore) Operational
oldest now
ap-southeast-2 (Sydney) Operational
oldest now
ca-central-1 (Montreal) Operational
oldest now
eu-central-1 (Frankfurt) Operational
oldest now
eu-west-1 (Dublin) Operational
oldest now
sa-east-1 (Sao Paulo) Operational
oldest now
us-east4 (Northern Virginia) Operational
oldest now
asia-northeast3 (Seoul) Operational
oldest now
ap-southeast-2 (Sydney) Operational
oldest now
ca-central-1 (Montreal) Operational
oldest now
us-central1 (Iowa) Operational
oldest now
us-east-2 (Ohio) Operational
oldest now
ap-south-1 (Mumbai) Operational
oldest now
ap-northeast-1 (Tokyo) Operational
oldest now
sa-east-1 (Sao Paulo) Operational
oldest now
ap-southeast-1 (Singapore) Operational
oldest now
ap-southeast-2 (Sydney) Operational
oldest now
us-west-2 (Oregon) Operational
oldest now
us-central1 (Iowa) Operational
oldest now
northamerica-northeast1 (Montréal) Operational
oldest now

Recent Incidents

Insights metrics underreportingmajor
Jan 1, 00:00 UTC — resolved 17:42
resolved Jul 24, 21:13 UTC

The incident has been resolved.

monitoring Jul 24, 17:04 UTC

Mitigations are in place and we're seeing signs of recovery. We continue to monitor the health of the system.

identified Jul 24, 14:41 UTC

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 underreportingminor
Jan 1, 00:00 UTC — resolved 15:18
resolved Jul 21, 15:18 UTC

Query Insights functionality is restored on all Postgres development branches.

monitoring Jul 20, 22:06 UTC

Query Insights is gradually recovering across all Postgres development branches.

identified Jul 20, 21:32 UTC

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 Jul 20, 20:37 UTC

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 Jul 20, 20:02 UTC

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 Jul 20, 19:31 UTC

We are continuing to work towards remediation.

identified Jul 20, 19:00 UTC

We have identified the cause of reduced Query Insights metrics reporting and are working on remediations.

investigating Jul 20, 18:29 UTC

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-1major
Jan 1, 00:00 UTC — resolved 21:05
resolved Jul 18, 21:05 UTC

Connection issues have been resolved. If you experience any further issues, please contact our support team.

monitoring Jul 18, 20:49 UTC

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 Jul 18, 20:32 UTC

We are observing connectivity issues on Postgres in the us-east-1 region. We are remediating.

API and dashboard errorsmajor
Jan 1, 00:00 UTC — resolved 17:09
resolved Jul 17, 17:09 UTC

API and dashboard service is restored.

monitoring Jul 17, 16:59 UTC

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 Jul 17, 16:49 UTC

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 Jul 17, 16:41 UTC

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) unavailableminor
Jan 1, 00:00 UTC — resolved 10:52
resolved Jul 16, 10:52 UTC

The issue is resolved. SSO is working fine again.

investigating Jul 16, 09:30 UTC

SSO login to the PlanetScale website and API is unavailable. We are investigating. Database operations are unaffected.

Refreshes every 30s. Last updated: 14:58:38