Liquid Web Outage History

Liquid Web is up right now

Liquid Web had 57 outages in the last 2 years totaling 1493h 20m of downtime — averaging 2.3 incidents per month.

There were 57 Liquid Web outages since October 2, 2025 totaling 1493h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.liquidweb.com

Minor June 6, 2026

Monitoring Service Degradation

Detected by Pingoru
Jun 06, 2026, 01:20 PM UTC
Resolved
Jun 07, 2026, 05:23 PM UTC
Duration
1d 4h
Timeline · 3 updates
  1. investigating Jun 06, 2026, 01:20 PM UTC

    We are currently experiencing a service degradation affecting our monitoring infrastructure and monitoring ticket integration. As a result, some monitoring alerts may be delayed in being generated, delivered, or escalated to our teams. Customer services themselves are not impacted by this issue; however, the delay in alert processing may result in slower detection and response to service-related incidents. Our engineers are actively investigating and working to restore normal monitoring performance 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. monitoring Jun 06, 2026, 09:52 PM UTC

    Our teams have implemented a fix for the issue affecting the monitoring system and are continuing to monitor the service to ensure stability. We will provide additional updates if any further issues are identified. Thank you for your patience.

  3. resolved Jun 07, 2026, 05:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 27, 2026

Phone System Issues

Detected by Pingoru
May 27, 2026, 07:58 PM UTC
Resolved
May 27, 2026, 11:52 PM UTC
Duration
3h 53m
Affected: Phone
Timeline · 3 updates
  1. investigating May 27, 2026, 07:58 PM UTC

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Major May 24, 2026

Issue Accessing Portal via login.liquidweb.com

Detected by Pingoru
May 24, 2026, 04:47 PM UTC
Resolved
May 25, 2026, 02:12 PM UTC
Duration
21h 24m
Affected: Management Portal
Timeline · 4 updates
  1. investigating May 24, 2026, 04:47 PM UTC

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

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

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Major May 11, 2026

Security Advisory: Linux Privilege Escalation Vulnerability (CVE-2026-31431)

Detected by Pingoru
May 11, 2026, 10:12 PM UTC
Resolved
Jun 06, 2026, 09:50 PM UTC
Duration
25d 23h
Affected: Cloud DedicatedCloud VPS HostingCPanel
Timeline · 2 updates
  1. identified May 11, 2026, 10:12 PM UTC

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

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

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026

Let's Encrypt Service Interruption

Detected by Pingoru
May 08, 2026, 08:56 PM UTC
Resolved
May 09, 2026, 01:16 AM UTC
Duration
4h 19m
Timeline · 3 updates
  1. investigating May 08, 2026, 08:56 PM UTC

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026

DC4 Networking Switch Issues

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

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Notice April 21, 2026

Spice Console disruption on Linux virtual machines

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

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

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

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

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

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

Read the full incident report →

Major April 14, 2026

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

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

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

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

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

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

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

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

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

Read the full incident report →

Minor April 10, 2026

Internal Network Outage Impacting Support Services.

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

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

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

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

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

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

Read the full incident report →

Minor April 7, 2026

Service disruption on multiple servers- DC3 Lansing

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

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Notice March 31, 2026

Magento 2 “PolyShell” File Upload Vulnerability efforts

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

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

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

    This incident has been resolved.

Read the full incident report →

Critical March 25, 2026

Infrastucture down issues at Phoenix Data Center

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

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

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

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

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

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

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

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

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

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

Read the full incident report →

Notice March 24, 2026

Service Disruption Due to Network Switch Failure

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

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

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

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

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

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

Read the full incident report →

Major March 16, 2026

ClamAV Service Disruption

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

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

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

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

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

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

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

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

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

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

Read the full incident report →

Minor February 27, 2026

Networking Instability

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

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

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

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

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

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

Read the full incident report →

Major February 24, 2026

Storm Switch Down Lansing (DC3)

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

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

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

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2026

Acronis Portal Degraded Performance.

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

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

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

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

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

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

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

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

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

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

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

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

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

    This incident has been resolved.

Read the full incident report →

Notice February 22, 2026

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

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

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

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

    We are continuing to investigate this issue.

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

    We are continuing to investigate this issue.

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

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

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

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

Read the full incident report →