Live  /  Code42 Software  /  Incident

Code42 Software: We are investigating an issue where alert rules and risk indicators may not be correctly generated and applied in a small subset of customer accounts.

Code42 Software · code42.comResolved2026-10-26 11:42 UTC
Public — what happened

Summary

Code42 Software said it was looking into a problem in which alert rules and risk indicators might not be created or applied correctly for a small number of customer accounts. The company began investigating on October 16, 2026 at 22:34 UTC and did not state a cause in its updates. On October 20 it said a fix had been put in place and it was watching the results, and the incident was later marked resolved on October 26.

Affected

Incydr - console.us.code42.com, Incydr - console.us2.code42.com, Incydr - console.us7.code42.com, Incydr - console.au.code42.com, Incydr - console.ca.code42.com, Incydr - console.de.code42.com, Incydr - console.ie.code42.com, Incydr - console.sg.code42.com, Incydr - console.uk.code42.com, Incydr - console.za.code42.com

As listed on Code42 Software’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Code42 Software against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Code42 Software: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Code42 Software report →

More from Code42 Software

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Code42 Software status & history page.

Related: Code42 Software status & history. SquidGrid is not affiliated with Code42 Software.