Historial de interrupciones de Liquid Web

1. August 17, 2026 at 3:35 PM UTCidentified

   GitHub está reportando un rendimiento degradado a través de su página de estado esta mañana: https://www.githubstatus.com/ Por la página, este problema puede estar afectando las solicitudes de Pull, Issues, Copilot, Actions, Webhooks y API, entre otros servicios. Los clientes deben seguir la página de estado de GitHub para la información más reciente.

2. August 18, 2026 at 8:17 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 13, 2026 at 12:53 PM UTCinvestigating

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

2. August 13, 2026 at 2:51 PM UTCidentified

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

3. August 13, 2026 at 4:19 PM UTCidentified

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

4. August 13, 2026 at 5:08 PM UTCidentified

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

5. August 13, 2026 at 6:47 PM UTCmonitoring

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

6. August 14, 2026 at 3:12 AM UTCmonitoring

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

7. August 14, 2026 at 6:57 AM UTCmonitoring

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

8. August 14, 2026 at 10:59 AM UTCmonitoring

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

9. August 14, 2026 at 9:13 PM UTCmonitoring

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

10. August 15, 2026 at 7:50 PM UTCmonitoring

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

11. August 16, 2026 at 6:24 AM UTCresolved

    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.

1. August 12, 2026 at 3:44 PM UTCinvestigating

   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

1. August 8, 2026 at 1:24 PM UTCinvestigating

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

1. August 1, 2026 at 1:34 AM UTCinvestigating

   Estamos investigando la conectividad intermitente y el aumento de latencia afectando algunos servicios alojados en el entorno VMware MT. Nuestros ingenieros están trabajando activamente para identificar la causa y restaurar el servicio normal lo antes posible. Apreciamos su paciencia y comprensión mientras trabajamos para resolver este problema. Si tiene alguna pregunta o preocupación, por favor abra un ticket de soporte o contáctenos a través de chat.

2. August 1, 2026 at 2:07 AM UTCresolved

   El servicio ha sido restaurado en este momento, y los servicios auspiciados por VMware MT están operando normalmente. Gracias por su paciencia y comprensión mientras nuestros equipos trabajaron para resolver este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 18, 2026 at 1:48 AM UTCinvestigating

   El 17 de julio Wordpress.org anunció dos vulnerabilidades críticas de ejecución de código remoto (RCE) comúnmente conocidas como WP2Shell. Estas vulnerabilidades existen en Wordpress Core y permiten una solicitud no realizada para ejecutar código arbitrario en el sitio web de destino. Los clientes que ejecutan las versiones de Wordpress a continuación se recomienda encarecidamente actualizar a la última versión mostrada lo antes posible: Wordpress 6.8.x; fijado en 6.8.6 WordPress 6.9.x; fijo en 6.9.5 WordPress 7.0.x; fijo en 7.0.2 WordPress 7.1 beta, fijo en 7.1 beta2 Fuente: https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ Publicado hace 2 minutos. 17 jul, 2026 - 21:44 EDT

2. July 18, 2026 at 11:15 PM UTCidentified

   Nuestros equipos continúan trabajando diligentemente para evaluar el impacto de las vulnerabilidades básicas de WordPress recientemente reveladas y verificar que las medidas de mitigación apropiadas están en vigor. Seguimos participando activamente en nuestra investigación y estamos monitoreando la situación para cualquier nuevo desarrollo. Seguiremos vigilando de cerca la situación y adoptaremos las medidas adicionales necesarias para mantener la seguridad y la estabilidad del sistema. Si necesita ayuda o tiene alguna duda, póngase en contacto con nuestro equipo de soporte.

3. July 20, 2026 at 11:43 AM UTCmonitoring

   Se han restaurado los servicios y los sitios web están cargando como se espera. Nuestro equipo de Red continúa investigando la causa subyacente y está monitoreando activamente el medio ambiente para garantizar la estabilidad. En este momento, todos los servicios parecen estar funcionando normalmente. Si experimenta algún problema o necesita ayuda, por favor contacte con nuestro equipo de soporte.

4. July 20, 2026 at 11:47 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

5. July 20, 2026 at 11:48 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

6. July 20, 2026 at 8:20 PM UTCidentified

   Dada la gravedad de esta vulnerabilidad, los ingenieros de sistemas web líquidos han estado mejorando proactivamente las aplicaciones de Wordpress en nuestra flota. Los clientes todavía están fuertemente alentados a revisar sus sitios web de Wordpress y, si están afectados, actualizar a la versión parcheada lo antes posible.

7. July 23, 2026 at 7:47 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 8:02 PM UTCinvestigating

   Un subconjunto de servidores dentro de nuestro centro de datos Phoenix, AZ perdió energía. Nuestro equipo está investigando.

2. July 16, 2026 at 8:02 PM UTCmonitoring

   Se ha restablecido la energía primaria y estamos monitoreando la situación.

3. July 17, 2026 at 12:25 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 9:35 PM UTCinvestigating

   Estamos investigando un problema que afecta los servicios de Apache en nuestros servidores después de una actualización reciente de EasyApache ModSecurity. Los clientes de los servidores afectados pueden experimentar que los sitios web no están disponibles, errores HTTP o tiempo de conexión. Nuestro equipo de ingeniería trabaja actualmente para restaurar servicios. ¿Necesitas ayuda? Hable con nosotros o cree un boleto a través de my.liquidweb.com. Apreciamos su paciencia y comprensión mientras trabajamos para restaurar el servicio normal.

2. July 15, 2026 at 11:57 PM UTCmonitoring

   Se ha implementado una solución, y nuestro equipo de Ingeniería está monitoreando los servidores afectados para confirmar que los servicios de Apache permanecen estables.

3. July 23, 2026 at 6:50 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 2:34 PM UTCinvestigating

   Nuestro equipo está evaluando el impacto y alcance de Januscape Vulnerability (CVE-2026-53359), y su impacto en los servidores de nuestra flota y la mejor manera de aplicar parches a nuestra infraestructura de alojamiento. Enviaremos comunicaciones a cualquier cliente afectado mientras trabajamos para aplicar las mitigacións necesarias. Siguientes pasos: En la actualidad, los equipos están examinando la vulnerabilidad; se seguirán actualizaciones posteriores sobre la situación.

2. July 13, 2026 at 5:49 PM UTCidentified

   Nuestros equipos continúan implementando las actualizaciones de seguridad necesarias en los sistemas afectados en respuesta a la vulnerabilidad de Januscape (CVE-2026-53359). Como parte de esta remediación, algunos sistemas requieren un reinicio controlado para completar el proceso de parche. Después de cada reinicio, estamos validando la disponibilidad del sistema, la salud del servicio y la conectividad de red. Los sistemas que no regresan al servicio como se espera están siendo investigados y restaurados activamente por nuestros equipos de operaciones. Comprendemos la importancia de mantener la disponibilidad y estamos trabajando cuidadosamente para completar esta remediación al minimizar el impacto del cliente. Se proporcionarán actualizaciones adicionales a medida que continúen los esfuerzos de parche y validación.

3. July 29, 2026 at 7:28 PM UTCresolved

   Las actualizaciones de seguridad se han aplicado en toda la flota de Liquid Web.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 8, 2026 at 9:49 PM UTCinvestigating

   Se ha señalado a nuestra atención que un gran subconjunto de nuestros clientes de cPanel están viendo un mensaje de error al intentar conectarse a WHM. "Invalid License File. Autoridad incorrecta entregando la licencia." WebPros (cPanel) es consciente del problema y actualmente están investigando. Apreciamos su paciencia mientras trabajan para resolver el problema.

2. July 8, 2026 at 10:53 PM UTCmonitoring

   cPanel ha estado trabajando en mejorar el desempeño de sus servidores de licencias y los cambios implementados. Estamos viendo acceso a WHM y cPanel restaurado sin intervención de apoyo. Si sigues teniendo problemas, por favor contacta para apoyar y estaremos encantados de ayudar.

3. July 8, 2026 at 11:04 PM UTCmonitoring

   WebPros ha declarado que el problema se ha resuelto y que los servidores deben comenzar a renovar las licencias correctamente. Si sigues experimentando problemas iniciando sesión, no dudes en contactarnos por chat o correo electrónico y podemos acelerar la resolución.

4. July 9, 2026 at 11:59 AM UTCresolved

   Hemos observado la estabilidad continua, y las actualizaciones de la licencia de cPanel han ido sin problemas hasta ahora. Si necesita más asistencia, no dude en contactar con nuestro equipo de soporte a través de chat o correo electrónico.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 2, 2026 at 4:49 AM UTCinvestigating

   Estamos investigando problemas que afectan a servidores en nuestro Centro de Datos Fénix. Usted puede experimentar problemas de conectividad. Nuestros Ingenieros están investigando el tema para aislar la causa y restaurar la estabilidad. ¿Necesitas ayuda? Hable con nosotros o cree un caso a través de my.liquidweb.com. Apreciamos su paciencia y comprensión mientras trabajamos para restaurar este servicio. Gracias.

2. July 2, 2026 at 5:26 AM UTCidentified

   Estamos investigando un problema que afecta la conectividad entre nuestro Phoenix Data Center y los servicios internos. Hemos identificado que el problema está relacionado con la conectividad de red con un proveedor de corriente avanzada durante una ventana de mantenimiento programada. En este momento, se espera que los servicios de atención al cliente sigan siendo accesibles desde las redes públicas, y no hemos identificado un impacto generalizado en los servicios accesibles externamente. Nuestros Ingenieros están trabajando activamente con el proveedor de corriente para restaurar la conectividad plena lo más rápido posible. ¿Necesitas ayuda? Hable con nosotros o cree un caso a través de my.liquidweb.com. Apreciamos su paciencia y comprensión mientras trabajamos para restaurar este servicio. Gracias.

3. July 2, 2026 at 7:16 AM UTCmonitoring

   Estamos viendo una mejora continua en la conectividad de red ya que los enlaces afectados comienzan a recuperarse. Todos los sitios web y servidores del cliente permanecen en línea y son accesibles. El mantenimiento programado todavía está en marcha, y nuestro equipo de Ingeniería está monitoreando activamente el medio ambiente para garantizar la conectividad se restablece completamente. Seguiremos proporcionando actualizaciones a medida que se disponga de información adicional. ¿Necesitas ayuda? Hable con nosotros o cree un caso a través de my.liquidweb.com. Apreciamos su paciencia y comprensión mientras trabajamos para restaurar este servicio. Gracias.

4. July 2, 2026 at 10:37 AM UTCresolved

   Hemos estado monitoreando la situación y todo ha permanecido estable. Este incidente ya se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 26, 2026 at 5:23 AM UTCinvestigating

   Estamos asesorando a todos los clientes usando WordPress para verificar que los siguientes plugins se actualizan a las últimas versiones disponibles. Las vulnerabilidades reveladas recientemente afectan las versiones anteriores de estos plugins: CVE-2026-6279 – Avada Builder (Fusion Builder) – Ejecución de código remoto no autenticado Versiones afectadas: 3.15.2 y anteriores CVE-2026-10795 – UpdraftPlus Backup Plugin – Authentication Bypass Versiones afectadas: 1.26.4 y anteriores Estas vulnerabilidades pueden permitir a los atacantes no autenticados ganar control de sitios de WordPress vulnerables y comprometer cuentas de usuario de WordPress si los plugins no han sido actualizados a las últimas versiones disponibles. Si su sitio web utiliza cualquiera de estos plugins, le recomendamos encarecidamente que: Actualice el plugin(s) afectado a la última versión disponible inmediatamente. Revisa tu instalación de WordPress para cualquier cuenta de administrador inesperado, plugins o archivos modificados. Contacte con nuestro equipo de Soporte si cree que su sitio web ha sido afectado o si necesita ayuda para revisar su instalación.

2. July 9, 2026 at 2:15 PM UTCresolved

   Esta asesoría está siendo cerrada. Alentamos a nuestros clientes a asegurar que cualquier plugin de WordPress afectado ha sido actualizado a las últimas versiones disponibles y continuar siguiendo las mejores prácticas de seguridad de WordPress. Si cree que su sitio web puede haber sido impactado o requerir asistencia, por favor póngase en contacto con nuestro equipo de soporte.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 24, 2026 at 1:57 PM UTCinvestigating

   Somos conscientes de un evento de servicio de red que afecta a un subconjunto de clientes en nuestro DC3 Data Center en Lansing, Michigan. Actualmente, los ingenieros de redes web líquidos están comprometidos y trabajan para restaurar el servicio lo antes posible. Proporcionaremos otra actualización lo antes posible esta mañana con más información.

2. June 24, 2026 at 2:46 PM UTCmonitoring

   Los ingenieros de Redes Líquidas han identificado la causa e implementado una solución, el tráfico de red se ha reanudado en este momento a las áreas afectadas del centro de datos. Estamos monitoreando activamente el medio ambiente. Proporcionaremos otra actualización lo antes posible esta mañana con más información.

3. June 24, 2026 at 4:47 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 18, 2026 at 5:11 PM UTCinvestigating

   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.

1. June 6, 2026 at 1:20 PM UTCinvestigating

   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. June 6, 2026 at 9:52 PM UTCmonitoring

   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. June 7, 2026 at 5:23 PM UTCresolved

   This incident has been resolved.

1. May 27, 2026 at 7:58 PM UTCinvestigating

   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. May 27, 2026 at 8:09 PM UTCmonitoring

   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. May 27, 2026 at 11:52 PM UTCresolved

   This incident has been resolved.

1. May 25, 2026 at 7:17 PM UTCidentified

   A recently disclosed vulnerability (CVE-2026-48172) in the LiteSpeed user-end cPanel plugin allows an unprivileged user to escalate to root privileges in plugin versions between v2.3 and v2.4.4. This issue has been classified as high severity. Public reports suggest the vulnerability was being exploited in the wild in May 2026, and indicators of compromise have been published. On May 19th cPanel issued a separate update which disabled and removed the plugin. This vulnerability is patched in v2.4.7 of the user-end plugin and v5.3.1.0 of the WHM plugin (which bundles the user-end plugin). Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-48172 https://blog.litespeedtech.com/2026/05/21/security-update-for-litespeed-cpanel-plugin/ https://support.cpanel.net/hc/en-us/articles/40599423437079-Security-LiteSpeed-plugin-automatically-removed-during-nightly-update-May-19-2026 Status Our security and operations teams are completing an assessment of our infrastructure and will force a upcp update today for all systems we are able to reach. We plan to review for Indicators of Compromise following the updates. Customer Guidance Customers managing their own systems or using unmanaged services should ensure they have applied the latest security updates or have removed the plugin. Customers should also review their systems for indicators of compromise using the information provided in the LiteSpeed blog article. Should you need any assistance or have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: [email protected] We will continue monitoring this vulnerability and will provide updates if new information becomes available.

2. May 26, 2026 at 12:29 AM UTCresolved

   Status Update Our security and operations teams completed the assessment of our infrastructure, which forcd a upcp update today for all systems we were able to reach. We also reviewed environments for the indicators of compromise noted in the LiteSpeed article below. We will address any findings via a support ticket. We are resolving this incident at this time. Customer Guidance Customers are strongly encouraged to ensure they are running the updated version of the LiteSpeed plugin and to review their systems for the indicators of compromise. If our team does not have access to your system because it is unmanaged, self-managed, or access has been updated but not shared with Liquid Web, then we would not have been able to reach your system in order to apply updates or check for indicators of compromise. If you have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: [email protected]

1. May 24, 2026 at 4:47 PM UTCinvestigating

   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. May 24, 2026 at 5:56 PM UTCinvestigating

   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. May 24, 2026 at 6:38 PM UTCmonitoring

   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. May 25, 2026 at 2:12 PM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 10:12 PM UTCidentified

   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. June 6, 2026 at 9:50 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 8:56 PM UTCinvestigating

   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. May 8, 2026 at 9:09 PM UTCmonitoring

   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. May 9, 2026 at 1:16 AM UTCresolved

   This incident has been resolved.