- Detected by Pingoru
- Aug 01, 2026, 01:34 AM UTC
- Resolved
- Aug 01, 2026, 02:07 AM UTC
- Duration
- 33m
Affected: VMware CloudVMware Private Cloud
Timeline · 2 updates
-
investigating Aug 01, 2026, 01:34 AM UTC
We are investigating intermittent connectivity and increased latency affecting some services hosted in the VMware MT environment. Our engineers are actively working to identify the cause and restore normal service as quickly as possible. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or concerns, please open a support ticket or contact us via chat.
-
resolved Aug 01, 2026, 02:07 AM UTC
Service has been restored at this time, and the affected VMware MT-hosted services are operating normally. Thank you for your patience and understanding while our teams worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 11:43 AM UTC
- Resolved
- Jul 23, 2026, 07:47 PM UTC
- Duration
- 3d 8h
Timeline · 7 updates
-
investigating Jul 18, 2026, 01:48 AM UTC
On July 17th Wordpress.org announced two critical remote code execution (RCE) vulnerabilities commonly known as WP2Shell. These vulnerabilities exist in Wordpress Core and allow an unauthenticated request to execute arbitrary code on the target website. Customers running the Wordpress versions below are strongly advised to upgrade to latest version shown as soon as possible: Wordpress 6.8.x; fixed in 6.8.6 WordPress 6.9.x; fixed in 6.9.5 WordPress 7.0.x; fixed in 7.0.2 WordPress 7.1 beta, fixed in 7.1 beta2 Source: https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ Posted 2 minutes ago. Jul 17, 2026 - 21:44 EDT
-
identified Jul 18, 2026, 11:15 PM UTC
Our teams continue to work diligently to assess the impact of the recently disclosed WordPress Core vulnerabilities and verify that appropriate mitigation measures are in place. We remain actively engaged in our investigation and are monitoring the situation for any new developments. We will continue to closely monitor the situation and take any additional steps necessary to maintain system security and stability. If you need assistance or have any concerns, please contact our Support team.
-
monitoring Jul 20, 2026, 11:43 AM UTC
Services have been restored, and websites are currently loading as expected. Our Network team is continuing to investigate the underlying cause and is actively monitoring the environment to ensure stability. At this time, all services appear to be operating normally. If you experience any issues or need assistance, please contact our Support team.
-
identified Jul 20, 2026, 11:47 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jul 20, 2026, 11:48 AM UTC
We are continuing to work on a fix for this issue.
-
identified Jul 20, 2026, 08:20 PM UTC
Given the severity of this vulnerability, Liquid Web Systems Engineers have been proactively upgrading affected Wordpress applications across our fleet. Customers are still strongly encouraged to review their Wordpress websites and, if affected, to update to the patched version as soon as possible.
-
resolved Jul 23, 2026, 07:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 08:02 PM UTC
- Resolved
- Jul 17, 2026, 12:25 AM UTC
- Duration
- 4h 23m
Affected: DC4 - PHX
Timeline · 3 updates
-
investigating Jul 16, 2026, 08:02 PM UTC
A subset of servers within our Phoenix, AZ data center lost power. Our on-site team is investigating.
-
monitoring Jul 16, 2026, 08:02 PM UTC
Primary power has been restored, and we are monitoring the situation.
-
resolved Jul 17, 2026, 12:25 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 09:35 PM UTC
- Resolved
- Jul 23, 2026, 06:50 PM UTC
- Duration
- 7d 21h
Affected: Cloud DedicatedCloud VPS Hosting
Timeline · 3 updates
-
investigating Jul 15, 2026, 09:35 PM UTC
We are investigating an issue affecting Apache services on our servers following a recent EasyApache ModSecurity update. Customers on affected servers may experience websites being unavailable, HTTP errors, or connection timeouts. Our Engineering team is currently working to restore services. Need help? Chat with us or create a ticket via my.liquidweb.com. We appreciate your patience and understanding while we work to restore normal service.
-
monitoring Jul 15, 2026, 11:57 PM UTC
A fix has been implemented, and our Engineering team is monitoring the affected servers to confirm Apache services remain stable.
-
resolved Jul 23, 2026, 06:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 02:34 PM UTC
- Resolved
- Jul 29, 2026, 07:28 PM UTC
- Duration
- 20d 4h
Affected: Cloud VPS Hosting
Timeline · 3 updates
-
investigating Jul 09, 2026, 02:34 PM UTC
Our team is currently assessing the impact and scope of Januscape Vulnerability (CVE-2026-53359), and its impact on servers in our fleet and the best way to apply patches to our hosting infrastructure. We will be sending communications to any affected customers as we work to apply the necessary mitigations. Next Steps: Teams are currently in review of vulnerability; subsequent status updates will follow.
-
identified Jul 13, 2026, 05:49 PM UTC
Our teams are continuing to deploy the required security updates across affected systems in response to the Januscape Vulnerability (CVE-2026-53359). As part of this remediation, some systems require a controlled reboot to complete the patching process. Following each reboot, we are validating system availability, service health, and network connectivity. Systems that do not return to service as expected are being actively investigated and restored by our operations teams. We understand the importance of maintaining availability and are working carefully to complete this remediation while minimizing customer impact. Additional updates will be provided as patching and validation efforts continue.
-
resolved Jul 29, 2026, 07:28 PM UTC
The security updates have been applied across the Liquid Web fleet.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 09:49 PM UTC
- Resolved
- Jul 09, 2026, 11:59 AM UTC
- Duration
- 14h 9m
Affected: CPanel
Timeline · 4 updates
-
investigating Jul 08, 2026, 09:49 PM UTC
It has been brought to our attention that a large subset of our cPanel customers are seeing an error message when attempting to log into WHM. "Invalid License File. Incorrect authority delivering the license." WebPros (cPanel) is aware of the issue and they are currently investigating. We appreciate your patience as they work to resolve the issue.
-
monitoring Jul 08, 2026, 10:53 PM UTC
cPanel has been working on improving the performance of their licensing servers and implemented changes. We are seeing access to WHM and cPanel restored without intervention from support. If you are still having issues please reach out to support and we will be happy to assist.
-
monitoring Jul 08, 2026, 11:04 PM UTC
WebPros has stated that the issue has been resolved and that servers should begin to renew licenses properly. If you are still experiencing issues logging in, feel free to contact us via chat or email and we can expedite the resolution.
-
resolved Jul 09, 2026, 11:59 AM UTC
We have observed continued stability, and the cPanel licence updates have gone smoothly so far. If you need any further assistance, please do not hesitate to reach out to our Support team via chat or email.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 04:49 AM UTC
- Resolved
- Jul 02, 2026, 10:37 AM UTC
- Duration
- 5h 47m
Affected: DC4 - PHX
Timeline · 4 updates
-
investigating Jul 02, 2026, 04:49 AM UTC
We are investigating issues affecting servers in our Phoenix Data Center. You may experience connectivity issues. Our Engineers currently investigating the issue to isolate the cause and restore stability. Need help? Chat with us or create a case via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.
-
identified Jul 02, 2026, 05:26 AM UTC
We are investigating an issue affecting connectivity between our Phoenix Data Center and internal services. We have identified that the issue is related to network connectivity with an upstream provider during a scheduled maintenance window. At this time, customer-facing services are expected to remain accessible from public networks, and we have not identified a widespread impact to externally accessible services. Our Engineers are actively working with the upstream provider to restore full connectivity as quickly as possible. Need help? Chat with us or create a case via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.
-
monitoring Jul 02, 2026, 07:16 AM UTC
We are seeing continued improvement in network connectivity as the affected links begin to recover. All customer websites and servers remain online and accessible. The scheduled maintenance is still in progress, and our Engineering team is actively monitoring the environment to ensure connectivity is fully restored. We will continue to provide updates as additional information becomes available. Need help? Chat with us or create a case via my.liquidweb.com. We appreciate your patience and understanding as we work to restore this service. Thank you.
-
resolved Jul 02, 2026, 10:37 AM UTC
We have been monitoring the situation, and everything has remained stable. This incident has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 05:23 AM UTC
- Resolved
- Jul 09, 2026, 02:15 PM UTC
- Duration
- 13d 8h
Affected: InterWorx
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 01:57 PM UTC
- Resolved
- Jun 24, 2026, 04:47 PM UTC
- Duration
- 2h 50m
Affected: LAN NetworkDC3 - LAN
Timeline · 3 updates
-
investigating Jun 24, 2026, 01:57 PM UTC
We are aware of a network service event affecting a subset of customers in our DC3 Data Center in Lansing, Michigan. Liquid Web Network Engineers are currently engaged and working to restore service as quickly as possible. We will provide another update as soon as possible this morning with more information.
-
monitoring Jun 24, 2026, 02:46 PM UTC
Liquid Web Network Engineers have identified the cause and implemented a fix, network traffic has resumed at this time to affected areas of the data center. We are actively monitoring the environment. We will provide another update as soon as possible this morning with more information.
-
resolved Jun 24, 2026, 04:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 05:11 PM UTC
- Resolved
- Jun 18, 2026, 05:59 PM UTC
- Duration
- 47m
Timeline · 1 update
-
investigating Jun 18, 2026, 05:11 PM UTC
We are currently experiencing a partial degradation in our monitoring and alerting system. Some monitoring components are intermittently unable to generate or relay alerts as expected. Our engineering teams are actively investigating the issue to identify the cause and restore full monitoring functionality. 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.
Read the full incident report →
- 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
-
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.
-
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.
-
resolved May 27, 2026, 11:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 25, 2026, 07:17 PM UTC
- Resolved
- May 26, 2026, 12:29 AM UTC
- Duration
- 5h 11m
Affected: CPanel
Timeline · 2 updates
Read the full incident report →
- 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
-
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.
-
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.
-
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.
-
resolved May 25, 2026, 02:12 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Jun 06, 2026, 09:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 08:56 PM UTC
- Resolved
- May 09, 2026, 01:16 AM UTC
- Duration
- 4h 19m
Timeline · 3 updates
-
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
-
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
-
resolved May 09, 2026, 01:16 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 09:57 PM UTC
- Resolved
- Jul 23, 2026, 07:52 PM UTC
- Duration
- 85d 21h
Affected: CPanel
Timeline · 16 updates
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 11:02 AM UTC
- Resolved
- Apr 25, 2026, 01:09 AM UTC
- Duration
- 2d 14h
Affected: CPanel
Timeline · 5 updates
Read the full incident report →
- 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
-
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.
-
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.
-
resolved Apr 23, 2026, 05:55 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
identified Apr 21, 2026, 11:47 AM UTC
The issue has been identified and a fix is being implemented.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Apr 08, 2026, 04:41 PM UTC
- Resolved
- Apr 08, 2026, 11:13 PM UTC
- Duration
- 6h 31m
Affected: Chat
Timeline · 6 updates
Read the full incident report →
- 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
-
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]).
-
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.
-
resolved Apr 07, 2026, 07:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 06:42 PM UTC
- Resolved
- Apr 15, 2026, 12:10 PM UTC
- Duration
- 13d 17h
Affected: CPanelInterWorxPlesk
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 06:55 PM UTC
- Resolved
- Mar 31, 2026, 09:05 PM UTC
- Duration
- 2h 10m
Timeline · 2 updates
-
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]).
-
resolved Mar 31, 2026, 09:05 PM UTC
This incident has been resolved.
Read the full incident report →