Liquid Web Outage History

Started Oct 26, 2026, 06:17 PM UTC· resolved Oct 27, 2026, 01:20 PM UTC

1. investigating Oct 26, 2026, 06:17 PM UTC

   We are currently investigating reported issues with Cloud Object Storage and Block Storage. Our engineering team is engaged and is reviewing the system to determine the cause.

2. monitoring Oct 26, 2026, 06:52 PM UTC

   A fix has been implemented and we are monitoring the results

3. resolved Oct 27, 2026, 01:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 21, 2026, 03:33 PM UTC· resolved Oct 26, 2026, 06:12 PM UTC

1. investigating Oct 21, 2026, 03:33 PM UTC

   We are currently investigating reports of service disruptions affecting Apache web servers. Initial findings indicate this is linked to a compatibility issue with mod_security following a recent release. Our engineering team is evaluating the impact and actively working on a resolution.

2. monitoring Oct 21, 2026, 05:44 PM UTC

   We have identified the issue and implemented a fix. Affected servers are now running and we will monitor the situation to ensure that the issue is fully resolved

3. resolved Oct 26, 2026, 06:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2026, 01:53 PM UTC· resolved Oct 21, 2026, 11:26 AM UTC

1. identified Oct 20, 2026, 01:53 PM UTC

   During scheduled evening maintenance, our operations team began deploying security patches to update server kernels to address the CVE-2026-74580 (vghost kernel vulnerability). Following the application of the patch and server reboots we identified a subset of our parent servers did not come up cleanly. Our engineering and development teams are actively addressing the down server and are working to bring them back online. Restoring affected parent servers and stabilizing services is currently our highest priority. We sincerely apologize for the unexpected interruption. Our team is working to bring all impacted systems back online as quickly and safely as possible. Further updates will be posted here as soon as new information becomes available.

2. identified Oct 20, 2026, 07:37 PM UTC

   Our engineering team has successfully brought the affected parent servers back online. Our engineers are actively working through restoring and verifying all child instances running on those parent servers to ensure full service functionality is restored. We appreciate your continued patience as we work to bring all impacted systems back online.

3. resolved Oct 21, 2026, 11:26 AM UTC

   All affected parent servers and child instances are now online, and services have been restored. The incident is considered resolved. We apologize for the inconvenience and appreciate your patience while our teams worked to restore service.

Read the full incident report →

Started Oct 14, 2026, 01:04 PM UTC· resolved Oct 14, 2026, 04:21 PM UTC

1. investigating Oct 14, 2026, 01:04 PM UTC

   We are currently aware of an issue affecting access to webmail. Our email vendor is aware of the issue and is actively working to resolve it. In the meantime, customers can access their email using the alternative webmail portal: https://webmail.liquidweb.services/ We apologize for the inconvenience and appreciate your patience while this issue is being resolved. We will provide further updates as more information becomes available. If you have any questions or concerns, please feel free to contact us via case or chat.

2. resolved Oct 14, 2026, 04:21 PM UTC

   Our email vendor has confirmed that the issues affecting webmail login have now been resolved. If you have any further questions or concerns, please don’t hesitate to contact us via a support case or Live Chat.

Read the full incident report →

Started Oct 12, 2026, 07:00 AM UTC· resolved Oct 12, 2026, 06:13 PM UTC

1. investigating Oct 12, 2026, 07:00 AM UTC

   We are currently investigating an issue affecting access to PBE Webmail. Customers attempting to access their webmail may encounter the following error message: "Looks Like We've Hit A Snag. Please wait a couple of minutes and try again. If the problem persists, please contact Support and provide this reference number." Our Email Vendor team is aware of the issue and is actively investigating to identify the cause and restore normal service. Workaround: SMTP and IMAP authentication are expected to remain functional. Customers should still be able to send and receive emails using configured email clients, including those on mobile devices. We'll continue to update this page as we make progress toward resolution. We appreciate your patience and understanding.

2. resolved Oct 12, 2026, 06:13 PM UTC

   Our email vendor has confirmed that the issues affecting webmail login have now been resolved. If you have any further questions or concerns, please don’t hesitate to contact us via a support case or Live Chat.

Read the full incident report →

Started Sep 26, 2026, 03:10 PM UTC· resolved Sep 27, 2026, 02:50 AM UTC

1. investigating Sep 26, 2026, 03:10 PM UTC

   We have identified a security vulnerability CVE-2026-87898 in the Plesk Site Import extension on Linux servers. This issue involves improper sanitization of database names during imports, which could allow unauthorized command execution with root privileges. Affected product version: Plesk for Linux: 1.12.1 and earlier Patched on: 1.12.2 Our engineering team is currently assessing our entire hosting fleet and determining next steps. If you have any further questions or concerns, please contact us at [email protected] or via Live Chat.

2. identified Sep 26, 2026, 04:10 PM UTC

   We have identified that only a subset of hosts are reported with the vulnerable Site Import extension. Our team is mitigating this vulnerability by upgrading this extension to the patched version. Meanwhile, your time and patience will be appreciated.

3. resolved Sep 27, 2026, 02:50 AM UTC

   Our team has completed the remediation work for the affected environments. No further action is required at this time. Thank you for your patience.

Read the full incident report →

Started Sep 23, 2026, 02:16 PM UTC· resolved Sep 23, 2026, 05:38 PM UTC

1. investigating Sep 23, 2026, 02:16 PM UTC

   We are currently experiencing a service disruption affecting some servers in our Lansing DC due to a rack outage. 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 Sep 23, 2026, 02:39 PM UTC

   Our Data Center Operations team identified the issue and immediately replaced the PSU. The affected servers are now back online and operating normally. We are continuing to monitor the environment closely to ensure stability. If you are still experiencing any issues, please reach out to us via Support Chat or by opening a support case, and our team will be happy to assist you.

3. resolved Sep 23, 2026, 05:38 PM UTC

   The affected servers are back online and operating normally. This incident has been resolved.

Read the full incident report →

Started Sep 22, 2026, 08:13 PM UTC· resolved Oct 01, 2026, 06:29 PM UTC

1. investigating Sep 22, 2026, 08:13 PM UTC

   WordPress has identified a critical security vulnerability designated as "Click2Shell" affecting all WordPress versions prior to 7.1.1. This vulnerability can enable unauthenticated Remote Code Execution (RCE) when a logged-in administrator visits a specially crafted link. Current Status & Hosting Actions Our engineering team is currently assessing our entire hosting fleet and determining next steps. There are currently no known workarounds for this vulnerability other than upgrading to the latest version of WordPress. Recommended Action for Customers We strongly advise all customers managing WordPress installations to review their environments immediately and update to WordPress version 7.1.1. We will continue to monitor the situation closely and provide further updates as new information becomes available.

2. identified Sep 23, 2026, 06:36 AM UTC

   Our Engineering team continues to assess and work on the WordPress security vulnerabilities across our hosting fleet. A new critical vulnerability, CVE-2026-87902, has been disclosed. WordPress 7.1.2 includes the security fix for this vulnerability. Recommended Action for Customers We strongly advise all customers managing WordPress installations to update to WordPress version 7.1.2 immediately. We will continue to monitor the situation closely and provide further updates as new information becomes available.

3. monitoring Sep 25, 2026, 07:36 PM UTC

   Liquid Web Systems Engineers continue to monitor this situation closely. All Customers are strongly encouraged to confirm that all Wordpress websites they host, including those in staging or development, have been updated to the latest minor version of Wordpress released on September 22nd in order to protect the website from this exploit. Customers with automatic security updates enabled should receive the applicable update automatically; however, we recommend verifying the currently running WordPress version. For additional information, please refer to the official WordPress security announcements: https://wordpress.org/news/2026/09/wordpress-7-1-2-release/ https://wordpress.org/documentation/wordpress-version/version-7-1-2/ If you have any questions or need assistance with the update process, please contact our Support team. You can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com/ Email: [email protected] We appreciate your patience and understanding as we work to secure your services.

4. resolved Oct 01, 2026, 06:29 PM UTC

   This incident is now resolved. All customers are strongly encouraged to confirm the Wordpress version for all of the websites, including those in staging or development, have been updated to the latest minor version of Wordpress released on September 22nd in order to protect the website from this exploit. For additional information, please refer to the official WordPress security announcements: https://wordpress.org/news/2026/09/wordpress-7-1-2-release/ https://wordpress.org/documentation/wordpress-version/version-7-1-2/

Read the full incident report →

Started Sep 16, 2026, 02:49 PM UTC· resolved Sep 19, 2026, 02:15 AM UTC

1. identified Sep 16, 2026, 02:49 PM UTC

   We are aware of the recent security advisory (SEC-10986) regarding the Acronis Cyber Protect Backup plugin for hosting control panels (cPanel/Plesk). Our Engineers are actively evaluating the impact across our fleet and verifying plugin versioning. We are conducting a thorough audit to confirm full patch coverage, identify any edge cases that require manual updates, and ensure that all managed systems remain secure. Service Disruption: None. Backups and control panel operations remain fully functional. We are actively auditing server inventory alongside our engineering teams. Further updates will be provided as soon as the fleet-wide verification is complete

2. identified Sep 17, 2026, 05:25 AM UTC

   The security patch for CVE-2026-87886 (SEC-10986) is being applied across the affected Acronis Cyber Protect Backup plugin. Our engineers continue to monitor the environment and validate the patched systems. We have not observed any new issues since our last update run. We will provide further updates as needed. Thank you for your patience and understanding.

3. monitoring Sep 17, 2026, 10:09 AM UTC

   The security patch for CVE-2026-87886 (SEC-10986) is applied across the affected Acronis Cyber Protect Backup plugins. Our Engineering team continues to monitor the environment and validate the patched systems. We have not observed any new issues since our last update. If you need assistance or have any concerns, please get in touch with our Support team.

4. resolved Sep 19, 2026, 02:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 09:13 AM UTC· resolved Sep 17, 2026, 03:12 AM UTC

1. investigating Sep 16, 2026, 09:13 AM UTC

   We are currently aware of an issue affecting a third-party platform used by our Support teams to manage and respond to client cases. The provider is actively investigating the issue and working toward a resolution. As a result, clients may experience delays in responses to support cases while the issue is ongoing. Our teams are monitoring the situation and will continue responding to cases as quickly as possible. We will provide further updates as more information becomes available.

2. resolved Sep 17, 2026, 03:12 AM UTC

   The issue affecting the third-party platform used by our Support teams has been resolved. The provider has confirmed that service stability and performance have returned to expected levels, and our teams are no longer seeing ongoing impact. Support case access and case management functionality have returned to normal. We apologize for the disruption and any delays this may have caused.

Read the full incident report →

Started Sep 14, 2026, 08:31 PM UTC· resolved Sep 15, 2026, 01:49 PM UTC

1. investigating Sep 14, 2026, 08:31 PM UTC

   WebPros (cPanel) posted news regarding a critical privilege-escalation vulnerability within the LiteSpeed software. A malicious website user could potentially gain root-level access to the server (even bypassing account isolation controls such as CageFS). More Information can be found here: https://support.cpanel.net/hc/en-us/articles/43483286674583-Security-LiteSpeed-Enterprise-security-advisory-September-14-2026 We will attempt to update LiteSpeed to the patched version (6.3.7) where we are able to via Automation. Regardless, please ensure your Litespeed is up-to-date. If you have any questions or concerns, please contact [email protected]

2. monitoring Sep 15, 2026, 04:19 AM UTC

   All accessible Fully and Core-Managed servers running outdated versions of LiteSpeed have been patched to version 6.3.7. The same webserver service that was in use before the LiteSpeed upgrade remains in use afterwards. If you have any questions or concerns, please contact [email protected].

3. resolved Sep 15, 2026, 01:49 PM UTC

   All accessible Fully Managed and Core Managed servers running outdated versions of LiteSpeed have been successfully updated to the patched version, 6.3.7. Services have remained operational, and no additional issues have been identified during monitoring. This incident is now resolved. If you have any questions or concerns, please contact [email protected].

Read the full incident report →

Started Sep 08, 2026, 06:52 PM UTC· resolved Sep 09, 2026, 09:24 PM UTC

1. investigating Sep 08, 2026, 06:52 PM UTC

   We are currently evaluating the impact of the recently released CVE-2026-67401 — cPanel/WHM EmailTrack SQL Injection and its impact on our hosting fleet. This vulnerability impacts all versions of cPanel. It is patched in the following versions of cPanel v11.110.0.143 v11.134.0.55 v11.136.0.39 v11.138.0.4 WP2: v11.138.1.9

2. identified Sep 08, 2026, 10:02 PM UTC

   We are currently applying the available security patches for CVE-2026-67401 across our hosting fleet. Our teams are proactively triggering manual cPanel updates on affected servers in order to bring them to a patched version. We are continuing to work through the affected fleet and will provide additional updates as remediation progresses.

3. monitoring Sep 09, 2026, 05:59 AM UTC

   The security patch for CVE-2026-67401 is being applied across the affected hosting fleet. Our teams continue to monitor the environment and validate the patched systems. We have not observed any new issues since our last update. We will provide further updates as needed. Thank you for your patience and understanding.

4. monitoring Sep 09, 2026, 09:24 PM UTC

   We have completed applying the security update across our hosting fleet to servers which we are able to access and patch but there still remains a subset of servers that we were unable to patch. This is partly due to End of Life software, e.g. cPanel on CentOS 6. Customers whose servers we were unable to patch should review their servers and ensure that their servers are running one of the following patched versions of cPanel: v11.110.0.143 v11.134.0.55 v11.136.0.39 v11.138.0.4 WP2: v11.138.1.9 Any version of cPanel which is not running one of these versions is vulnerable and should be updated. cPanel can be updated by using the following steps: https://docs.cpanel.net/whm/cpanel/upgrade-to-latest-version/ For the customers on CentOS 6 (or older) we strongly suggest migrating to an Alma 9 server in order to receive future security patches

5. resolved Sep 09, 2026, 09:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 05, 2026, 01:48 PM UTC· resolved Sep 09, 2026, 10:51 PM UTC

1. identified Sep 05, 2026, 01:48 PM UTC

   We are aware of recent reports regarding a critical, unpatched zero-day vulnerability, commonly referred to as “StyleSmuggler”, affecting Magento and Adobe Commerce. At this time, our teams are actively reviewing server environments to assess any potential impact. As a precautionary measure, our Security team is implementing the appropriate mitigations while we continue our investigation and monitor for further guidance. We will provide further updates as more information becomes available. If you need assistance or have any concerns, please contact our Support team .

2. identified Sep 05, 2026, 11:03 PM UTC

   As part of our ongoing mitigation efforts, we have implemented additional security protections across affected Magento/Adobe Commerce environments. This includes a full block on GraphQL requests to help reduce the risk of unauthorized code execution. Customers using headless/PWA storefronts or applications that rely heavily on GraphQL may experience some impact from these protections. At this time, there is no official vendor patch available. We recommend continuing to monitor your site for unusual activity or unexpected changes and contacting Support if you notice any issues with your storefront or suspect your site may have been compromised. We will provide further updates once an official security patch becomes available. Our teams are continuing to monitor the affected environments and the effectiveness of these mitigations. We will continue to assess the situation and provide additional updates as new information becomes available.

3. identified Sep 06, 2026, 09:08 AM UTC

   Our security teams are actively scanning affected environments for indicators of compromise. Initial scanning has identified potential findings that are currently being reviewed and validated. We are continuing to enhance our scanning capabilities to provide additional visibility into potential compromises. We are also reviewing affected Magento environments and developing remediation guidance for confirmed cases. Customers may experience some impact if their storefront or applications rely heavily on GraphQL, including headless/PWA implementations. We recommend continuing to monitor your environment for unusual activity or unexpected changes and contacting Support if you observe any issues or suspect your site may have been compromised. Our teams will continue to monitor the situation closely and provide further updates as additional information becomes available.

4. identified Sep 06, 2026, 02:28 PM UTC

   Our teams remain actively engaged and are continuing to investigate the Magento vulnerability and its potential impact. Security and Engineering are working closely to validate findings, expand scanning, and provide clear remediation guidance for any confirmed cases. We understand the importance and urgency of this situation and really appreciate your patience. This remains a high priority for us, and we’re here to support you throughout the process. We recommend continuing to monitor your environment for unusual activity or unexpected changes. If you notice anything suspicious or believe your site may have been affected, please reach out to Support. We’ll continue to closely monitor the situation and share further updates as more information becomes available. Thank you for your patience.

5. identified Sep 06, 2026, 09:53 PM UTC

   Our Security and Engineering teams remain actively engaged and are continuing to investigate the affected environments. Confirmed threats are being quarantined as part of our ongoing containment efforts, while findings are reviewed and validated. We are also preparing to begin restoration work where necessary. An estimated restoration timeline is not yet available, but we will share additional details as soon as they are confirmed. This remains a high priority, and we will continue to provide updates as progress is made.

6. identified Sep 07, 2026, 06:22 AM UTC

   Our Security and Engineering teams continue to work on containment and remediation efforts across affected environments. Deep-system scanning remains active as we work to identify, isolate, and quarantine compromised instances. Restoration planning is also ongoing, with our technical teams validating safe recovery paths for impacted sites. While a precise time-to-resolution is still being established, restoring full system integrity safely remains our highest priority. We appreciate your continued patience as this work continues. We will provide another status update as soon as there are meaningful developments or milestones to share. If you need assistance or have any concerns, please contact our Support team.

7. identified Sep 07, 2026, 03:06 PM UTC

   Our Security and Engineering teams remain actively engaged in the ongoing containment, investigation, and remediation efforts across affected environments. Our teams continue to review scanning results, validate findings, and take appropriate remediation actions where potential compromise has been identified. We understand the importance and urgency of this situation and appreciate your continued patience. We will provide further updates as meaningful progress is made and additional remediation details become available. If you need assistance or have any concerns, please contact our Support team.

8. identified Sep 08, 2026, 06:24 AM UTC

   Our technical teams continue to make progress on containment, investigation, and remediation across affected environments. Adobe has recently released a patch addressing the underlying vulnerability. Our technical teams are actively reviewing, testing, and deploying the patch while continuing deep-system scans and validating safe recovery paths to restore impacted sites to a known-good state. We will continue to share updates as new remediation details become available. Please contact Support if you have any questions or require assistance in the meantime.

9. resolved Sep 09, 2026, 10:51 PM UTC

   Our engineering teams continue to make progress on containment, investigation, and remediation across affected environments. Adobe has released a patch addressing the underlying vulnerability. We have contacted customers running affected versions of Magento and recommend applying the appropriate security patch as soon as possible. Customers should also review their environments and ensure their sites are clean and have not been impacted by the vulnerability. If you have any questions or concerns. please contact Liquid Web Support so we can guide you further.

Read the full incident report →

Started Aug 17, 2026, 03:35 PM UTC· resolved Aug 18, 2026, 08:17 PM UTC

1. identified Aug 17, 2026, 03:35 PM UTC

   GitHub is reporting degraded performance via their status page this morning: https://www.githubstatus.com/ Per the page, this problem may be affecting Pull Requests, Issues, Copilot, Actions, Webhooks, and API requests, among other services. Customers should follow the GitHub status page for the latest information.

2. resolved Aug 18, 2026, 08:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2026, 12:53 PM UTC· resolved Aug 16, 2026, 06:24 AM UTC

1. investigating Aug 13, 2026, 12:53 PM UTC

   We are currently investigating network issues affecting servers in our Phoenix Data Center. During this time, you may experience connectivity disruptions or degraded performance. Our engineers are actively working to identify the root cause and restore service stability as quickly as possible. If you have any questions or require assistance, please contact us via chat or open a support case through portal.liquidweb.com We appreciate your patience and understanding while we work to resolve this issue. Thank you.

2. identified Aug 13, 2026, 02:51 PM UTC

   Dear Valued Customer, We are currently responding to a critical facilities issue affecting our Phoenix, Arizona data center. A major chiller equipment failure at the facility has significantly reduced cooling capacity, resulting in elevated temperatures and an increased risk of service disruption and potential hardware impact. The data center provider is actively working to restore normal cooling operations. Replacement work is underway, with current estimates indicating repairs may take 10–16 hours or longer. Additional information regarding the facility incident is available on the data center provider's status page: https://status.phoenixnap.com/incidents/dnjp5pfv2mmh Our teams are closely monitoring conditions and working directly with the data center provider to minimize customer impact. To protect customer infrastructure and reduce the risk of hardware damage or data loss, we may need to perform controlled shutdowns of affected systems if facility temperatures reach unsafe levels. Where necessary, we will prioritize orderly shutdown procedures to protect the underlying infrastructure. Customers with services hosted within the affected Phoenix facility should prepare for potential service interruptions while remediation efforts continue. We understand the seriousness of this situation and the impact an extended disruption may have on your business. We will continue to provide updates as conditions change and additional information becomes available. We sincerely apologize for the disruption and appreciate your patience as we work to protect your infrastructure and restore normal operations. Sincerely, Nexcess Support Team

3. identified Aug 13, 2026, 04:19 PM UTC

   Dear Valued Customer, Update: Our teams are continuing to work closely with our data center provider at the Phoenix location. Our data center teams and on-site vendors continue working to restore adequate cooling. As part of our ongoing mitigation efforts, we are gracefully shutting down impacted systems where necessary to help protect customer data and reduce the risk of data corruption or hardware-related issues while temperatures remain elevated. We apologize for the disruption and appreciate your patience as we work to protect your infrastructure and restore normal operations. We will continue to provide updates as the situation progresses. Sincerely, Nexcess Support Team

4. identified Aug 13, 2026, 05:08 PM UTC

   Dear Valued Customer, We are continuing to work closely with our provider as they address the elevated temperatures at the Phoenix facility. Progress is being made, and temperatures are continuing to come down as cooling systems are restored and additional mitigation efforts are put in place. We apologize for the disruption and appreciate your patience as we work to protect your infrastructure and restore normal operations. We will continue to provide updates as the situation progresses. For the latest status and updates from the facility, please visit: https://status.phoenixnap.com/incidents/dnjp5pfv2mmh Sincerely, Nexcess Support Team

5. monitoring Aug 13, 2026, 06:47 PM UTC

   Internal ambient temperatures in our Phoenix, Arizona data center have continued to moderate and onsite Nexcess Engineers have begun to restore service to networking equipment and other services. Our Senior Engineering and Leadership teams are actively monitoring the situation and will continue to protect customer infrastructure and reduce the risk of hardware damage or data loss where necessary, however at this time customers should begin to see network service restoring to their environments.

6. monitoring Aug 14, 2026, 03:12 AM UTC

   Our Nexcess Engineering teams continue working to restore all remaining systems and services in our Phoenix, Arizona data center. While significant progress has been made and many systems have returned to service, our teams are continuing to bring remaining infrastructure back online in a controlled and careful manner. As systems and network services are restored, our Engineering and Operations teams are monitoring them very closely to confirm they remain stable and continue operating as expected. We are also actively watching environmental conditions and infrastructure health throughout the facility to reduce the risk of additional service disruption, hardware damage, or data loss. Work will continue until all affected systems and services have been fully restored. Our Engineering and Leadership teams remain actively engaged, and we will continue to provide updates as restoration efforts progress and overall service stability is confirmed.

7. monitoring Aug 14, 2026, 06:57 AM UTC

   Our Nexcess Engineering teams have successfully brought the majority of systems and services in our Phoenix, Arizona data center back online, and work continues actively to restore the remaining pending services. For all restored systems, our teams are conducting thorough checks across the infrastructure to confirm complete stability and ensure there is no ongoing operational impact. Out of an abundance of caution, we continue to closely monitor facility environmental conditions and overall infrastructure health. We will provide further updates in this space as restoration and verification efforts progress.

8. monitoring Aug 14, 2026, 10:59 AM UTC

   Our Nexcess Engineering teams have brought the majority of systems and services in our Phoenix, Arizona data center back online, and work remains actively underway to restore the remaining pending services. Over the past several hours, we have observed continued stability across all restored systems with no red flags identified. Out of an abundance of caution, our teams are continuing to perform ongoing checks and closely monitor facility environmental conditions alongside overall infrastructure health. We will provide further updates in this space as restore and verification efforts progress.

9. monitoring Aug 14, 2026, 09:13 PM UTC

   The vast majority of impacted servers have been brought online and are functional at this time. We continue to monitor the stability of the network to ensure normal operations. Our engineers are still working on restoring functionality to the Cloud Sites Platform but are making progress. The root cause has been identified and progress is being made. Updates and more information regarding those efforts can be found on our Cloud Sites Status Page here: https://status.websitesettings.com/incidents/0l8hyyhr6v93

10. monitoring Aug 15, 2026, 07:50 PM UTC

    We have restored all services and observed continued stability. We will keep a close eye on the platform and continue to update this page with any new developments.

11. resolved Aug 16, 2026, 06:24 AM UTC

    All post-outage cleanup activities have been completed, and everything is working as expected. We will continue to monitor the environment, and this incident is now resolved.

Read the full incident report →

Started Aug 12, 2026, 03:44 PM UTC· resolved Sep 03, 2026, 01:52 PM UTC

1. investigating Aug 12, 2026, 03:44 PM UTC

   A security vulnerability, CVE-2026-65640, has been identified in WordPress that could allow an authenticated Author-level or higher user to achieve remote code execution through a malicious file upload on sites using Imagick and Ghostscript. The vulnerability has been addressed through updates across supported WordPress branches. Patched Versions: Customers should update to the following patched version for their respective WordPress branch: 7.0.4 6.9.7 6.8.8 6.7.7 6.6.7 6.5.10 6.4.10 6.3.10 6.2.11 6.1.12 6.0.14 5.9.16 5.8.15 5.7.17 5.6.19 5.5.20 5.4.21 5.3.23 5.2.26 5.1.24 5.0.27 4.9.31 4.8.30 4.7.35 Recommended Action: Customers are strongly encouraged to update WordPress core to the latest available patched version and ensure automatic updates are enabled where appropriate. Customers with automatic updates enabled should receive the applicable update automatically. However, we recommend verifying the currently running WordPress version to ensure the security update has been successfully applied. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please reach us via live chat or via a case. Additional information: https://wordpress.org/news/2026/08/wordpress-7-0-4-release/ https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-8vr3-7mxf-gx8w

2. resolved Sep 03, 2026, 01:52 PM UTC

   The WordPress security vulnerability CVE-2026-65640 has been addressed in the latest WordPress security releases. Customers are encouraged to keep their WordPress installations updated to the latest available security release within their current supported branch. We have proactively contacted customers identified as running potentially affected WordPress versions and provided recommendations to update their installations. At this time, the incident has been resolved, and the related status page notification will be closed.

Read the full incident report →

Started Aug 08, 2026, 01:24 PM UTC· resolved Sep 03, 2026, 01:53 PM UTC

1. investigating Aug 08, 2026, 01:24 PM UTC

   A high-severity reflected XSS vulnerability, CVE-2026-64638, has been identified in the WordPress login interface. Exploitation requires a victim to visit a specially crafted URL and, under specific conditions, could potentially lead to PHP code execution. Impacted versions Impacted versions: WordPress 4.7 – 7.0.2 (every release on every branch) WordPress 4.6 and earlier — end of life, no patch available Fixed versions: WordPress 7.0.3 WordPress 6.9.6 WordPress 6.8.7 Equivalent minor releases on every remaining supported branch back to 4.7 Recommended Action Customers are strongly encouraged to update WordPress core and ensure automatic security updates are enabled where appropriate. Since exploitation requires user interaction, customers should also remain vigilant against phishing attempts and avoid clicking suspicious or unsolicited links. Customers with automatic security updates enabled should receive the applicable update automatically; however, we recommend verifying the currently running WordPress version. There is currently no reported evidence of widespread exploitation in the wild. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please contact our Support team.

2. resolved Sep 03, 2026, 01:53 PM UTC

   The WordPress security vulnerability CVE-2026-64638 has been addressed in the latest WordPress security releases. Customers are encouraged to keep their WordPress installations updated to the latest available security release within their current supported branch. We have proactively contacted customers identified as running potentially affected WordPress versions and provided recommendations to update their installations. At this time, the incident has been resolved, and the related status page notification will be closed.

Read the full incident report →

Started Aug 01, 2026, 01:34 AM UTC· resolved Aug 01, 2026, 02:07 AM UTC

1. investigating Aug 01, 2026, 01:34 AM UTC

   We are investigating intermittent connectivity and increased latency affecting some services hosted in the VMware MT environment. Our engineers are actively working to identify the cause and restore normal service as quickly as possible. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or concerns, please open a support ticket or contact us via chat.

2. resolved Aug 01, 2026, 02:07 AM UTC

   Service has been restored at this time, and the affected VMware MT-hosted services are operating normally. Thank you for your patience and understanding while our teams worked to resolve this issue.

Read the full incident report →

Started Jul 18, 2026, 01:48 AM UTC· resolved Jul 23, 2026, 07:47 PM UTC

1. investigating Jul 18, 2026, 01:48 AM UTC

   On July 17th Wordpress.org announced two critical remote code execution (RCE) vulnerabilities commonly known as WP2Shell. These vulnerabilities exist in Wordpress Core and allow an unauthenticated request to execute arbitrary code on the target website. Customers running the Wordpress versions below are strongly advised to upgrade to latest version shown as soon as possible: Wordpress 6.8.x; fixed in 6.8.6 WordPress 6.9.x; fixed in 6.9.5 WordPress 7.0.x; fixed in 7.0.2 WordPress 7.1 beta, fixed in 7.1 beta2 Source: https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ Posted 2 minutes ago. Jul 17, 2026 - 21:44 EDT

2. identified Jul 18, 2026, 11:15 PM UTC

   Our teams continue to work diligently to assess the impact of the recently disclosed WordPress Core vulnerabilities and verify that appropriate mitigation measures are in place. We remain actively engaged in our investigation and are monitoring the situation for any new developments. We will continue to closely monitor the situation and take any additional steps necessary to maintain system security and stability. If you need assistance or have any concerns, please contact our Support team.

3. monitoring Jul 20, 2026, 11:43 AM UTC

   Services have been restored, and websites are currently loading as expected. Our Network team is continuing to investigate the underlying cause and is actively monitoring the environment to ensure stability. At this time, all services appear to be operating normally. If you experience any issues or need assistance, please contact our Support team.

4. identified Jul 20, 2026, 11:47 AM UTC

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

5. identified Jul 20, 2026, 11:48 AM UTC

   We are continuing to work on a fix for this issue.

6. identified Jul 20, 2026, 08:20 PM UTC

   Given the severity of this vulnerability, Liquid Web Systems Engineers have been proactively upgrading affected Wordpress applications across our fleet. Customers are still strongly encouraged to review their Wordpress websites and, if affected, to update to the patched version as soon as possible.

7. resolved Jul 23, 2026, 07:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 16, 2026, 08:02 PM UTC· resolved Jul 17, 2026, 12:25 AM UTC

1. investigating Jul 16, 2026, 08:02 PM UTC

   A subset of servers within our Phoenix, AZ data center lost power. Our on-site team is investigating.

2. monitoring Jul 16, 2026, 08:02 PM UTC

   Primary power has been restored, and we are monitoring the situation.

3. resolved Jul 17, 2026, 12:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 15, 2026, 09:35 PM UTC· resolved Jul 23, 2026, 06:50 PM UTC

1. investigating Jul 15, 2026, 09:35 PM UTC

   We are investigating an issue affecting Apache services on our servers following a recent EasyApache ModSecurity update. Customers on affected servers may experience websites being unavailable, HTTP errors, or connection timeouts. Our Engineering team is currently working to restore services. Need help? Chat with us or create a ticket via my.liquidweb.com. We appreciate your patience and understanding while we work to restore normal service.

2. monitoring Jul 15, 2026, 11:57 PM UTC

   A fix has been implemented, and our Engineering team is monitoring the affected servers to confirm Apache services remain stable.

3. resolved Jul 23, 2026, 06:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 09, 2026, 02:34 PM UTC· resolved Jul 29, 2026, 07:28 PM UTC

1. investigating Jul 09, 2026, 02:34 PM UTC

   Our team is currently assessing the impact and scope of Januscape Vulnerability (CVE-2026-53359), and its impact on servers in our fleet and the best way to apply patches to our hosting infrastructure. We will be sending communications to any affected customers as we work to apply the necessary mitigations. Next Steps: Teams are currently in review of vulnerability; subsequent status updates will follow.

2. identified Jul 13, 2026, 05:49 PM UTC

   Our teams are continuing to deploy the required security updates across affected systems in response to the Januscape Vulnerability (CVE-2026-53359). As part of this remediation, some systems require a controlled reboot to complete the patching process. Following each reboot, we are validating system availability, service health, and network connectivity. Systems that do not return to service as expected are being actively investigated and restored by our operations teams. We understand the importance of maintaining availability and are working carefully to complete this remediation while minimizing customer impact. Additional updates will be provided as patching and validation efforts continue.

3. resolved Jul 29, 2026, 07:28 PM UTC

   The security updates have been applied across the Liquid Web fleet.

Read the full incident report →

Started Jul 08, 2026, 09:49 PM UTC· resolved Jul 09, 2026, 11:59 AM UTC

1. investigating Jul 08, 2026, 09:49 PM UTC

   It has been brought to our attention that a large subset of our cPanel customers are seeing an error message when attempting to log into WHM. "Invalid License File. Incorrect authority delivering the license." WebPros (cPanel) is aware of the issue and they are currently investigating. We appreciate your patience as they work to resolve the issue.

2. monitoring Jul 08, 2026, 10:53 PM UTC

   cPanel has been working on improving the performance of their licensing servers and implemented changes. We are seeing access to WHM and cPanel restored without intervention from support. If you are still having issues please reach out to support and we will be happy to assist.

3. monitoring Jul 08, 2026, 11:04 PM UTC

   WebPros has stated that the issue has been resolved and that servers should begin to renew licenses properly. If you are still experiencing issues logging in, feel free to contact us via chat or email and we can expedite the resolution.

4. resolved Jul 09, 2026, 11:59 AM UTC

   We have observed continued stability, and the cPanel licence updates have gone smoothly so far. If you need any further assistance, please do not hesitate to reach out to our Support team via chat or email.

Read the full incident report →

Started Jul 02, 2026, 04:49 AM UTC· resolved Jul 02, 2026, 10:37 AM UTC

1. investigating Jul 02, 2026, 04:49 AM UTC

   We are investigating 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. identified Jul 02, 2026, 05:26 AM UTC

   We are investigating an issue affecting connectivity between our Phoenix Data Center and internal services. We have identified that the issue is related to network connectivity with an upstream provider during a scheduled maintenance window. At this time, customer-facing services are expected to remain accessible from public networks, and we have not identified a widespread impact to externally accessible services. Our Engineers are actively working with the upstream provider to restore full connectivity 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 restore this service. Thank you.

3. monitoring Jul 02, 2026, 07:16 AM UTC

   We are seeing continued improvement in network connectivity as the affected links begin to recover. All customer websites and servers remain online and accessible. The scheduled maintenance is still in progress, and our Engineering team is actively monitoring the environment to ensure connectivity is fully restored. We will continue to provide updates as additional information becomes available. 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.

4. resolved Jul 02, 2026, 10:37 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 Jun 26, 2026, 05:23 AM UTC· resolved Jul 09, 2026, 02:15 PM UTC

1. investigating Jun 26, 2026, 05:23 AM UTC

   We are advising all customers using WordPress to verify that the following plugins are updated to the latest available versions. Recently disclosed vulnerabilities affect older versions of these plugins: CVE-2026-6279 – Avada Builder (Fusion Builder) – Unauthenticated Remote Code Execution Affected versions: 3.15.2 and earlier CVE-2026-10795 – UpdraftPlus Backup Plugin – Authentication Bypass Affected versions: 1.26.4 and earlier These vulnerabilities may allow unauthenticated attackers to gain control of vulnerable WordPress sites and compromise WordPress user accounts if the plugins have not been updated to the latest available versions. If your website uses either of these plugins, we strongly recommend that you: Update the affected plugin(s) to the latest available version immediately. Review your WordPress installation for any unexpected administrator accounts, plugins, or modified files. Contact our Support team if you believe your website has been affected or if you need assistance reviewing your installation.

2. resolved Jul 09, 2026, 02:15 PM UTC

   This advisory is now being closed. We encourage our customers to ensure that any affected WordPress plugins have been updated to the latest available versions and continue following WordPress security best practices. If you believe your website may have been impacted or require assistance, please contact our Support team.

Read the full incident report →