Development branches with MySQL Vectors not serving

Update timeline

1. investigating Jul 06, 2026, 07:18 PM UTC

   Status: Investigating 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. Affected components us-east-1 (Northern Virginia) (Partial outage) us-central1 (Iowa) (Partial outage) northamerica-northeast1 (Montréal) (Partial outage) us-east4 (Northern Virginia) (Partial outage) ap-southeast-2 (Sydney) (Partial outage) us-east-2 (Ohio) (Partial outage) ap-south-1 (Mumbai) (Partial outage) eu-central-1 (Frankfurt) (Partial outage) us-west-2 (Oregon) (Partial outage) ca-central-1 (Montreal) (Partial outage) ap-northeast-1 (Tokyo) (Partial outage) sa-east-1 (Sao Paulo) (Partial outage) eu-west-1 (Dublin) (Partial outage) asia-northeast3 (Seoul) (Partial outage) ap-southeast-1 (Singapore) (Partial outage)

2. identified Jul 06, 2026, 07:23 PM UTC

   Status: Identified We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0. Affected components ap-south-1 (Mumbai) (Partial outage) us-east-1 (Northern Virginia) (Partial outage) us-central1 (Iowa) (Partial outage) ca-central-1 (Montreal) (Partial outage) sa-east-1 (Sao Paulo) (Partial outage) ap-southeast-1 (Singapore) (Partial outage) eu-west-1 (Dublin) (Partial outage) northamerica-northeast1 (Montréal) (Partial outage) asia-northeast3 (Seoul) (Partial outage) ap-northeast-1 (Tokyo) (Partial outage) ap-southeast-2 (Sydney) (Partial outage) us-east4 (Northern Virginia) (Partial outage) us-east-2 (Ohio) (Partial outage) eu-central-1 (Frankfurt) (Partial outage) us-west-2 (Oregon) (Partial outage)

3. monitoring Jul 06, 2026, 08:38 PM UTC

   Status: Monitoring Branches are recovering and we are monitoring the situation. Affected components ap-south-1 (Mumbai) (Partial outage) sa-east-1 (Sao Paulo) (Partial outage) ap-southeast-1 (Singapore) (Partial outage) asia-northeast3 (Seoul) (Partial outage) us-east4 (Northern Virginia) (Partial outage) ca-central-1 (Montreal) (Partial outage) eu-central-1 (Frankfurt) (Partial outage) us-central1 (Iowa) (Partial outage) ap-northeast-1 (Tokyo) (Partial outage) eu-west-1 (Dublin) (Partial outage) us-east-1 (Northern Virginia) (Partial outage) northamerica-northeast1 (Montréal) (Partial outage) us-east-2 (Ohio) (Partial outage) ap-southeast-2 (Sydney) (Partial outage) us-west-2 (Oregon) (Partial outage)

4. resolved Jul 06, 2026, 09:45 PM UTC

   Status: Resolved 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. Affected components us-east4 (Northern Virginia) (Operational) us-west-2 (Oregon) (Operational) northamerica-northeast1 (Montréal) (Operational) asia-northeast3 (Seoul) (Operational) sa-east-1 (Sao Paulo) (Operational) ap-southeast-1 (Singapore) (Operational) us-east-2 (Ohio) (Operational) ap-south-1 (Mumbai) (Operational) ap-northeast-1 (Tokyo) (Operational) ap-southeast-2 (Sydney) (Operational) eu-central-1 (Frankfurt) (Operational) us-east-1 (Northern Virginia) (Operational) eu-west-1 (Dublin) (Operational) us-central1 (Iowa) (Operational) ca-central-1 (Montreal) (Operational)