Is PlanetScale Down?

PlanetScale: Operational

No, PlanetScale is up. All systems operational.

checked 47s ago·All Systems Operational·Official PlanetScale status page →

PlanetScale components

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

What is PlanetScale?

PlanetScale is a serverless database platform built on Vitess, the same technology that powers MySQL scaling at YouTube and other large internet properties. It provides MySQL-compatible databases with features such as branching, non-blocking schema changes, and automatic horizontal sharding. Developers and companies rely on PlanetScale as their primary relational data store for production applications, making availability directly tied to the functioning of their products.

Signs PlanetScale is having problems

  • Database connection attempts fail or time out, with drivers reporting errors such as "too many connections", "connection refused", or TLS handshake failures against the PlanetScale proxy endpoint.
  • Queries that normally return in milliseconds begin hanging or returning 503 / 504 errors, often surfacing as application-level 500 errors or slow API responses for end users.
  • The PlanetScale web console at app.planetscale.com becomes unreachable or shows errors when attempting to view branches, run queries in the query editor, or manage schema changes.
  • Deploy requests or schema change operations get stuck in a pending state or fail immediately, blocking teams from shipping database migrations.

Find out when your own services go down

You can check PlanetScale here — but a heartbeat monitor tells you the moment your API, website, or cron job stops responding, so you hear about your own downtime before your users do.

Frequently asked questions

How can I tell if PlanetScale is down?

The most direct way is to check the official status page at https://www.planetscalestatus.com, which lists the current status of the API, database connections, console, and other components. You can also look at your application logs for a spike in database connection errors or timeouts. Community discussion on platforms like X (Twitter) often surfaces widespread issues quickly as well.

Where is the official PlanetScale status page?

The official status page is at https://www.planetscalestatus.com. It is maintained by PlanetScale and shows real-time and historical incident information broken down by service component. You can subscribe to updates directly on that page to receive notifications when incidents are opened or resolved.

Is a database error in my app always caused by a PlanetScale outage?

Not necessarily. Database errors can originate from your application code, network connectivity between your servers and PlanetScale, misconfigured connection strings, exhausted connection limits on your plan, or expired credentials. Before concluding there is a platform outage, check your own logs and verify the issue is not isolated to your account or region. Cross-reference with https://www.planetscalestatus.com to confirm whether an incident has been declared.

How can I get alerted when my own services that depend on PlanetScale go down?

Beyond monitoring PlanetScale itself, you can set up a heartbeat monitor on your own application endpoints so you are notified the moment your service stops responding, regardless of the underlying cause. Tools like CronJobPro let you configure heartbeat checks that alert you immediately if your app goes silent, which is useful when any dependency including your database has a problem.

Not affiliated with or endorsed by PlanetScale. Status data is sourced from PlanetScale's official status page (www.planetscalestatus.com); for critical incidents, always verify at the official source. All trademarks are property of their respective owners.