PlanetScale Status · History · Incident #5174

RESOLVED

Development branches with MySQL Vectors not serving

Major · Started Jul 6, 2026 · 7:18 PM

  • Duration

    2h 26m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Development branches with MySQL Vectors not serving

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.


  • Started

    Jul 6, 2026 · 7:18 PM

  • Resolved

    Jul 6, 2026 · 9:45 PM

  • Duration

    2h 26m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Jul 6 · 7:18 PM PlanetScale

    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

    Jul 6 · 7:23 PM PlanetScale

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

  • Monitoring

    Jul 6 · 8:38 PM PlanetScale

    Branches are recovering and we are monitoring the situation.

  • Resolved

    Jul 6 · 9:45 PM 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.

Get alerted before the next PlanetScale outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free