ThreatLocker incident
Machines not checking in on instances G & H
ThreatLocker experienced a minor incident on May 11, 2026 affecting API [Instance G] and API [Instance H], lasting 22m. The incident has been resolved; the full update timeline is below.
Affected components
API [Instance G]API [Instance H]
Update timeline
- identified May 11, 2026, 08:45 PM UTC
Following the earlier incident we have had reports of some machines not checking in on Instance G & H. The issue has been identified and is currently being worked on
- resolved May 11, 2026, 09:08 PM UTC
This incident has been resolved.