Liquid Web Outage History

Let's Encrypt experienced a service interruption that prevented the issuance of new SSL certificates for 4.4 hours. This affected Liquid Web customers who needed to obtain or renew SSL certificates during this period. The issue was resolved when Let's Encrypt resumed normal certificate issuance operations.

MySQL services failed across multiple Liquid Web servers due to automatic upgrades from MySQL 8.4 to 9.7 triggered by cPanel nightly updates using the MySQL Community repository. The issue was caused by a bug in the MySQL repositories that allowed unintended major version upgrades, affecting cPanel services for over 62 hours. Liquid Web implemented workarounds on affected systems and coordinated with both cPanel and MySQL teams to resolve the incident.

A faulty networking switch in Liquid Web's DC4 Phoenix data center caused network degradation affecting a subset of servers, resulting in intermittent latency and connectivity drops for customers. Engineers identified and fixed the problematic switch after 22.4 hours, restoring affected services. The incident was fully resolved after a monitoring period to ensure network stability.

Liquid Web experienced a 39.3-hour disruption where the Spice Console was not functioning on Linux virtual private servers, while Windows servers remained unaffected. The issue prevented users from accessing their Linux VPS through the console interface, though server stability and uptime were not impacted. The engineering team identified the root cause, implemented a fix, and restored normal console access functionality.

An incompatible update from the imunify360-ea-php-hardened repository caused Apache service instability on a subset of Liquid Web servers running cPanel, requiring manual intervention to restore service in some cases. The engineering team remediated affected systems by disabling the problematic repository and completed patching efforts across the environment to restore service stability. The incident was fully resolved after 20.1 hours with all systems stabilized and monitoring confirming no new issues.

Liquid Web experienced an internal network outage that lasted 3 hours and caused delays in support response times across chat, ticket, and phone support channels. Customer websites and services remained fully operational throughout the incident. The Network Engineering team resolved the issue and restored normal support operations.

Liquid Web experienced intermittent issues with ticket creation from email submissions for 6.6 hours, caused by a disruption with Google's email services that affected Salesforce's Email-to-Case functionality. Customers could still create tickets through the portal and chat support remained available as alternative contact methods. The issue was resolved after Google's email services stabilized, restoring normal email-to-ticket processing.

Liquid Web experienced a service disruption affecting multiple servers in their Lansing data center (DC3) for 5.7 hours. The issue was isolated to a specific section of the data center, impacting a subset of parent servers and their associated hosts. All affected servers were restored and brought back online, with the incident fully resolved.

Liquid Web implemented additional security enhancements across their managed environment to address the Magento "PolyShell" unrestricted file upload vulnerability, affecting CPanel and Plesk components. The security hardening included strengthened file upload validation, enhanced monitoring and detection mechanisms, stricter execution controls, and broader platform protections. After nearly 14 days of implementation work, all planned security measures were completed and the incident was resolved.

A malformed patch update deployed during Magento 2 "PolyShell" vulnerability mitigation efforts caused Apache to fail to start properly for a subset of Liquid Web customers. This resulted in complete website failures for all affected customers' sites. The incident was resolved after 2.2 hours.