ThreatLocker logo and current status indicator

ThreatLocker Incident History

Degraded

threatlocker.com ↗7 top-level components

checked Nov 4, 2026 11:13 AM UTC · ThreatLocker's official status page

ThreatLocker has disruptions affecting Portal [Instance H] and Twilio SMS.

2 of 41 components currently report disruptions.

Get updates without checking back

Get email updates for the reported ThreatLocker status changes you choose. Follow your other dependencies in the same workspace.

30-day free trial, no card needed. First-time customers; continued monitoring requires a paid subscription.

ThreatLocker incident history

7 reports published by ThreatLocker in the last 30 days

When ThreatLocker breaks, it is typically resolved in 5h 7m — median across 5 resolved incidents over 30 days.

November 3, 2026

Instance H AgentAPI Issue

Last update
  1. resolvedNov 3 · 13:18 UTC

    This incident has been resolved.

Reported by ThreatLocker on their status page.

October 30, 2026

Unified Audit Delays

Last update
  1. resolvedOct 31 · 00:02 UTC

    This is now resolved and Instances D & H are now fully up to date. If you experience any further issues, please come into a LiveChat from the portal.

Reported by ThreatLocker on their status page.

October 22, 2026

Instance G Performance Issues

Last update
  1. resolvedNov 3 · 13:18 UTC

    This incident has been resolved.

Reported by ThreatLocker on their status page.

October 14, 2026

Degraded Performance on Instance G

Last update
  1. resolvedOct 14 · 18:02 UTC

    This incident has been resolved.

Reported by ThreatLocker on their status page.

Degraded Performance on Instance G

Last update
  1. ResolvedOct 14 · 18:02 UTC

    This incident has been resolved.

Reported by ThreatLocker on their status page.

October 9, 2026

Degraded Performance on Instance G

Last update
  1. resolvedOct 9 · 18:12 UTC

    This incident has been resolved.

Reported by ThreatLocker on their status page.

October 6, 2026

Degraded Performance on Instance G

Last update
  1. resolvedOct 6 · 17:49 UTC

    This incident has been resolved.

Reported by ThreatLocker on their status page.