Nexcess Outage History

Nexcess is up right now

There were 19 Nexcess outages since February 9, 2026 totaling 690h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nexcess.net

Major April 15, 2026

Minor Outage on Subset of Cloudhosts on UK-South-2 Data Center

Detected by Pingoru
Apr 15, 2026, 10:58 PM UTC
Resolved
Apr 15, 2026, 11:51 PM UTC
Duration
52m
Affected: uk-south-2
Timeline · 2 updates
  1. identified Apr 15, 2026, 10:58 PM UTC

    Following a scheduled maintenance on our UK-South infrastructure a hardware issue was identified and is impacting a subset of the maintained hosts. We have engaged with engineers onsite and are working to correct the issue. If you have any questions please reach out to our support team. Live Chat via the Customer Portal: https://sites-portal.nexcess.com Email: [email protected] We appreciate your understanding and patience as we work to enhance our service. System Maintenance Reference: [CC-13363]

  2. resolved Apr 15, 2026, 11:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 11, 2026

Service Disruption Due to Network Switch Failure

Detected by Pingoru
Apr 11, 2026, 08:29 PM UTC
Resolved
Apr 11, 2026, 09:44 PM UTC
Duration
1h 15m
Affected: Lansing, MI (DC3)
Timeline · 3 updates
  1. identified Apr 11, 2026, 08:29 PM UTC

    We are currently experiencing a service disruption affecting some servers due to a failed network switch. Our engineering team is actively working to resolve the issue as quickly as possible. We appreciate your patience as our engineers work to restore full service. If you have any further questions or concerns, please contact us at [email protected] or via Live Chat.

  2. monitoring Apr 11, 2026, 08:49 PM UTC

    The issue was caused by a failed network switch, which has now been replaced. 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.

  3. resolved Apr 11, 2026, 09:44 PM UTC

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

Read the full incident report →

Minor April 10, 2026

Internal Network Outage Impacting Support Services.

Detected by Pingoru
Apr 10, 2026, 03:16 PM UTC
Resolved
Apr 10, 2026, 06:15 PM UTC
Duration
2h 58m
Affected: TicketsPhonesChats
Timeline · 3 updates
  1. 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.

  2. monitoring Apr 10, 2026, 05:37 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.

  3. resolved Apr 10, 2026, 06:15 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 →

Minor April 10, 2026

DDOS attack on cloudhost-1743976.uk-south-2.nxcli.net

Detected by Pingoru
Apr 10, 2026, 08:23 AM UTC
Resolved
Apr 10, 2026, 08:08 PM UTC
Duration
11h 45m
Affected: uk-south-2
Timeline · 3 updates
  1. investigating Apr 10, 2026, 08:23 AM UTC

    We have been alerted to a DDoS attack targeting cloudhost-1743976.uk-south-2.nxcli.net. Our network engineers are currently engaged and actively working on mitigation measures to minimize impact and restore normal service stability. We will provide further updates as more information becomes available and mitigation progresses. If you have any questions or concerns, please feel free to reach out to us at [email protected] or via Live Chat.

  2. monitoring Apr 10, 2026, 11:55 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 10, 2026, 08:08 PM UTC

    The issue has been resolved following the implementation of a fix. We have closely monitored the environment and have not observed any further issues. The server is stable and operating normally. 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 →

Minor April 10, 2026

US-Midwest Cloud Host Server Outage (2 Servers Down)

Detected by Pingoru
Apr 10, 2026, 06:08 AM UTC
Resolved
Apr 10, 2026, 08:25 AM UTC
Duration
2h 16m
Affected: us-midwest-1
Timeline · 4 updates
  1. investigating Apr 10, 2026, 06:08 AM UTC

    We are currently experiencing an issue affecting two cloud host servers in the US-Midwest region. Our internal teams are actively investigating and working to restore services. We will continue to provide updates here as more information becomes available. We appreciate your patience. If you have any questions or concerns, please contact us at [email protected] or via Live Chat.

  2. monitoring Apr 10, 2026, 06:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Apr 10, 2026, 06:53 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Apr 10, 2026, 08:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Issues Creating Tickets from Email

Detected by Pingoru
Apr 08, 2026, 04:40 PM UTC
Resolved
Apr 09, 2026, 12:33 AM UTC
Duration
7h 52m
Affected: Tickets
Timeline · 4 updates
  1. investigating Apr 08, 2026, 04:40 PM UTC

    We are currently experiencing intermittent issues with ticket creation for requests submitted via email. Ticket creation through the portal is functioning as expected. Our team is actively investigating the issue. We will share additional updates as they become available. If you need immediate assistance, please submit your request through the portal or contact us via chat. We appreciate your patience and understanding as we work to restore normal service. Thank you.

  2. monitoring Apr 08, 2026, 06:12 PM UTC

    The issue affecting ticket creation for requests submitted via email has been resolved. Ticket creation through both email and the portal is now functioning as expected. Our team will continue to closely monitor the system and will share any further updates if needed. If you experience any issues or need immediate assistance, please contact us via chat or case. We appreciate your patience and understanding. Thank you.

  3. investigating Apr 08, 2026, 06:49 PM UTC

    We are currently experiencing intermittent issues with ticket creation for requests submitted via email. Ticket creation through the portal continues to function as expected. After initial signs of recovery, we have observed that the issue persists. This has been confirmed as related to an ongoing disruption with Salesforce’s Email-to-Case functionality, which may prevent some cases from being created successfully. Our team is actively monitoring the situation and working with Salesforce for further updates. If you experience any issues or need immediate assistance, please contact us via chat or submit a case through the portal. We appreciate your patience and understanding. Thank you.

  4. resolved Apr 09, 2026, 12:33 AM UTC

    The issue affecting ticket creation from email has been resolved. Email submissions are now being received and processed successfully, and ticket creation is functioning as expected. If you experience any further issues or need assistance, please submit your request through the portal or contact us via chat. We appreciate your patience and understanding. Thank you.

Read the full incident report →

Minor April 1, 2026

Security Hardening - Magento “PolyShell” File Upload Vulnerability Enhancements

Detected by Pingoru
Apr 01, 2026, 06:37 PM UTC
Resolved
Apr 15, 2026, 12:13 PM UTC
Duration
13d 17h
Affected: Platform Updates / Other
Timeline · 4 updates
  1. investigating Apr 01, 2026, 06:37 PM UTC

    Following the actions taken to prohibit execution of files exploiting the Magento “PolyShell” unrestricted file upload vulnerability, our engineering teams are continuing to implement additional security enhancements across our managed environment. These efforts include strengthening file upload validation and execution restrictions, enhancing monitoring and detection mechanisms, and implementing additional hardening measures across Magento platforms. We are also conducting internal reviews to reduce potential attack surfaces and reinforce overall platform security. These proactive improvements reflect our ongoing commitment to maintaining a secure and resilient hosting environment. While the initial issue has been addressed, we are taking additional steps to further strengthen our systems and help prevent future risks. While the additional measures that we have deployed should reduce the risk for potential compromise, we strongly urge that our customers take proactive measures to review and secure their sites If you have any questions or concerns, please reach out to us through the following channels: Live Chat: https://my.nexcess.net/ Email: [email protected] We will continue to share updates as these enhancements are completed.

  2. investigating Apr 09, 2026, 01:29 PM UTC

    Our engineering teams have made significant progress in implementing additional security enhancements related to the Magento "PolyShell" unrestricted file upload vulnerability. At this stage, we are nearing completion of all planned mitigation efforts across our managed environment. The measures deployed, including strengthened file upload validation, enhanced malware scanning to detect files, stricter execution controls, and broader platform hardening, have significantly reduced the risk of exploitation. While these mitigations provide strong protection, security is a shared responsibility. We strongly encourage customers to review their Magento installations, ensure all updates and patches are applied, and follow general security best practices to help keep their sites secure. If you have any questions or need assistance, please reach out to us through chat or via case. We will provide further updates if any additional actions are required.

  3. investigating Apr 15, 2026, 12:13 PM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 15, 2026, 12:13 PM UTC

    Our engineering teams have completed the planned security enhancements and hardening efforts related to the Magento "PolyShell" unrestricted file upload vulnerability across our managed environment. With these measures now fully implemented, we consider this incident resolved. As security is a shared responsibility, we recommend that customers review their Magento installations, ensure all updates and patches are applied, and take additional steps to further secure their applications. If you have any questions or require assistance, please reach out via chat or support case.

Read the full incident report →

Notice April 1, 2026

Nexcess Portal Access Issues

Detected by Pingoru
Apr 01, 2026, 10:17 AM UTC
Resolved
Apr 02, 2026, 02:02 AM UTC
Duration
15h 45m
Affected: Customer Portal
Timeline · 4 updates
  1. investigating Apr 01, 2026, 10:17 AM UTC

    Our team has identified a performance delay that is causing portal access issues, primarily manifesting as timeouts when attempting to access via a browser. We are actively working on this and will keep this space updated as we make progress.

  2. identified Apr 01, 2026, 10:24 AM UTC

    Our team has identified the problem and are working on getting things back online. We are actively working on this and will keep this space updated as we make progress.

  3. monitoring Apr 01, 2026, 10:43 AM UTC

    Our team has implemented the necessary steps to ensure seamless accessibility, and everything is working as expected at this time. We will continue to monitor for stability.

  4. resolved Apr 02, 2026, 02:02 AM UTC

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

Read the full incident report →

Major March 21, 2026

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

Detected by Pingoru
Mar 21, 2026, 04:45 AM UTC
Resolved
Mar 22, 2026, 04:06 AM UTC
Duration
23h 20m
Affected: us-midwest-1
Timeline · 4 updates
  1. investigating Mar 21, 2026, 04:45 AM UTC

    Our teams have identified multiple Cloudhost outages in the Midwest-1 region. Our network engineers are working on mitigation at this time. We will provide another update as soon as more information becomes available. We appreciate your patience as our networking teams work to mitigate the DDoS. If you have further questions or concerns, please contact us at [email protected] or via Live chat.

  2. monitoring Mar 21, 2026, 05:49 AM UTC

    We have mitigated the impact of the issue. Our network engineers have applied a fix, and all servers are now operating normally. We will continue to monitor the situation to ensure ongoing stability. We understand the disruption this may have caused and appreciate your patience as our teams worked to resolve the issue. For any additional questions or concerns, please contact us at [email protected] or via Live Chat.

  3. monitoring Mar 21, 2026, 05:50 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 22, 2026, 04:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Magento “PolyShell” File Upload Vulnerability

Detected by Pingoru
Mar 18, 2026, 04:17 PM UTC
Resolved
Mar 18, 2026, 10:23 PM UTC
Duration
6h 5m
Affected: Platform Updates / Other
Timeline · 2 updates
  1. investigating Mar 18, 2026, 04:17 PM UTC

    We are aware of recent reports regarding a potential unrestricted file upload vulnerability, commonly referred to as “PolyShell”, affecting Magento and Adobe Commerce. At this time, our teams are actively reviewing our environment to assess any potential impact and determine whether any systems/customer sites may be affected. We will provide further updates as more information becomes available. If you have any questions or concerns. You can reach us through the following channels: Live Chat: https://my.nexcess.net/ Email: Nexcess Support

  2. resolved Mar 18, 2026, 10:23 PM UTC

    We have taken steps to prohibit execution of files exploiting the "PolyShell" unrestricted file upload vulnerability across our managed fleet. If you have any questions or concerns. You can reach us through the following channels: Live Chat: https://my.nexcess.net/ Email: [email protected]

Read the full incident report →

Major March 16, 2026

ClamAV Service Disruption

Detected by Pingoru
Mar 16, 2026, 05:26 PM UTC
Resolved
Mar 18, 2026, 12:41 PM UTC
Duration
1d 19h
Affected: Email
Timeline · 5 updates
  1. investigating Mar 16, 2026, 05:26 PM UTC

    We are currently investigating an issue affecting the ClamAV service, where clamd restarts may fail due to a problematic signature update. Our System Engineering team is actively working to identify the root cause and implement a fix. This issue may affect Maldet scans and cause mail delivery failures if the ClamAV service is not running.

  2. identified Mar 16, 2026, 06:05 PM UTC

    We have identified the cause of the issue affecting the ClamAV service. A recent malware signature update introduced an invalid entry in the ClamAV signature database, which can prevent the clamd service from restarting successfully. Our team is currently applying a signature database refresh on affected servers to remove the invalid entry and restore normal operation of the ClamAV service. We are currently applying this fix across all affected servers and will provide another update once the process is completed.

  3. identified Mar 16, 2026, 08:18 PM UTC

    Our engineering team has implemented a fix to address the issue affecting the ClamAV service. The invalid signature entry has been removed and services have been restored. We are continuing to monitor the environment to ensure stability and will provide further updates if needed.

  4. monitoring Mar 16, 2026, 08:18 PM UTC

    Our engineering team has implemented a fix to address the issue affecting the ClamAV service. The invalid signature entry has been removed and services have been restored. We are continuing to monitor the environment to ensure stability and will provide further updates if needed.

  5. resolved Mar 18, 2026, 12:41 PM UTC

    We have not observed any further issues since implementing the fix. The environment remains stable. If you have any questions or concerns. You can reach us through the following channels: Live Chat: https://my.nexcess.net/ Email: [email protected]

Read the full incident report →

Minor March 15, 2026

Service Interruption on US-Midwest 2 region

Detected by Pingoru
Mar 15, 2026, 09:41 AM UTC
Resolved
Mar 15, 2026, 03:13 PM UTC
Duration
5h 31m
Affected: us-midwest-2
Timeline · 3 updates
  1. investigating Mar 15, 2026, 09:41 AM UTC

    We are currently investigating a service interruption affecting servers in our US-Midwest-2 Data Center. Our dedicated Engineering teams are engaged and are working to restore service as quickly as possible. We will provide further updates as they become available. Affected services : cloudhost-4428571.us-midwest-2.nxcli.net cloudhost-4486445.us-midwest-2.nxcli.net cloudhost-4428478.us-midwest-2.nxcli.net cloudhost-4486490.us-midwest-2.nxcli.net If you have any further questions or concerns, please feel free to reach out to us at [email protected] or via chat.

  2. investigating Mar 15, 2026, 01:31 PM UTC

    Our Engineering team has identified the cause of the service interruption affecting a subset of servers in our US-Midwest-2 Data Center. The team is actively working to implement a resolution and restore full service as quickly as possible. We will continue to provide updates as more information becomes available. If you have any further questions or concerns, please feel free to reach out to us at [email protected] or via chat.

  3. resolved Mar 15, 2026, 03:13 PM UTC

    The issue affecting a subset of servers in our US-Midwest-2 Data Center has been resolved. Our Engineering team has confirmed that services are operating normally. If you have any further questions or concerns, please feel free to reach out to us at [email protected] or via chat.

Read the full incident report →

Minor March 12, 2026

Outgoing Connectivity Issues Affecting Servers in UK South 2 Region

Detected by Pingoru
Mar 12, 2026, 12:40 PM UTC
Resolved
Mar 16, 2026, 02:03 PM UTC
Duration
4d 1h
Affected: DNSuk-south-2
Timeline · 6 updates
  1. investigating Mar 12, 2026, 12:40 PM UTC

    We are currently investigating a connectivity issue affecting servers in the UK South 2 region and internal DNS resolvers. This may result in DNS resolution failures and impact connectivity to containers and APIs configured on customer sites. Our engineering team is actively working to identify the root cause and restore normal service as quickly as possible. Need help? You can chat with us or create a ticket through my.nexcess.net. We appreciate your patience and understanding while we work to stabilize connectivity. Thank you.

  2. investigating Mar 12, 2026, 02:23 PM UTC

    Our engineering and Networking teams are continuing to investigate the issue affecting servers in the UK South 2 region. We are currently observing intermittent connectivity latency, which may cause sites and servers to respond slowly and impact connectivity. The containers and APIs configured on customer sites might fail to connect. The team is actively working to identify the root cause and restore normal service as quickly as possible. We appreciate your patience and understanding while we work to stabilize connectivity. Thank you.

  3. monitoring Mar 12, 2026, 03:15 PM UTC

    Our Engineering and Networking teams have implemented a fix for the issue affecting servers in the UK South 2 region. Services are currently stable, though there may be slight latency while the systems continue to stabilize. We will continue to monitor the systems to ensure stability and confirm that services remain operating normally.

  4. monitoring Mar 13, 2026, 12:01 AM UTC

    Our Engineering and Networking teams have implemented a fix for the issue affecting servers in the UK South 2 region. Services are currently stable, though there may be slight latency while the systems continue to stabilize. We will continue to monitor the systems to ensure stability and confirm that services remain operating normally.

  5. monitoring Mar 13, 2026, 03:09 AM UTC

    Our Engineering and Networking teams are continuing to implement mitigation measures and are actively working to mitigate elevated traffic levels impacting the environment. Systems are currently stable, though slight latency may still be experienced while conditions continue to normalize. We will continue to closely monitor the environment to ensure stability and confirm that services remain operating normally.

  6. resolved Mar 16, 2026, 02:03 PM UTC

    The mitigation measures implemented by our Engineering and Networking teams have successfully stabilized the environment. We have not observed any further issues following the fix, and all systems and services are currently operating normally. If you have any further questions or concerns, please feel free to reach out to us at [email protected] or via chat.

Read the full incident report →

Minor March 10, 2026

Service Disruption

Detected by Pingoru
Mar 10, 2026, 08:57 AM UTC
Resolved
Mar 10, 2026, 09:05 AM UTC
Duration
7m
Affected: us-midwest-1us-west-1uk-south-2nl-west-1au-south-1us-midwest-2
Timeline · 2 updates
  1. investigating Mar 10, 2026, 08:57 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 Mar 10, 2026, 09:05 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. We sincerely apologize for any inconvenience this disruption may have caused and appreciate your patience while our team worked to resolve the issue. If you continue to experience any problems or have questions, please reach out to our support team via Live Chat or by opening a support case.

Read the full incident report →

Notice March 6, 2026

WordPress: W3 Total Cache Vulnerability CVE-2026-27384

Detected by Pingoru
Mar 06, 2026, 06:23 PM UTC
Resolved
Mar 10, 2026, 06:29 AM UTC
Duration
3d 12h
Affected: Platform Updates / Other
Timeline · 4 updates
  1. investigating Mar 06, 2026, 06:23 PM UTC

    We have been made aware of a critical vulnerability, CVE-2026-27384, affecting versions equal to or less than 2.9.1, of the WordPress W3 Total Cache plugin. Recommended Action We strongly encourage all clients to update any sites running versions 2.9.1 or older to the patched version 2.9.2 immediately. Current Status Exploit Availability: There are currently no known public Proof of Concept (PoC) exploits for this vulnerability. Our team is assessing the impact on our managed sites and evaluating the deployment of necessary patches across our managed systems. We will provide further updates as they become available. If you have any questions or require assistance with the update, please reach out to our support team.

  2. identified Mar 09, 2026, 05:37 AM UTC

    Our team is currently applying patches to instances of outdated W3 Total Cache plugins identified across our managed systems where the update is viable based on the WordPress and PHP version requirements. Recommended Action We strongly encourage all clients to update any sites running W3 Total Cache version 2.9.1 or earlier to the patched version 2.9.2 immediately. For environments where the current WordPress or PHP version does not meet the plugin's update requirements, we strongly recommend upgrading WordPress and/or PHP first from your end, and then updating the W3 Total Cache plugin to version 2.9.2 or later at the earliest opportunity. We will continue to update this space as we make further progress. If you have any questions or require assistance with the update, please do not hesitate to contact our Support Team.

  3. monitoring Mar 09, 2026, 09:17 AM UTC

    Update Our team has now applied patches to all instances of the W3 Total Cache plugin across our managed systems where the update was possible based on the current WordPress and PHP version requirements. In some environments, the patch could not be applied as the underlying WordPress or PHP versions do not meet the minimum compatibility requirements for the updated plugin, or due to other configuration limitations. These instances will require updates at the application or environment level before the plugin can be upgraded. For cases where the patch could not be applied for the reasons mentioned above, we will be reaching out to the affected clients directly with additional details and recommended next steps. Recommended Action Clients with sites running W3 Total Cache version 2.9.1 or earlier are strongly advised to update to the patched version 2.9.2 as soon as possible. Where the plugin update is not currently possible due to WordPress or PHP version constraints, we recommend upgrading WordPress and/or PHP first, and then completing the update to W3 Total Cache version 2.9.2 or later at the earliest opportunity. If you require assistance with upgrading your environment or applying the update, please contact our support team, who will be happy to assist. We will continue to monitor this matter and will provide further updates here should any additional actions be required.

  4. resolved Mar 10, 2026, 06:29 AM UTC

    Update Our team has completed patching the W3 Total Cache plugin across all managed systems where the update was possible based on the current WordPress and PHP version requirements. In cases where the patch could not be applied due to compatibility constraints or other configuration limitations, the affected clients have been contacted directly with the relevant details and recommended next steps. In most instances, this involves upgrading the underlying WordPress and/or PHP versions before updating the plugin. At this time, the planned remediation work has been completed and this matter is considered resolved. Recommended Action Clients with sites running W3 Total Cache version 2.9.1 or earlier are encouraged to update to the patched version 2.9.2 as soon as possible. Where the update is not currently possible due to WordPress or PHP version constraints, please upgrade those components first and then proceed with the plugin update. If you require assistance with completing the update, please contact our support team. Thank you for your patience and understanding while we worked to address this matter.

Read the full incident report →

Notice March 3, 2026

Subset of Elasticsearch containers down in us-midwest-2

Detected by Pingoru
Mar 03, 2026, 07:44 AM UTC
Resolved
Mar 03, 2026, 12:50 PM UTC
Duration
5h 6m
Affected: us-midwest-2
Timeline · 4 updates
  1. investigating Mar 03, 2026, 07:44 AM UTC

    We are currently observing degraded performance, primarily due to a network error affecting a subset of Elasticsearch containers within the us-midwest-2 region. Our team is actively investigating and working to resolve the issue as swiftly as possible. We will provide further updates here as progress is made. In the meantime, if you have any questions or believe your Elasticsearch containers may not be operating as expected, please do not hesitate to contact Support.

  2. identified Mar 03, 2026, 07:59 AM UTC

    We have identified the root cause of the issue and are currently implementing a fix. We will provide further updates here as progress is made. In the meantime, if you have any questions or believe your Elasticsearch containers may not be operating as expected, please do not hesitate to contact Support.

  3. monitoring Mar 03, 2026, 08:40 AM UTC

    Our team has now implemented a fix, and services should be operating as expected at this time. We will continue to monitor the situation closely to ensure ongoing stability.

  4. resolved Mar 03, 2026, 12:50 PM UTC

    We've now observed sustained stability, and the issue is considered resolved. Thank you very much for your patience while we worked through this. If you have any further questions or concerns, please don’t hesitate to get in touch with support.

Read the full incident report →

Critical February 25, 2026

Network/Server Issues - US-Midwest-2 Region

Detected by Pingoru
Feb 25, 2026, 10:47 PM UTC
Resolved
Feb 26, 2026, 12:51 AM UTC
Duration
2h 4m
Affected: us-midwest-2
Timeline · 4 updates
  1. investigating Feb 25, 2026, 10:47 PM UTC

    We are currently investigating an issue affecting multiple cloud hosts in our US-Midwest-2 region. Our engineering team is actively working to identify the root cause and restore full functionality. We will provide 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 case.

  2. investigating Feb 25, 2026, 10:52 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 25, 2026, 11:07 PM UTC

    The issue affecting multiple cloud hosts in the US-Midwest-2 region has been resolved. All affected services have been restored to normal operation. Our engineering team will continue to monitor the environment to ensure stability. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  4. resolved Feb 26, 2026, 12:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2026

Acronis Portal Degraded Performance.

Detected by Pingoru
Feb 23, 2026, 10:23 PM UTC
Resolved
Feb 25, 2026, 01:46 AM UTC
Duration
1d 3h
Affected: Customer Portal
Timeline · 8 updates
  1. investigating Feb 23, 2026, 10:23 PM UTC

    We would like to notify you that Acronis Cyber Protect Cloud in the USA (US5) data center is degraded. Acronis Cloud team is working on the issue resolution and will keep notifying you on the service status. Service impact: Some customers might be unable to reach Acronis Web Restore, Acronis Cyber Protection Console and Management Console.

  2. identified Feb 23, 2026, 11:26 PM UTC

    Acronis Cloud team is actively working on the issue resolution and we will keep notifying you on the service status.

  3. identified Feb 24, 2026, 03:45 AM UTC

    Acronis Cloud team is actively working on the issue resolution and we will keep notifying you on the service status.

  4. identified Feb 24, 2026, 07:09 AM UTC

    Acronis Cloud team has implemented a fix and resolved the issue. We are currently monitoring the results to ensure stability. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  5. monitoring Feb 24, 2026, 07:13 AM UTC

    Acronis Cloud team has implemented a fix and resolved the issue. We are currently monitoring the results to ensure stability. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  6. identified Feb 24, 2026, 02:40 PM UTC

    We are observing a recurrence of the issue affecting Acronis Cyber Protect Cloud in the USA (US5) data center; the Acronis Cloud team is actively investigating, and some customers may continue to experience intermittent access issues to Web Restore, Cyber Protection Console, and Management Console. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  7. monitoring Feb 24, 2026, 04:03 PM UTC

    The Acronis Cloud team has applied corrective measures, and services have been restored. We are actively monitoring the platform to confirm sustained stability and performance. If you have any questions or concerns, please don't hesitate to contact us via Live Chat or by opening a case.

  8. resolved Feb 25, 2026, 01:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026

DDoS Attack on cloudhost-144200.us-midwest-1.nxcli.net

Detected by Pingoru
Feb 09, 2026, 02:40 AM UTC
Resolved
Feb 10, 2026, 02:43 AM UTC
Duration
1d
Affected: us-midwest-1
Timeline · 3 updates
  1. identified Feb 09, 2026, 02:40 AM UTC

    Our teams have identified a distributed denial of service attack (DDoS) on cloudhost-144200.us-midwest-1.nxcli.net. Our network engineers are working on mitigation at this time. We will provide another update as soon as more information becomes available. Need help? Chat with us or create a ticket via my.liquidweb.com. We appreciate your patience and understanding as we work to stabilize connectivity. Thank you.

  2. monitoring Feb 09, 2026, 08:08 AM UTC

    The servers are back online and fully operational. Our Network and Support teams are continuing to monitor them to ensure stable performance. We’ll keep you updated with any new information. If you have further questions or concerns, please contact us via ticket or via Live chat.

  3. resolved Feb 10, 2026, 02:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Nexcess downtime and outages?

Pingoru polls Nexcess's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Nexcess reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Nexcess alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Nexcess for free

5 free monitors · No credit card required