Code 42 Outage History

Code 42 is up right now

There were 8 Code 42 outages since February 4, 2026 totaling 127h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.code42.com

Notice April 29, 2026

Delay in processing events

Detected by Pingoru
Apr 29, 2026, 08:42 PM UTC
Resolved
Apr 30, 2026, 12:10 PM UTC
Duration
15h 28m
Affected: Incydr - console.us.code42.com
Timeline · 2 updates
  1. monitoring Apr 29, 2026, 08:42 PM UTC

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

  2. resolved Apr 30, 2026, 12:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 28, 2026

Delay in processing agent settings.

Detected by Pingoru
Apr 28, 2026, 10:24 PM UTC
Resolved
Apr 28, 2026, 11:25 PM UTC
Duration
1h
Affected: Incydr - console.us.code42.com
Timeline · 2 updates
  1. identified Apr 28, 2026, 10:24 PM UTC

    We identified an issue with agents processing settings. The issue has been identified and a fix is being implemented.

  2. resolved Apr 28, 2026, 11:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 23, 2026

Delay in processing Alerts

Detected by Pingoru
Apr 23, 2026, 05:31 PM UTC
Resolved
Apr 23, 2026, 09:27 PM UTC
Duration
3h 55m
Affected: Incydr - console.us.code42.comIncydr - console.us2.code42.comIncydr - console.us7.code42.comIncydr - console.gov.code42.comIncydr - console.au.code42.comIncydr - console.de.code42.comIncydr - console.ie.code42.comIncydr - console.uk.code42.comIncydr - console.za.code42.comIncydr - console.sg.code42.com
Timeline · 3 updates
  1. investigating Apr 23, 2026, 05:31 PM UTC

    We are currently investigating the issue.

  2. monitoring Apr 23, 2026, 05:46 PM UTC

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

  3. resolved Apr 23, 2026, 09:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 30, 2026

Event Processing Delays

Detected by Pingoru
Mar 30, 2026, 01:29 PM UTC
Resolved
Mar 31, 2026, 10:09 AM UTC
Duration
20h 39m
Affected: Incydr - console.de.code42.com
Timeline · 3 updates
  1. investigating Mar 30, 2026, 01:29 PM UTC

    Some events may be delayed before appearing in search and alerts.

  2. monitoring Mar 30, 2026, 03:24 PM UTC

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

  3. resolved Mar 31, 2026, 10:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 23, 2026

Failing Logins for Incydr

Detected by Pingoru
Mar 23, 2026, 09:56 PM UTC
Resolved
Mar 24, 2026, 12:40 PM UTC
Duration
14h 43m
Affected: Incydr - console.us.code42.comIncydr - console.us2.code42.comIncydr - console.us7.code42.comIncydr - console.gov.code42.comIncydr - console.au.code42.comIncydr - console.ca.code42.comIncydr - console.de.code42.comIncydr - console.ie.code42.comIncydr - console.uk.code42.comIncydr - console.za.code42.com
Timeline · 10 updates
  1. investigating Mar 23, 2026, 09:56 PM UTC

    We are currently investigating an issue that is causing login to fail in the production environment

  2. identified Mar 23, 2026, 09:57 PM UTC

    The issue with logins has been and identified and a fix is being worked on.

  3. identified Mar 23, 2026, 10:36 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Mar 23, 2026, 10:40 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Mar 23, 2026, 11:24 PM UTC

    We are continuing to work on a fix for this issue.

  6. identified Mar 23, 2026, 11:33 PM UTC

    We are continuing to work on a fix for this issue.

  7. identified Mar 23, 2026, 11:53 PM UTC

    We are continuing to work on a fix for this issue.

  8. monitoring Mar 24, 2026, 12:28 AM UTC

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

  9. resolved Mar 24, 2026, 12:40 PM UTC

    This incident has been resolved.

  10. 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.

Read the full incident report →

Critical March 20, 2026

Authentication Failures in Prod Gov

Detected by Pingoru
Mar 20, 2026, 02:50 AM UTC
Resolved
Mar 20, 2026, 03:10 AM UTC
Duration
19m
Affected: Incydr - console.gov.code42.com
Timeline · 2 updates
  1. investigating Mar 20, 2026, 02:50 AM UTC

    We are currently investigating an issue with authentications. Users are currently not be able to login.

  2. resolved Mar 20, 2026, 03:10 AM UTC

    This incident has been resolved all services are back and running.

Read the full incident report →

Notice March 10, 2026

Delay in Processing Cloud Detector Security Events

Detected by Pingoru
Mar 10, 2026, 11:27 PM UTC
Resolved
Mar 11, 2026, 10:26 AM UTC
Duration
10h 58m
Affected: Incydr - console.us.code42.comIncydr - console.us2.code42.comIncydr - console.us7.code42.comIncydr - console.gov.code42.comIncydr - console.au.code42.comIncydr - console.ca.code42.comIncydr - console.de.code42.comIncydr - console.ie.code42.comIncydr - console.uk.code42.comIncydr - console.za.code42.com
Timeline · 2 updates
  1. investigating Mar 10, 2026, 11:27 PM UTC

    We are currently investigating the issue.

  2. resolved Mar 11, 2026, 10:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Code 42 downtime and outages?

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

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

5 free monitors · No credit card required