Nexcess incident
Subset of Elasticsearch containers down in us-midwest-2
Nexcess experienced a notice incident on March 3, 2026 affecting us-midwest-2, lasting 5h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- 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.
- 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.