PlanetScale outage, 6 July 2026

Development branches with MySQL Vectors not serving

Started
Resolved
6 Jul 2026, 21:45 UTC (after 2 h 26 min)
Impact
Minor

Last update from PlanetScale

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 resulted in the upgrade immediately failing on startup. Because Vitess development branches only have one instance - the primary - impacted development branches did not have a primary during the impact window. The incident was resolved by reverting impacted branches to their previous MySQL version. PlanetScale will fix the bug in the MySQL Vectors 8.4.x build before re-attempting the upgrade at a later date.

6 Jul 2026, 21:45 UTC

Is PlanetScale down now?

This page is the record of one past incident. For the live status, see Is PlanetScale down right now? - it reads the official status page every 2 minutes.

Other PlanetScale incidents

  1. AWS us-east-1 connectivity failures

  2. Branch creation delays in GCP europe-west-1

  3. Connectivity issues with Vitess databases in GCP

  4. Dashboard and API 500 errors for postgres databases

  5. Insights metrics underreporting

  6. Insights metrics underreporting

  7. Connectivity issues in us-east-1

  8. API and dashboard errors

All recorded PlanetScale incidents