Liquid Web Status · History · Incident #2658

RESOLVED

MySQL Service Disruption via MySQL-community repo

Major · Started Apr 22, 2026 · 7:02 AM

  • Duration

    2d 14h 6m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

MySQL Service Disruption via MySQL-community repo

This incident has been resolved.


  • Started

    Apr 22, 2026 · 7:02 AM

  • Resolved

    Apr 24, 2026 · 9:09 PM

  • Duration

    2d 14h 6m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Apr 22 · 7:02 AM Liquid Web

    We are currently observing MySQL failure alerts across multiple servers. Initial investigation suggests the issue may be related to an automatic upgrade from MySQL 8.4 to 9.7 via yum on systems using the MySQL Community repository (mysql-community.repo). This upgrade via the mysql-community repo is likely contributing to the ongoing service disruptions. If you have any questions or require assistance, please contact us via Live Chat or submit a support case. We appreciate your patience and will continue to provide updates as progress is made.

  • Identified

    Apr 22 · 9:25 AM Liquid Web

    We are currently observing MySQL failure alerts across multiple servers. Initial investigation indicates the issue may be related to an automatic upgrade from MySQL 8.4 to 9.7 via yum on systems using the MySQL Community repository (mysql-community.repo). This upgrade via the mysql-community repo is likely contributing to the ongoing service disruptions. We have identified the issue, and our teams are actively working on remediation and service restoration. If you have any questions or require assistance, please contact us via Live Chat or submit a support case.

  • Identified

    Apr 23 · 1:08 AM Liquid Web

    The cPanel nightly updates are triggering system updates, which has resulted in servers running MySQL 8.4 being upgraded to MySQL 9.7. This appears to be due to the official mysql-community.repo making MySQL 9.7 available, causing dnf/yum to recognise it as the latest version. This issue stems from a bug within the MySQL repositories that is allowing automatic upgrades to the next major version. We have raised this with the MySQL team as well. We are currently in touch with the cPanel team, who have opened an internal case and are actively investigating the matter. A workaround is being implemented on affected servers, and we will continue to provide updates here as more information becomes available. If you have any questions or require assistance, please contact us via Live Chat or by submitting a support case. Thank you for your patience and understanding.

  • Monitoring

    Apr 24 · 1:20 AM Liquid Web

    We continue to actively monitor the situation related to unintended MySQL upgrades triggered via the MySQL-Community repo during cPanel nightly updates. Our teams remain engaged with both the cPanel and MySQL teams, and their investigations are still ongoing. The previously identified workaround continues to be applied on affected systems to prevent further impact, and we are closely observing system stability. We understand the importance of a permanent resolution and will share further updates as soon as more information becomes available or once a fix is confirmed. If you have any questions or need assistance, please reach out via Live Chat or by submitting a support case. Thank you for your continued patience.

  • Resolved

    Apr 24 · 9:09 PM Liquid Web

    This incident has been resolved.

Get alerted before the next Liquid Web outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free
Hey there 👋  Friends from designmodo are here to help!