PlanetScale Outage History
PlanetScale is up right nowPingoru has recorded 28 incidents for PlanetScale: 25 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 0 of 720 (0%) |
| May 2026 | 3 | 18 of 744 (2%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 6 | 32 of 744 (4%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 3 | 2 of 720 (0%) |
| October 2026 | 3 | 3 of 744 (0%) |
| November 2026 | 0 | 0 of 75 (0%) |
Incidents, newest first
Major October 26, 2026 Problems with Vitess connectivity and credential changes 1h 15m Database Connectivity: Vitess (AWS) (sa-east-1 (Sao Paulo)), Database Connectivity: Vitess (GCP) (us-central1 (Iowa)), Database Connectivity: Vitess (GCP) (asia-northeast3 (Seoul)), Database Connectivity: Vitess (GCP) (us-east4 (Northern Virginia)) and 15 more
Started Oct 26, 2026, 09:28 PM UTC· resolved Oct 26, 2026, 10:43 PM UTC
- investigating Oct 26, 2026, 09:53 PM UTC
We are investigating internal and external reports of Vitess database connectivity problems for certain branches and long delays in credential changes (including creating new users/passwords) propagating into Vitess databases.
- monitoring Oct 26, 2026, 10:13 PM UTC
We've identified the resource exhaustion in credential distribution and are monitoring the restoration of service.
- resolved Oct 26, 2026, 11:31 PM UTC
We've observed service restored and successful credential changes across PlanetScale's environments.
Minor October 20, 2026 Gap in dashboard metrics for AWS us-east-1 1h 7m
Started Oct 20, 2026, 07:38 PM UTC· resolved Oct 20, 2026, 08:46 PM UTC
- monitoring Oct 20, 2026, 07:38 PM UTC
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.
- resolved Oct 20, 2026, 08:46 PM UTC
The issue has been resolved.
Major October 9, 2026 AWS us-east-1 connectivity failures 25m Database Connectivity: Postgres (AWS) (us-east-1 (Northern Virginia)), Database Connectivity: Vitess (AWS) (us-east-1 (Northern Virginia))
Started Oct 09, 2026, 10:53 PM UTC· resolved Oct 09, 2026, 11:19 PM UTC
- investigating Oct 09, 2026, 10:53 PM UTC
We are investigating reports of connectivity failures scoped to a single AZ in AWS us-east-1 causing replica delay and connectivity issues.
- monitoring Oct 09, 2026, 11:13 PM UTC
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.
- resolved Oct 09, 2026, 11:19 PM UTC
AWS us-east-1 cross-zone networking has fully recovered.
Minor September 28, 2026 Branch creation delays in GCP europe-west-1 2h 3m Database Operations
Started Sep 28, 2026, 06:59 PM UTC· resolved Sep 28, 2026, 09:02 PM UTC
- investigating Sep 28, 2026, 06:59 PM UTC
We have identified an issue and are investigating branch creation delays in GCP europe-west-1.
- identified Sep 28, 2026, 08:04 PM UTC
We have identified a problem relating to scheduling of database branches and are rolling out a mitigation.
- resolved Sep 28, 2026, 09:02 PM UTC
We have resolved the branch creation issue and no further impact is expected at this time.
Major September 5, 2026 Connectivity issues with Vitess databases in GCP 14m Database Connectivity: Vitess (GCP) (us-central1 (Iowa)), Database Connectivity: Vitess (GCP) (asia-northeast3 (Seoul)), Database Connectivity: Vitess (GCP) (us-east4 (Northern Virginia)), Database Connectivity: Vitess (GCP) (northamerica-northeast1 (Montréal)) and 3 more
Started Sep 05, 2026, 06:39 PM UTC· resolved Sep 05, 2026, 06:53 PM UTC
- investigating Sep 05, 2026, 06:39 PM UTC
We're currently experiencing issues with connectivity to Vitess databases in GCP. We're investigating the issue.
- monitoring Sep 05, 2026, 06:47 PM UTC
We've identified an issue in our networking and deployed mitigation. Connectivity is back to normal. We're continuing to monitor.
- resolved Sep 05, 2026, 06:53 PM UTC
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.
Major September 2, 2026 Dashboard and API 500 errors for postgres databases 7m Dashboard and API Requests
Started Sep 02, 2026, 04:17 PM UTC· resolved Sep 02, 2026, 04:24 PM UTC
- monitoring Sep 02, 2026, 04:34 PM UTC
For postgres databases, API requests and the dashboard were returning 500 errors. We've deployed a fix.
- resolved Sep 02, 2026, 04:44 PM UTC
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.
Major July 24, 2026 Insights metrics underreporting 6h 32m Query Insights
Started Jul 24, 2026, 02:41 PM UTC· resolved Jul 24, 2026, 09:13 PM UTC
- identified Jul 24, 2026, 02:41 PM 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.
- monitoring Jul 24, 2026, 05:04 PM UTC
Mitigations are in place and we're seeing signs of recovery. We continue to monitor the health of the system.
- resolved Jul 24, 2026, 05:42 PM UTC
The incident has been resolved.
Minor July 20, 2026 Insights metrics underreporting 20h 49m Query Insights
Started Jul 20, 2026, 06:29 PM UTC· resolved Jul 21, 2026, 03:18 PM UTC
- investigating Jul 20, 2026, 06:29 PM UTC
Insights metrics are underreporting for Postgres and Vitess databases. Database traffic and connectivity are unaffected. We are actively investigating the Insights issue.
- identified Jul 20, 2026, 07:00 PM UTC
We have identified the cause of reduced Query Insights metrics reporting and are working on remediations.
- identified Jul 20, 2026, 07:31 PM UTC
We are continuing to work towards remediation.
- identified Jul 20, 2026, 08:02 PM 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, 2026, 08:37 PM 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, 2026, 09:32 PM 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.
- monitoring Jul 20, 2026, 10:06 PM UTC
Query Insights is gradually recovering across all Postgres development branches.
- resolved Jul 21, 2026, 03:18 PM UTC
Query Insights functionality is restored on all Postgres development branches.
Major July 18, 2026 Connectivity issues in us-east-1 34m
Started Jul 18, 2026, 08:15 PM UTC· resolved Jul 18, 2026, 08:49 PM UTC
- investigating Jul 18, 2026, 08:32 PM UTC
We are observing connectivity issues on Postgres in the us-east-1 region. We are remediating.
- monitoring Jul 18, 2026, 08:49 PM 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.
- resolved Jul 18, 2026, 09:05 PM UTC
Connection issues have been resolved. If you experience any further issues, please contact our support team.
Major July 17, 2026 API and dashboard errors 24m Dashboard and API Requests
Started Jul 17, 2026, 04:35 PM UTC· resolved Jul 17, 2026, 04:59 PM UTC
- investigating Jul 17, 2026, 04:41 PM 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.
- identified Jul 17, 2026, 04:49 PM 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.
- monitoring Jul 17, 2026, 04:59 PM 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.
- resolved Jul 17, 2026, 05:09 PM UTC
API and dashboard service is restored.
Minor July 16, 2026 Single Sign On (SSO) unavailable 1h 21m Dashboard and API Requests
Started Jul 16, 2026, 09:30 AM UTC· resolved Jul 16, 2026, 10:52 AM UTC
- investigating Jul 16, 2026, 09:30 AM UTC
SSO login to the PlanetScale website and API is unavailable. We are investigating. Database operations are unaffected.
- resolved Jul 16, 2026, 10:52 AM UTC
The issue is resolved. SSO is working fine again.
Major July 6, 2026 Development branches with MySQL Vectors not serving 2h 26m
Started Jul 06, 2026, 07:18 PM UTC· resolved Jul 06, 2026, 09:45 PM UTC
- investigating Jul 06, 2026, 07:18 PM UTC
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.
- identified Jul 06, 2026, 07:23 PM UTC
We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.
- monitoring Jul 06, 2026, 08:38 PM UTC
Branches are recovering and we are monitoring the situation.
- resolved Jul 06, 2026, 09:45 PM UTC
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.
Major May 14, 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. 32m
Started May 14, 2026, 08:30 PM UTC· resolved May 14, 2026, 09:03 PM UTC
- investigating May 14, 2026, 08:30 PM UTC
A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters.
- identified May 14, 2026, 08:42 PM UTC
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.
- monitoring May 14, 2026, 08:51 PM UTC
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.
- resolved May 14, 2026, 09:03 PM UTC
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.
Major May 13, 2026 Database operations degraded in eu-west-2 15m Database Operations
Started May 13, 2026, 05:17 PM UTC· resolved May 13, 2026, 05:32 PM UTC
- investigating May 13, 2026, 05:17 PM UTC
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.
- monitoring May 13, 2026, 05:32 PM UTC
We've identified the issue and have taken steps to mitigate it. Database operations will successfully complete again. We continue to monitor the situation.
- resolved May 13, 2026, 06:04 PM UTC
PlanetScale has remediated the issue and it is fully resolved.
Minor May 8, 2026 AWS use1-az4 thermal event 16h 59m
Started May 08, 2026, 02:22 AM UTC· resolved May 08, 2026, 07:22 PM UTC
- monitoring May 08, 2026, 02:22 AM UTC
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.
- resolved May 08, 2026, 07:22 PM UTC
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.
Minor April 8, 2026 Errors with database webhooks 8m Dashboard and API Requests
Started Apr 08, 2026, 12:34 AM UTC· resolved Apr 08, 2026, 12:42 AM UTC
- investigating Apr 08, 2026, 12:34 AM UTC
We're investigating an issue with webhook deliveries failing.
- monitoring Apr 08, 2026, 12:42 AM UTC
We've made a fix and are seeing webhooks trigger properly again.
- resolved Apr 08, 2026, 12:49 AM UTC
The errors have been resolved.
Minor April 2, 2026 Currently experiencing issues with creating/updating/deleting Vitess credentials 14m Dashboard and API Requests
Started Apr 02, 2026, 10:37 PM UTC· resolved Apr 02, 2026, 10:52 PM UTC
- investigating Apr 02, 2026, 10:37 PM UTC
All existing credentials still work and will continue to work. We are investigating an issue affecting only modifying or creating new ones.
- monitoring Apr 02, 2026, 10:46 PM UTC
We have applied a fix and see recovery.
- resolved Apr 02, 2026, 10:52 PM UTC
Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.
Major March 11, 2026 us-east-1 connection errors 50m
Started Mar 11, 2026, 12:50 PM UTC· resolved Mar 11, 2026, 01:40 PM UTC
- identified Mar 11, 2026, 01:04 PM UTC
We're investigating an issue with connection errors to Vitess databases in us-east-1.
- resolved Mar 11, 2026, 01:19 PM UTC
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.
- monitoring Mar 11, 2026, 02:17 PM UTC
We're continuing to monitor. We've updated the status history to reflect the time periods where customers experienced connection issues.
- resolved Mar 11, 2026, 02:52 PM UTC
This incident has been resolved.
Major February 24, 2026 Vitess branch creation unavailable 2h 29m Database Operations
Started Feb 24, 2026, 09:31 AM UTC· resolved Feb 24, 2026, 12:00 PM UTC
- investigating Feb 24, 2026, 10:26 AM UTC
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.
- investigating Feb 24, 2026, 11:00 AM UTC
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.
- resolved Feb 24, 2026, 12:00 PM UTC
Vitess branch creation is available once again.
Major February 18, 2026 Vitess database availability issues in GCP northamerica-northeast1 20m
Started Feb 18, 2026, 08:23 PM UTC· resolved Feb 18, 2026, 08:43 PM UTC
- investigating Feb 18, 2026, 08:23 PM UTC
We are currently investigating impact.
- identified Feb 18, 2026, 08:34 PM UTC
We're working on a fix for the impacted databases.
- monitoring Feb 18, 2026, 08:43 PM UTC
Impacted databases are recovering, we're continuing to monitor.
- resolved Feb 18, 2026, 09:06 PM UTC
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.
Critical January 31, 2026 Query insights outage 2h 19m Query Insights
Started Jan 31, 2026, 09:38 AM UTC· resolved Jan 31, 2026, 11:58 AM UTC
- investigating Jan 31, 2026, 09:38 AM UTC
We are investigating an issue with Query Insights
- identified Jan 31, 2026, 10:08 AM UTC
There is an incident with a downstream provider. https://status.clickhouse.com/incidents/01KG9R4QYASZW9VXHG3S2YD4WD
- monitoring Jan 31, 2026, 11:06 AM UTC
Insights service is restored and we are blasting through the backlog of data.
- resolved Jan 31, 2026, 11:58 AM UTC
Query Insights is fully operational.
Major January 9, 2026 API availability issues 16m
Started Jan 09, 2026, 01:29 AM UTC· resolved Jan 09, 2026, 01:46 AM UTC
No vendor updates were posted for this incident.
Minor January 8, 2026 Insights ingestion delayed 1h 44m
Started Jan 08, 2026, 04:30 PM UTC· resolved Jan 08, 2026, 06:14 PM UTC
No vendor updates were posted for this incident.
Major January 6, 2026 Errors with branch creation for GCP databases 1h 13m
Started Jan 06, 2026, 04:27 PM UTC· resolved Jan 06, 2026, 05:41 PM UTC
No vendor updates were posted for this incident.
Major November 13, 2025 API and dashboard: 500 errors –
Started Nov 13, 2025, 06:45 PM UTC· resolved Nov 13, 2025, 06:45 PM UTC
No vendor updates were posted for this incident.