PlanetScale statusLiveFetched seconds agoSource: planetscalestatus.com
Is PlanetScale down?
Live status check · All systems operational
Live status pulled from planetscalestatus.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About PlanetScale status
PlanetScale runs serverless MySQL (Vitess) and serverless Postgres (Neki). Incidents are usually regional and scoped to one component — the data plane, the control plane (deploys, branches), or the Console. The data plane stays available across most control-plane blips.
Components and surfaces that can break
- Surface 01
Database endpoints (MySQL and Postgres, per region).
- Surface 02
Branches, deploy requests, the Console.
- Surface 03
Boost (query cache), Insights, the PlanetScale CLI.
What to do if PlanetScale is actually down
Check whether it's data plane or control plane
planetscalestatus.com splits these. Data plane red = your live queries are failing. Control plane red = you can't ship a schema change but production traffic is still served.
Open connection pools survive most blips
PlanetScale's edge proxies tolerate short interruptions. If you're using a connection pool (most ORMs do), a 5-15 second incident is often invisible to your app.
Don't trigger a schema deploy during an incident
Schema deploys hit the control plane. Queuing one during an active incident can fail mid-rollout and leave you with a half-applied branch. Wait for the all-clear.
Keep firing through the incident
Schedule your own PlanetScale health check with Crontap
Recurring database maintenance (analytics rollups, partition cleanup, soft-delete sweeps) is HTTP cron when wrapped in a small endpoint. Crontap fires the endpoint and surfaces the MySQL/Postgres error in the failure alert.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
PlanetScale status: FAQ
- Where do I check PlanetScale status?
- planetscalestatus.com publishes component status per region and per product (Vitess MySQL, Neki Postgres, Boost, Insights). The history page tracks past incidents.
- Will my queries fail during a PlanetScale incident?
- It depends on which component is degraded. The data plane is the one that serves live SQL; if it's healthy and only the Console is red, your app is fine. Use connection pooling in your app so short data-plane blips don't surface as user errors.
- How do I monitor PlanetScale connectivity from outside?
- Add a /api/db-health endpoint on your app that runs SELECT 1; against PlanetScale, and probe it with Crontap every minute. The probe catches connectivity issues, pooler exhaustion, and replication lag before users feel them.