Code 42 Outage History
Code 42 is up right nowPingoru has recorded 52 incidents for Code 42: 40 in the last 12 months and 10 in the last 90 days.
52incidents recorded
40last 12 months
10last 90 days
32 hourstypical duration
Pingoru began tracking Code 42 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 4 | 0 of 720 (0%) |
| May 2026 | 4 | 0 of 744 (0%) |
| June 2026 | 5 | 0 of 720 (0%) |
| July 2026 | 5 | 16 of 744 (2%) |
| August 2026 | 2 | 0 of 744 (0%) |
| September 2026 | 2 | 10 of 720 (1%) |
| October 2026 | 6 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 22 (0%) |
Incidents, newest first
Minor September 19, 2025 Event Processing Delays 1h 57m Incydr - console.us2.code42.com
Started Sep 19, 2025, 04:11 PM UTC· resolved Sep 19, 2025, 06:08 PM UTC
- investigating Sep 19, 2025, 04:11 PM UTC
Some events may be delayed before appearing in search and alerts.
- identified Sep 19, 2025, 04:35 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Sep 19, 2025, 06:08 PM UTC
This incident has been resolved.
Notice September 9, 2025 Delay in processing events 3h 56m Incydr - console.us2.code42.com
Started Sep 09, 2025, 09:01 PM UTC· resolved Sep 10, 2025, 12:58 AM UTC
- monitoring Sep 09, 2025, 09:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 10, 2025, 12:58 AM UTC
This incident has been resolved.