Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Nexcess Outage History

Every past Nexcess outage tracked by IsDown, with detection times, duration, and resolution details.

There were 343 Nexcess outages since December 2020. The 63 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major March 21, 2026

March 2026: Multiple cloud hosts in the US-Midwest-1 region are currently experiencing an outage.

Detected Mar 21, 2026 12:45 AM EDT · Resolved Mar 22, 2026 12:10 AM EDT · Duration about 23 hours

Multiple cloud hosts in Nexcess's US-Midwest-1 region experienced a major outage caused by a DDoS attack, lasting approximately 23.4 hours. The incident affected all servers in the region, causing service disruptions for customers hosted in that location. Network engineers successfully mitigated the DDoS attack and applied fixes to restore normal operations across all affected servers.

Minor March 18, 2026

March 2026: Magento “PolyShell” File Upload Vulnerability

Detected Mar 18, 2026 12:17 PM EDT · Resolved Mar 18, 2026 6:30 PM EDT · Duration about 6 hours

Nexcess identified a potential "PolyShell" unrestricted file upload vulnerability affecting Magento and Adobe Commerce platforms in their managed environment. The security issue impacted their platform updates and other components for 6.2 hours while teams assessed potential exposure across customer sites. The incident was resolved by implementing measures to prohibit execution of files that could exploit this vulnerability across their entire managed fleet.

Major March 16, 2026

March 2026: ClamAV Service Disruption

Detected Mar 16, 2026 1:26 PM EDT · Resolved Mar 18, 2026 8:43 AM EDT · Duration 2 days

The ClamAV service experienced disruption due to a problematic signature update that caused clamd restart failures. This affected Maldet scans and potentially caused mail delivery failures when the ClamAV service was not running. The issue was resolved by the System Engineering team within 12 minutes.

Minor March 15, 2026

March 2026: Service Interruption on US-Midwest 2 region

Detected Mar 15, 2026 5:41 AM EDT · Resolved Mar 15, 2026 11:15 AM EDT · Duration about 6 hours

Nexcess experienced a service interruption affecting four specific cloud host servers in their US-Midwest-2 data center for 5.6 hours. The engineering team identified the root cause and implemented a resolution to restore normal service operations. All affected servers are now operating normally.

Minor March 12, 2026

March 2026: Outgoing Connectivity Issues Affecting Servers in UK South 2 Region

Detected Mar 12, 2026 8:40 AM EDT · Resolved Mar 16, 2026 10:06 AM EDT · Duration 4 days

Nexcess experienced a connectivity issue affecting servers in the UK South 2 region and internal DNS resolvers, causing DNS resolution failures, slow site responses, and connectivity problems with containers and APIs on customer sites. The incident lasted 97.4 hours with intermittent connectivity latency throughout the outage period. Engineering and networking teams implemented fixes and mitigation measures to address elevated traffic levels, successfully stabilizing the environment with all systems returning to normal operation.

Minor March 10, 2026

March 2026: Service Disruption

Detected Mar 10, 2026 4:57 AM EDT · Resolved Mar 10, 2026 5:08 AM EDT · Duration 11 minutes

Nexcess experienced a service disruption affecting a subset of Cloudhosts on a KVM node across multiple regions including us-midwest-1, us-west-1, uk-south-2, nl-west-1, and au-south-1. The issue impacted the availability and functionality of affected cloud hosting services for customers in these regions. The problem was resolved within 11 minutes, with all Cloudhosts restored to normal operation.

Minor March 6, 2026

March 2026: WordPress: W3 Total Cache Vulnerability CVE-2026-27384

Detected Mar 6, 2026 1:23 PM EST · Resolved Mar 10, 2026 2:31 AM EDT · Duration 4 days

Nexcess identified a critical vulnerability (CVE-2026-27384) in the WordPress W3 Total Cache plugin affecting versions 2.9.1 and older, which required immediate patching to version 2.9.2. The Nexcess team applied patches across all managed systems where possible, but some sites couldn't be updated due to WordPress or PHP version compatibility constraints. The incident was resolved after 84 hours once all viable patches were deployed and affected clients with compatibility issues were contacted directly with upgrade recommendations.

Minor March 3, 2026

March 2026: Subset of Elasticsearch containers down in us-midwest-2

Detected Mar 3, 2026 2:44 AM EST · Resolved Mar 3, 2026 7:55 AM EST · Duration about 5 hours

A network error caused degraded performance for a subset of Elasticsearch containers in Nexcess's us-midwest-2 region. The issue affected Elasticsearch container operations and lasted 5.2 hours. The team identified the root cause, implemented a fix, and confirmed sustained stability before marking the incident resolved.

Major February 25, 2026

February 2026: Network/Server Issues - US-Midwest-2 Region

Detected Feb 25, 2026 5:47 PM EST · Resolved Feb 25, 2026 7:51 PM EST · Duration about 2 hours

Nexcess experienced a major network/server issue affecting multiple cloud hosts in their US-Midwest-2 region for 2.1 hours. The incident impacted cloud hosting services and required active investigation by the engineering team to identify the root cause. All affected services were restored to normal operation, with continued monitoring to ensure stability.

Minor February 23, 2026

February 2026: Acronis Portal Degraded Performance.

Detected Feb 23, 2026 5:23 PM EST · Resolved Feb 24, 2026 8:50 PM EST · Duration 1 day

The Acronis Cyber Protect Cloud service in the USA (US5) data center experienced degraded performance for 27.5 hours, preventing some customers from accessing Acronis Web Restore, Cyber Protection Console, and Management Console. The issue recurred after an initial fix was implemented, requiring additional corrective measures from the Acronis Cloud team. The incident was ultimately resolved with sustained monitoring to ensure platform stability.