Vendor Status Watch

← all vendors

Code 42 status history

Current state: operational — “All Systems Operational” per https://status.code42.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
11incidents, last 90 days
50incidents on record
Incidents per week, last 12 weeks:

How long do Code 42 incidents last?

7.0 hmedian incident duration50 measured
42.5 h90th percentile1 in 10 ran longer
14.7 hmedian, major/critical only3 incidents

From 50 incidents with a vendor-posted start and resolve time. Longest on record: Microsoft Office 365 event processing. — 10.4 days (2025-11-14 14:34 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (50)

StartedIncidentStatusImpactDuration
2026-08-25 13:26 UTCDelay in processing eventsresolvednone4 h 07 min
2026-08-11 12:46 UTCDelay in processing Alertsresolvednone14 h 21 min
2026-07-30 02:40 UTCEvent Processing Delaysresolvedminor10 h 29 min
2026-07-28 16:22 UTCDelay in processing Google Drive eventsresolvednone47 h 29 min
2026-07-20 21:08 UTCDelay in processing Alertsresolvednone3 h 20 min
2026-07-13 20:00 UTCExfiltrated File Collection Disruption (Incydr Gov Only)postmortemnone0 min
2026-07-06 14:06 UTCEvent Processing Delaysresolvedminor5 h 17 min
2026-06-24 19:34 UTCDelay in processing eventsresolvednone16 h 11 min
2026-06-24 14:20 UTCDelay in processing eventsresolvednone5 h 13 min
2026-06-22 22:46 UTCDelay in processing eventsresolvednone12 h 32 min
2026-06-22 15:57 UTCDelay in processing Alertsresolvednone0 min
2026-06-13 12:39 UTCDelayed processing of events for Cloud Connectorsresolvednone1 h 56 min
2026-06-11 13:19 UTCDelay in processing eventsresolvednone9 h 54 min
2026-05-29 12:59 UTCDelayed event processing of Cloud Data Connector eventsresolvednone3 d 0 h
2026-05-27 01:32 UTCDelay in processing eventsresolvednone10 h 12 min
2026-05-21 22:12 UTCDelay in processing eventsresolvednone4 h 29 min
2026-05-11 22:05 UTCDelay in Processing events from Cloud and Email Connectorsresolvednone2 d 19 h
2026-04-30 01:49 UTCDelay in processing OneDrive, O365, Gmail and Gdrive Eventsresolvednone2 d 12 h
2026-04-29 20:42 UTCDelay in processing eventsresolvednone15 h 28 min
2026-04-28 22:24 UTCDelay in processing agent settings.resolvednone1 h 00 min
2026-04-23 17:31 UTCDelay in processing Alertsresolvednone3 h 55 min
2026-03-30 13:29 UTCEvent Processing Delaysresolvedminor20 h 39 min
2026-03-25 13:31 UTCEvent Processing Delaysresolvedminor8 h 38 min
2026-03-23 21:56 UTCFailing Logins for Incydrpostmortemcritical14 h 43 min
2026-03-20 02:50 UTCAuthentication Failures in Prod Govresolvedcritical19 min
2026-03-10 23:27 UTCDelay in Processing Cloud Detector Security Eventsresolvednone10 h 58 min
2026-03-05 13:21 UTCDelay in processing Alertsresolvednone7 h 16 min
2026-02-18 20:37 UTCDelay in processing Alertsresolvednone21 h 16 min
2026-02-04 21:16 UTCEvent Processing Delaysresolvedminor5 h 21 min
2026-02-04 02:07 UTCEvent Processing Delaysresolvedminor2 h 07 min
2026-02-04 02:00 UTCEvent Processing Delaysresolvedminor10 h 46 min
2026-01-12 22:20 UTCDelay in processing Alertsresolvednone0 min
2025-11-14 14:34 UTCMicrosoft Office 365 event processing.resolvednone10 d 9 h
2025-11-07 17:36 UTCDelay in processing OneDrive eventsresolvednone42 h 27 min
2025-10-29 05:14 UTCDue to an AWS ECS service incident a subset of alerting services are unavailable. The following services are impacted: Alert Page visualizations and Alert Session API temporarily unavailable.resolvednone6 h 44 min
2025-10-28 18:27 UTCDue to an AWS ECS service incident a subset of alerting services are unavailable. The following services are impacted: Alert Page visualizations and Alert Session API temporarily unavailable.resolvednone7 h 30 min
2025-10-27 16:17 UTCErrors when downloading files from Alerts and Forensic File Searchresolvednone2 h 56 min
2025-10-27 16:01 UTCDelay in processing Alertsresolvednone4 h 49 min
2025-10-24 20:19 UTCDelayed processing of OneDrive Eventsresolvednone6 h 31 min
2025-10-24 16:07 UTCDelay in processing Alertsresolvednone3 h 51 min
2025-10-21 16:26 UTCEvent Processing Delaysresolvedminor6 h 06 min
2025-10-20 12:59 UTCEvent Processing Delaysresolvedmajor22 h 40 min
2025-09-25 16:30 UTCDelay in processing watchlist memberships.resolvednone0 min
2025-09-24 17:50 UTCDelay in processing OneDrive eventsresolvednone20 h 34 min
2025-09-19 16:11 UTCEvent Processing Delaysresolvedminor1 h 57 min
2025-09-09 21:01 UTCDelay in processing eventsresolvednone3 h 56 min
2025-09-03 01:08 UTCDelay in processing Alertsresolvednone10 h 47 min
2025-09-01 21:05 UTCEvent Processing Delaysresolvedminor1 h 23 min
2025-08-27 15:53 UTCErrors when displaying Alerts and Session API inaccessibleresolvednone5 h 42 min
2025-08-26 20:46 UTCUnable to access Casesresolvedminor15 h 42 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Code 42 with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "code-42"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}