Provider
PlanetScaleIncident detail
Development branches with MySQL Vectors not serving
Resolved incidentMinor3 affected services19 regions: ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2, asia-northeast3, ca-central-1, eu-central-1, eu-west-1, eu-west-2, europe-west1, europe-west4, northamerica-northeast1, sa-east-1, us-central1, us-east-1, us-east-2, us-east1, us-east4, us-west-2
Timeline window
to
Get alerted the next time PlanetScale breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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.
Identified
We have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.
Monitoring
Branches are recovering and we are monitoring the situation.
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.
Keep exploring
More from PlanetScale
Neighboring incidents on PlanetScale's timeline and the rest of their record on OutageDeck.