PlanetScale Outage History

PlanetScale is up right now

PlanetScale had 21 outages in the last 2 years totaling 14h 12m of downtime — averaging 0.9 incidents per month.

There were 21 PlanetScale outages since July 14, 2025 totaling 14h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.planetscalestatus.com

Minor 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.

Detected by Pingoru
May 14, 2026, 09:03 PM UTC
Resolved
May 14, 2026, 09:03 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 14, 2026, 08:30 PM UTC

    Status: Investigating A high availability component that Postgres clusters depend on is restarting unexpectedly, triggering unplanned failovers in Postgres clusters. Affected components us-central1 (Iowa) (Partial outage)

  2. identified May 14, 2026, 08:42 PM UTC

    Status: 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. Affected components us-central1 (Iowa) (Partial outage)

  3. monitoring May 14, 2026, 08:51 PM UTC

    Status: 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. Affected components us-central1 (Iowa) (Partial outage)

  4. resolved May 14, 2026, 09:03 PM UTC

    Status: 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. Affected components us-central1 (Iowa) (Operational)

Read the full incident report →

Minor May 13, 2026

Database operations degraded in eu-west-2

Detected by Pingoru
May 13, 2026, 06:04 PM UTC
Resolved
May 13, 2026, 06:04 PM UTC
Duration
—
Affected: Database Operations
Timeline · 3 updates
  1. investigating May 13, 2026, 05:17 PM UTC

    Status: 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. Affected components Database Operations (Partial outage)

  2. monitoring May 13, 2026, 05:32 PM UTC

    Status: 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. Affected components Database Operations (Operational)

  3. resolved May 13, 2026, 06:04 PM UTC

    Status: Resolved PlanetScale has remediated the issue and it is fully resolved. Affected components Database Operations (Operational)

Read the full incident report →

Minor May 8, 2026

AWS use1-az4 thermal event

Detected by Pingoru
May 08, 2026, 07:22 PM UTC
Resolved
May 08, 2026, 07:22 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring May 08, 2026, 02:22 AM UTC

    Status: 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. resolved May 08, 2026, 07:22 PM UTC

    Status: 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.

Read the full incident report →

Minor April 8, 2026

Errors with database webhooks

Detected by Pingoru
Apr 08, 2026, 12:49 AM UTC
Resolved
Apr 08, 2026, 12:49 AM UTC
Duration
—
Affected: Dashboard and API Requests
Timeline · 3 updates
  1. investigating Apr 08, 2026, 12:34 AM UTC

    Status: Investigating We're investigating an issue with webhook deliveries failing. Affected components Dashboard and API Requests (Degraded performance)

  2. monitoring Apr 08, 2026, 12:42 AM UTC

    Status: Monitoring We've made a fix and are seeing webhooks trigger properly again. Affected components Dashboard and API Requests (Operational)

  3. resolved Apr 08, 2026, 12:49 AM UTC

    Status: Resolved The errors have been resolved. Affected components Dashboard and API Requests (Operational)

Read the full incident report →

Minor April 2, 2026

Currently experiencing issues with creating/updating/deleting Vitess credentials

Detected by Pingoru
Apr 02, 2026, 10:52 PM UTC
Resolved
Apr 02, 2026, 10:52 PM UTC
Duration
—
Affected: Dashboard and API Requests
Timeline · 3 updates
  1. investigating Apr 02, 2026, 10:37 PM UTC

    Status: Investigating All existing credentials still work and will continue to work. We are investigating an issue affecting only modifying or creating new ones. Affected components Dashboard and API Requests (Degraded performance)

  2. monitoring Apr 02, 2026, 10:46 PM UTC

    Status: Monitoring We have applied a fix and see recovery. Affected components Dashboard and API Requests (Degraded performance)

  3. resolved Apr 02, 2026, 10:52 PM UTC

    Status: Resolved Some percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes. Affected components Dashboard and API Requests (Operational)

Read the full incident report →

Minor March 11, 2026

us-east-1 connection errors

Detected by Pingoru
Mar 11, 2026, 02:52 PM UTC
Resolved
Mar 11, 2026, 02:52 PM UTC
Duration
—
Timeline · 4 updates
  1. identified Mar 11, 2026, 01:04 PM UTC

    Status: Identified We're investigating an issue with connection errors to Vitess databases in us-east-1. Affected components us-east-2 (Ohio) (Degraded performance)

  2. resolved Mar 11, 2026, 01:19 PM UTC

    Status: 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. Affected components us-east-2 (Ohio) (Operational)

  3. monitoring Mar 11, 2026, 02:17 PM UTC

    Status: Monitoring We're continuing to monitor. We've updated the status history to reflect the time periods where customers experienced connection issues. Affected components us-east-1 (Northern Virginia) (Operational) us-east-2 (Ohio) (Operational)

  4. resolved Mar 11, 2026, 02:52 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Northern Virginia) (Operational) us-east-2 (Ohio) (Operational)

Read the full incident report →

Minor February 24, 2026

Vitess branch creation unavailable

Detected by Pingoru
Feb 24, 2026, 12:00 PM UTC
Resolved
Feb 24, 2026, 12:00 PM UTC
Duration
—
Affected: Database Operations
Timeline · 3 updates
  1. investigating Feb 24, 2026, 10:26 AM UTC

    Status: 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. Affected components Dashboard and API Requests (Degraded performance)

  2. investigating Feb 24, 2026, 11:00 AM UTC

    Status: 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. Affected components Dashboard and API Requests (Degraded performance)

  3. resolved Feb 24, 2026, 12:00 PM UTC

    Status: Resolved Vitess branch creation is available once again. Affected components Database Operations (Operational)

Read the full incident report →

Minor February 18, 2026

Vitess database availability issues in GCP northamerica-northeast1

Detected by Pingoru
Feb 18, 2026, 09:06 PM UTC
Resolved
Feb 18, 2026, 09:06 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Feb 18, 2026, 08:23 PM UTC

    Status: Investigating We are currently investigating impact. Affected components northamerica-northeast1 (Montréal) (Partial outage)

  2. identified Feb 18, 2026, 08:34 PM UTC

    Status: Identified We're working on a fix for the impacted databases. Affected components northamerica-northeast1 (Montréal) (Partial outage)

  3. monitoring Feb 18, 2026, 08:43 PM UTC

    Status: Monitoring Impacted databases are recovering, we're continuing to monitor. Affected components northamerica-northeast1 (Montréal) (Operational)

  4. resolved Feb 18, 2026, 09:06 PM UTC

    Status: 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. Affected components northamerica-northeast1 (Montréal) (Operational)

Read the full incident report →

Minor January 31, 2026

Query insights outage

Detected by Pingoru
Jan 31, 2026, 11:58 AM UTC
Resolved
Jan 31, 2026, 11:58 AM UTC
Duration
—
Affected: Query Insights
Timeline · 4 updates
  1. investigating Jan 31, 2026, 09:38 AM UTC

    Status: Investigating We are investigating an issue with Query Insights Affected components Query Insights (Full outage)

  2. identified Jan 31, 2026, 10:08 AM UTC

    Status: Identified There is an incident with a downstream provider. https://status.clickhouse.com/incidents/01KG9R4QYASZW9VXHG3S2YD4WD Affected components Query Insights (Full outage)

  3. monitoring Jan 31, 2026, 11:06 AM UTC

    Status: Monitoring Insights service is restored and we are blasting through the backlog of data. Affected components Query Insights (Partial outage)

  4. resolved Jan 31, 2026, 11:58 AM UTC

    Status: Resolved Query Insights is fully operational. Affected components Query Insights (Operational)

Read the full incident report →