PlanetScale status
Is PlanetScale down? This is PlanetScale’s current status, its components and its recent incidents, read from PlanetScale’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by PlanetScale’s status page, read Oct 24, 2026, 18:03 UTC.
Components
| Component | Status |
|---|---|
| us-east-1 (Northern Virginia) | 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 |
| eu-west-2 (London) | Operational |
| sa-east-1 (Sao Paulo) | Operational |
| us-central1 (Iowa) | Operational |
| us-east1 (Moncks Corner) | Operational |
| us-east4 (Northern Virginia) | Operational |
| asia-northeast3 (Seoul) | Operational |
| northamerica-northeast1 (Montréal) | Operational |
| europe-west1 (St. Ghislain) | Operational |
| europe-west4 (Eemshaven) | Operational |
| centralus (Iowa) | Operational |
| eastus2 (Virginia) | Operational |
| westeurope (Netherlands) | Operational |
| us-east-1 (Northern Virginia) | Operational |
| us-east-2 (Ohio) | Operational |
| us-west-2 (Oregon) | Operational |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent PlanetScale incidents
- Gap in dashboard metrics for AWS us-east-1 · Oct 20, 2026, 19:38 UTC · resolved, lasted 1 h 8 min
The issue has been resolved.
- AWS us-east-1 connectivity failures · Oct 9, 2026, 22:53 UTC · resolved, major impact, lasted 26 min
AWS us-east-1 cross-zone networking has fully recovered.
- Branch creation delays in GCP europe-west-1 · Sep 28, 2026, 18:59 UTC · resolved, minor impact, lasted 2 h 3 min
We have resolved the branch creation issue and no further impact is expected at this time.
- Connectivity issues with Vitess databases in GCP · Sep 5, 2026, 18:39 UTC · resolved, major impact, lasted 14 min
We've identified an issue with database connectivity for Vitess databases in GCP. We've taken steps to resolve the issue and are making immediate improvements to address root-causes and detection. Databases connectivity is now restored.
- Dashboard and API 500 errors for postgres databases · Sep 2, 2026, 16:34 UTC · resolved, major impact, lasted 10 min
The incident has been resolved. Between 12:17 and 12:24 UTC, the dashboard and API were returning 500 errors for postgres database management pages and API endpoints.
- Insights metrics underreporting · Jul 24, 2026, 14:41 UTC · resolved, major impact, lasted 3 h 0 min
The incident has been resolved.
- Insights metrics underreporting · Jul 20, 2026, 18:29 UTC · resolved, minor impact, lasted 20 h 49 min
Query Insights functionality is restored on all Postgres development branches.
- Connectivity issues in us-east-1 · Jul 18, 2026, 20:32 UTC · resolved, major impact, lasted 33 min
Connection issues have been resolved. If you experience any further issues, please contact our support team.
- API and dashboard errors · Jul 17, 2026, 16:41 UTC · resolved, major impact, lasted 28 min
API and dashboard service is restored.
- Single Sign On (SSO) unavailable · Jul 16, 2026, 09:30 UTC · resolved, minor impact, lasted 1 h 21 min
The issue is resolved. SSO is working fine again.
- Development branches with MySQL Vectors not serving · Jul 6, 2026, 19:18 UTC · resolved, minor impact, lasted 2 h 27 min
All impacted branches are recovered. PlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. A bug in the 8.4.x version of our Vectors builds…
- There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information. · May 14, 2026, 20:30 UTC · resolved, major impact, lasted 32 min
The changes we applied are effectively preventing further unexpected restarts to the high availability component shared by Postgres clusters. We have not seen further restarts to this component nor unplanned failovers in Postgres clusters since applying these changes.
- Database operations degraded in eu-west-2 · May 13, 2026, 17:17 UTC · resolved, minor impact, lasted 48 min
PlanetScale has remediated the issue and it is fully resolved.
- AWS use1-az4 thermal event · May 8, 2026, 02:22 UTC · resolved, lasted 17 h 0 min
PlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.
- Errors with database webhooks · Apr 8, 2026, 00:34 UTC · resolved, minor impact, lasted 15 min
The errors have been resolved.
Source: PlanetScale, PlanetScale’s public status page, read Oct 24, 2026, 18:03 UTC. Uptimely is not affiliated with PlanetScale; incident text is PlanetScale’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of planetscale.com to see whether it answers right now.
Get alerted when PlanetScale has an incident
Uptimely’s External Status Page monitor watches PlanetScale’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
- GitHub status
- Bitbucket status
- npm status
- Docker status
- Twilio status
- Datadog status
- Sentry status
- Supabase status
- MongoDB Atlas status
- Elastic Cloud status
- Snowflake status
- Grafana Cloud status
- CircleCI status
- Mailgun status
- Resend status
- Clerk status
- Segment status
- Cloudinary status
Is PlanetScale down right now?
The status at the top of this page is PlanetScale's own, read from its public status page every couple of minutes. It shows what PlanetScale's team has confirmed. For an independent check of whether planetscale.com answers right now, use the live check on the is-it-down page.
Where is PlanetScale's official status page?
PlanetScale publishes its status at https://www.planetscalestatus.com. This page shows the same data with the recent incident history in one place, and links each incident to PlanetScale's own write-up.
Why does PlanetScale not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when PlanetScale has an incident?
Add an External Status Page monitor in Uptimely pointed at https://www.planetscalestatus.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when PlanetScale reports a problem, beside the monitors for your own services.