Delay in processing events
- identified
The issue has been identified and a fix is being implemented.
- resolved
This incident has been resolved.
61 recorded Code 42 incidents since May 2025, with official updates, affected components, duration and resolution information.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Some events may be delayed before appearing in search and alerts.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between July 8, 2026 and July 13, 2026, Incydr Gov experienced a disruption to the service responsible for collecting copies of exfiltrated files. During this period, customers may have encountered errors when attempting to view or download exfiltrated files, and alert rules dependent on content inspection risk indicators may not have generated alerts.
## Incydr Gov Only On July 8 2026 21:00UTC, the service cluster responsible for managing exfiltrated files in our Incydr Gov environment experienced an outage. During the outage, users were unable to download previously captured exfiltrated files from the Incydr console, and the Incydr agent was unable to upload newly captured files to the service. Alerts that rely on file content based risk indicators for exfiltrated file activity would not have been generated during this period. Mimecast Engineering identified and resolved the underlying issue on July 13, 2026, and confirmed the service was fully restored as of 15:00UTC We are reviewing Incydr agent behavior during extended service interruptions to ensure captured files are reliably retained and delivered once service is restored, and we are adding additional monitoring to detect this class of issue more quickly going forward. Please reach out to your Mimecast representative with any questions.
Some events may be delayed before appearing in search and alerts.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There was a delay in processing of events for the IE, ZA, and DE regions. This was resolved on 6/20/2026.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We identified an issue with agents processing settings. The issue has been identified and a fix is being implemented.
This incident has been resolved.