# Is PlanetScale down?

> PlanetScale is operational. Checked 2026-11-02 02:06 UTC.

- Official status page: https://www.planetscalestatus.com
- Web page: https://outages.live/planetscale
- JSON: https://outages.live/api/v1/providers/planetscale
- RSS: https://outages.live/feed.xml?providers=planetscale

## Active incidents

PlanetScale reports no active incident. Status pages can lag the start of a problem by a few minutes.

## Last 90 days

6 incidents on 6 of the last 90 days.

- [PlanetScale: Problems with Vitess connectivity and credential changes](https://outages.live/outages/planetscale-14q0vzgp6ml.md): Resolved, started 2026-10-26 21:53 UTC, lasted 1 h 38 min. We've observed service restored and successful credential changes across PlanetScale's environments.
- [PlanetScale: Gap in dashboard metrics for AWS us-east-1](https://outages.live/outages/planetscale-2dp7tqk01u6.md): Resolved, started 2026-10-20 19:38 UTC, lasted 1 h 8 min. The issue has been resolved.
- [PlanetScale: AWS us-east-1 connectivity failures](https://outages.live/outages/planetscale-1qaorv8o92x.md): Resolved, started 2026-10-09 22:53 UTC, lasted 26 min. AWS us-east-1 cross-zone networking has fully recovered.
- [PlanetScale: Branch creation delays in GCP europe-west-1](https://outages.live/outages/planetscale-jlpabutqzi.md): Resolved, started 2026-09-28 18:59 UTC, lasted 2 h 3 min. We have resolved the branch creation issue and no further impact is expected at this time.
- [PlanetScale: Connectivity issues with Vitess databases in GCP](https://outages.live/outages/planetscale-15x2mqe613d.md): Resolved, started 2026-09-05 18:39 UTC, 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.
- [PlanetScale: Dashboard and API 500 errors for postgres databases](https://outages.live/outages/planetscale-13ho4yngmcm.md): Resolved, started 2026-09-02 16:34 UTC, 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.