Code 42 experienced a critical incident on March 23, 2026 affecting Incydr - console.us.code42.com and Incydr - console.us2.code42.com and 1 more component, lasting 14h 43m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 23, 2026, 09:56 PM UTC
We are currently investigating an issue that is causing login to fail in the production environment
- identified Mar 23, 2026, 09:57 PM UTC
The issue with logins has been and identified and a fix is being worked on.
- identified Mar 23, 2026, 10:36 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 23, 2026, 10:40 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 23, 2026, 11:24 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 23, 2026, 11:33 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 23, 2026, 11:53 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 24, 2026, 12:28 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 24, 2026, 12:40 PM UTC
This incident has been resolved.
- postmortem Mar 26, 2026, 10:21 PM UTC
At 21:35 UTC on March 23, 2026, an engineering change was released to all Incydr production environments. This change caused a temporary outage of Incydr services. During the service outage, users were able to authenticate to the Incydr console, but all features and functionality were unavailable. Incydr agents that had already established communication with the Incydr cloud prior to the outage were not affected. A subset of agents that established a connection during the outage may have experienced a monitoring gap of up to six hours. Mimecast Engineering teams identified the issue and worked to restore services. All Incydr services were verified to be functioning normally as of 01:30 UTC on March 24, 2026. Please reach out to your Mimecast representative with any questions.