Liquid Web Outage History

Liquid Web major outage · 1 active incident View live status →

There were 21 Liquid Web outages since February 13, 2026 totaling 817h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.liquidweb.com

Major April 22, 2026

MySQL Service Disruption via MySQL-community repo

Detected by Pingoru
Apr 22, 2026, 11:02 AM UTC
Resolved
Apr 25, 2026, 01:09 AM UTC
Duration
2d 14h
Affected: CPanel
Timeline · 5 updates
  1. investigating Apr 22, 2026, 11:02 AM UTC

    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.

  2. identified Apr 22, 2026, 01:25 PM UTC

    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.

  3. identified Apr 23, 2026, 05:08 AM UTC

    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.

  4. monitoring Apr 24, 2026, 05:20 AM UTC

    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.

  5. resolved Apr 25, 2026, 01:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026

DC4 Networking Switch Issues

Detected by Pingoru
Apr 22, 2026, 07:35 AM UTC
Resolved
Apr 23, 2026, 05:55 AM UTC
Duration
22h 19m
Affected: PHX NetworkDC4 - PHX
Timeline · 3 updates
  1. investigating Apr 22, 2026, 07:35 AM UTC

    We are investigating network degradation affecting a subset of servers in our DC4 Data Center. You may experience intermittent latency or connectivity drops. Our Network team is currently analyzing traffic patterns and upstream connections to isolate the issue. Need help? Chat with us or create a ticket via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.

  2. monitoring Apr 22, 2026, 08:30 AM UTC

    Our engineers have fixed the problematic switch, and it is now resolved. Affected services are coming back online, and we are currently monitoring to ensure stability. We appreciate your patience as our team worked to resolve this issue. If you have any further questions or concerns, please feel free to reach out to us via live chat in your customer portal.

  3. resolved Apr 23, 2026, 05:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 21, 2026

Spice Console disruption on Linux virtual machines

Detected by Pingoru
Apr 21, 2026, 08:40 AM UTC
Resolved
Apr 22, 2026, 11:56 PM UTC
Duration
1d 15h
Affected: Cloud DedicatedCloud VPS Hosting
Timeline · 3 updates
  1. investigating Apr 21, 2026, 08:40 AM UTC

    We have identified that Spice Console at my.liquidweb.com/manage.liquidweb.com is not functioning as intended on Linux virtual private servers (VPS), while it is functioning as expected on Windows servers. There are no issues with server stability or up-time related to this, however the servers cannot be reached via spice console. Our engineers are investigating and will provide updates as they become available. If you have any questions or need assistance, please reach out to us via Live Chat or by submitting a support case. We appreciate your patience and will provide updates as progress is made.

  2. identified Apr 21, 2026, 11:47 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 22, 2026, 11:56 PM UTC

    This incident has been resolved. Our Engineering team has fully resolved the Spice Console access issue on Linux VPS Servers. Access has been restored, and workflows are operating normally. Corrective measures have been implemented to address the root cause and help prevent recurrence. Thank you for your patience and understanding throughout this process.

Read the full incident report →

Major April 14, 2026

Apache Service Disruption Caused by immunify360-ea-php-hardened Repository Incompatibility

Detected by Pingoru
Apr 14, 2026, 03:44 PM UTC
Resolved
Apr 15, 2026, 11:48 AM UTC
Duration
20h 4m
Affected: CPanel
Timeline · 4 updates
  1. identified Apr 14, 2026, 03:44 PM UTC

    We are currently investigating an issue affecting a subset of servers where the imunify360-ea-php-hardened repository is incompatible with certain packages installed on the systems. As a result of this incompatible update, Apache service stability may be impacted, and in some cases may require manual intervention to restore service on affected hosts. As an immediate step, we are turning off the imunify360-ea-php-hardened repository on affected systems to help restore service stability. Our engineering team is actively monitoring for this condition and is working closely with cPanel and CloudLinux support to identify the root cause and implement a stable and permanent resolution.

  2. identified Apr 15, 2026, 12:33 AM UTC

    Patching and remediation efforts are ongoing across all affected systems. Our team has successfully stabilized a significant portion of impacted servers by disabling the incompatible repository where necessary, and we are continuing to review and remediate the remaining systems to ensure full stability. We are actively investigating the root cause and working toward a permanent resolution, while closely monitoring system performance and service health throughout this process. We will continue to provide updates as progress is made. If you have any questions or need assistance, please reach out to us via chat or by opening a support case. Thank you for your patience.

  3. monitoring Apr 15, 2026, 02:28 AM UTC

    All identified affected systems have now been remediated, and patching efforts have been completed across the environment. Service stability has been restored, and we have not observed any new issues since remediation was applied. At this time, we will be transitioning to a monitoring phase to continue observing system performance and ensure ongoing stability. Once a patched package is made available by the upstream provider, we will schedule maintenance windows to safely deploy the permanent fix across all systems. We will continue to provide updates if any new developments arise. If you have any questions or need assistance, please reach out to us via chat or by opening a support case. Thank you for your patience.

  4. resolved Apr 15, 2026, 11:48 AM UTC

    All systems remain stable following remediation, and no new issues have been observed during the monitoring phase. We will continue to track updates from the upstream provider, and once a patched package is made available, we will schedule maintenance windows to roll out these changes in the future. Thank you for your patience.

Read the full incident report →

Minor April 10, 2026

Internal Network Outage Impacting Support Services.

Detected by Pingoru
Apr 10, 2026, 03:16 PM UTC
Resolved
Apr 10, 2026, 06:14 PM UTC
Duration
2h 57m
Affected: ChatCasePhone
Timeline · 3 updates
  1. investigating Apr 10, 2026, 03:16 PM UTC

    We are currently experiencing an issue with our internal network. Our Network Engineering team is actively working to resolve this as quickly as possible. This issue does not impact customer websites or services, which remain fully operational. However, there may be delays in support response times during this period. If you have any questions or need assistance, please reach out to us via Live Chat or by submitting a support case. We appreciate your patience and will provide updates as progress is made.

  2. monitoring Apr 10, 2026, 05:36 PM UTC

    Our internal network issue has been mitigated, and services have returned to normal operation. Our Network Engineering team will continue to monitor the environment to ensure stability. Customer websites and services remain fully operational. Support response times are returning to normal. If you continue to experience any issues or need assistance, please reach out to us via Live Chat or by submitting a support case. We appreciate your patience and will provide further updates if necessary.

  3. resolved Apr 10, 2026, 06:14 PM UTC

    This issue has been fully resolved, and all services are operating normally. We have continued to monitor the environment and have not observed any further issues. Customer websites and services remain fully operational, and support response times have returned to normal. If you experience any issues or need assistance, please reach out via Live Chat or by submitting a support case. We appreciate your patience throughout this incident.

Read the full incident report →

Minor April 8, 2026

Issues Creating Tickets from Email

Detected by Pingoru
Apr 08, 2026, 04:41 PM UTC
Resolved
Apr 08, 2026, 11:13 PM UTC
Duration
6h 31m
Affected: Chat
Timeline · 6 updates
  1. investigating Apr 08, 2026, 04:41 PM UTC

    We are currently experiencing intermittent issues with ticket creation for requests submitted via email. Ticket creation through the portal is functioning as expected. Our team is actively investigating the issue. We will share additional updates as they become available. If you need immediate assistance, please submit your request through the portal or contact us via chat. We appreciate your patience and understanding as we work to restore normal service. Thank you.

  2. monitoring Apr 08, 2026, 06:12 PM UTC

    The issue affecting ticket creation for requests submitted via email has been resolved. Ticket creation through both email and the portal is now functioning as expected. Our team will continue to closely monitor the system and will share any further updates if needed. If you experience any issues or need immediate assistance, please contact us via chat or case. We appreciate your patience and understanding. Thank you.

  3. investigating Apr 08, 2026, 06:48 PM UTC

    We are currently experiencing intermittent issues with ticket creation for requests submitted via email. Ticket creation through the portal continues to function as expected. After initial signs of recovery, we have observed that the issue persists. This has been confirmed as related to an ongoing disruption with Salesforce’s Email-to-Case functionality, which may prevent some cases from being created successfully. Our team is actively monitoring the situation and working with Salesforce for further updates. If you experience any issues or need immediate assistance, please contact us via chat or submit a case through the portal. We appreciate your patience and understanding. Thank you.

  4. investigating Apr 08, 2026, 08:18 PM UTC

    We are continuing to follow the issue affecting ticket creation from emails. Salesforce has confirmed that this issue is related to a disruption with a third-party email provider, identified as Google. The provider is currently experiencing delays in receiving and sending emails, which is impacting Salesforce’s Email-to-Case functionality. Salesforce has indicated that their internal systems are operating normally and they are actively monitoring the situation with the third-party provider. We are continuing to track progress closely and will share updates as more information becomes available. If you need immediate assistance, please submit your request through the portal or reach out via chat. We appreciate your patience and understanding as this is being resolved.

  5. monitoring Apr 08, 2026, 09:50 PM UTC

    We are seeing continued improvement in ticket creation from email, with submissions now coming through and working as expected. Our team will continue to monitor to ensure stability remains consistent. If you need immediate assistance, please submit your request through the portal or contact us via chat. We appreciate your patience and understanding. Thank you.

  6. resolved Apr 08, 2026, 11:13 PM UTC

    The issue affecting ticket creation from email has been resolved. Email submissions are now being received and processed successfully, and ticket creation is functioning as expected. If you experience any further issues or need assistance, please submit your request through the portal or contact us via chat. We appreciate your patience and understanding. Thank you.

Read the full incident report →

Minor April 7, 2026

Service disruption on multiple servers- DC3 Lansing

Detected by Pingoru
Apr 07, 2026, 02:17 PM UTC
Resolved
Apr 07, 2026, 07:57 PM UTC
Duration
5h 40m
Affected: DC3 - LAN
Timeline · 3 updates
  1. investigating Apr 07, 2026, 02:17 PM UTC

    We are currently investigating an issue affecting multiple servers in our Lansing data center(DC3). We will provide updates as we learn more. If you have any questions or concerns, please contact a member of our support team via live-chat or case ([email protected]).

  2. monitoring Apr 07, 2026, 03:09 PM UTC

    We experienced an issue impacting a subset of servers within our Lansing data center. Initial investigation indicates the disruption was isolated to a specific section in our data center. All affected parent servers and associated hosts have now been restored and are back online. Our team is continuing to investigate the root cause of this incident. If you continue to experience any issues with your server, please contact our support team for assistance. We appreciate your patience while we worked to resolve this matter.

  3. resolved Apr 07, 2026, 07:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 1, 2026

Security Hardening - Magento “PolyShell” File Upload Vulnerability Enhancements

Detected by Pingoru
Apr 01, 2026, 06:42 PM UTC
Resolved
Apr 15, 2026, 12:10 PM UTC
Duration
13d 17h
Affected: CPanelInterWorxPlesk
Timeline · 3 updates
  1. investigating Apr 01, 2026, 06:42 PM UTC

    Following the actions taken to prohibit execution of files exploiting the Magento “PolyShell” unrestricted file upload vulnerability, our engineering teams are continuing to implement additional security enhancements across our managed environment. These efforts include strengthening file upload validation and execution restrictions, enhancing monitoring and detection mechanisms, and implementing additional hardening measures across Magento platforms. We are also conducting internal reviews to reduce potential attack surfaces and reinforce overall platform security. These proactive improvements reflect our ongoing commitment to maintaining a secure and resilient hosting environment. While the initial issue has been addressed, we are taking additional steps to further strengthen our systems and help prevent future risks. While the additional measures that we have deployed should reduce the risk for potential compromise, we strongly urge that our customers take proactive measures to review and secure their sites If you have any questions or concerns, please reach out to us through the following channels: Live Chat: https://my.liquidweb.com/ Email: [email protected]. We will continue to share updates as these enhancements are completed.

  2. investigating Apr 09, 2026, 01:27 PM UTC

    Our engineering teams have made significant progress in implementing additional security enhancements related to the Magento "PolyShell" unrestricted file upload vulnerability. At this stage, we are nearing completion of all planned mitigation efforts across our managed environment. The measures deployed, including strengthened file upload validation, enhanced malware scanning to detect files, stricter execution controls, and broader platform hardening, have significantly reduced the risk of exploitation. While these mitigations provide strong protection, security is a shared responsibility. We strongly encourage customers to review their Magento installations, ensure all updates and patches are applied, and follow general security best practices to help keep their sites secure. If you have any questions or need assistance, please reach out to us through chat or via case. We will provide further updates if any additional actions are required.

  3. resolved Apr 15, 2026, 12:10 PM UTC

    Our engineering teams have completed the planned security enhancements and hardening efforts related to the Magento "PolyShell" unrestricted file upload vulnerability across our managed environment. With these measures now fully implemented, we consider this incident resolved. As security is a shared responsibility, we recommend that customers review their Magento installations, ensure all updates and patches are applied, and take additional steps to further secure their applications. If you have any questions or require assistance, please reach out via chat or support case.

Read the full incident report →

Notice March 31, 2026

Magento 2 “PolyShell” File Upload Vulnerability efforts

Detected by Pingoru
Mar 31, 2026, 06:55 PM UTC
Resolved
Mar 31, 2026, 09:05 PM UTC
Duration
2h 10m
Timeline · 2 updates
  1. identified Mar 31, 2026, 06:55 PM UTC

    During our continuing efforts to proactively mitigate the recent Magento 2 “PolyShell” File Upload Vulnerability a sub-set of customers received a malformed patch update which caused Apache to not start up properly. For those affected, all websites are failing to load. We apologize for the inconvenience and are working diligently to correct the issue. If you have any questions or concerns, please contact a member of our support team via live-chat, or case ([email protected]).

  2. resolved Mar 31, 2026, 09:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 25, 2026

Infrastucture down issues at Phoenix Data Center

Detected by Pingoru
Mar 25, 2026, 09:44 AM UTC
Resolved
Mar 25, 2026, 08:30 PM UTC
Duration
10h 46m
Affected: DC4 - PHX
Timeline · 5 updates
  1. investigating Mar 25, 2026, 09:44 AM UTC

    We are investigating network performance issues affecting servers in our Phoenix Data Center. You may experience connectivity issues. Our Engineers currently investigating the issue to isolate the cause and restore stability. Need help? Chat with us or create a case via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.

  2. investigating Mar 25, 2026, 10:53 AM UTC

    We are continuing to investigate network performance issues affecting servers in our Phoenix Data Center. Some clients may still experience connectivity issues. Our Engineers are actively working to isolate the cause and restore full stability as quickly as possible. Need help? Chat with us or create a case via my.liquidweb.com . We appreciate your patience and understanding as we work to resolve this issue. Thank you.

  3. monitoring Mar 25, 2026, 12:38 PM UTC

    Servers are fully operational. Our Engineers are still mitigating and monitoring the situation. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or need assistance, please chat with us or create a case via my.liquidweb.com.

  4. monitoring Mar 25, 2026, 03:17 PM UTC

    We are currently performing a planned maintenance window to stabilize and enhance the reliability of our network. During this time, some users may experience intermittent connectivity issues. We appreciate your patience as our team works to complete this maintenance. If you have any questions or need assistance, please chat with us or create a case via my.liquidweb.com.

  5. resolved Mar 25, 2026, 08:30 PM UTC

    We have been monitoring the situation, and everything has remained stable. This incident has now been resolved.

Read the full incident report →

Notice March 24, 2026

Service Disruption Due to Network Switch Failure

Detected by Pingoru
Mar 24, 2026, 05:53 PM UTC
Resolved
Mar 25, 2026, 07:50 AM UTC
Duration
13h 57m
Timeline · 3 updates
  1. investigating Mar 24, 2026, 05:53 PM UTC

    We are currently experiencing a service disruption affecting some servers due to a failed network switch. Our engineering team is actively working to resolve the issue as quickly as possible. We appreciate your patience as our engineers work to restore full service. If you have any further questions or concerns, please contact us at [email protected] or via Live Chat.

  2. monitoring Mar 24, 2026, 06:09 PM UTC

    The issue was caused by a failed network switch, which has now been replaced. Affected services are coming back online, and we are currently monitoring to ensure stability. We appreciate your patience as our team worked to resolve this issue. If you have any further questions or concerns, please feel free to reach out to us via live chat in your customer portal.

  3. resolved Mar 25, 2026, 07:50 AM UTC

    We have been monitoring the situation, and everything has remained stable. This incident has now been resolved.

Read the full incident report →

Minor March 18, 2026

Magento “PolyShell” File Upload Vulnerability

Detected by Pingoru
Mar 18, 2026, 06:32 PM UTC
Resolved
Mar 20, 2026, 12:29 AM UTC
Duration
1d 5h
Affected: CPanelInterWorxPlesk
Timeline · 3 updates
  1. investigating Mar 18, 2026, 06:32 PM UTC

    We are aware of recent reports regarding a potential unrestricted file upload vulnerability, commonly referred to as “PolyShell”, affecting Magento and Adobe Commerce. At this time, our teams are actively reviewing server environments to assess any potential impact and determine whether any systems/customer sites may be affected. We will provide further updates as more information becomes available. If you have any questions or concerns. You can reach us through the following channels: Live Chat: https://my.liquidweb.com/ Email: [email protected]

  2. monitoring Mar 19, 2026, 12:15 AM UTC

    Following our investigation, we are implementing a mitigation measure for Magento 2 installations on our Managed hosting platform for which we have access between 21:00 EDT and 23:00 EDT tonight. We have sent a ticket to all customers with servers where mitigations will be applied. For these customers, we will be deploying an .htaccess file to block direct web-request access to the uploads directory. This change is expected to have minimal impact. If your site has been customised to serve or process requests through the upload directory, this functionality will be affected. Please contact us with any questions. Customers with Magento2 websites who did not receive a ticket should review the Sansec article below announcing this vulnerability and apply the recommended changes: https://sansec.io/research/magento-polyshell If you have any questions or concerns. You can reach us through the following channels: Live Chat: https://my.liquidweb.com/ Email: [email protected] We appreciate your patience and understanding.

  3. resolved Mar 20, 2026, 12:29 AM UTC

    We have taken steps to prohibit execution of files exploiting the "PolyShell" unrestricted file upload vulnerability on a subset of servers in our environment. We have sent a ticket to all customers we've protected identifying the servers and paths involved. If you have any questions or concerns. You can reach us through the following channels: Live Chat: https://my.liquidweb.com/ Email: [email protected]

Read the full incident report →

Major March 18, 2026

An issue reported with provisioning operations.

Detected by Pingoru
Mar 18, 2026, 06:34 AM UTC
Resolved
Mar 19, 2026, 01:32 PM UTC
Duration
1d 6h
Affected: Cloud DedicatedCloud VPS Hosting
Timeline · 6 updates
  1. investigating Mar 18, 2026, 06:34 AM UTC

    On our Cloud VPS and Cloud Dedicated hosting platforms, certain provisioning workflows are failing to execute hard reboots and might affect resize, backup process, and firewall rule updates. The servers themselves are still online, but a provisioning workflow will be affected by this issue. Our Engineers are investigating the issue, and we will share the updates here. Need help? Chat with us or create a ticket via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.

  2. investigating Mar 18, 2026, 08:07 AM UTC

    We have expanded the scope of our investigation as we identify impacts on core workflows, specifically on; Order Processing: New orders are being accepted, but cannot be processed at this time. Storm Workflows: All active provisioning workflows are currently stalled. Our engineering team is actively investigating the root cause. Further updates will be posted here as they become available.

  3. identified Mar 18, 2026, 12:41 PM UTC

    Our Engineers have identified the issue and are currently troubleshooting the connectivity failure where Provisioning servers and Storm parents are unable to connect to their respective RabbitMQ (RMQ) hubs. We appreciate your patience and understanding as we work to restore this service. Thank you. Need help? Chat with us or create a ticket via my.liquidweb.com.

  4. monitoring Mar 18, 2026, 02:18 PM UTC

    Update: Our Engineers have identified the root cause of the earlier connectivity issue impacting Provisioning servers and Storm parent communication with RabbitMQ (RMQ) hubs. At this time, connectivity has been restored and workflows are progressing. Our team continues to monitor the environment closely to ensure ongoing stability. We appreciate your patience and understanding throughout this process. Need help? Chat with us or create a ticket via my.liquidweb.com.

  5. monitoring Mar 19, 2026, 12:08 AM UTC

    Our Engineering team has identified and are working on fully resolving the root cause of the earlier connectivity issue affecting Provisioning servers. Services have been restored, and workflows are now progressing normally. We are continuing to actively monitor the environment to ensure ongoing stability and performance. Thank you for your patience and understanding throughout this process. Need help? Chat with us or create a ticket via my.liquidweb.com.

  6. resolved Mar 19, 2026, 01:32 PM UTC

    Our Engineering team has fully resolved the earlier connectivity issue that was impacting Provisioning servers. All services have been restored, and workflows are operating normally. Corrective measures have been implemented to address the root cause and help prevent recurrence. Thank you for your patience and understanding throughout this process. If you need further assistance, please reach out via Live Chat or open a ticket through the my.liquidweb.com portal. Thank you

Read the full incident report →

Major March 16, 2026

ClamAV Service Disruption

Detected by Pingoru
Mar 16, 2026, 05:22 PM UTC
Resolved
Mar 19, 2026, 01:46 PM UTC
Duration
2d 20h
Affected: CPanel
Timeline · 5 updates
  1. investigating Mar 16, 2026, 05:22 PM UTC

    We are currently investigating an issue affecting the ClamAV service, where clamd restarts may fail due to a problematic signature update. Our System Engineering team is actively working to identify the root cause and implement a fix. This issue may affect Maldet scans and cause mail delivery failures if the ClamAV service is not running.

  2. identified Mar 16, 2026, 06:07 PM UTC

    We have identified the cause of the issue affecting the ClamAV service. A recent malware signature update introduced an invalid entry in the ClamAV signature database, which can prevent the clamd service from restarting successfully. Our team is currently applying a signature database refresh on affected servers to remove the invalid entry and restore normal operation of the ClamAV service. We are currently applying this fix across all affected servers and will provide another update once the process is completed.

  3. identified Mar 17, 2026, 06:06 AM UTC

    We have automated the ClamAV signature database updates for all impacted servers. Deployment is currently underway, and we will provide another update once the process is completed. If you have any questions, please chat with us or create a support ticket via my.liquidweb.com. We appreciate your patience and understanding.

  4. identified Mar 18, 2026, 01:55 PM UTC

    We have automated the ClamAV signature database updates for all impacted servers, and the deployment is currently still in progress. Based on the results so far, systems appear to have already received the updated signatures and are functioning as expected. We are continuing to monitor the automation to ensure completion across all hosts. We will provide a final update once the process has fully completed. If you have any questions, please chat with us or create a support ticket via my.liquidweb.com. We appreciate your patience and understanding.

  5. resolved Mar 19, 2026, 01:46 PM UTC

    The ClamAV signature updates have been successfully applied, and systems are operating as expected. We will continue to monitor as part of normal operations. If you have any questions, please chat with us or create a support ticket via my.liquidweb.com. We appreciate your patience and understanding.

Read the full incident report →

Notice March 6, 2026

WordPress: W3 Total Cache Vulnerability CVE-2026-27384

Detected by Pingoru
Mar 06, 2026, 06:21 PM UTC
Resolved
Mar 10, 2026, 06:28 AM UTC
Duration
3d 12h
Affected: Cloud DedicatedCloud VPS Hosting
Timeline · 4 updates
  1. investigating Mar 06, 2026, 06:21 PM UTC

    We have been made aware of a critical vulnerability, CVE-2026-27384, affecting versions equal to or less than 2.9.1, of the WordPress W3 Total Cache plugin. Recommended Action We strongly encourage all clients to update any sites running versions 2.9.1 or older to the patched version 2.9.2 immediately. Current Status Exploit Availability: There are currently no known public Proof of Concept (PoC) exploits for this vulnerability. Our team is assessing the impact on our managed sites and evaluating the deployment of necessary patches across our managed systems. We will provide further updates as they become available. If you have any questions or require assistance with the update, please reach out to our support team.

  2. identified Mar 06, 2026, 08:20 PM UTC

    We have been made aware of a critical vulnerability, CVE-2026-27384, affecting versions equal to or less than 2.9.1, of the WordPress W3 Total Cache plugin. Recommended Action We strongly encourage all clients to update any sites running versions 2.9.1 or older to the patched version 2.9.2 immediately. Current Status Exploit Availability: There are currently no known public Proof of Concept (PoC) exploits for this vulnerability. Our team is currently applying patches to instances of outdated W3TC plugins that we were able to identify on our managed systems. You may receive server login notifications from internal IPs as we patch detected W3TC installations. We will provide further updates as they become available. If you have any questions or require assistance with the update, please reach out to our support team.

  3. monitoring Mar 09, 2026, 08:10 AM UTC

    Update Our team has now applied patches to all instances of the W3 Total Cache plugin across our managed systems where the update was possible based on the current WordPress and PHP version requirements. In some environments, the patch could not be applied as the underlying WordPress or PHP versions do not meet the minimum compatibility requirements for the updated plugin, or due to other configuration limitations. These instances will require updates at the application or environment level before the plugin can be upgraded. For cases where the patch could not be applied for the reasons mentioned above, we will be reaching out to the affected clients directly with additional details and recommended next steps. Recommended Action Clients with sites running W3 Total Cache version 2.9.1 or earlier are strongly advised to update to the patched version 2.9.2 as soon as possible. Where the plugin update is not currently possible due to WordPress or PHP version constraints, we recommend upgrading WordPress and/or PHP first, and then completing the update to W3 Total Cache version 2.9.2 or later at the earliest opportunity. If you require assistance with upgrading your environment or applying the update, please contact our support team, who will be happy to assist. We will continue to monitor this matter and will provide further updates here should any additional actions be required.

  4. resolved Mar 10, 2026, 06:28 AM UTC

    Update Our team has completed patching the W3 Total Cache plugin across all managed systems where the update was possible based on the current WordPress and PHP version requirements. In cases where the patch could not be applied due to compatibility constraints or other configuration limitations, the affected clients have been contacted directly with the relevant details and recommended next steps. In most instances, this involves upgrading the underlying WordPress and/or PHP versions before updating the plugin. At this time, the planned remediation work has been completed and this matter is considered resolved. Recommended Action Clients with sites running W3 Total Cache version 2.9.1 or earlier are encouraged to update to the patched version 2.9.2 as soon as possible. Where the update is not currently possible due to WordPress or PHP version constraints, please upgrade those components first and then proceed with the plugin update. If you require assistance with completing the update, please contact our support team. Thank you for your patience and understanding while we worked to address this matter.

Read the full incident report →

Minor February 27, 2026

Networking Instability

Detected by Pingoru
Feb 27, 2026, 12:09 AM UTC
Resolved
Feb 27, 2026, 03:54 PM UTC
Duration
15h 45m
Affected: DC2 - LANDC3 - LAN
Timeline · 3 updates
  1. investigating Feb 27, 2026, 12:09 AM UTC

    We are currently investigating reports of network instability impacting a small subset of IP addresses on our network. Our network engineers are actively engaged and reviewing the situation to identify the root cause. We will provide further updates as more information becomes available.

  2. monitoring Feb 27, 2026, 12:36 AM UTC

    We were able to identify the impacted range and have implemented proper mitigation protocols. We are seeing stability return across our network. We will continue to monitor the situation to ensure that the full impact has been resolved. If you notice any issues with your server please reach out to our support team and they will be happy to assist.

  3. resolved Feb 27, 2026, 03:54 PM UTC

    The network instability affecting a small subset of IP addresses in DC2 and DC3 has been fully resolved. Our network engineers identified the impacted range and implemented the necessary mitigation measures to restore normal connectivity and performance.

Read the full incident report →

Major February 24, 2026

Storm Switch Down Lansing (DC3)

Detected by Pingoru
Feb 24, 2026, 09:23 AM UTC
Resolved
Feb 24, 2026, 11:24 AM UTC
Duration
2h
Affected: LAN NetworkDC3 - LAN
Timeline · 4 updates
  1. investigating Feb 24, 2026, 09:23 AM UTC

    A possible switch failure has been reported at our DC3 location. Our networking team is currently investigating and will provide an update once more information has been gathered. Some customers in this location may experience an outage. Please contact Support if you have any questions or notice any anomalies.

  2. identified Feb 24, 2026, 09:30 AM UTC

    Our team is currently working on replacing the faulty switch. We will keep this space updated as soon as the work is completed.

  3. monitoring Feb 24, 2026, 10:15 AM UTC

    Thank you for your time and patience. Our engineers have successfully replaced the switch and recovered the server access. We are closely monitoring the situation now. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  4. resolved Feb 24, 2026, 11:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2026

Acronis Portal Degraded Performance.

Detected by Pingoru
Feb 23, 2026, 10:20 PM UTC
Resolved
Feb 25, 2026, 01:46 AM UTC
Duration
1d 3h
Affected: Management Portal
Timeline · 7 updates
  1. investigating Feb 23, 2026, 10:20 PM UTC

    We would like to notify you that Acronis Cyber Protect Cloud in the USA (US5) data center is degraded. Acronis Cloud team is working on the issue resolution and will keep notifying you on the service status. Service impact: Some customers might be unable to reach Acronis Web Restore, Acronis Cyber Protection Console and Management Console.

  2. identified Feb 23, 2026, 11:26 PM UTC

    Acronis Cloud team is actively working on the issue resolution and we will keep notifying you on the service status.

  3. identified Feb 24, 2026, 03:45 AM UTC

    Acronis Cloud team is actively working on the issue resolution and we will keep notifying you on the service status.

  4. monitoring Feb 24, 2026, 07:09 AM UTC

    Acronis Cloud team has implemented a fix and resolved the issue. We are currently monitoring the results to ensure stability. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  5. identified Feb 24, 2026, 02:40 PM UTC

    We are observing a recurrence of the issue affecting Acronis Cyber Protect Cloud in the USA (US5) data center; the Acronis Cloud team is actively investigating, and some customers may continue to experience intermittent access issues to Web Restore, Cyber Protection Console, and Management Console. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  6. monitoring Feb 24, 2026, 04:03 PM UTC

    The Acronis Cloud team has applied corrective measures, and services have been restored. We are actively monitoring the platform to confirm sustained stability and performance. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  7. resolved Feb 25, 2026, 01:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 22, 2026

DDOS Attack on cloudhost-323832-us-midwest-1-nxcli-net

Detected by Pingoru
Feb 22, 2026, 10:24 AM UTC
Resolved
Feb 23, 2026, 07:19 PM UTC
Duration
1d 8h
Affected: Cloud VPS Hosting
Timeline · 5 updates
  1. investigating Feb 22, 2026, 10:24 AM UTC

    We have been alerted to a DDoS attack targeting cloudhost-323832-us-midwest-1-nxcli-net. Our network engineers are engaged and we will update with further details regarding mitigation as soon as we are able. If you have any further questions or concerns, please feel free to reach out to us at [email protected] or call us at 866-639-2377, 313-279-0722 (international).

  2. investigating Feb 22, 2026, 10:26 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 22, 2026, 10:27 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Feb 22, 2026, 11:04 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Feb 23, 2026, 07:19 PM UTC

    Following the mitigation efforts, we are no longer observing any signs of malicious or abnormal traffic, and the server is operating normally. All services remain stable at this time. If you have further questions or concerns, please contact us at [email protected] or via Live chat.

Read the full incident report →

Minor February 15, 2026

Service disruption on the parent server: host8233.c.lan.xvps.liquidweb.com | Lansing DC3

Detected by Pingoru
Feb 15, 2026, 07:01 AM UTC
Resolved
Feb 15, 2026, 12:01 PM UTC
Duration
5h
Affected: DC3 - LAN
Timeline · 3 updates
  1. investigating Feb 15, 2026, 07:01 AM UTC

    We have identified a Service disruption with several hosts under the Parent: host8233.c.lan.xvps.liquidweb.com within our Lancing DC3. Our engineers are working on resolving the problem as soon as possible. If you have any further questions or concerns, please feel free to reach out to us via live chat in your customer portal (https://my.liquidweb.com/) or via case ([email protected]),

  2. monitoring Feb 15, 2026, 11:13 AM UTC

    We have successfully resolved the issue on the parent server: host8233.c.lan.xvps.liquidweb.com. We are continuing to monitor the systems closely to ensure ongoing stability. If you have any questions or concerns, please feel free to reach out via chat or case. Thank you for your continued patience.

  3. resolved Feb 15, 2026, 12:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 13, 2026

Issue deploying new servers within London Data Center

Detected by Pingoru
Feb 13, 2026, 09:11 PM UTC
Resolved
Feb 14, 2026, 03:00 AM UTC
Duration
5h 49m
Timeline · 3 updates
  1. investigating Feb 13, 2026, 09:11 PM UTC

    We are investigating a networking issue that is preventing new server deployments within our London Data Center. Existing customer servers are not impacted. Need help? Chat with us or create a ticket via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.

  2. monitoring Feb 13, 2026, 10:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 14, 2026, 03:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Liquid Web downtime and outages?

Pingoru polls Liquid Web's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Liquid Web reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Liquid Web alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Liquid Web for free

5 free monitors · No credit card required