Databases / Postgres and MySQL / PlanetScale

PlanetScale

OPERATIONAL

Since Oct 2025 · 25 incidents · www.planetscalestatus.com · checked just now

CompareStatus page
GradeALast 90 days
A+PRODA+SHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade A
IncidentsEverything posted on the status page except scheduled maintenance.
50 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
26m
LongestLongest single incident, start to resolved.
2h 03m
Since lastTime since the last counted incident was resolved.
46h 35m

By area

A+Production
2INCIDENTS
40mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Oct 9, 2026 · 26mAWS us-east-1 connectivity failures
SEV 2Sep 5, 2026 · 14mConnectivity issues with Vitess databases in GCP
Worse. 5 in the last 6 months, 4 in the 6 before.
A+Shipping
2INCIDENTS
2h 14mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Sep 28, 2026 · 2h 03mBranch creation delays in GCP europe-west-1
SEV 3Sep 2, 2026 · 10mDashboard and API 500 errors for postgres databases
Worse. 6 in the last 6 months, 4 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production database, per month10 GB of data, about 1 GB of RAM on all month, 10M queries a month, one region, no replicas, commercial use. Cheapest plan that runs it.
Postgres PS-10, single node0 of 4 cheaper
BEST VALUE$10/mo
PS-10 arm64 (1 GiB RAM, 10 GB storage included)$10

Single node has no replicas; the HA version is $30. planetscale.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 14 in the last 6 months, 10 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down2
Sev 3 · Can't shipCan't deploy, build or manage it2
Sev 4 · PapercutDocs, status page, slow dashboard1

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
3.3Last 12 months
Update gapMedian time between status page updates during an incident.
24mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 9Sev 1–2

Incident history

Oct 20, 20261h 08mSEV 4
Gap in dashboard metrics for AWS us-east-1Dashboard metrics for databases in AWS us-east-1 were delayed or missing for about 10 minutes; queries and data were unaffected.AI-graded · regional
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · REGIONAL · HIGH CONFIDENCE
    Dashboard metrics for databases in AWS us-east-1 were delayed or missing for about 10 minutes; queries and data were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 19:38 UTC · monitoring
    From 19:20 - 19:30 UTC we had a delay with metrics in AWS us-east-1. For databases in this region you may see missing metrics in the dashboard. We've made a fix and are seeing metrics recover.
  2. 20:46 UTC · resolved
    The issue has been resolved.
Source
Oct 9, 202626mSEV 2
AWS us-east-1 connectivity failuresConnectivity failures in one AWS us-east-1 availability zone caused replica delay and connection issues for a small number of branches for about 26 minutes.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Connectivity failures in one AWS us-east-1 availability zone caused replica delay and connection issues for a small number of branches for about 26 minutes.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 22:53 UTC · investigating
    We are investigating reports of connectivity failures scoped to a single AZ in AWS us-east-1 causing replica delay and connectivity issues.
  2. 23:13 UTC · monitoring
    A small number of database branches in AWS us-east-1 were impacted by cross-zone networking issues, for which the impact window has ended. If you continue to see impact, please reach out to PlanetScale support.
  3. 23:19 UTC · resolved
    AWS us-east-1 cross-zone networking has fully recovered.
Source
Sep 28, 20262h 03mSEV 3
Branch creation delays in GCP europe-west-1Database branch creation was delayed in GCP europe-west-1 for about two hours; the text does not describe serving impact.AI-graded · regional
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Database branch creation was delayed in GCP europe-west-1 for about two hours; the text does not describe serving impact.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:59 UTC · investigating
    We have identified an issue and are investigating branch creation delays in GCP europe-west-1.
  2. 20:04 UTC · identified
    We have identified a problem relating to scheduling of database branches and are rolling out a mitigation.
  3. 21:02 UTC · resolved
    We have resolved the branch creation issue and no further impact is expected at this time.
Source
Sep 5, 202614mSEV 2
Connectivity issues with Vitess databases in GCPConnectivity to Vitess databases in GCP was disrupted for about 15 minutes before mitigation; scope beyond GCP-hosted databases is not stated.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Connectivity to Vitess databases in GCP was disrupted for about 15 minutes before mitigation; scope beyond GCP-hosted databases is not stated.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:39 UTC · investigating
    We're currently experiencing issues with connectivity to Vitess databases in GCP. We're investigating the issue.
  2. 18:47 UTC · monitoring
    We've identified an issue in our networking and deployed mitigation. Connectivity is back to normal. We're continuing to monitor.
  3. 18:53 UTC · resolved
    We'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.
Source
Sep 2, 202610mSEV 3
Dashboard and API 500 errors for postgres databasesSev 3 from the incident title (no components listed)
2 updates
  1. 16:34 UTC · monitoring
    For postgres databases, API requests and the dashboard were returning 500 errors. We've deployed a fix.
  2. 16:44 UTC · resolved
    The 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.
Source
Jul 24, 20263h 00mSEV 4
Insights metrics underreportingSev 4 from the incident title (no components listed)
3 updates
  1. 14:41 UTC · 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.
  2. 17:04 UTC · monitoring
    Mitigations are in place and we're seeing signs of recovery. We continue to monitor the health of the system.
  3. 17:42 UTC · resolved
    The incident has been resolved.
Source
Jul 20, 202620h 49mSEV 4
Insights metrics underreportingSev 4 from the incident title (no components listed)
8 updates
  1. 18:29 UTC · investigating
    Insights metrics are underreporting for Postgres and Vitess databases. Database traffic and connectivity are unaffected. We are actively investigating the Insights issue.
  2. 19:00 UTC · identified
    We have identified the cause of reduced Query Insights metrics reporting and are working on remediations.
  3. 19:31 UTC · identified
    We are continuing to work towards remediation.
  4. 20:02 UTC · 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.
  5. 20:37 UTC · 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.
  6. 21:32 UTC · 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.
  7. 22:06 UTC · monitoring
    Query Insights is gradually recovering across all Postgres development branches.
  8. 15:18 UTC · resolved
    Query Insights functionality is restored on all Postgres development branches.
Source
Jul 18, 202633mSEV 1
Connectivity issues in us-east-1Sev 1 from the incident title (no components listed)
3 updates
  1. 20:32 UTC · investigating
    We are observing connectivity issues on Postgres in the us-east-1 region. We are remediating.
  2. 20:49 UTC · 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.
  3. 21:05 UTC · resolved
    Connection issues have been resolved. If you experience any further issues, please contact our support team.
Source
Jul 17, 202628mSEV 3
API and dashboard errorsSev 3 from the incident title (no components listed)
4 updates
  1. 16:41 UTC · 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.
  2. 16:49 UTC · 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.
  3. 16:59 UTC · 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.
  4. 17:09 UTC · resolved
    API and dashboard service is restored.
Source
Jul 16, 20261h 21mSEV 2
Single Sign On (SSO) unavailableSev 2 from the incident title (no components listed)
2 updates
  1. 09:30 UTC · investigating
    SSO login to the PlanetScale website and API is unavailable. We are investigating. Database operations are unaffected.
  2. 10:52 UTC · resolved
    The issue is resolved. SSO is working fine again.
Source
Jul 6, 20262h 27mSEV 3
Development branches with MySQL Vectors not servingSev 3 from the incident title (no components listed)
4 updates
  1. 19:18 UTC · 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.
  2. 19:23 UTC · identified
    We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.
  3. 20:38 UTC · monitoring
    Branches are recovering and we are monitoring the situation.
  4. 21:45 UTC · resolved
    All 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.
Source
May 14, 202632mSEV 3
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.Sev 3 from the incident title (no components listed)
4 updates
  1. 20:30 UTC · investigating
    A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters.
  2. 20:42 UTC · identified
    We have identified the likely cause of unexpected restarts to the high availability component used by Postgres clusters, and are applying changes to prevent recurrences.
  3. 20:51 UTC · monitoring
    We applied changes to prevent unexpected restarts of the high availability component shared by Postgres clusters. We have not seen further restarts of this component nor unplanned Postgres failovers since applying these changes. We are actively monitoring the situation.
  4. 21:03 UTC · resolved
    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 in Postgres clusters since applying these changes.
Source
May 13, 202648mSEV 3
Database operations degraded in eu-west-2Sev 3 from the incident title (no components listed)
3 updates
  1. 17:17 UTC · investigating
    We're aware of a degradation in eu-west-2 where database operations such as resizes, branch creations or parameter changes may not complete. We're investigating the problem.
  2. 17:32 UTC · monitoring
    We've identified the issue and have taken steps to mitigate it. Database operations will successfully complete again. We continue to monitor the situation.
  3. 18:04 UTC · resolved
    PlanetScale has remediated the issue and it is fully resolved.
Source
May 8, 202617h 00mSEV 2
AWS use1-az4 thermal eventSev 2 from the incident title (no components listed)
2 updates
  1. 02:22 UTC · monitoring
    PlanetScale is aware of the AWS use1-az4 thermal event. We expect databases to be unaffected. Please contact support if you have any questions or notice any disruption.
  2. 19:22 UTC · resolved
    PlanetScale 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.
Source
Apr 8, 202615mSEV 3
Errors with database webhooksSev 3 from the incident title (no components listed)
3 updates
  1. 00:34 UTC · investigating
    We're investigating an issue with webhook deliveries failing.
  2. 00:42 UTC · monitoring
    We've made a fix and are seeing webhooks trigger properly again.
  3. 00:49 UTC · resolved
    The errors have been resolved.
Source
Apr 2, 202615mSEV 1 · SECURITY
Currently experiencing issues with creating/updating/deleting Vitess credentialsSev 2 from the incident title (no components listed), raised to Sev 1 for security
3 updates
  1. 22:37 UTC · investigating
    All existing credentials still work and will continue to work. We are investigating an issue affecting only modifying or creating new ones.
  2. 22:46 UTC · monitoring
    We have applied a fix and see recovery.
  3. 22:52 UTC · resolved
    Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.
Source
Mar 11, 202615mSEV 1
us-east-1 connection errorsSev 1 from the incident title (no components listed)
4 updates
  1. 13:04 UTC · identified
    We're investigating an issue with connection errors to Vitess databases in us-east-1.
  2. 13:19 UTC · resolved
    At **12:51 PM UTC** and **1:38 PM UTC** some Vitess databases in us-east-1 were impacted by connection errors for approximately 5 minutes due to an issue in our edge network. We resolved the issue and are no longer seeing errors. We will be taking action to protect customers from this issue happening again in the future and apologize for the error.
  3. 14:17 UTC · monitoring
    We're continuing to monitor. We've updated the status history to reflect the time periods where customers experienced connection issues.
  4. 14:52 UTC · resolved
    This incident has been resolved.
Source
Feb 24, 20261h 34mSEV 3
Vitess branch creation unavailableSev 3 from the incident title (no components listed)
3 updates
  1. 10:26 UTC · investigating
    New Vitess databases are being accepted by the PlanetScale API but we are unable to provision the infrastructure to serve them. We've confirmed this impact and are investigating the cause. We will provide further updates by 11:00 UTC.
  2. 11:00 UTC · investigating
    We're rolling out a mitigation now that will allow Vitess branch creation to succeed while we continue to investigate. No database operations or anything about Postgres database creation are impacted. Next update by 12:00 UTC.
  3. 12:00 UTC · resolved
    Vitess branch creation is available once again.
Source
Feb 18, 202643mSEV 1
Vitess database availability issues in GCP northamerica-northeast1Sev 1 from the incident title (no components listed)
4 updates
  1. 20:23 UTC · investigating
    We are currently investigating impact.
  2. 20:34 UTC · identified
    We're working on a fix for the impacted databases.
  3. 20:43 UTC · monitoring
    Impacted databases are recovering, we're continuing to monitor.
  4. 21:06 UTC · resolved
    Problem 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.
Source
Jan 31, 20262h 19mSEV 4
Query insights outageSev 4 from the incident title (no components listed)
4 updates
  1. 09:38 UTC · investigating
    We are investigating an issue with Query Insights
  2. 10:08 UTC · identified
    There is an incident with a downstream provider. [https://status.clickhouse.com/incidents/01KG9R4QYASZW9VXHG3S2YD4WD](https://status.clickhouse.com/incidents/01KG9R4QYASZW9VXHG3S2YD4WD "https://status.clickhouse.com/incidents/01KG9R4QYASZW9VXHG3S2YD4WD")
  3. 11:06 UTC · monitoring
    Insights service is restored and we are blasting through the backlog of data.
  4. 11:58 UTC · resolved
    Query Insights is fully operational.
Source
Jan 9, 202617mSEV 1
API availability issuesSev 1 from the incident title (no components listed)
3 updates
  1. 01:29 UTC · investigating
    We are investigating internal errors on some API endpoints. Database connectivity is unaffected.
  2. 01:38 UTC · monitoring
    A fix has been applied, and we are monitoring recovery.
  3. 01:46 UTC · resolved
    The issue has been resolved.
Source
Jan 8, 20261h 44mSEV 4
Insights ingestion delayedSev 4 from the incident title (no components listed)
2 updates
  1. 16:30 UTC · identified
    Insights data ingestion is delayed. This underlying issue has identified and the Insights data backlog is being processed
  2. 18:14 UTC · resolved
    Insights data ingestion encountered an error due to an unexpected data format. The issue was identified and fixed, and ingestion resumed.
Source
Jan 6, 20261h 14mSEV 3
Errors with branch creation for GCP databasesSev 3 from the incident title (no components listed)
4 updates
  1. 16:27 UTC · investigating
    We're aware of an issue impacting new branch creation, deploy requests and cluster size changes for Vitess databases deployed to GCP. We are working on a fix.
  2. 17:12 UTC · identified
    We're continuing to work on a fix and will share an update once it has been deployed.
  3. 17:37 UTC · monitoring
    We've deployed a fix and are seeing error rates resolve.
  4. 17:41 UTC · resolved
    This incident is resolved.
Source
Nov 17, 20250mSEV 3
API and dashboard: 500 errorsSev 3 from the incident title (no components listed)
2 updates
  1. 18:25 UTC · identified
    The dashboard and API are currently returning 500 errors. We are rolling out a fix.
  2. 18:45 UTC · resolved
    We've made a fix and the errors have resolved.
Source
Oct 20, 202527mSEV 2
Delays in Datadog metric publishingSev 2 from the incident title (no components listed)
2 updates
  1. 16:09 UTC · monitoring
    During the ongoing incident, some branches are seeing delays in metrics via the Datadog integration.
  2. 16:36 UTC · resolved
    Datadog metrics are back up-to-date.
Source

Peers, 90 days

Compare
UpstashGrade A+100.00% up4 incidentsMTTR 0m~$22.25/moPlanetScaleGrade A100.00% up5 incidentsMTTR 26m$10/moCockroachDB CloudGrade B100.00% up5 incidentsMTTR 7h 00m–/moMongoDB AtlasGrade D100.00% up18 incidentsMTTR 2h 35m$56.94/moSupabaseGrade F100.00% up26 incidentsMTTR 2h 00m$25.25/mo

README badge

PlanetScale's live grade, for your README.

PlanetScale grade badge
[![planetscale on downagain.dev](https://downagain.dev/badge/planetscale.svg)](https://downagain.dev/p/planetscale)