Is Liquid Web down?
Last checked 4m agoNo incidents right now.
Liquid Web is operational right now. Last checked 4m ago; the most recent incident resolved 3d ago.
Real-time Liquid Web status, recent outages, and incident history — pulled directly from Liquid Web's official status page at https://status.liquidweb.com every 5 minutes. Pingoru tracks 27 Liquid Web services and has captured 31 incidents in the last 90 days (98.63% uptime). Get email, Slack, Discord, or webhook alerts the moment Liquid Web reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- CPanel
Timeline · 5 updates
- 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
- 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.
- 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.
- 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
- resolved · Sep 09, 2026, 09:24 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- CPanelInterWorxPlesk
Timeline · 9 updates
- 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 .
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Latest: Our engineering teams continue to make progress on containment, investigation, and remediation across affected environments. Adobe has released a patch addressing the underlying vu…
-
-
Timeline · 2 updates
- 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.
- resolved · Aug 18, 2026, 08:17 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- PHX Network
Timeline · 11 updates
- 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.
- 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
- 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
- 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
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
Latest: 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.
-
-
Timeline · 2 updates
- 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
- 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.
Latest: The WordPress security vulnerability CVE-2026-65640 has been addressed in the latest WordPress security releases. Customers are encouraged to keep their WordPress installations upd…
-
See the full Liquid Web outage history
11 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Liquid Web outage history →Or sign up free to get alerts when Liquid Web breaks · 10 free monitors · No credit card
- Started Sep 08, 2026, 06:52 PM UTC · Resolved Sep 09, 2026, 09:24 PM UTC · 1d 2h
- Started Sep 05, 2026, 01:48 PM UTC · Resolved Sep 09, 2026, 10:51 PM UTC · 4d 9h
- GitHub Peformance Impact ResolvedStarted Aug 17, 2026, 03:35 PM UTC · Resolved Aug 18, 2026, 08:17 PM UTC · 1d 4h
- Started Aug 13, 2026, 12:53 PM UTC · Resolved Aug 16, 2026, 06:24 AM UTC · 2d 17h
- Started Aug 12, 2026, 03:44 PM UTC · Resolved Sep 03, 2026, 01:52 PM UTC · 21d 22h
- Started Aug 08, 2026, 01:24 PM UTC · Resolved Sep 03, 2026, 01:53 PM UTC · 26d
- VMware MT Service Degradation ResolvedStarted Aug 01, 2026, 01:34 AM UTC · Resolved Aug 01, 2026, 02:07 AM UTC · 33m
- Started Jul 20, 2026, 11:43 AM UTC · Resolved Jul 23, 2026, 07:47 PM UTC · 3d 8h