Liquid Web Outage History

Started May 27, 2026, 07:58 PM UTC· resolved May 27, 2026, 11:52 PM UTC

1. investigating May 27, 2026, 07:58 PM UTC

   We are investigating an issue preventing customers from reaching support via Phone. Please use Live Chat or open a Support Case at my.liquidweb.com for immediate assistance while we restore the phone service. We appreciate your patience and understanding as we work to restore this service. Thank you.

2. monitoring May 27, 2026, 08:09 PM UTC

   Our phone system is now back online, and agents should be able to connect and accept calls. We will continue to monitor the system to ensure stability. Thank you for your continued patience.

3. resolved May 27, 2026, 11:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 25, 2026, 07:17 PM UTC· resolved May 26, 2026, 12:29 AM UTC

1. identified May 25, 2026, 07:17 PM UTC

   A recently disclosed vulnerability (CVE-2026-48172) in the LiteSpeed user-end cPanel plugin allows an unprivileged user to escalate to root privileges in plugin versions between v2.3 and v2.4.4. This issue has been classified as high severity. Public reports suggest the vulnerability was being exploited in the wild in May 2026, and indicators of compromise have been published. On May 19th cPanel issued a separate update which disabled and removed the plugin. This vulnerability is patched in v2.4.7 of the user-end plugin and v5.3.1.0 of the WHM plugin (which bundles the user-end plugin). Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-48172 https://blog.litespeedtech.com/2026/05/21/security-update-for-litespeed-cpanel-plugin/ https://support.cpanel.net/hc/en-us/articles/40599423437079-Security-LiteSpeed-plugin-automatically-removed-during-nightly-update-May-19-2026 Status Our security and operations teams are completing an assessment of our infrastructure and will force a upcp update today for all systems we are able to reach. We plan to review for Indicators of Compromise following the updates. Customer Guidance Customers managing their own systems or using unmanaged services should ensure they have applied the latest security updates or have removed the plugin. Customers should also review their systems for indicators of compromise using the information provided in the LiteSpeed blog article. Should you need any assistance or have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: [email protected] We will continue monitoring this vulnerability and will provide updates if new information becomes available.

2. resolved May 26, 2026, 12:29 AM UTC

   Status Update Our security and operations teams completed the assessment of our infrastructure, which forcd a upcp update today for all systems we were able to reach. We also reviewed environments for the indicators of compromise noted in the LiteSpeed article below. We will address any findings via a support ticket. We are resolving this incident at this time. Customer Guidance Customers are strongly encouraged to ensure they are running the updated version of the LiteSpeed plugin and to review their systems for the indicators of compromise. If our team does not have access to your system because it is unmanaged, self-managed, or access has been updated but not shared with Liquid Web, then we would not have been able to reach your system in order to apply updates or check for indicators of compromise. If you have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: [email protected]

Read the full incident report →

Started May 24, 2026, 04:47 PM UTC· resolved May 25, 2026, 02:12 PM UTC

1. investigating May 24, 2026, 04:47 PM UTC

   We are investigating an issue preventing customers from accessing the portal through login.liquidweb.com. Updates are forthcoming as more information becomes available. Need help? Chat with us or contact Support for assistance. We appreciate your patience and understanding as we work to restore portal access. Thank you.

2. investigating May 24, 2026, 05:56 PM UTC

   We are continuing to investigate the issue impacting access to the portal through login.liquidweb.com. While the site may be loading for some users, our teams are still reviewing the issue and working to confirm full service stability. Updates will be provided as more information becomes available. Thank you for your patience while we continue working toward a resolution.

3. monitoring May 24, 2026, 06:38 PM UTC

   Access to the portal through login.liquidweb.com has been restored, and the site is now loading successfully. Our teams have implemented a fix and are continuing to monitor the service to ensure stability. We will provide additional updates if any further issues are identified. Thank you for your patience while we worked to restore access.

4. resolved May 25, 2026, 02:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 11, 2026, 10:12 PM UTC· resolved Jun 06, 2026, 09:50 PM UTC

1. identified May 11, 2026, 10:12 PM UTC

   A recently disclosed Linux vulnerability (CVE-2026-31431), sometimes referred to as “Copy Fail,” affects certain Linux distributions and may allow a local, unprivileged user to escalate privileges under specific conditions. This issue has been classified as high severity. Status Our security and operations teams have completed an assessment of our infrastructure and have applied all relevant vendor patches and mitigations to affected systems. Impact No evidence of exploitation has been identified within our environment Systems under our management have been patched or otherwise mitigated Customer Guidance Customers managing their own systems or using unmanaged services should ensure they have applied the latest security updates provided by their Linux distribution and review any related vendor advisories. We will continue monitoring this vulnerability and will provide updates if new information becomes available.

2. resolved Jun 06, 2026, 09:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 08:56 PM UTC· resolved May 09, 2026, 01:16 AM UTC

1. investigating May 08, 2026, 08:56 PM UTC

   We have been made aware of an incident that is affecting Let's Encrypt. The third party SSL provider is currently not issuing SSL certificates as they investigate the issue further. More information is available at at Let's Encrypts status page here: https://letsencrypt.status.io/ If you have any additional questions please reach out to our support team and we will be happy to assist

2. monitoring May 08, 2026, 09:09 PM UTC

   Let's Encrypt has updated their status post indicating that they are resuming their typical issuance of certificates. We will continue to monitor to see if there are any changes in their status going forward

3. resolved May 09, 2026, 01:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 28, 2026, 06:45 PM UTC· resolved Jul 23, 2026, 07:52 PM UTC

1. investigating Apr 28, 2026, 06:45 PM UTC

   We are actively responding to a critical vulnerability affecting all versions of cPanel & WHM. This vulnerability impacts the authentication process and could allow unauthorized access if left unmitigated. More information from cPanel is available here: https://support.cpanel.net/hc/en-us/articles/40073787579671-Critical-Vulnerability-with-cPanel-WHM-Login-Authentication Our team is working alongside vendor guidance and implementing proactive safeguards to protect environments. As an immediate precaution, we have temporarily restricted access to cPanel/WHM interfaces on the following ports 2082, 2083, 2086, and 2087. Restricted access will remain in place until a patch is developed and deployed. This action is being taken to prevent potential unauthorized access while a permanent fix is finalized. Impact: -Restricting access to cPanel/WHM Ports via a network firewall block. During this time customers will not be able to login to either WHM or cPanel unless they use a Cloud VPN Connection. -No impact to hosted websites, applications, email or services. We are closely monitoring the official patch release from cPanel and will deploy it as quickly as possible. Once mitigations are no longer required, normal access will be restored. Until a patch is released by cPanel customers will need to utilize a Cloud VPN connection to access WHM or cPanel, or reach out to support via live chat or ticket for assistance WHM or cPanel assistance. Instructions on how to create a Cloud VPN user can be found here: https://www.liquidweb.com/help-docs/portal/account/account-security/setting-up-your-cloud-vpn/ If you require access to cPanel and WHM please feel free to reach out to us via chat or open up a support ticket with your request and we will be happy to assist you. No additional action is required at this time. We will provide additional updates to this status page as more information is made available.

2. investigating Apr 28, 2026, 08:12 PM UTC

   A brief configuration issue in our Ashburn (NTT) data center caused an un-intended disruption to outbound network traffic. Customers with servers in this location may have experienced intermittent connectivity or downtime lasting approximately 10 minutes. Our team quickly identified and corrected the issue. All services have since been restored and are functioning normally. We continue to restrict access to cPanel/WHM interfaces on ports 2082, 2083, 2086, and 2087 across our data centers until a patch is released by cPanel. If you need assistance with any cPanel/WHM items please reach out to support through live chat or a ticket. We will provide additional updates to this status page as more information is made available.

3. investigating Apr 28, 2026, 09:13 PM UTC

   cPanel has disclosed that the additional cPanel-provided services Webmail and Web Disk are impacted by this vulnerability. Out of an abundance of caution, and based on cPanel’s current recommendation, we are implementing temporary protective changes on servers hosted on our network. Temporary changes being implemented: -Blocking access to ports related to cPanel services: WHM: 2082 / 2083 cPanel: 2086 / 2087 Webmail: 2096 / 2097 Web Disk: 2077 / 2078 -Temporarily disabling cpsrvd, which is the web wrapper for cPanel web services.As a result, cPanel, WHM, Webmail, Web Disk, and related cPanel services will be inaccessible, including over Cloud VPN connections. These changes do not impact websites, email delivery, databases, or Apache functionality. Customers who normally access email through Webmail can still access email by using a mail client. Setup instructions are available here: https://www.liquidweb.com/help-docs/email/mail-clients/setup-an-email-client/ These temporary restrictions will be reverted as soon as cPanel releases a patch addressing the critical vulnerabilities. Additional information from cPanel is available here: https://support.cpanel.net/hc/en-us/articles/40073787579671-Critical-Vulnerability-with-cPanel-WHM-Login-Authentication If you have further questions or need assistance, please contact our Support team.

4. identified Apr 28, 2026, 09:57 PM UTC

   Update: cPanel Patch Deployment Underway cPanel has released a patch to address the authentication vulnerability that was identified today. Our engineers are currently working on deploying this patch across eligible cPanel services. Once the patch is successfully applied, we will take the following actions: Remove the network-level firewall blocks. WHM: 2082 / 2083 cPanel: 2086 / 2087 Webmail: 2096 / 2097 Web Disk: 2077 / 2078 Re-enable the cPanel web service (cpsrvd). More information from cPanel is available here: https://support.cpanel.net/hc/en-us/articles/40073787579671-Critical-Vulnerability-with-cPanel-WHM-Login-Authentication We appreciate your continued patience as we complete these actions to restore full service. If you have any questions in the meantime, please contact us for assistance.

5. identified Apr 29, 2026, 05:32 AM UTC

   Update: cPanel patch implemented. We have deployed cPanel’s latest patch across eligible servers. cPanel versions: TIER 11.110 WAS: 11.110.0.96 NOW: 11.110.0.97 TIER 11.118 WAS: 11.118.0.61 NOW: 11.118.0.63 TIER 11.126 WAS: 11.126.0.53 NOW: 11.126.0.54 TIER 11.132 WAS: 11.132.0.27 NOW: 11.132.0.29 TIER 11.134 WAS: 11.134.0.19 NOW: 11.134.0.20 TIER 11.136 WAS: 11.136.0.4. NOW: 11.136.0.5 We are currently evaluating servers that failed to update (or had pre-existing update blockers), and we will be sending further updates as soon as more information is available. Network-level firewall blocks for cPanel, WHM, webmail, and webdisk ports remain in place at this time. We appreciate your continued patience as we complete these actions to restore full service. If you have any questions in the meantime, please contact us for assistance.

6. identified Apr 29, 2026, 01:08 PM UTC

   The cPanel patch remains deployed across eligible systems, and network-level firewall restrictions for cPanel, WHM, webmail, and web disk ports are still in place at this time. Our team is reconvening this morning to review overall progress, evaluate any remaining update exceptions, and determine the appropriate timing for safely removing these access restrictions. We will provide additional updates as soon as more information becomes available. We appreciate your continued patience as we work toward restoring full access. If you have any issues in the meantime, please contact our support team for assistance.

7. identified Apr 29, 2026, 04:44 PM UTC

   cPanel patches have been deployed across all eligible servers. As mitigation measures are now in place for the majority of systems, we have lifted the temporary network-level blocks that were implemented to prevent unauthorized access. For servers ineligible for the patch, we are applying temporary protections at the server level using CSF. As part of this step, CSF rules are being implemented to restrict access to the affected ports. This approach allows access to be controlled by whitelisting trusted client IP addresses while maintaining appropriate security protections. We strongly recommend that all customers update to the latest version of cPanel & WHM as soon as possible to ensure full protection against this vulnerability. For servers not eligible for the patch, we will be reaching out shortly with guidance on what options are available to secure your environment. We will continue to closely monitor the situation and take any additional steps necessary to maintain system security and stability. If you need assistance with updating cPanel or have any concerns, please contact our Support team.

8. identified Apr 29, 2026, 10:15 PM UTC

   cPanel patches have been deployed across all eligible servers. For a subset of systems running versions that cannot be updated, additional security protections are being implemented to allow continued access to cPanel services while maintaining necessary safeguards. To ensure ongoing protection, cPanel service ports will remain restricted on these systems. Customers who prefer to fully restore standard access will need to update to a supported version of cPanel. Our team will be reaching out with guidance on available options. If you have questions or need assistance, please contact Support.

9. identified May 03, 2026, 09:04 PM UTC

   Support chat is temporarily unavailable while our support team focuses on responding to the backlog of tickets related to the recent cPanel vulnerability. Our teams are working as quickly as possible to review and respond to open tickets. If you already have a ticket open, please avoid submitting duplicate tickets, as this can increase overall support volume and slow our ability to respond to impacted customers. cPanel security patches have been deployed across eligible servers, and network restrictions have been removed. For servers not eligible for the patch, additional protections are in place that may limit access to certain cPanel services. Thank you for your patience while we continue working through these requests.

10. identified May 06, 2026, 12:03 AM UTC

    Update: Support through chat remains temporarily unavailable while our teams continue working through elevated ticket volume related to the recent cPanel vulnerability. Our teams are actively reviewing and responding to open tickets as quickly as possible. While progress has been made, response times may still be longer than usual. If you already have a ticket open, please avoid submitting duplicate requests, as this can increase overall volume and delay responses. We will continue to monitor volumes and restore chat support once conditions allow. Thank you for your continued patience while we work through these requests.

11. identified May 07, 2026, 04:13 AM UTC

    We are diligently working through an elevated ticket volume related to the recent cPanel vulnerability. Chat will remain temporarily unavailable during this time. During this time our responses may be delayed. If you already have a ticket open, please avoid submitting duplicate requests, as this can increase overall volume and delay progress. Thank you for your continued patience while we work through this.

12. identified May 07, 2026, 09:22 PM UTC

    We continue to work through securing and patching services due to the recent cPanel vulnerability. Chat Support will remain temporarily unavailable as we continue to work through patching affected servers. If you have an active case, please try to avoid opening duplicate cases by keeping all communication to the open thread. Our Support team is working hard to respond to all active cases. Thank you for your continued patience while we work through this.

13. identified May 12, 2026, 02:45 PM UTC

    Our teams continue to work diligently through elevated support volume related to the recent cPanel vulnerability and the associated remediation efforts. We are making strong progress in reviewing and resolving the cases associated with this incident, while continuing patching and security mitigation activities across affected environments. Our teams are also actively working through the remaining systems requiring additional remediation or upgrade planning. To allow our staff to remain focused on active recovery efforts and customer assistance, support chat will remain temporarily unavailable at this time. Customers with existing support cases are kindly encouraged to continue communication through their open ticket rather than submitting duplicate requests, as this helps us respond to all customers as efficiently as possible. Although overall ticket volume has improved, response times may still be longer than usual while we continue working through the remaining requests and follow-up actions. We are still working diligently on restoring servers where compromises were evident. During this time public access to those servers may be limited or removed. If you feel your server may be blocked un-necessarily, please reach out to our support team to have them review that. We sincerely appreciate your continued patience, understanding, and cooperation as we work to fully complete these efforts and restore normal support operations. If you have questions or need assistance, please contact Support.

14. identified May 18, 2026, 06:00 PM UTC

    While our teams continue to advance remediation efforts following the cPanel vulnerability (CVE-2026-41940), significant progress has been made in restoring essential systems. We are diligently addressing the remaining requests and follow-up actions; however, please be aware that response times may remain extended. Your continued patience is greatly appreciated as we work through this process. Live Chat Support will begin to be available once again starting today, operating with partial staff. To ensure efficient support and allow our teams to focus on active recovery: - Please use live chat only for new, non-CVE issues. - Live chat staff are currently unable to provide status updates on existing restore work. - If you are awaiting a server restore, or need assistance throughout the restore process, please request an update within your existing support ticket. We sincerely appreciate your continued patience, understanding, and cooperation as we work to fully complete these efforts and restore normal support operations.

15. monitoring Jul 21, 2026, 03:05 PM UTC

    At this time all known affected systems have been addressed and are either fully remediated or being actively addressed. Normal support operations, including Live Chat Support, have resumed. If you experience any further issues with your environments or if you have any further questions or concerns, please open a support ticket or reach out to our support team. We sincerely appreciate your patience, cooperation, and understanding throughout our mitigation and recovery efforts.

16. resolved Jul 23, 2026, 07:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 11:02 AM UTC· resolved Apr 25, 2026, 01:09 AM UTC

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 →

Started Apr 22, 2026, 07:35 AM UTC· resolved Apr 23, 2026, 05:55 AM UTC

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 →

Started Apr 21, 2026, 08:40 AM UTC· resolved Apr 22, 2026, 11:56 PM UTC

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 →

Started Apr 14, 2026, 03:44 PM UTC· resolved Apr 15, 2026, 11:48 AM UTC

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 →

Started Apr 10, 2026, 03:16 PM UTC· resolved Apr 10, 2026, 06:14 PM UTC

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 →

Started Apr 08, 2026, 04:41 PM UTC· resolved Apr 08, 2026, 11:13 PM UTC

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 →

Started Apr 07, 2026, 02:17 PM UTC· resolved Apr 07, 2026, 07:57 PM UTC

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 →

Started Apr 01, 2026, 06:42 PM UTC· resolved Apr 15, 2026, 12:10 PM UTC

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 →

Started Mar 31, 2026, 06:55 PM UTC· resolved Mar 31, 2026, 09:05 PM UTC

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 →

Started Mar 24, 2026, 05:53 PM UTC· resolved Mar 25, 2026, 07:50 AM UTC

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 →

Started Mar 18, 2026, 06:32 PM UTC· resolved Mar 20, 2026, 12:29 AM UTC

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 →

Started Mar 18, 2026, 06:34 AM UTC· resolved Mar 19, 2026, 01:32 PM UTC

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 →

Started Mar 16, 2026, 05:22 PM UTC· resolved Mar 19, 2026, 01:46 PM UTC

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 →

Started Mar 06, 2026, 06:21 PM UTC· resolved Mar 10, 2026, 06:28 AM UTC

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 →

Started Feb 27, 2026, 12:09 AM UTC· resolved Feb 27, 2026, 03:54 PM UTC

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 →

Started Feb 24, 2026, 09:23 AM UTC· resolved Feb 24, 2026, 11:24 AM UTC

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 →

Started Feb 23, 2026, 10:20 PM UTC· resolved Feb 25, 2026, 01:46 AM UTC

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 →

Started Feb 22, 2026, 10:24 AM UTC· resolved Feb 23, 2026, 07:19 PM UTC

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 →

Started Feb 15, 2026, 07:01 AM UTC· resolved Feb 15, 2026, 12:01 PM UTC

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 →