PlanetScale incident: Development branches with MySQL Vectors not serving

1. resolvedJul 6, 2026, 21:45 UTC

   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.

2. monitoringJul 6, 2026, 20:38 UTC

   Branches are recovering and we are monitoring the situation.

3. identifiedJul 6, 2026, 19:23 UTC

   We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.

4. investigatingJul 6, 2026, 19:18 UTC

   PlanetScale initiated a system wide upgrade of branches with Vectors enabled and running on MySQL 8.0 to MySQL 8.4. A number of development branches were disrupted and have not yet recovered. We are investigating and remediating.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in PlanetScale's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• LaunchDarkly: High volume of error alerts related to flag delivery network.Major · Jul 6, 2026, 20:30 UTC
• Linode: Service Issue - ACLP MetricsMinor · Jun 26, 2026, 17:35 UTC

How often does PlanetScale have incidents?

PlanetScale reported 9 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 21m. See PlanetScale's uptime and incident history