PlanetScale

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-10-20 19:38 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.

2. resolved 2026-10-20 20:46 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-10-09 22:53 UTC

   We are investigating reports of connectivity failures scoped to a single AZ in AWS us-east-1 causing replica delay and connectivity issues.

2. monitoring 2026-10-09 23:13 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.

3. resolved 2026-10-09 23:19 UTC

   AWS us-east-1 cross-zone networking has fully recovered.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-09-28 18:59 UTC

   We have identified an issue and are investigating branch creation delays in GCP europe-west-1.

2. identified 2026-09-28 20:04 UTC

   We have identified a problem relating to scheduling of database branches and are rolling out a mitigation.

3. resolved 2026-09-28 21:02 UTC

   We have resolved the branch creation issue and no further impact is expected at this time.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-09-05 18:39 UTC

   We're currently experiencing issues with connectivity to Vitess databases in GCP. We're investigating the issue.

2. monitoring 2026-09-05 18:47 UTC

   We've identified an issue in our networking and deployed mitigation. Connectivity is back to normal. We're continuing to monitor.

3. resolved 2026-09-05 18:53 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.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-02 16:34 UTC

   For postgres databases, API requests and the dashboard were returning 500 errors. We've deployed a fix.

2. resolved 2026-09-02 16:44 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.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-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.

2. monitoring 2026-07-24 17:04 UTC

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

3. resolved 2026-07-24 17:42 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-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.

2. identified 2026-07-20 19:00 UTC

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

3. identified 2026-07-20 19:31 UTC

   We are continuing to work towards remediation.

4. identified 2026-07-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.

5. identified 2026-07-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.

6. identified 2026-07-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.

7. monitoring 2026-07-20 22:06 UTC

   Query Insights is gradually recovering across all Postgres development branches.

8. resolved 2026-07-21 15:18 UTC

   Query Insights functionality is restored on all Postgres development branches.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-18 20:32 UTC

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

2. monitoring 2026-07-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.

3. resolved 2026-07-18 21:05 UTC

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

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-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.

2. identified 2026-07-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.

3. monitoring 2026-07-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.

4. resolved 2026-07-17 17:09 UTC

   API and dashboard service is restored.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 09:30 UTC

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

2. resolved 2026-07-16 10:52 UTC

   The issue is resolved. SSO is working fine again.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-06 19:18 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.

2. identified 2026-07-06 19:23 UTC

   We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.

3. monitoring 2026-07-06 20:38 UTC

   Branches are recovering and we are monitoring the situation.

4. resolved 2026-07-06 21:45 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...

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-05-14 20:30 UTC

   A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters.

2. identified 2026-05-14 20:42 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.

3. monitoring 2026-05-14 20:51 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.

4. resolved 2026-05-14 21:03 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.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 17:17 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.

2. monitoring 2026-05-13 17:32 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.

3. resolved 2026-05-13 18:04 UTC

   PlanetScale has remediated the issue and it is fully resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-05-08 02:22 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.

2. resolved 2026-05-08 19:22 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.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-08 00:34 UTC

   We're investigating an issue with webhook deliveries failing.

2. monitoring 2026-04-08 00:42 UTC

   We've made a fix and are seeing webhooks trigger properly again.

3. resolved 2026-04-08 00:49 UTC

   The errors have been resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-02 22:37 UTC

   All existing credentials still work and will continue to work. We are investigating an issue affecting only modifying or creating new ones.

2. monitoring 2026-04-02 22:46 UTC

   We have applied a fix and see recovery.

3. resolved 2026-04-02 22:52 UTC

   Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-03-11 13:04 UTC

   We're investigating an issue with connection errors to Vitess databases in us-east-1.

2. resolved 2026-03-11 13:19 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...

3. monitoring 2026-03-11 14:17 UTC

   We're continuing to monitor. We've updated the status history to reflect the time periods where customers experienced connection issues.

4. resolved 2026-03-11 14:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-24 10:26 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.

2. investigating 2026-02-24 11:00 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.

3. resolved 2026-02-24 12:00 UTC

   Vitess branch creation is available once again.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-02-18 20:23 UTC

   We are currently investigating impact.

2. identified 2026-02-18 20:34 UTC

   We're working on a fix for the impacted databases.

3. monitoring 2026-02-18 20:43 UTC

   Impacted databases are recovering, we're continuing to monitor.

4. resolved 2026-02-18 21:06 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.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-31 09:38 UTC

   We are investigating an issue with Query Insights

2. identified 2026-01-31 10:08 UTC

   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. monitoring 2026-01-31 11:06 UTC

   Insights service is restored and we are blasting through the backlog of data.

4. resolved 2026-01-31 11:58 UTC

   Query Insights is fully operational.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-09 01:29 UTC

   We are investigating internal errors on some API endpoints. Database connectivity is unaffected.

2. monitoring 2026-01-09 01:38 UTC

   A fix has been applied, and we are monitoring recovery.

3. resolved 2026-01-09 01:46 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-08 16:30 UTC

   Insights data ingestion is delayed. This underlying issue has identified and the Insights data backlog is being processed

2. resolved 2026-01-08 18:14 UTC

   Insights data ingestion encountered an error due to an unexpected data format. The issue was identified and fixed, and ingestion resumed.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-01-06 16:27 UTC

   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. identified 2026-01-06 17:12 UTC

   We're continuing to work on a fix and will share an update once it has been deployed.

3. monitoring 2026-01-06 17:37 UTC

   We've deployed a fix and are seeing error rates resolve.

4. resolved 2026-01-06 17:41 UTC

   This incident is resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-13 18:25 UTC

   The dashboard and API are currently returning 500 errors. We are rolling out a fix.

2. resolved 2025-11-13 18:45 UTC

   We've made a fix and the errors have resolved.

Excerpts are shortened. Read the full incident on PlanetScale's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-10-20 16:09 UTC

   During the ongoing incident, some branches are seeing delays in metrics via the Datadog integration.

2. resolved 2025-10-20 16:36 UTC

   Datadog metrics are back up-to-date.

Excerpts are shortened. Read the full incident on PlanetScale's status page.