PlanetScale Status · History · Incident #5174
RESOLVEDDevelopment branches with MySQL Vectors not serving
Major · Started Jul 6, 2026 · 7:18 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
PlanetScale Status · History · Incident #5174
RESOLVEDMajor · Started Jul 6, 2026 · 7:18 PM
Duration
2h 26m
Severity
Major
Detection lead
—
User reports
—
Summary
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
Investigating
Jul 6 · 7:18 PM PlanetScalePlanetScale 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 PlanetScaleWe have identified the issue and are rolling impacted development branches from 8.4 back to 8.0.
Monitoring
Jul 6 · 8:38 PM PlanetScaleBranches are recovering and we are monitoring the situation.
Resolved
Jul 6 · 9:45 PM PlanetScaleAll 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.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026