Why PlanetScale Outages Are Easy to Misdiagnose
PlanetScale is a serverless MySQL-compatible database built on Vitess, with branching, sharding, and per-branch credentials layered on top. Because so much of that architecture lives between your app and the underlying database, a failing query can mean a genuine platform incident — or it can mean a stale connection string, a rotated password, or a Vitess compatibility quirk that has nothing to do with uptime.
The fastest way to avoid wasted debugging time is to separate the two categories immediately: platform-wide incident (check the status page) versus your specific connection or query (check your app first).
Monitor Your PlanetScale-Backed Endpoints
PlanetScale's status page tracks platform health, not your database connection. Better Stack can monitor your app's database-dependent endpoints directly and alert you the moment queries start failing.
Try Better Stack Free →How to Check if PlanetScale Is Down
1. The Official PlanetScale Status Page
Visit status.planetscale.com. PlanetScale breaks status out by component — database reads, database writes, branching, the web console, and the management API — and by region. A read incident in one region does not necessarily mean your database, in a different region, is affected.
If the status page shows "All Systems Operational" but your app still cannot connect, the issue is almost always local rather than a lagging status page — see the diagnosis table below.
2. Test the Connection Directly
Log into app.planetscale.com and run a test query in the built-in console, or use the CLI:
pscale connect your-database main --port 3309If the console or CLI also fails to connect, that is strong evidence of a platform-level issue rather than something specific to your app's configuration.
3. Independent Monitors
Use our live PlanetScale status monitor for a check that does not depend on PlanetScale's own reporting. Search planetscale down on X — the Next.js, Rails, and Laravel communities that lean on PlanetScale heavily tend to report incidents within minutes.
📡 Monitor PlanetScale uptime every 30 seconds — get alerted in under a minute
Trusted by 100,000+ websites · Free tier available
PlanetScale Not Working: Diagnosis by Symptom
- Check status.planetscale.com for active Reads or Writes incidents in your region
- Regenerate a fresh connection string from the PlanetScale console — passwords are per-branch and may have been rotated
- Verify the branch name in your connection string matches an existing branch (usually "main" for production)
- Confirm your app server IP is not blocked by an IP allowlist restriction, if one is configured
- Test with `pscale connect` to rule out an application-level config issue
- Check status.planetscale.com specifically for the "Database Writes" component — it is tracked separately from reads
- Write incidents typically take longer to resolve than read incidents because they involve the primary replica
- Confirm you are not hitting a Vitess-specific write restriction (e.g., unsupported multi-shard transaction)
- Check the PlanetScale Insights tool for query-level errors before assuming an outage
- Check status.planetscale.com for the "Branching" component specifically — this is isolated from production reads/writes
- A stuck migration does not affect your live production branch; it is contained to the development branch
- Check the deploy request status in the PlanetScale console for a specific error message
- Retry the schema diff after confirming no active Branching incident
- This is almost always query-level, not a platform outage — check status.planetscale.com to rule it out first
- Use the Insights tool to identify the specific slow query
- Add missing indexes or break up large analytical queries
- Consider routing analytics workloads to a read replica or separate database
- This is a Vitess compatibility quirk, not an outage
- Use UTC offset notation (e.g. '+00:00') instead of named time zones like 'America/New_York'
- Update any ORM timezone configuration to match
PlanetScale Status Indicators Explained
| Status | What It Means | What To Do |
|---|---|---|
| Operational | All components working normally | If your app still fails, check your connection string and credentials |
| Degraded Performance | Higher latency on reads or writes than normal | App keeps working but slower — no action needed, monitor for escalation |
| Partial Outage | Some regions or components unavailable | Check whether your specific region and component (reads vs writes) is affected |
| Major Outage | Large-scale failure across most databases or regions | Enable read-only fallback if your app supports it; monitor status.planetscale.com for updates |
| Maintenance | Planned maintenance window, announced in advance | Reads/writes are usually preserved; management features may be briefly unavailable |
Rotate PlanetScale Credentials Securely
Stale database passwords are one of the most common causes of a false PlanetScale 'outage.' Use 1Password to store and rotate per-branch credentials without breaking production.
Try 1Password Free →Best Practices: Staying Resilient During PlanetScale Incidents
1. Add a Database Health Check Endpoint
PlanetScale's status page reflects platform health, not your specific database connection. Add a lightweight endpoint to your app that runs SELECT 1 against your production branch, and monitor that endpoint independently — it will catch connection-string and credential issues that never show up on status.planetscale.com.
2. Isolate Read and Write Paths
Because PlanetScale tracks reads and writes as separate incident categories, apps that can temporarily degrade to read-only mode during a write incident stay available for most users instead of failing completely.
3. Monitor Proactively, Not Reactively
Set up alerts on your database-dependent endpoints so you know about a query failure before users start reporting it — PlanetScale incidents are often regional, so your team may not notice until a specific customer segment is affected.
Alert Pro
14-day free trialStop checking — get alerted instantly
Alert Pro checks the 60+ APIs we monitor every hour and emails you within the hour of a detected change.
- Email alerts for up to 10 of the APIs we monitor
- $0 charged today — card required to start
- Cancel anytime — $9/mo after trial
PlanetScale Alternatives During Outages
If PlanetScale is down and you need a fallback for testing or an urgent migration, these are common alternatives in the same serverless MySQL/Postgres space:
- Neon — Serverless Postgres with branching, a close conceptual analog to PlanetScale for teams open to switching engines. See Neon Status Guide.
- Supabase — Managed Postgres with a broader platform (auth, storage, edge functions). Check Is Supabase Down?
- Railway — Managed MySQL/Postgres hosting with simple provisioning. Check Is Railway Down?
- Self-hosted MySQL on RDS or Cloud SQL — Slower to provision but useful as a documented disaster-recovery path for critical production workloads.
FAQ: PlanetScale Down Questions
Is PlanetScale down right now?
Check our live PlanetScale status monitor and the official status.planetscale.com page for the latest.
Is PlanetScale down for everyone or just me?
If status.planetscale.com is green but your app can't connect, the problem is almost always local — an outdated connection string, a rotated database password, or an IP allowlist restriction. Test the connection independently with the PlanetScale console or the pscale connect CLI before assuming a platform-wide incident.
Why do PlanetScale writes fail but reads still work?
PlanetScale tracks database reads and writes as separate status components. A write-specific incident affects INSERT/UPDATE/DELETE operations while SELECT queries continue to succeed. Check status.planetscale.com for the "Database Writes" row specifically.
How often does PlanetScale go down?
Reported incidents run roughly one to two per month, and most are regional rather than global thanks to Vitess's sharding and automatic failover. Read incidents tend to resolve in 30–60 minutes; write incidents can take longer since they involve the primary replica.
Conclusion
Most PlanetScale "outages" reported by developers turn out to be a stale connection string or a rotated password rather than an actual platform incident. Check status.planetscale.com first, test your connection directly with the console or CLI, and only escalate to "this is a real outage" once both point the same direction.
If your production app depends on PlanetScale, set up an independent health-check endpoint so you find out about connection failures before your status-page check would ever catch them.