Liquid Web Outage History

Started Feb 13, 2026, 09:11 PM UTC· resolved Feb 14, 2026, 03:00 AM UTC

1. investigating Feb 13, 2026, 09:11 PM UTC

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

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

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

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

   This incident has been resolved.

Read the full incident report →

Started Jan 29, 2026, 04:06 AM UTC· resolved Feb 03, 2026, 06:56 PM UTC

1. investigating Jan 29, 2026, 04:06 AM UTC

   We are currently investigating the POP3 and SSH service down alerts on a subset of servers. The issue appears to have occurred after an endpoint update on the Mbdaemon associated with the Threatdown add-on service. Our engineering team is actively working to identify the root cause and resolve the issue. If you need assistance, please chat with us or submit a ticket at my.liquidweb.com. Thank you for your patience and understanding. We appreciate your support.

2. identified Jan 29, 2026, 05:08 AM UTC

   The issue has been identified, and our Support team is actively working to implement the fix as quickly as possible. We appreciate your patience and understanding. Further updates will be shared here as they become available.

3. identified Jan 29, 2026, 03:27 PM UTC

   The issue has been identified and is affecting only services with the ThreatDown (TD) add-on enabled. Our Support team is actively working to implement a fix as quickly as possible. We appreciate your patience and understanding. Further updates will be shared here as they become available. If you need assistance, please chat with us or submit a ticket at my.liquidweb.com. Thank you for your patience and understanding. We appreciate your support.

4. identified Jan 29, 2026, 04:25 PM UTC

   We’ve identified the issue and confirmed it impacts a subset of services with the ThreatDown (TD) add-on enabled. Our team is actively identifying affected systems and deploying a fix as quickly as possible. We’ll provide additional updates as they become available. If you believe your system is impacted or are experiencing a service interruption, please chat with us or submit a ticket at my.liquidweb.com. Thank you for your patience and support.

5. identified Jan 29, 2026, 10:07 PM UTC

   Our team is actively addressing impacted systems and working to restore service as quickly as possible. If you believe your system is affected or need assistance, please chat with us or submit a ticket at my.liquidweb.com. Thank you for your patience and support.

6. identified Jan 30, 2026, 01:18 AM UTC

   We have identified the issue and confirmed it impacts a subset of services with the ThreatDown (TD) add-on enabled. WE have additional resources engaged with Threat Stack. Our team is working through and applying manual fixes to servers that we have been able to identify as affected by this incident. We’ll provide additional updates as they become available. If you believe your system is impacted or are experiencing a service interruption, please chat with us or submit a ticket at my.liquidweb.com. Thank you for your patience and support.

7. monitoring Jan 30, 2026, 04:40 AM UTC

   Our team has made progress by applying the fix to the affected servers. We have been working closely with the ThreatDown team to obtain the latest updates from their side in order to address this issue. We will continue to monitor the situation and take action where necessary. If you believe your system may be affected or you are experiencing a service interruption, please contact us via chat or submit a support ticket at my.liquidweb.com. We will provide further updates as they become available. Thank you for your patience and support.

8. monitoring Jan 30, 2026, 01:57 PM UTC

   Our team is actively working to resolve the issue by running the mblinux-updater-fix, which has proven effective when combined with a server reboot. Based on ongoing service alerts, we are applying this fix where required and closely monitoring affected systems to ensure stability. We are actively working with ThreatDown to identify the best permanent resolution and outline next steps. If you believe your system may still be affected or you experience any service interruption, please contact us via chat or submit a support ticket at my.liquidweb.com. Further updates will be provided as they become available.

9. monitoring Jan 31, 2026, 12:41 AM UTC

   At this time, we have downgraded the severity of this incident. Our teams remain actively engaged and continue to monitor the affected systems. Any new issues will be addressed by applying the mblinux-updater-fix, followed by a server reboot as needed. We are also continuing to work closely with ThreatDown support toward a permanent resolution. If you experience any service interruptions, please don’t hesitate to reach out via chat or submit a support ticket through your customer portal at my.liquidweb.com. We appreciate your patience and understanding as our teams work through this, and we’ll provide further updates as they become available.

10. monitoring Feb 01, 2026, 05:17 AM UTC

    We are making steady progress by implementing necessary fixes and working closely with ThreatDown to find a lasting solution. The systems are stabilizing, and we are in good shape to manage the situation. We will continue to monitor the situation and share further updates as they become available. Please contact support if you experience any issues. Thank you for your patience.

11. monitoring Feb 02, 2026, 04:52 AM UTC

    We are continuing to see stability across the fleet and have not observed any recent alerts related to this issue. Our team has been actively working on this incident to apply the fix across the affected servers, and we have made solid progress so far, with completion on the impacted list. We are actively monitoring the situation and will keep this space updated as soon as we have further information available. If you believe your system may be affected or require assistance, please chat with us or submit a ticket at my.liquidweb.com. Thank you for your understanding and patience!

12. resolved Feb 03, 2026, 06:56 PM UTC

    This incident has been resolved. We have successfully mitigated the impact caused by the ThreatDown update and are observing stability across our fleet. If you have ThreatDown installed and continue to experience issues—such as your server being unresponsive or down—please reboot your server via the management portal at my.liquidweb.com and reach out to our support team for further assistance.

Read the full incident report →

Started Jan 28, 2026, 04:06 AM UTC· resolved Jan 29, 2026, 02:15 AM UTC

1. investigating Jan 28, 2026, 04:06 AM UTC

   We have identified that users of the Premium Business Email services are experiencing difficulties sending emails to Microsoft and Yahoo-related addresses. We are actively working with Microsoft's and Yahoo's teams to resolve this issue. We appreciate your patience and understanding. If you need assistance, please chat with us or create a case at my.liquidweb.com.

2. identified Jan 28, 2026, 10:21 PM UTC

   Our email vendor continues to monitor email delivery to Yahoo and Microsoft recipients. Yahoo is still deferring some emails, and the vendor is actively working to clear the queue and address the senders causing these deferrals. For Microsoft, the vendor is coordinating directly with Microsoft to resolve the delivery issues. We will provide updates here as soon as new information becomes available. We appreciate your patience as we work to fully restore email delivery.

3. resolved Jan 29, 2026, 02:15 AM UTC

   The outgoing email issue with the Premium Business Email service affecting Yahoo and Microsoft has been completely resolved. We have been monitoring the platform and have not observed any further problems. Thank you for your patience during this time.

Read the full incident report →

Started Jan 27, 2026, 08:37 PM UTC· resolved Jan 28, 2026, 03:18 AM UTC

1. investigating Jan 27, 2026, 08:37 PM UTC

   We are currently tracking a network degradation issue affecting the Chicago, IL area. Our upstream provider, Cloudflare, is working to resolve the matter. We are monitoring the situation closely and will provide updates as they become available. Cloudflare Status: https://www.cloudflarestatus.com/incidents/3xb30dhqfkw7

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

   Cloudflare is currently experiencing network degradation in the Chicago area. This is impacting some Liquid Web services, including: Account Signups: Potential failures during registration. Provisioning: Delays in getting new orders online. Portal Tools: Intermittent errors when adjusting Cloudflare features. We apologize for the inconvenience. We are monitoring the situation closely and will provide updates as they become available. Cloudflare Status: https://www.cloudflarestatus.com/incidents/3xb30dhqfkw7

3. identified Jan 27, 2026, 09:31 PM UTC

   Cloudflare is currently experiencing network degradation in the Chicago area. This is impacting some Liquid Web services, including: Account Signups: Potential failures during registration. Provisioning: Delays in getting new orders online. Portal Tools: Intermittent errors when adjusting Cloudflare features. We apologize for the inconvenience. We are monitoring the situation closely and will provide updates as they become available. Cloudflare Status: https://www.cloudflarestatus.com/incidents/3xb30dhqfkw7

4. monitoring Jan 28, 2026, 12:33 AM UTC

   A fix has been implemented to address the issue, and services are stabilizing. We are actively monitoring the updates to ensure continued recovery. We apologize for the inconvenience and will provide additional updates if needed. Cloudflare Status: https://www.cloudflarestatus.com/incidents/3xb30dhqfkw7

5. resolved Jan 28, 2026, 03:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 23, 2026, 05:50 AM UTC· resolved Jan 23, 2026, 09:32 AM UTC

1. identified Jan 23, 2026, 05:50 AM UTC

   Microsoft is currently experiencing widespread service degradation. This issue specifically impacts users attempting to send or receive emails to Microsoft-hosted accounts (including Outlook, Hotmail, and Office 365). Affected users may experience limited functionality across multiple Microsoft 365 services or receive delivery errors such as "451 4.3.2 Temporary server" or "Host lookup failed." Our team is monitoring the situation closely and will provide further updates as more information becomes available. We appreciate your patience and understanding. If you need any help, please chat with us or create a ticket via my.liquidweb.com.

2. monitoring Jan 23, 2026, 06:56 AM UTC

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

3. resolved Jan 23, 2026, 09:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 15, 2026, 09:33 PM UTC· resolved Jan 16, 2026, 12:04 AM UTC

1. investigating Jan 15, 2026, 09:33 PM UTC

   We are currently investigating a delay in our Provisioning system that is affecting reboot, resize, and reimage workflows. Servers are still online and responsive. We are currently working to identify the underlying causes. More information will be provided as it becomes available. If you have any issues or questions, please get in touch with a member of our support team via live chat or case at my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.

2. monitoring Jan 15, 2026, 09:50 PM UTC

   At this time the provisioning system has recovered and is functioning as normal. We are continuing to monitor the situation to ensure that the system remains stable and our engineers are reviewing our systems to complete any workflows that may have been stuck as a result of the incident. If you have any issues or questions, please get in touch with a member of our support team via live chat or case at my.liquidweb.com.

3. resolved Jan 16, 2026, 12:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 14, 2026, 10:17 PM UTC· resolved Jan 15, 2026, 02:54 PM UTC

1. investigating Jan 14, 2026, 10:17 PM UTC

   We are investigating errors affecting Checkout services. Customers may experience errors when placing orders. 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. identified Jan 14, 2026, 11:04 PM UTC

   The issue has been identified, however the fix will take time to implement. In the meantime if you come across shopping errors, please visit our site in Incognito mode to successfully add items to your cart.

3. resolved Jan 15, 2026, 02:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 07, 2026, 06:02 AM UTC· resolved Jan 08, 2026, 08:25 PM UTC

1. investigating Jan 07, 2026, 06:02 AM UTC

   We are currently investigating a delay in our Provisioning system that is affecting reboot, resize, and reimage workflows. Servers are still online and responsive. We are currently working to identify the underlying causes. More information will be provided as it becomes available. If you have any issues or questions, please get in touch with a member of our support team via live chat or case at my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.

2. identified Jan 07, 2026, 08:59 AM UTC

   The issue has been identified, and our teams are actively working toward a resolution. We will provide further updates as more information becomes available. Thank you for your patience.

3. investigating Jan 07, 2026, 03:09 PM UTC

   We are currently accepting new orders; however, provisioning for Cloud Servers is experiencing a temporary delay. We are continuing to investigate issues where workflows begin, but struggle to finish. We will provide updates as progress is made. Thank you for your patience and understanding, which is truly appreciated.

4. investigating Jan 07, 2026, 11:14 PM UTC

   We are continuing to investigate this issue.

5. investigating Jan 07, 2026, 11:16 PM UTC

   We are currently accepting new orders; however, provisioning for Cloud Servers is experiencing a temporary delay. We are continuing to investigate issues where workflows begin, but struggle to finish. We will provide updates as progress is made. Our engineers are continuing to work on pushing through backlogged workflows Thank you for your patience and understanding, which is truly appreciated.

6. monitoring Jan 08, 2026, 02:05 AM UTC

   Our Engineers have identified the issue and implemented a fix. We are starting to see improvements in the operation, and past workflows are now functioning as expected. We will continue to monitor the situation closely. Thank you for your patience and understanding.

7. resolved Jan 08, 2026, 08:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 04, 2026, 04:52 PM UTC· resolved Jan 04, 2026, 07:57 PM UTC

1. investigating Jan 04, 2026, 04:52 PM UTC

   We are aware of service interruptions affecting domain registrations due to an issue with our vendor, eNom. Our team is tracking the issue and will share updates here as they become available. We apologize for the inconvenience.

2. monitoring Jan 04, 2026, 06:12 PM UTC

   Enom has confirmed that their service issues are resolved, and our domain registration systems are back online. We have verified that transactions are processing correctly; however, we will continue to monitor the situation closely to ensure continued stability.

3. resolved Jan 04, 2026, 07:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 31, 2025, 12:51 PM UTC· resolved Dec 31, 2025, 07:25 PM UTC

1. investigating Dec 31, 2025, 12:51 PM UTC

   We are currently investigating an issue affecting access to the My.liquidweb.com portal. This status post will be updated as more information becomes available. If you have any questions, don't hesitate to get in touch with a member of our support team via live chat, ticket, or by phone at (800)-580-4985, (517)-322-0434 (international).

2. monitoring Dec 31, 2025, 01:22 PM UTC

   The access to my.liquidweb.com and https://login.liquidweb.com customer portals are functioning as expected at this time. We are monitoring the situation closely. If you have any questions, please contact a member of our support team via live chat, ticket, or by phone at (800)-580-4985, or (517)-322-0434 (international).

3. resolved Dec 31, 2025, 07:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 29, 2025, 05:35 PM UTC· resolved Dec 30, 2025, 02:02 AM UTC

1. investigating Dec 29, 2025, 05:35 PM UTC

   We are currently experiencing issues with accessing the Premium Business Email webmail interface. We are actively working with our email provider to resolve this as quickly as possible. Please note that email delivery is not currently affected. We will continue to post updates here as more information becomes available. If you have any questions, please contact our support team via LiveChat or by submitting a case.

2. monitoring Dec 29, 2025, 07:38 PM UTC

   Our email vendor has implemented a fix for the Premium Business Email webmail access issue, and service access is being restored. We are currently monitoring the situation to ensure stability. Email delivery continues to function normally. We will provide further updates if needed. If you have any questions, please contact our support team via LiveChat or by submitting a case.

3. resolved Dec 30, 2025, 02:02 AM UTC

   This issue has been resolved. Webmail is now accessible, and we are no longer experiencing any further problems. Again, thank you for your patience! If you have any questions, please get in touch with a member of our support team via live chat or case.

Read the full incident report →

Started Dec 18, 2025, 07:11 PM UTC· resolved Dec 18, 2025, 10:50 PM UTC

1. investigating Dec 18, 2025, 07:11 PM UTC

   We are currently investigating an issue where the VMware Cloud Director portal is returning a 503 error, making it temporarily inaccessible. Our engineering team is actively working to restore service as quickly as possible. We understand the importance of this tool to your operations and will provide regular updates as we move toward a resolution.

2. identified Dec 18, 2025, 08:20 PM UTC

   We have successfully identified the root cause of the 503 errors affecting access to the VMware Cloud Director portal. Our engineering team is currently applying a fix to restore full access. Portal Access: Users may continue to experience 503 errors when attempting to log in to the management interface. Server Stability: All existing virtual servers and workloads hosted on VMware remain fully operational and unaffected. This issue is strictly limited to the management portal interface. We will provide another update as soon as the fix has been fully implemented and verified.

3. monitoring Dec 18, 2025, 08:41 PM UTC

   The engineering team has successfully completed the necessary maintenance, and full access to the VMware Cloud Director portal has been restored. All management portal functionalities are now fully operational. We are continuing to monitor the environment to ensure sustained stability. As noted throughout the incident, all virtual server workloads remained unaffected and fully operational during this period.

4. resolved Dec 18, 2025, 10:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 16, 2025, 10:16 PM UTC· resolved Jan 02, 2026, 07:02 PM UTC

1. investigating Dec 16, 2025, 10:16 PM UTC

   We are aware of an increase in email delivery issues affecting messages sent from Microsoft 365/Outlook to Premium Business email-hosted mailboxes. Some emails may bounce or be delayed due to Microsoft IP addresses appearing on the SenderScore blocklist. If you are experiencing this issue, you can resolve it by safelisting Microsoft's sending IP addresses at the mailbox level: 1. Go to cp.rackspace.com > Domains > Spam settings > Safelists 2. Select your domain 3. Add the following IP ranges: 52.102.%.% 40.107.%.% 52.101.%.% 52.103.%.% We are actively working with our partners to determine if fleet-wide mitigations can be applied. We will provide updates as more information becomes available. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

2. resolved Jan 02, 2026, 07:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 11, 2025, 06:39 PM UTC· resolved Dec 16, 2025, 09:59 PM UTC

1. investigating Dec 11, 2025, 06:39 PM UTC

   We are currently investigating an issue where a recent cPanel update is causing the Dovecot service to crash and fail to properly restart on a specific subset of servers. This service interruption can result in connectivity problems with IMAP and POP3 and may affect mail sending from the server. Not all cPanel servers are impacted. We have identified that the issue primarily affects servers that meet one of the following criteria: 1. Servers that have performed an in-place OS upgrade from CentOS 7 to AlmaLinux 8 using the cPanel Elevate script. https://support.cpanel.net/hc/en-us/articles/36882183127959-Socket-file-usr-local-cpanel-var-cpdoveauth-domainownerd-sock-incorrectly-set-in-etc-dovecot-dovecot-conf 2. Servers running AlmaLinux 8 and cPanel that had the dovecot-solr service installed prior to the cPanel version 132 release. https://support.cpanel.net/hc/en-us/articles/36830044341655-Dovecot-not-starting-when-dovecot-solr-is-installed-cPanel-version-132 cPanel has released documentation and provided remediation steps for these issues. If you are currently experiencing issues with Dovecot reporting down, please open a support ticket via our help center portal or open a chat with our support team so our team can address the issue on your server.

2. identified Dec 12, 2025, 05:00 PM UTC

   Our team is actively working on automating remediation steps related to the AlmaLinux 8 repository configuration associated with Issue #1 (servers upgraded in-place from CentOS 7 to AlmaLinux 8 using the cPanel Elevate process). This effort is intended to ensure consistent configuration for that group. Regarding Issue #2, our investigation indicates this scenario affects a much smaller subset of clients, primarily servers where dovecot-solr was installed prior to the cPanel v132 release. At this time, we are not seeing widespread impact related to this condition. If you believe your server may be affected by either issue, or if you are experiencing email-related disruptions such as IMAP/POP3 connectivity problems or Dovecot reporting as down, please contact our support team by opening a ticket or starting a live chat so we can review and address the issue on your server.

3. identified Dec 15, 2025, 04:49 PM UTC

   While progress has been made, the issue is not yet fully resolved on all affected servers. Our engineering team has identified the underlying cause as a hardlink tied to a legacy EL7 hard-coded repository, most commonly present on servers that were upgraded from EL7 to AlmaLinux 8. The team is actively validating a scalable, long-term fix to address this behavior consistently across impacted systems. In the meantime, we are continuing targeted remediation where needed and closely monitoring results. Further updates will be shared as progress continues.

4. resolved Dec 16, 2025, 09:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 09:18 AM UTC· resolved Dec 05, 2025, 04:41 PM UTC

1. investigating Dec 05, 2025, 09:18 AM UTC

   Cloudflare is currently investigating issues affecting the Cloudflare Dashboard and related APIs. Customers using the Dashboard or Cloudflare APIs may experience failed requests or see error messages. We are monitoring the progress being made by the Cloudflare team and will keep this space updated.

2. investigating Dec 05, 2025, 09:19 AM UTC

   We are continuing to investigate this issue.

3. monitoring Dec 05, 2025, 09:29 AM UTC

   Cloudflare team has implemented a fix and resolved the issue. We are monitoring the results.

4. monitoring Dec 05, 2025, 09:58 AM UTC

   A change made to the way Cloudflare’s Web Application Firewall parses requests caused Cloudflare’s network to be unavailable for several minutes this morning (ET hours). We are continuing to see stability, and we will keep this space updated as we receive further information from the Cloudflare team.

5. resolved Dec 05, 2025, 04:41 PM UTC

   Cloudflare has reverted the change to their Web Application Firewall that caused the brief network disruption earlier today. Since the rollback, we have not observed any further issues. For more details about the incident, please refer to Cloudflare’s official post: https://blog.cloudflare.com/5-december-2025-outage/ If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

Read the full incident report →

Started Nov 27, 2025, 10:50 PM UTC· resolved Nov 28, 2025, 12:53 AM UTC

1. investigating Nov 27, 2025, 10:50 PM UTC

   Our Network team detected an emergent issue with our CloudVPN service. Existing customer VPN connections are not impacted, however new attempts are not connecting. Our Engineers are currently investigating the situation and we will provide updates as progress unfolds. If you have any questions or concerns, please contact a member of our support team via live-chat or ticket ([email protected]).

2. resolved Nov 28, 2025, 12:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 07:30 PM UTC· resolved Dec 01, 2025, 02:36 PM UTC

1. monitoring Nov 24, 2025, 07:30 PM UTC

   As part of our ongoing effort to provide the best services and prepare for the holidays, we identified that several default php.ini values on client servers were set lower than the improved defaults now used in our current provisioning templates. Lower PHP values can contribute to performance slowdowns, timeouts, or resource-related PHP errors under load. To ensure consistency and improve performance across the fleet: -- Our engineers logged into affected customer servers and increased these PHP configuration values only when the current values were lower than our new, updated standards. -- Our team also adjusted our provisioning templates to provide wiser resource usage for future deployments. These changes were applied safely and did not trigger any PHP-FPM service restarts, ensuring that sites remained online during the updates. Clients may have noticed logins to their servers from internal IP addresses. Updates have been applied across the impacted servers with no issues at this time. We are continuing to monitor for any anomalies or elevated error rates. No action is required from customers. CC-12998

2. monitoring Nov 24, 2025, 09:53 PM UTC

   This effort does not include servers running Windows Server IIS. Our team is continuing to monitor the progress of these changes.

3. resolved Dec 01, 2025, 02:36 PM UTC

   All updates have been successfully applied, and no issues have been detected; we are closing this status as resolved. Please reach out if you need further assistance.

Read the full incident report →

Started Nov 21, 2025, 07:12 AM UTC· resolved Nov 21, 2025, 05:58 PM UTC

1. investigating Nov 21, 2025, 07:12 AM UTC

   We are currently investigating a networking issue affecting the DC4 location. Our team is actively working on a resolution, and we will keep you updated on the status.

2. monitoring Nov 21, 2025, 09:06 AM UTC

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

3. monitoring Nov 21, 2025, 09:06 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 21, 2025, 05:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 20, 2025, 07:50 PM UTC· resolved Dec 22, 2025, 02:13 PM UTC

1. identified Nov 20, 2025, 07:50 PM UTC

   Our team will be updating the W3 Total Cache (W3TC) plugin on WordPress sites where the installed version is lower than 2.8.13. This update addresses CVE-2025-9501, a critical security vulnerability. A fixed version is available in W3TC 2.8.13 and later. To ensure the continued security and stability of your sites, our engineering team will apply this update. We do not anticipate any downtime during this process. No action is required on your part. Our team will monitor the update closely to ensure your sites remain fully functional. We appreciate your co-operation as we take this proactive step to protect your sites. For additional details on the Vulnerability, please refer: https://wpscan.com/vulnerability/6697a2c9-63ae-42f0-8931-f2e5d67d45ae/ If you encounter any issues after the update please contact our support team through a ticket in your portal or via live chat. We will provide updates on the progress of the patching.

2. identified Nov 21, 2025, 01:04 PM UTC

   Our team is actively involved in updating the W3 Total Cache (W3TC) plugin to the latest version for all sites running W3TC version 2.8.13 or earlier, as part of the ongoing remediation for CVE-2025-9501. We are closely monitoring all systems throughout this process to ensure the updates are applied successfully and to verify that there is no customer impact. Further updates will be shared as progress continues.

3. identified Dec 02, 2025, 09:17 PM UTC

   We have successfully applied the W3 Total Cache (W3TC) plugin update to thousands of customer sites where an outdated installation was identified and the environment met the minimum requirements for the upgrade. Our teams are continuing to review the hosting fleet and will apply updates wherever possible. In most cases, we are able to complete the update for our customers. However, several common blockers have prevented updates on some sites, including: Outdated PHP versions (older than PHP 7.2.5) Outdated WordPress installations (earlier than WordPress 5.3) Restricted or limited server access Once our update efforts are complete, we will contact customers whose environments contain a vulnerable W3TC installation that we were able to identify but could not be updated automatically, so that they and their teams can take any required remediation steps. We strongly recommend that all customers review their hosting environments and update the plugin as soon as possible, as a proof-of-concept for the exploit has been publicly released.

4. identified Dec 10, 2025, 08:10 PM UTC

   As shared in our earlier update, our teams are continuing to roll out the W3 Total Cache (W3TC) plugin update on sites that meet the minimum requirements. We’ve already been able to successfully update many sites running vulnerable or outdated versions, and this work is still in progress across the fleet. We’re also reviewing the remaining sites to determine where the update can be safely applied. In some cases, factors like outdated PHP/WordPress versions or limited server access may prevent the update from completing. For those situations, we will follow up directly with customers once our review is finished. We still strongly encourage all customers to review their sites and manually update the W3TC plugin if needed, as details about the exploit have already been made public. Further updates will be shared as progress continues.

5. identified Dec 18, 2025, 01:59 PM UTC

   Our teams are nearing the completion of the W3 Total Cache (W3TC) plugin update rollout across all eligible sites. The majority of sites running vulnerable or outdated versions have already been successfully updated. We are now finalizing reviews on the remaining sites where updates could not be automatically applied. In these cases, customer involvement may be required (for example, due to outdated PHP or WordPress versions, or access limitations). We will reach out directly to affected customers to review their hosting environment and update the plugin. We continue to recommend that all customers review their sites and manually update the W3TC plugin to version 2.8.14 or higher, if it has not already been updated, as exploit details are now publicly available. We’ll share a final update once this process is fully complete. If you have any questions or concerns, please don't hesitate to contact our support team through a ticket in your portal or via live chat.

6. resolved Dec 22, 2025, 02:13 PM UTC

   We’ve completed the update process for the affected W3TC plugin on sites that meet the required WordPress and PHP versions. For sites that did not meet the requirements and the server which is not accessible, we’ve contacted affected customers directly via support cases, as the update could not be applied safely at this time & We recommend that they review their all sites on the server and manually update the W3TC plugin to version 2.8.14 or higher, if it has not already been updated, as exploit details are now publicly available. Our support team is available. If you have any questions or concerns, please don't hesitate to contact our support team through a ticket in your portal or via live chat.

Read the full incident report →

Started Nov 19, 2025, 03:57 PM UTC· resolved Nov 19, 2025, 09:36 PM UTC

1. investigating Nov 19, 2025, 03:57 PM UTC

   We are currently experiencing an issue affecting access to the Customer Portal. Our teams are actively investigating the cause and working to restore full functionality as quickly as possible. At this time, customers may be unable to log in, and instead will see a maintenance page upon logging in. We will provide updates as soon as more information becomes available. We appreciate your patience while we work to resolve this.

2. identified Nov 19, 2025, 04:06 PM UTC

   Our team has identified the underlying issue impacting the Customer Portal and is working on a fix. Access may remain limited during this time. We will share another update shortly.

3. identified Nov 19, 2025, 04:18 PM UTC

   Our teams are actively investigating and working to restore full functionality as quickly as possible. In the meantime, clients can still open new support cases by emailing us directly at [email protected], or by replying to a previous case via email for any new issues. Our Support Team will continue to assist from there.

4. monitoring Nov 19, 2025, 04:24 PM UTC

   Access to the Customer Portal has been restored, and functionality should now be coming back online. Our teams have applied the necessary fixes and will continue to closely monitor performance and stability to ensure the portal remains fully operational. If you continue to experience any issues accessing the portal, please reach out to Support. Thank you for your patience while we worked through this incident.

5. resolved Nov 19, 2025, 09:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 11:49 AM UTC· resolved Nov 18, 2025, 08:06 PM UTC

1. investigating Nov 18, 2025, 11:49 AM UTC

   We are currently experiencing an issue affecting access to our official website (liquidweb.com) and websites routed through Cloudflare. Our engineering team is actively investigating the cause and working to restore full availability as quickly as possible. We will share additional updates as soon as more information becomes available. Thank you for your patience and understanding. If you need assistance, please reach out via live chat or open a support case.

2. investigating Nov 18, 2025, 12:17 PM UTC

   We are currently aware of a Cloudflare-related outage that may cause connectivity issues or downtime for customers' sites using Cloudflare services. Cloudflare is actively working to resolve the issue. We will provide updates as more information becomes available. Thank you for your patience and understanding.

3. investigating Nov 18, 2025, 12:35 PM UTC

   Cloudflare’s Global Network has been experiencing an incident affecting services across multiple regions. As a quick update, we’re now seeing signs of recovery. However, customers using Cloudflare may still notice higher-than-normal error rates while their team continues to work on fully resolving the issue. We’re monitoring the situation closely and will keep this space updated.

4. investigating Nov 18, 2025, 01:28 PM UTC

   As a status update - Cloudflare team have made changes that have allowed several Cloudflare services to recover. We're still seeing intermittent flapping for Cloudflare services. We will keep a close eye on the progress made by Cloudflare and will keep this space updated as they continue to work towards resolution.

5. investigating Nov 18, 2025, 02:18 PM UTC

   The Cloudflare team is continuing to work on restoring service for application services customers. We will closely monitor Cloudflare's progress and update the status as they work towards a resolution.

6. monitoring Nov 18, 2025, 02:51 PM UTC

   A fix has been implemented by Cloudflare, and affected sites appear to be recovering. We believe the incident is now resolved. We will continue to monitor for any errors to ensure all services are fully back to normal and will follow Cloudflare’s ongoing updates.

7. monitoring Nov 18, 2025, 04:50 PM UTC

   Websites using Cloudflare services now appear to be largely recovered after Cloudflare implemented their fix, and we are no longer seeing any new site-down reports related to this incident. However, according to Cloudflare’s updates, they are still observing reports of intermittent errors and are working to clear the remaining issues. We will continue to monitor Cloudflare’s updates and will provide status updates if any new issues are reported.

8. resolved Nov 18, 2025, 08:06 PM UTC

   Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency issues. This incident has been resolved.

Read the full incident report →

Started Nov 14, 2025, 07:16 PM UTC· resolved Nov 14, 2025, 10:25 PM UTC

1. investigating Nov 14, 2025, 07:16 PM UTC

   We recently identified an issue with a rack switch in one of our Lansing Data Centers. If your server is located in the affected area, you may have experienced a brief disruption in connectivity or a temporary increase in latency. The Network Team is actively working on a resolution; we are aware of the impact and will keep you updated on progress. Our teams are here to help you. Please do not hesitate to get help via Chat or Case at my.liquidweb.com.

2. monitoring Nov 14, 2025, 08:10 PM UTC

   The connectivity issue affecting a rack switch in our Lansing Data Center has been fully resolved. Our team is closely monitoring the network to ensure ongoing stability and optimal performance.

3. resolved Nov 14, 2025, 10:25 PM UTC

   The connectivity issue affecting a rack switch in our Lansing Data Center has been fully resolved, and everything is operational.

Read the full incident report →

Started Nov 12, 2025, 03:50 PM UTC· resolved Nov 18, 2025, 02:41 PM UTC

1. investigating Nov 12, 2025, 03:50 PM UTC

   We are currently investigating an issue that is impacting Windows Servers 2019 with a recent Windows update . 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. investigating Nov 12, 2025, 03:50 PM UTC

   Our Windows Engineering team is currently investigating a November 11th release KB5068791 (OS Build 17763.8027). Windows support article. https://support.microsoft.com/en-us/topic/november-11-2025-kb5068791-os-build-17763-8027-485c3175-0dc0-45c6-8328-553863ea2cbc#id0ebdh=windows_server_2019. We will provide updates as we have more details to share.

3. monitoring Nov 12, 2025, 05:18 PM UTC

   The issue has been identified, and we will continue to monitor affected systems for any further impact. Our Windows Engineering team has confirmed the incident is related to the November 11th, 2025 cumulative update (KB5068791 – OS Build 17763.8027). You can review Microsoft’s official release notes here: https://support.microsoft.com/en-us/topic/november-11-2025-kb5068791-os-build-17763-8027-485c3175-0dc0-45c6-8328-553863ea2cbc#id0ebdh=windows_server_2019 We will continue to monitor affected systems closely and provide updates as additional information becomes available. Our support team is on standby if you need any help or have questions or concerns. You can connect with us through the following channels: Live Chat: https://my.liquidweb.com/ Email: [email protected]

4. resolved Nov 18, 2025, 02:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 11, 2025, 06:00 PM UTC· resolved Nov 11, 2025, 06:46 PM UTC

1. investigating Nov 11, 2025, 06:00 PM UTC

   We are currently working to resolve a networking related issue which may result in sites being unreachable at this time. The issue should be resolved shortly, bringing sites back online.

2. monitoring Nov 11, 2025, 06:16 PM UTC

   The situation is currently being monitored however the issue with sites being unavailable as a result should now be resolved.

3. resolved Nov 11, 2025, 06:46 PM UTC

   The networking issue has been resolved.

Read the full incident report →

Started Nov 05, 2025, 05:02 PM UTC· resolved Dec 15, 2025, 08:39 PM UTC

1. investigating Nov 05, 2025, 05:02 PM UTC

   Liquid Web Systems Engineers are currently investigating a networking issues in our DC2 & DC3 Data Center. Liquid Web's Networking team have been engaged and are working to restore service as quickly as possible. We will provide further updates as soon as they become available. Our support team is on standby if you need any help or have questions or concerns. If you have any questions or concerns, please contact a member of our support team via live-chat or ticket ([email protected]).

2. investigating Nov 05, 2025, 05:03 PM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 05, 2025, 06:57 PM UTC

   Our Liquid Web Networking team identified the the networking issue with our DC2 & DC3 data centers. Networking is currently back online. We will continue to monitor the system to ensure stability. Thank you for your continued patience.

4. monitoring Nov 07, 2025, 01:24 AM UTC

   Our Network Team will be installing security patches over the next few days to fully resolve this issue. Any clients with hardware firewalls that were affected will receive a ticket regarding an emergency maintenance. Security patching will result in down times of 30 minutes or less. High-availability firewall configurations can be patched without any downtime. Please check your customer portal for that notification. We understand that up-time is critical, and we appreciate your cooperation as we take this proactive measure to protect your systems from potential threats. We will keep this status page updated with our team's progress.

5. monitoring Nov 07, 2025, 02:46 PM UTC

   Our Network Team has made strong progress on the ongoing network patching. This work will continue over the next few days as we complete updates across all systems. Our engineers are working continuously to ensure the process is completed efficiently and with minimal impact. Clients with hardware firewalls will continue to receive direct maintenance notifications via support tickets. Most updates result in brief interruptions of 30 minutes or less. We have high confidence that high-availability firewall configurations can be updated without downtime, however we may not be able to guarantee zero interruption. We appreciate your patience and understanding as we complete this important upgrade. Further updates will be posted here as progress continues.

6. monitoring Nov 07, 2025, 05:00 PM UTC

   This work is still in progress, and our engineers continue to update the remaining affected systems. Clients with hardware firewalls will continue receiving direct maintenance notifications via support tickets. Most updates are still expected to result in brief interruptions of 30 minutes or less. We appreciate your continued patience as we work through the remaining updates. Further updates will be posted here as progress continues.

7. monitoring Nov 07, 2025, 08:31 PM UTC

   Our Network Team has covered a great deal of ground as we continue progressing through the upgrade schedule. Updates and patching are being completed in cohorts to ensure a controlled and efficient roll out. Clients with hardware firewalls should continue to check their customer portal for ticket notifications regarding scheduled maintenance. We appreciate your continued patience and understanding as we work to complete these updates across all environments. Further updates will be posted here as progress continues.

8. monitoring Nov 08, 2025, 12:31 AM UTC

   Our Network Team has made significant progress in the current phase of client patching and upgrade work. Operations are proceeding smoothly. As we move into the weekend, additional patching and upgrade work will continue. Clients with hardware firewalls should check their customer portal for any maintenance ticket notifications. If you experience any issues following your upgrade, please reach out to our Support Team for assistance. Most updates are still expected to result in brief interruptions of 30 minutes or less. High-availability firewall configurations may see less downtime or possibly none. We appreciate your continued patience and understanding as we complete this phase of the upgrades. Further updates will be shared here as our work progresses.

9. monitoring Nov 08, 2025, 07:54 AM UTC

   As a quick update - our team has been working round the clock on the patching process, and we're seeing tremendous progress so far. Everything we patched so far has gone smoothly, with only minimal interruptions, to ensure all machines are patched and updated successfully. If you have a hardware firewall, please take a moment to check your customer portal for any maintenance ticket notifications. We'll be reaching out to each client directly before starting their maintenance. Should you notice any issues following your upgrade or have any questions, please don't hesitate to get in touch with our Support team - we'll be happy to help. Most updates are still expected to cause only brief interruptions of around 30 minutes or less, and high-availability firewall setups may see little to no downtime. We truly appreciate your continued patience and understanding while we complete this important phase of the upgrades. We'll keep this space updated as we make further progress.

10. monitoring Nov 09, 2025, 12:16 AM UTC

    Our Network Team has completed the patching and upgrade phase for client firewalls. All systems have been updated as planned; however, a small number of firewalls that have reached end-of-life status will need to be replaced. Clients affected by this next step should check their customer portal for a notification regarding the required firewall upgrade. This upgrade is part of our ongoing efforts to ensure your infrastructure remains secure and fully supported. We appreciate your continued cooperation and understanding as we complete this important maintenance initiative. Further updates will be provided here as work continues.

11. monitoring Nov 10, 2025, 06:05 PM UTC

    Our networking and data center teams continue to work on firewall replacements for clients who are on end of life hardware. Clients affected by this next step should check their customer portal for a notification ticket regarding the required firewall upgrade. Please coordinate in the ticket a window of time where our teams can perform the hardware replacement and upgrade. This will be an approximate 2 hour window of down time. This upgrade is part of our ongoing efforts to ensure your infrastructure remains secure and fully supported. We appreciate your continued cooperation and understanding as we complete this important maintenance initiative. Further updates will be provided here as work continues.

12. monitoring Nov 11, 2025, 01:56 PM UTC

    We’d like to thank our clients who have scheduled their firewall replacements with our team. Coordination and replacements for end of life firewalls have started smoothly in this next phase, and we appreciate the timely responses that have helped keep this process on track. We will continue to reach out to affected clients once a firewall is prepped and ready for replacement. As we continue with the remaining replacements, clients are encouraged to coordinate directly with our Support Team through their ticket once a new firewall is ready to go for their account. This will be an approximate 2 hour window of down time. We appreciate your continued partnership and cooperation as we complete this important upgrade initiative. Further updates will be shared here as progress continues.

13. monitoring Nov 18, 2025, 02:46 PM UTC

    We sincerely appreciate the continued cooperation from all clients in scheduling their firewall upgrades with our team. We are making strong and consistent progress across this initiative. Our teams are diligently working to complete the remaining upgrades as effectively and efficiently as possible. We will continue to proactively reach out to affected clients to schedule their 2-hour replacement window once their new hardware is prepped. Thank you for your ongoing partnership as we complete this critical infrastructure upgrade.

14. monitoring Nov 20, 2025, 05:34 PM UTC

    We sincerely appreciate your ongoing cooperation in coordinating firewall upgrades with our team. Significant progress is being made across this initiative, and our teams remain focused on completing the remaining upgrades as efficiently and effectively as possible. All affected clients have been contacted, and many of the firewall replacements have now been completed. For the few pending replacements, we are waiting for the scheduling confirmation from the remaining clients. For any clients we do not hear from, we will proactively coordinate a replacement window and notify you once it is scheduled. We thank you for your continued partnership as we finalize this critical infrastructure upgrade.

15. monitoring Dec 01, 2025, 03:33 PM UTC

    We sincerely appreciate your continued cooperation throughout the firewall upgrade initiative. Significant progress has been made so far, and our teams remain fully focused on planning and completing the remaining upgrades as efficiently and smoothly as possible. For those clients we have not yet heard back from, we are now moving forward with scheduling the remaining firewall replacements. Our team is reviewing availability and coordinating the final windows to ensure minimal impact wherever possible. You will be contacted soon with the confirmed date and time for your specific upgrade. Thank you again for your partnership and patience as we work to complete this critical improvement.

16. resolved Dec 15, 2025, 08:39 PM UTC

    The patching process has been completed, and our engineers have successfully updated all remaining affected systems. All updates were applied with minimal, expected interruptions. Thank you for your patience and understanding while we worked through this event. If you experience any issues or need assistance, please contact our Support Team via Live Chat or by opening a Support Case. Thank you, the Liquidweb Team.

Read the full incident report →