Is PlanetScale down?
Loading the latest status…
Is PlanetScale down right now? Live status from PlanetScale’s status page, our own checks and user reports, updated every minute.
- Official status
- Reachable
- Reports in the last hour
Detailed data for this service is briefly unavailable. The status above comes from our latest check.
PlanetScale’s status page
- us-east-1 (Northern Virginia) Database Connectivity: Postgres (AWS)
- us-east-2 (Ohio) Database Connectivity: Postgres (AWS)
- us-west-2 (Oregon) Database Connectivity: Postgres (AWS)
- ap-northeast-1 (Tokyo) Database Connectivity: Postgres (AWS)
- ap-south-1 (Mumbai) Database Connectivity: Postgres (AWS)
- ap-southeast-1 (Singapore) Database Connectivity: Postgres (AWS)
- ap-southeast-2 (Sydney) Database Connectivity: Postgres (AWS)
- ca-central-1 (Montreal) Database Connectivity: Postgres (AWS)
Show all 44 components
- eu-central-1 (Frankfurt) Database Connectivity: Postgres (AWS)
- eu-west-1 (Dublin) Database Connectivity: Postgres (AWS)
- eu-west-2 (London) Database Connectivity: Postgres (AWS)
- sa-east-1 (Sao Paulo) Database Connectivity: Postgres (AWS)
- us-central1 (Iowa) Database Connectivity: Postgres (GCP)
- us-east1 (Moncks Corner) Database Connectivity: Postgres (GCP)
- us-east4 (Northern Virginia) Database Connectivity: Postgres (GCP)
- asia-northeast3 (Seoul) Database Connectivity: Postgres (GCP)
- northamerica-northeast1 (Montréal) Database Connectivity: Postgres (GCP)
- europe-west1 (St. Ghislain) Database Connectivity: Postgres (GCP)
- europe-west4 (Eemshaven) Database Connectivity: Postgres (GCP)
- centralus (Iowa) Database Connectivity: Postgres (Azure)
- eastus2 (Virginia) Database Connectivity: Postgres (Azure)
- westeurope (Netherlands) Database Connectivity: Postgres (Azure)
- us-east-1 (Northern Virginia) Database Connectivity: Vitess (AWS)
- us-east-2 (Ohio) Database Connectivity: Vitess (AWS)
- us-west-2 (Oregon) Database Connectivity: Vitess (AWS)
- ap-northeast-1 (Tokyo) Database Connectivity: Vitess (AWS)
- ap-south-1 (Mumbai) Database Connectivity: Vitess (AWS)
- ap-southeast-1 (Singapore) Database Connectivity: Vitess (AWS)
- ap-southeast-2 (Sydney) Database Connectivity: Vitess (AWS)
- ca-central-1 (Montreal) Database Connectivity: Vitess (AWS)
- eu-central-1 (Frankfurt) Database Connectivity: Vitess (AWS)
- eu-west-1 (Dublin) Database Connectivity: Vitess (AWS)
- eu-west-2 (London) Database Connectivity: Vitess (AWS)
- sa-east-1 (Sao Paulo) Database Connectivity: Vitess (AWS)
- us-central1 (Iowa) Database Connectivity: Vitess (GCP)
- us-east1 (Moncks Corner) Database Connectivity: Vitess (GCP)
- us-east4 (Northern Virginia) Database Connectivity: Vitess (GCP)
- asia-northeast3 (Seoul) Database Connectivity: Vitess (GCP)
- northamerica-northeast1 (Montréal) Database Connectivity: Vitess (GCP)
- europe-west1 (St. Ghislain) Database Connectivity: Vitess (GCP)
- europe-west4 (Eemshaven) Database Connectivity: Vitess (GCP)
- Database Operations
- Dashboard and API Requests
- Query Insights
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.planetscale.com)
By region
| Region | PlanetScale API api.planetscale.com |
|---|---|
| N. Virginia | |
| Oregon | |
| Frankfurt | |
| Singapore | |
| Tokyo | |
| São Paulo |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked PlanetScale ourselves since Oct 28, 2026. Earlier days come from its status page.
7 days with problems in the last 90 days.
Recent incidents
Incidents: 3 in the last 30 days and 7 in the last 90, lasting a median of 25 min.
- Vitess - development branch delays in us-east-1Degraded23 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 depends on PlanetScale, your users feel its outages too. Point a Site Qwality monitor at the PlanetScale endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.