ThreatLocker incident

We are currently experiencing busyness on our APIs for Instance B, C, D, G

Notice Resolved View vendor source →

ThreatLocker experienced a notice incident on October 21, 2025 affecting API [Instance B] and API [Instance C] and 1 more component, lasting 6h 44m. The incident has been resolved; the full update timeline is below.

Started
Oct 21, 2025, 02:20 PM UTC
Resolved
Oct 21, 2025, 09:04 PM UTC
Duration
6h 44m
Detected by Pingoru
Oct 21, 2025, 02:20 PM UTC

Affected components

API [Instance B]API [Instance C]API [Instance D]API [Instance G]

Update timeline

  1. investigating Oct 21, 2025, 02:20 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 21, 2025, 02:28 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 21, 2025, 03:34 PM UTC

    We are continuing to investigate this issue. Instance D APIs are back operational.

  4. identified Oct 21, 2025, 04:38 PM UTC

    The issue has been identified. APIs for Instance B & C have been resolved. APIs for Instance G are currently working through a backlog.

  5. monitoring Oct 21, 2025, 05:52 PM UTC

    Instance G APIs are back operational. We will continue to monitor this issue.

  6. resolved Oct 21, 2025, 09:04 PM UTC

    This Incident has been resolved, we are now downgrading this outage.