Problems with Vitess connectivity and credential changes
OutageWe've observed service restored and successful credential changes across PlanetScale's environments.
PlanetScale is up and running. PlanetScale is a hosted MySQL-compatible database built on Vitess.
Worked out from the incidents PlanetScale reported, so it is an estimate and not a measurement.
Last incident: “Problems with Vitess connectivity and credential changes”, 2 days ago.
We've observed service restored and successful credential changes across PlanetScale's environments.
The issue has been resolved.
AWS us-east-1 cross-zone networking has fully recovered.
We have resolved the branch creation issue and no further impact is expected at this time.
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.
PlanetScale’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident PlanetScale reported was “Problems with Vitess connectivity and credential changes”, 2 days ago (2026-10-26 21:53 UTC). Its last full outage started 2 days ago.
PlanetScale reports 25 components on its status page, including us-east-1 (Northern Virginia), us-east-2 (Ohio), us-west-2 (Oregon), ap-northeast-1 (Tokyo), ap-south-1 (Mumbai). Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Either, depending on where the branch is deployed: the status page lists AWS regions (us-east-1…) and GCP regions (us-east4…) separately. `pscale database show` reports your cluster's region.
PlanetScale supports read-only regions: adding a replica in another region lets read traffic fail over there while the primary region is degraded.
If the status above is operational but PlanetScale still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.