Nexcess Outage History

Started Sep 26, 2026, 07:26 PM UTC· resolved Sep 27, 2026, 12:01 AM UTC

1. identified Sep 26, 2026, 07:26 PM UTC

   Our team has identified a subset of Cloudhost outages in the US-Midwest-2 region and is actively investigating the issue. We will provide another update as soon as more information becomes available. We appreciate your patience as our team works to resolve this issue. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

2. monitoring Sep 26, 2026, 10:05 PM UTC

   Our team has confirmed that the affected Cloudhost services in the US-Midwest-2 region are operating normally. We are continuing to monitor the environment to ensure services remain stable. We appreciate your patience while our team worked to resolve the issue.

3. resolved Sep 27, 2026, 12:01 AM UTC

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

Read the full incident report →

Started Sep 22, 2026, 08:13 PM UTC· resolved Sep 25, 2026, 07:19 PM UTC

1. investigating Sep 22, 2026, 08:13 PM UTC

   WordPress has identified a critical security vulnerability designated as "Click2Shell" affecting all WordPress versions prior to 7.1.1. This vulnerability can enable unauthenticated Remote Code Execution (RCE) when a logged-in administrator visits a specially crafted link. Current Status & Hosting Actions Our engineering team is currently assessing our entire hosting fleet and determining next steps. There are currently no known workarounds for this vulnerability other than upgrading to the latest version of WordPress. Recommended Action for Customers We strongly advise all customers managing WordPress installations to review their environments immediately and update to WordPress version 7.1.1. We will continue to monitor the situation closely and provide further updates as new information becomes available.

2. identified Sep 23, 2026, 06:35 AM UTC

   Our Engineering team continues to assess and work on the WordPress security vulnerabilities across our hosting fleet. A new critical vulnerability, CVE-2026-87902, has been disclosed. WordPress 7.1.2 includes the security fix for this vulnerability. Recommended Action for Customers We strongly advise all customers managing WordPress installations to update to WordPress version 7.1.2 immediately. We will continue to monitor the situation closely and provide further updates as new information becomes available.

3. resolved Sep 25, 2026, 07:19 PM UTC

   As part of our proactive security efforts, Nexcess System Engineers scanned our fleet and automatically upgraded WordPress installations where possible to the appropriate patched versions. Automated update attempts were unsuccessful for some websites due to site-specific errors. Customers with websites that were unable to be upgraded should receive a ticket identifying the server and path to the website. All customers are strongly encouraged to confirm the Wordpress version for all of the websites, including those in staging or development, have been updated to the latest minor version of Wordpress released on September 22nd in order to protect the website from this exploit. For additional information, please refer to the official WordPress security announcements: https://wordpress.org/news/2026/09/wordpress-7-1-2-release/ https://wordpress.org/documentation/wordpress-version/version-7-1-2/ If you have any questions or need assistance with the update process, please contact our Support team. You can reach us through the following channels: Live Chat via the Customer Portal: https://my.nexcess.net/ Email: [email protected] We appreciate your patience and understanding as we work to secure your services.

Read the full incident report →

Started Sep 16, 2026, 09:14 AM UTC· resolved Sep 17, 2026, 03:13 AM UTC

1. investigating Sep 16, 2026, 09:14 AM UTC

   We are currently aware of an issue affecting a third-party platform used by our Support teams to manage and respond to client cases. The provider is actively investigating the issue and working toward a resolution. As a result, clients may experience delays in responses to support cases while the issue is ongoing. Our teams are monitoring the situation and will continue responding to cases as quickly as possible. We will provide further updates as more information becomes available.

2. resolved Sep 17, 2026, 03:13 AM UTC

   The issue affecting the third-party platform used by our Support teams has been resolved. The provider has confirmed that service stability and performance have returned to expected levels, and our teams are no longer seeing ongoing impact. Support case access and case management functionality have returned to normal. We apologize for the disruption and any delays this may have caused.

Read the full incident report →

Started Sep 12, 2026, 08:12 AM UTC· resolved Sep 12, 2026, 01:56 PM UTC

1. investigating Sep 12, 2026, 08:12 AM UTC

   We are currently investigating a performance issue affecting a subset of our cloudhosts, cloudhost-4892688.us-midwest-2.nxcli.net and cloudhost-4892180.us-midwest-2.nxcli.net, in the US-Midwest-2 region. Customers may experience slowness or degraded performance, and there is a potential for service interruption while the issue is being investigated. Our systems engineers have been engaged and are working to identify the cause and restore normal performance as quickly as possible. We appreciate your patience. If you have any questions or concerns, please contact us via live chat or case.

2. monitoring Sep 12, 2026, 08:35 AM UTC

   Our engineers have successfully recovered the impacted cloudhosts. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed

3. resolved Sep 12, 2026, 01:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 11:31 AM UTC· resolved Sep 09, 2026, 09:27 PM UTC

1. investigating Sep 09, 2026, 11:31 AM UTC

   Our Engineers are investigating an interruption in service affecting cloudhost-9412708-us-midwest-1-nxcli-net and cloudhost-10309510.us-midwest-1.nxcli.net. We understand the inconvenience this may cause and truly appreciate your patience while we resolve the issue. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

2. identified Sep 09, 2026, 11:50 AM UTC

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

3. monitoring Sep 09, 2026, 11:54 AM UTC

   Our engineers have successfully recovered the service on the impacted cloudhost. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

4. resolved Sep 09, 2026, 09:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 05, 2026, 01:50 PM UTC· resolved Oct 26, 2026, 05:28 PM UTC

1. identified Sep 05, 2026, 01:50 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 .

2. identified Sep 06, 2026, 12:51 AM 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.

3. identified Sep 06, 2026, 09:09 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.

4. identified Sep 06, 2026, 02:29 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.

5. 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.

6. 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.

7. identified Sep 07, 2026, 03:07 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. Restoration efforts are also progressing as we work to safely return affected sites to a known-good state. 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.

8. identified Sep 08, 2026, 06:25 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.

9. identified Sep 09, 2026, 10:52 PM UTC

   Our Engineering 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 applying the patch across affected environments in batches. There is no specific priority or ordering for the affected Magento versions; the rollout is progressing batch by batch, with our teams continuing to apply the patch across all affected versions. At the same time, we will continue deep-system scans and validate the patched environments to ensure safe recovery paths and restore impacted sites to a known-good state. We will continue to share updates as additional remediation details and progress become available. If you need assistance or have any concerns, please contact our Support team.

10. identified Sep 10, 2026, 08:15 AM UTC

    Our technical teams continue to actively work through the remediation process across affected environments. The patch rollout is progressing in batches, with teams continuing to apply the available Adobe security patch across affected Magento versions. We are also continuing system scans and validation of patched environments to help ensure affected sites can be safely restored to a known-good state. We will continue to keep clients informed as meaningful progress is made. If you need assistance or have any concerns, please contact our Support team.

11. resolved Oct 26, 2026, 05:28 PM UTC

    Our Engineering teams have completed the patching process for all affected Magento sites where the available Adobe security patch could be successfully applied. For sites where the patch could not be applied, individual support cases have been created, and affected customers have been contacted with additional information and recommended next steps. Our patching efforts related to this incident are now complete. We encourage all customers to remain vigilant and keep their Magento installations up to date with the latest available security patches and supported versions. Thank you for your cooperation and patience while our teams worked through this security event. If you have any questions or require assistance, please reach out via chat or support case.

Read the full incident report →

Started Sep 03, 2026, 12:08 AM UTC· resolved Sep 03, 2026, 03:33 AM UTC

1. identified Sep 03, 2026, 12:08 AM UTC

   Our teams have identified a distributed denial of service attack (DDOS) on cloudhost-2038507.us-west-1.nxcli.net. Our network engineers are already enabled for mitigation. We will provide another update as soon as more information becomes available. If you have any questions or concerns, please contact us via live chat or case.

2. monitoring Sep 03, 2026, 01:27 AM UTC

   The mitigation has taken effect, and the server is stable and operating normally. We have closely monitored the environment and have not observed any further issues. 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.

3. resolved Sep 03, 2026, 03:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 03:04 PM UTC· resolved Sep 03, 2026, 11:13 AM UTC

1. investigating Sep 02, 2026, 03:04 PM UTC

   We are currently investigating a performance issue affecting a subset of our servers in the au-south-1 region. Customers may experience slowness or degraded performance, and there is a potential for service interruption while the issue is being investigated. Our systems engineers have been engaged and are working to identify the cause and restore normal performance as quickly as possible. We appreciate your patience. If you have any questions or concerns, please contact us via live chat or case.

2. identified Sep 02, 2026, 05:37 PM UTC

   As an update regarding the ongoing latency issue: Some customers may experience increased latency and/or intermittent service interruptions when traffic traverses affected network paths in the US West region. The issue has been linked to two separate fiber cuts impacting an upstream network provider in the Los Angeles and Honolulu areas. The upstream provider's engineers are actively working to address both fiber cuts, and their third-party fiber vendor has also been engaged. Our Network Administration team is continuing to monitor the situation closely. At this time, our monitoring indicates that customer sites remain operational, though some users may experience intermittent increased latency depending on their network path. We will provide further updates as more information becomes available. We appreciate your patience and understanding.

3. resolved Sep 03, 2026, 11:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 30, 2026, 05:30 AM UTC· resolved Aug 30, 2026, 08:31 AM UTC

1. investigating Aug 30, 2026, 05:30 AM UTC

   We are investigating issues affecting the Nexcess Client Portal login at https://portal.nexcess.net/. Our engineering team is working to identify the cause and restore full availability as quickly as possible. We will provide updates as more information becomes available. We appreciate your patience and understanding during this time.

2. monitoring Aug 30, 2026, 06:05 AM UTC

   A fix has been implemented that resolves the issues with the portal login. We are currently monitoring the results to ensure stability.

3. resolved Aug 30, 2026, 08:31 AM UTC

   The Nexcess Client Portal login issue has been resolved. Services are now fully operational, and no further impact has been observed.

Read the full incident report →

Started Aug 20, 2026, 11:28 AM UTC· resolved Aug 24, 2026, 02:03 PM UTC

1. investigating Aug 20, 2026, 11:28 AM UTC

   We are aware of an issue affecting some WordPress websites using the WP Rocket plugin following the WordPress 7.1 update. This may result in website interruptions or fatal errors. Resolution: WP Rocket has released a fix in version 3.23.2.2. If your website is affected, please update the WP Rocket plugin to version 3.23.2.2 or later. If you are unable to update the plugin, WP Rocket has also provided temporary workarounds in their documentation: https://docs.wp-rocket.me/article/1927-fatal-error-on-wordpress-7-1 We will provide additional updates as more information becomes available. If you have any questions or concerns, please don't hesitate to contact us via live chat or by opening a support case.

2. resolved Aug 24, 2026, 02:03 PM UTC

   We have completed our review of this issue and are closing this incident. The root cause was identified as a compatibility issue within the WP Rocket plugin following the WordPress 7.1 update. WP Rocket has released a fix, and customers can resolve the issue by updating the plugin to version 3.23.2.2 or later. As this involves a third-party plugin, we are not performing automated plugin updates across customer environments. However, we conducted a fleet-wide review to identify customers using affected WP Rocket versions and proactively communicated the issue, available fix, and recommended actions to those customers. Customers who continue to experience issues can contact our Support team for assistance with disabling the plugin or for guidance on updating WP Rocket to a fixed version. No further actions are pending from our side, and this incident is now considered closed.

Read the full incident report →

Started Aug 17, 2026, 03:35 PM UTC· resolved Aug 18, 2026, 08:16 PM UTC

1. 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.

2. investigating Aug 17, 2026, 04:27 PM UTC

   This issue is currently affecting the ability to create new Magento, Wordpress, and WooCommerce websites and some dedicated cloud plans through the Nexcess customer portal. Nexcess Engineering and Development teams are currently reviewing the service impact and evaluating options to return service as quickly as possible. We will provide further updates as soon as they are available. We appreciate your patience as our team works to resolve this issue. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

3. resolved Aug 18, 2026, 08:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 16, 2026, 09:34 PM UTC· resolved Aug 18, 2026, 07:30 PM UTC

1. investigating Aug 16, 2026, 09:34 PM UTC

   We are currently investigating a service-impacting issue affecting the server cloudhost-4895770.us-midwest-2.nxcli.net. Our Nexcess Systems Engineering team has been engaged and is actively working to restore 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 don't hesitate to contact us via live chat or by opening a support case.

2. identified Aug 16, 2026, 11:32 PM UTC

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

3. monitoring Aug 17, 2026, 02:02 AM UTC

   Service has been successfully restored on the impacted cloudhost. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

4. resolved Aug 18, 2026, 07:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2026, 03:45 PM UTC· resolved Sep 02, 2026, 08:31 PM UTC

1. investigating Aug 12, 2026, 03:45 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

2. resolved Sep 02, 2026, 08:31 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.

Read the full incident report →

Started Aug 11, 2026, 05:55 AM UTC· resolved Aug 11, 2026, 08:30 AM UTC

1. investigating Aug 11, 2026, 05:55 AM UTC

   We are currently investigating an issue affecting a subset of our servers in the us-west-1 region. Our systems engineers have been engaged and are working to restore service as quickly as possible. We appreciate your patience. If you have any questions or concerns. Please contact us via live chat or case.

2. monitoring Aug 11, 2026, 06:39 AM UTC

   Our team has now implemented a fix, and affected servers and services should be operating as expected at this time. We will continue to monitor the situation closely to ensure ongoing stability. If you have any questions or concerns, please contact us via live chat or case.

3. resolved Aug 11, 2026, 08:30 AM UTC

   The issue affecting a subset of our servers in the us-west-1 region has been resolved. Our team has restored service, and the affected servers are operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding while we worked to resolve the issue.

Read the full incident report →

Started Aug 08, 2026, 01:28 PM UTC· resolved Sep 02, 2026, 08:33 PM UTC

1. investigating Aug 08, 2026, 01:28 PM UTC

   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: 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.

2. resolved Sep 02, 2026, 08:33 PM UTC

   The WordPress security vulnerability CVE-2026-64638 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.

Read the full incident report →

Started Aug 07, 2026, 11:32 PM UTC· resolved Aug 08, 2026, 11:48 AM UTC

1. investigating Aug 07, 2026, 11:32 PM UTC

   Our Engineers are investigating an interruption in service affecting cloudhost-2915341.us-midwest-1.nxcli.net & cloudhost-2915335.us-midwest-1.nxcli.net. We understand the inconvenience this may cause and truly appreciate your patience while we resolve the issue. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

2. monitoring Aug 08, 2026, 01:25 AM UTC

   Our Engineers have successfully restored service to the affected servers, and all services are currently operating normally. The incident is now in a monitoring state. We will continue to watch the environment closely to ensure stability following the restoration of service. We appreciate your patience throughout this incident and will provide additional updates if there are any significant changes. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

3. resolved Aug 08, 2026, 11:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 04, 2026, 05:31 AM UTC· resolved Aug 04, 2026, 11:51 AM UTC

1. investigating Aug 04, 2026, 05:31 AM UTC

   We are currently investigating a service-impacting issue affecting the server cloudhost-1189763.au-south-1.nxcli.net. Our Nexcess Systems Engineering team has been engaged and is actively working to restore 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 don't hesitate to contact us via live chat or by opening a support case.

2. identified Aug 04, 2026, 08:40 AM UTC

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

3. monitoring Aug 04, 2026, 09:24 AM UTC

   Our engineers have successfully recovered the service on the impacted cloudhost. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

4. resolved Aug 04, 2026, 11:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 18, 2026, 01:44 AM UTC· resolved Jul 23, 2026, 07:45 PM UTC

1. investigating Jul 18, 2026, 01:44 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/

2. identified Jul 18, 2026, 11:17 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.

3. monitoring Jul 20, 2026, 08:36 PM UTC

   The Nexcess Managed Wordpress platform configures Wordpress Core updates by default and the vast majority of websites have been updated. Nexcess System Engineers proactively attempted to update affected websites that were not already on the patched version. In some cases this was not possible to do. The Nexcess Managed Wordpress Development team has pushed a must-use plugin that mitigates this vulnerability where the application is not on a patched version. All customers are strongly encouraged to ensure their websites have been updated to the latest version of Wordpress.

4. resolved Jul 23, 2026, 07:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 10, 2026, 09:15 AM UTC· resolved Jul 10, 2026, 04:29 PM UTC

1. investigating Jul 10, 2026, 09:15 AM UTC

   We have encountered an issue with a CloudHost, and our engineers have identified the cause. The team is actively working towards a resolution. We understand the impact this may have and will continue to provide updates here as progress is made. In the meantime, if you have any questions, please do not hesitate to contact our Support team via chat or email.

2. monitoring Jul 10, 2026, 09:34 AM UTC

   Our Engineering team has resolved the issue, and the host is now back online. We are continuing to monitor the environment to ensure stability and will keep this space updated as needed.

3. resolved Jul 10, 2026, 04:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 09, 2026, 02:36 PM UTC· resolved Aug 06, 2026, 01:07 PM UTC

1. investigating Jul 09, 2026, 02:36 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.

2. identified Jul 13, 2026, 05:51 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.

3. resolved Aug 06, 2026, 01:07 PM UTC

   The security updates have been applied across our fleet.

Read the full incident report →

Started Jun 26, 2026, 05:27 AM UTC· resolved Jul 09, 2026, 02:16 PM UTC

1. investigating Jun 26, 2026, 05:27 AM UTC

   We are advising all customers using WordPress to verify that the following plugins are updated to the latest available versions. Recently disclosed vulnerabilities affect older versions of these plugins: CVE-2026-6279 – Avada Builder (Fusion Builder) – Unauthenticated Remote Code Execution Affected versions: 3.15.2 and earlier CVE-2026-10795 – UpdraftPlus Backup Plugin – Authentication Bypass Affected versions: 1.26.4 and earlier These vulnerabilities may allow unauthenticated attackers to gain control of vulnerable WordPress sites and compromise WordPress user accounts if the plugins have not been updated to the latest available versions. If your website uses either of these plugins, we strongly recommend that you: Update the affected plugin(s) to the latest available version immediately. Review your WordPress installation for any unexpected administrator accounts, plugins, or modified files. Contact our Support team if you believe your website has been affected or if you need assistance reviewing your installation.

2. resolved Jul 09, 2026, 02:16 PM UTC

   This advisory is now being closed. We encourage our customers to ensure that any affected WordPress plugins have been updated to the latest available versions and continue following WordPress security best practices. If you believe your website may have been impacted or require assistance, please contact our Support team.

Read the full incident report →

Started Jun 19, 2026, 12:34 AM UTC· resolved Jun 19, 2026, 01:20 AM UTC

1. investigating Jun 19, 2026, 12:34 AM UTC

   Our team has identified a subset of Cloudhost outages in the US-Midwest region and is actively investigating the issue. We will provide another update as soon as more information becomes available. We appreciate your patience as our team works to resolve this issue. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

2. resolved Jun 19, 2026, 01:20 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 17, 2026, 09:02 PM UTC· resolved Jun 18, 2026, 06:53 AM UTC

1. investigating Jun 17, 2026, 09:02 PM UTC

   Our team has identified a subset of Cloudhost outages in the US-Midwest-1 region and is actively investigating the issue. We will provide another update as soon as more information becomes available. We appreciate your patience as our team works to resolve this issue. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

2. identified Jun 17, 2026, 11:50 PM UTC

   Our team has identified the cause of a subset of Cloudhost outages in the US-Midwest-1 region and is actively working to resolve the issue. Affected services may experience intermittent availability during this time. We will provide another update as soon as more information becomes available. We appreciate your patience as our team works to restore full service. If you have further questions or concerns, please contact us at [email protected] or via Live Chat.

3. resolved Jun 18, 2026, 06:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 15, 2026, 07:24 AM UTC· resolved Jun 15, 2026, 07:16 PM UTC

1. investigating Jun 15, 2026, 07:24 AM UTC

   Our Engineers are investigating an interruption in service affecting the cloudhost: cloudhost-5012850.us-midwest-2.nxcli.net. We understand the inconvenience this may cause and truly appreciate your patience while we resolve the issue. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

2. identified Jun 15, 2026, 09:51 AM UTC

   Our Engineers have made good progress in restoring service to the affected server. At this time, the server is back online and sites should begin coming back online as services continue to recover. Our Engineers are still completing the remaining work required to ensure everything is fully operational and stable. We appreciate your continued patience while we complete these final checks. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

3. identified Jun 15, 2026, 01:57 PM UTC

   Our Engineers have successfully restored service to the affected server, and the server is currently online and operational. We are continuing to monitor the environment to ensure ongoing stability and performance. While services are available, some users may experience intermittent increases in latency as we complete additional monitoring and validation activities. We appreciate your patience and will provide further updates as they become available. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

4. monitoring Jun 15, 2026, 05:18 PM UTC

   Our Engineers have successfully restored service to the affected server, and all services are currently operating normally. The incident is now in a monitoring state. We will continue to watch the environment closely to ensure stability following the restoration of service. We appreciate your patience throughout this incident and will provide additional updates if there are any significant changes. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a Support Case.

5. resolved Jun 15, 2026, 07:16 PM UTC

   Our Engineers have successfully restored service to the affected server, and all services are operating normally. Following a period of monitoring, the environment has remained stable and no further issues have been observed. As a result, this incident has been resolved. We appreciate your patience and understanding throughout this incident. If you experience any issues or have any questions, please feel free to contact our support team via Live Chat or by opening a Support Case.

Read the full incident report →

Started Jun 13, 2026, 05:36 AM UTC· resolved Jun 13, 2026, 06:16 AM UTC

1. investigating Jun 13, 2026, 05:36 AM UTC

   We are currently experiencing an issue affecting a subset of services on a KVM. Our engineers have detected the problem and are actively working to restore full functionality as quickly as possible. We understand the inconvenience this may cause and truly appreciate your patience while we resolve the issue. If you have any questions or concerns, please feel free to reach out to our support team via Live Chat or by opening a support case

2. resolved Jun 13, 2026, 06:16 AM UTC

   The earlier issue affecting a subset of Cloudhosts under the KVM has now been fully resolved. All Cloudhosts on the KVM node are currently online and operating normally. Our engineering team has confirmed that services have been restored and are continuing to monitor the system to ensure stability

Read the full incident report →