Is PlanetScale down?
No, PlanetScale is not down.
PlanetScale’s status page reports no incidents, api.planetscale.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsplanetscalestatus.com
- Reachable6 of 6 regionsPlanetScale API · api.planetscale.com
- Reports in the last hour0Normal
PlanetScale’s status page
From planetscalestatus.com. Read at
- us-east-1 (Northern Virginia) Database Connectivity: Postgres (AWS)Operational
- us-east-2 (Ohio) Database Connectivity: Postgres (AWS)Operational
- us-west-2 (Oregon) Database Connectivity: Postgres (AWS)Operational
- ap-northeast-1 (Tokyo) Database Connectivity: Postgres (AWS)Operational
- ap-south-1 (Mumbai) Database Connectivity: Postgres (AWS)Operational
- ap-southeast-1 (Singapore) Database Connectivity: Postgres (AWS)Operational
- ap-southeast-2 (Sydney) Database Connectivity: Postgres (AWS)Operational
- ca-central-1 (Montreal) Database Connectivity: Postgres (AWS)Operational
Show all 44 components
- eu-central-1 (Frankfurt) Database Connectivity: Postgres (AWS)Operational
- eu-west-1 (Dublin) Database Connectivity: Postgres (AWS)Operational
- eu-west-2 (London) Database Connectivity: Postgres (AWS)Operational
- sa-east-1 (Sao Paulo) Database Connectivity: Postgres (AWS)Operational
- us-central1 (Iowa) Database Connectivity: Postgres (GCP)Operational
- us-east1 (Moncks Corner) Database Connectivity: Postgres (GCP)Operational
- us-east4 (Northern Virginia) Database Connectivity: Postgres (GCP)Operational
- asia-northeast3 (Seoul) Database Connectivity: Postgres (GCP)Operational
- northamerica-northeast1 (Montréal) Database Connectivity: Postgres (GCP)Operational
- europe-west1 (St. Ghislain) Database Connectivity: Postgres (GCP)Operational
- europe-west4 (Eemshaven) Database Connectivity: Postgres (GCP)Operational
- centralus (Iowa) Database Connectivity: Postgres (Azure)Operational
- eastus2 (Virginia) Database Connectivity: Postgres (Azure)Operational
- westeurope (Netherlands) Database Connectivity: Postgres (Azure)Operational
- us-east-1 (Northern Virginia) Database Connectivity: Vitess (AWS)Operational
- us-east-2 (Ohio) Database Connectivity: Vitess (AWS)Operational
- us-west-2 (Oregon) Database Connectivity: Vitess (AWS)Operational
- ap-northeast-1 (Tokyo) Database Connectivity: Vitess (AWS)Operational
- ap-south-1 (Mumbai) Database Connectivity: Vitess (AWS)Operational
- ap-southeast-1 (Singapore) Database Connectivity: Vitess (AWS)Operational
- ap-southeast-2 (Sydney) Database Connectivity: Vitess (AWS)Operational
- ca-central-1 (Montreal) Database Connectivity: Vitess (AWS)Operational
- eu-central-1 (Frankfurt) Database Connectivity: Vitess (AWS)Operational
- eu-west-1 (Dublin) Database Connectivity: Vitess (AWS)Operational
- eu-west-2 (London) Database Connectivity: Vitess (AWS)Operational
- sa-east-1 (Sao Paulo) Database Connectivity: Vitess (AWS)Operational
- us-central1 (Iowa) Database Connectivity: Vitess (GCP)Operational
- us-east1 (Moncks Corner) Database Connectivity: Vitess (GCP)Operational
- us-east4 (Northern Virginia) Database Connectivity: Vitess (GCP)Operational
- asia-northeast3 (Seoul) Database Connectivity: Vitess (GCP)Operational
- northamerica-northeast1 (Montréal) Database Connectivity: Vitess (GCP)Operational
- europe-west1 (St. Ghislain) Database Connectivity: Vitess (GCP)Operational
- europe-west4 (Eemshaven) Database Connectivity: Vitess (GCP)Operational
- Database OperationsOperational
- Dashboard and API RequestsOperational
- Query InsightsOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 353 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.planetscale.com)
By region
| Region | PlanetScale API api.planetscale.com |
|---|---|
| N. Virginia us-east-1 | 401 · 28 ms |
| Oregon us-west-2 | 401 · 197 ms |
| Frankfurt eu-central-1 | 401 · 320 ms |
| Singapore ap-southeast-1 | 401 · 767 ms |
| Tokyo ap-northeast-1 | 401 · 456 ms |
| São Paulo sa-east-1 | 401 · 514 ms |
Two regions check PlanetScale every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked PlanetScale ourselves since Oct 28, 2026. Earlier days come from its status page.
6 days with problems in the last 90 days.
Recent incidents
Incidents: 4 in the last 30 days and 6 in the last 90, lasting a median of 46 min.
- Problems with Vitess connectivity and credential changesPartial outage1 h 38 min
- Gap in dashboard metrics for AWS us-east-1Degraded1 h 7 min
- AWS us-east-1 connectivity failuresPartial outage25 min
- Branch creation delays in GCP europe-west-1Degraded2 h 3 min
- Connectivity issues with Vitess databases in GCPPartial outage14 min
- Dashboard and API 500 errors for postgres databasesPartial outage10 min
If PlanetScale isn’t working for you
PlanetScale is a managed database platform for MySQL (built on Vitess) and Postgres, used for high-scale production workloads.
Common PlanetScale errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
ResourceExhausted desc = transaction pool connection limit exceeded | Your database hit its limit on concurrent transactions. | Your side | Shorten long-running transactions or size up the database. Source |
Row count exceeded 100000 | A single query returned, updated or deleted more than 100,000 rows. | Your side | Paginate SELECTs or batch large UPDATEs and DELETEs. Source |
Is it just you?
- Check planetscalestatus.com for your region and database engine.
- Read the error text: Vitess errors such as ResourceExhausted describe limits on your database, not an outage.
- Use connection pooling; long-held connections can be terminated and add memory pressure.
- Try connecting from another network or with the CLI to rule out your app's network.
Alternatives to PlanetScale
Questions
Every PlanetScale database has a limit on concurrent transactions, and you hit it. Shorten long transactions or size up the database.
Errors about row counts or the transaction pool connection limit come from your queries and connection use, not an outage. If connections fail from every client, check PlanetScale's status page.
Sources: planetscale.com, planetscalestatus.com
Get alerted when PlanetScale breaks your app.
If your product or your team depends on PlanetScale, its outage is your outage, and your users will blame you, not PlanetScale. Point a Site Qwality monitor at the PlanetScale endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.