Is ThreatLocker down?

Last checked 6m ago
Current status
ThreatLocker has degraded performance

Affected component: Twilio SMS

Official status page: https://threatlockerstatus.com · Polled every 5 minutes · 39 components tracked

ThreatLocker is reporting degraded performance right now (last checked 6m ago). Services are up but slower or partially failing.

Real-time ThreatLocker status, recent outages, and incident history — pulled directly from ThreatLocker's official status page at https://threatlockerstatus.com every 5 minutes. Pingoru tracks 39 ThreatLocker services and has captured 14 incidents in the last 90 days (98.94% uptime). Get email, Slack, Discord, or webhook alerts the moment ThreatLocker reports a new incident — free for 5 monitors, no credit card.

Users who monitor ThreatLocker also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
ThreatLocker uptime 98.94% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 13m
    Started Jun 09, 2026, 03:36 PM UTC · Resolved Jun 09, 2026, 03:50 PM UTC
    Portal [Instance G]
    Timeline · 3 updates
    • investigating · Jun 09, 2026, 03:36 PM UTC

      We are currently investigating this issue.

    • investigating · Jun 09, 2026, 03:37 PM UTC

      We are continuing to investigate this issue.

    • resolved · Jun 09, 2026, 03:50 PM UTC

      We have identified the cause, and the issue has been resolved. The team continues to monitor the situation closely to ensure ongoing stability. The outage is now being downgraded. Thank you for your time, patience, and understanding.

    Latest: We have identified the cause, and the issue has been resolved. The team continues to monitor the situation closely to ensure ongoing stability. The outage is now being downgraded. …

  2. Resolved 2h 17m
    Started Jun 04, 2026, 11:48 AM UTC · Resolved Jun 04, 2026, 02:05 PM UTC
    API [Instance B]API [Instance D]
    Timeline · 4 updates
    • investigating · Jun 04, 2026, 11:48 AM UTC

      We are currently investigating this issue.

    • monitoring · Jun 04, 2026, 12:53 PM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Jun 04, 2026, 01:06 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Jun 04, 2026, 05:55 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1d 2h
    Started May 14, 2026, 03:20 PM UTC · Resolved May 15, 2026, 05:52 PM UTC
    Portal [Instance A]Portal [Instance B]Portal [Instance C]Portal [Instance D]Portal [Instance E]Portal [Instance F]Portal [Instance G]Portal [Instance H]Portal [Instance AE1]Portal [Instance AU1]
    Timeline · 3 updates
    • investigating · May 14, 2026, 03:20 PM UTC

      We are receiving reports of 417 errors when downloading any Endpoint Detect policies from Community across multiple instances. Infrastructure and Dev have been alerted. We are investigating.

    • identified · May 14, 2026, 03:56 PM UTC

      Potential issue has been identified with a solution ready to be deployed. Until we can verify this resolves this issue, we will keep this post active. More updates to come.

    • resolved · May 15, 2026, 05:52 PM UTC

      Solution has been pushed in resolving the 417 errors when downloading Endpoint Detect Policies from Community. Thank you all for your patience and understanding throughout this issue.

    Latest: Solution has been pushed in resolving the 417 errors when downloading Endpoint Detect Policies from Community. Thank you all for your patience and understanding throughout this iss…

  4. Resolved 25m
    Started May 13, 2026, 05:56 PM UTC · Resolved May 13, 2026, 06:21 PM UTC
    API [Instance H]Portal [Instance H]
    Timeline · 3 updates
    • investigating · May 13, 2026, 05:56 PM UTC

      We are currently investigating an issue with machines not checking in on instance H

    • investigating · May 13, 2026, 05:57 PM UTC

      We are continuing to investigate this issue.

    • resolved · May 13, 2026, 06:21 PM UTC

      Infrastructure was able to identify the cause quickly and was able to resolve the check-in issue. Instance H is back to fully operational.

    Latest: Infrastructure was able to identify the cause quickly and was able to resolve the check-in issue. Instance H is back to fully operational.

  5. Resolved 22m
    Started May 11, 2026, 08:45 PM UTC · Resolved May 11, 2026, 09:08 PM UTC
    API [Instance G]API [Instance H]
    Timeline · 2 updates
    • 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.

    Latest: This incident has been resolved.

See the full ThreatLocker outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse ThreatLocker outage history →

Or sign up free to get alerts when ThreatLocker breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 10 incidents View full outage history →