ThreatLocker Outage History

ThreatLocker is up right now

Pingoru has recorded 64 incidents for ThreatLocker: 63 in the last 12 months and 22 in the last 90 days.

Source: threatlockerstatus.com

64incidents recorded
63last 12 months
22last 90 days
42 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct13%
Pingoru began tracking ThreatLocker in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202634 of 720 (1%)
May 2026536 of 744 (5%)
June 2026978 of 720 (11%)
July 20261437 of 744 (5%)
August 20267430 of 744 (58%)
September 20267110 of 720 (15%)
October 2026676 of 592 (13%)

Incidents, newest first

Minor July 8, 2026 It's been reported that the Unified Audits on EU1 are delayed. This is impacted both Portal and Beta 2h 14m Portal [Instance EU1]

Started Jul 08, 2026, 11:30 AM UTC· resolved Jul 08, 2026, 01:45 PM UTC

  1. investigating Jul 08, 2026, 11:30 AM UTC

    We are currently investigating this issue.

  2. identified Jul 08, 2026, 11:42 AM UTC

    We have identified the cause and working on bringing everything up to speed. Stay tuned

  3. monitoring Jul 08, 2026, 12:50 PM UTC

    The Unified Audit is current and we are monitoring

  4. resolved Jul 08, 2026, 01:45 PM UTC

    This is now resolved

Read the full incident report →

Major July 5, 2026 Reported Issues within logging in on the FedRamp instance. 21m Portal [Instance FedRAMP]

Started Jul 05, 2026, 05:22 AM UTC· resolved Jul 05, 2026, 05:44 AM UTC

  1. investigating Jul 05, 2026, 05:22 AM UTC

    We are currently investigating this issue.

  2. resolved Jul 05, 2026, 05:44 AM UTC

    Team was able to resolve the internal errors that caused the login issues on FedRamp. Access has returned and systems are fully operational. Outage is being downgraded.

Read the full incident report →

Minor July 2, 2026 Login issues have been reported on Instance G 2h 28m Portal [Instance G]

Started Jul 02, 2026, 06:04 PM UTC· resolved Jul 02, 2026, 08:32 PM UTC

  1. investigating Jul 02, 2026, 06:04 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 02, 2026, 06:09 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 02, 2026, 06:16 PM UTC

    Login issues are being addressed. Accessibility to the portal should be fine. We are monitoring this closely

  4. monitoring Jul 02, 2026, 06:30 PM UTC

    Team was able to pinpoint the cause. Will continue to monitor this situation to ensure stability has fully been returned.

  5. resolved Jul 02, 2026, 08:32 PM UTC

    Instance G is functioning as expected with no new reports of any issues with logging in. Everything is fully operational at this time. Downgrading outage post

Read the full incident report →

Notice July 2, 2026 Log In issues have been reported for customers on Instance G for portal.threatlocker.com 1h 53m Portal [Instance G]

Started Jul 02, 2026, 04:15 PM UTC· resolved Jul 02, 2026, 06:09 PM UTC

  1. investigating Jul 02, 2026, 04:15 PM UTC

    We are currently investigating this issue. Please use beta.threatlocker.com, if you are having any issues, please reach out to Support.

  2. monitoring Jul 02, 2026, 04:24 PM UTC

    A fix has been implemented and we are monitoring the results. Please contact Support if you are still unable to login to portal.threatlocker.com

  3. resolved Jul 02, 2026, 06:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 1, 2026 Log In issues have been reported for customers on Instance EU1 3h 3m Portal [Instance EU1], API [Instance EU1]

Started Jul 01, 2026, 09:15 AM UTC· resolved Jul 01, 2026, 12:18 PM UTC

  1. investigating Jul 01, 2026, 10:06 AM UTC

    Please access the portal using beta.threatlocker.com while we investigate this issue. Device check-ins may also be affected.

  2. investigating Jul 01, 2026, 10:57 AM UTC

    We are continuing to investigate this issue. Device check-ins are returning to normal.

  3. investigating Jul 01, 2026, 11:06 AM UTC

    We are continuing to investigate this issue. Devices are now checking in as normal.

  4. monitoring Jul 01, 2026, 11:42 AM UTC

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

  5. monitoring Jul 01, 2026, 11:51 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jul 01, 2026, 12:18 PM UTC

    This is now resolved

Read the full incident report →

Major June 29, 2026 Log In issues have been reported for customers on Instance C 16m Portal [Instance C]

Started Jun 29, 2026, 12:57 PM UTC· resolved Jun 29, 2026, 01:14 PM UTC

  1. investigating Jun 29, 2026, 12:57 PM UTC

    We are currently investigating this issue.

  2. resolved Jun 29, 2026, 01:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 25, 2026 Investigating machines not checking into the Portal on Instance H 45m Portal [Instance H]

Started Jun 25, 2026, 04:29 PM UTC· resolved Jun 25, 2026, 05:15 PM UTC

  1. investigating Jun 25, 2026, 04:29 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 25, 2026, 04:30 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 25, 2026, 04:50 PM UTC

    We have identified an internal issue that may have contributed to this incident. We are still investigating the root cause and will provide updates as more information becomes available. Machines on Instance H should now be returning to an "Active" state. Thank you for everyone's patience and understanding while we continue our investigation.

  4. resolved Jun 25, 2026, 05:15 PM UTC

    We have confirmed that Instance H has returned to a stable state, and all indicators show that systems are operating as expected. Outage is being downgraded at this time. Thank you for everyone's patience.

Read the full incident report →

Minor June 22, 2026 Instance CA1 Performance Issues 29m Portal [Instance CA1]

Started Jun 22, 2026, 01:47 PM UTC· resolved Jun 22, 2026, 02:17 PM UTC

  1. investigating Jun 22, 2026, 01:47 PM UTC

    We are currently investigating login and performance issues on Instance CA1

  2. resolved Jun 22, 2026, 02:17 PM UTC

    This is now resolved

Read the full incident report →

Minor June 19, 2026 Delayed Unified Audit logs on Instance H 2h 37m Portal [Instance H]

Started Jun 19, 2026, 08:05 PM UTC· resolved Jun 19, 2026, 10:43 PM UTC

  1. identified Jun 19, 2026, 08:05 PM UTC

    The issue has been identified and we are working on getting this resolved as quickly as possible

  2. identified Jun 19, 2026, 08:05 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jun 19, 2026, 08:06 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Jun 19, 2026, 10:43 PM UTC

    We were able to identify the cause early on in our investigation., I can confirm the issue is now resolved, and logs are up-to-date at this time. Downgrading the outage accordingly.

Read the full incident report →

Minor June 19, 2026 SAML Login Issues 2d 23h Portal [Instance A]

Started Jun 19, 2026, 12:23 PM UTC· resolved Jun 22, 2026, 11:56 AM UTC

  1. identified Jun 19, 2026, 12:23 PM UTC

    We are aware of SAML login issues affecting some customers. If you experience any issues with SAML login please come into a LiveChat and we can assist in login. We have identified the issue and are currently working to resolve.

  2. monitoring Jun 19, 2026, 01:05 PM UTC

    URL validation was added to the SAML integration which affected some customers that were using legacy URL configuration. If you cannot log in using SAML, please enter a LiveChat for assistance, or you can adjust your Assertation URL. Legacy URLs may contain a double forward slash after threatlocker.com - examples below. https://betaportalapi.X.threatlocker.com//portalApi/AuthenticationSAML/AssertionConsumerService To fix, this needs to be changed to a single forward slash: https://betaportalapi.X.threatlocker.com/portalApi/AuthenticationSAML/AssertionConsumerService **Please note that X is your Instance and should not be changed from the current value (B, C, D, F, G, H etc)

  3. resolved Jun 22, 2026, 11:56 AM UTC

    This is now resolved

Read the full incident report →

Notice June 18, 2026 Delayed Unified Audit Logs Instance B 42m Portal [Instance B]

Started Jun 18, 2026, 02:22 AM UTC· resolved Jun 18, 2026, 03:05 AM UTC

  1. identified Jun 18, 2026, 02:22 AM UTC

    We are aware of an issue causing Unified Audit Logs to be delayed on Instance B. We have Identified the Issue and are currently working on a resolution.

  2. resolved Jun 18, 2026, 03:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 9, 2026 We are receiving reports that Admins are not able to Log in. This appears to only impact those on Instance G. We are investigating. 13m Portal [Instance G]

Started Jun 09, 2026, 03:36 PM UTC· resolved Jun 09, 2026, 03:50 PM UTC

  1. investigating Jun 09, 2026, 03:36 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 09, 2026, 03:37 PM UTC

    We are continuing to investigate this issue.

  3. 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.

Read the full incident report →

Notice June 4, 2026 Computers not reporting check-ins properly, this does not impact your policy deployment or anything else 2h 17m API [Instance B], API [Instance D]

Started Jun 04, 2026, 11:48 AM UTC· resolved Jun 04, 2026, 02:05 PM UTC

  1. investigating Jun 04, 2026, 11:48 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 04, 2026, 12:53 PM UTC

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

  3. monitoring Jun 04, 2026, 01:06 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 04, 2026, 05:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2026 Unable to download Endpoint Detect policies from Community. 1d 2h Portal [Instance A], Portal [Instance B], Portal [Instance C], Portal [Instance D] and 9 more

Started May 14, 2026, 03:20 PM UTC· resolved May 15, 2026, 05:52 PM UTC

  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Minor May 13, 2026 Computers not showing check-ins on Instance H 25m API [Instance H], Portal [Instance H]

Started May 13, 2026, 05:56 PM UTC· resolved May 13, 2026, 06:21 PM UTC

  1. investigating May 13, 2026, 05:56 PM UTC

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

  2. investigating May 13, 2026, 05:57 PM UTC

    We are continuing to investigate this issue.

  3. 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.

Read the full incident report →

Minor May 11, 2026 Machines not checking in on instances G & H 22m API [Instance G], API [Instance H]

Started May 11, 2026, 08:45 PM UTC· resolved May 11, 2026, 09:08 PM UTC

  1. 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

  2. resolved May 11, 2026, 09:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 11, 2026 Portal Login Issues 2h 58m Portal [Instance A], Portal [Instance B], Portal [Instance C], Portal [Instance D] and 9 more

Started May 11, 2026, 05:35 PM UTC· resolved May 11, 2026, 08:33 PM UTC

  1. investigating May 11, 2026, 05:35 PM UTC

    We are aware of an issue affecting logins to the portal and are currently investigating

  2. investigating May 11, 2026, 06:32 PM UTC

    We are continuing to actively investigate this issue.

  3. monitoring May 11, 2026, 07:52 PM UTC

    Access has been restored and we are currently monitoring

  4. resolved May 11, 2026, 08:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026 Instance EU1 has degraded performance on portal.threatlocker.com 5h 18m Portal [Instance EU1]

Started May 08, 2026, 12:48 PM UTC· resolved May 08, 2026, 06:06 PM UTC

  1. investigating May 08, 2026, 12:48 PM UTC

    It's been reported that 500 errors are occurring on instance EU1 while in portal.threatlocker.com. Beta.threatlocker.com works for the time being. Please use beta while we work on getting the portal issues resolved. Thank you for everyone's patience at this time.

  2. identified May 08, 2026, 01:43 PM UTC

    With the help of our engineers, we identified the root cause. The solution should be pushed out momentarily.

  3. resolved May 08, 2026, 06:06 PM UTC

    Solution has been implemented and the errors are fully resolved. Thank you for everyone's patience on the matter.

Read the full incident report →

Minor April 30, 2026 Portal - Instance C performance issues 4h 22m Portal [Instance C]

Started Apr 30, 2026, 08:00 PM UTC· resolved May 01, 2026, 12:22 AM UTC

  1. investigating Apr 30, 2026, 08:00 PM UTC

    We have received reports of customers experiencing performance issues and logouts on Instance C. We are investigating.

  2. monitoring Apr 30, 2026, 08:11 PM UTC

    We have identified the cause of this performance issue as too many active connections on the instance, which was causing high CPU usage on the server. We have since allocated additional resources and are monitoring.

  3. resolved May 01, 2026, 12:22 AM UTC

    We have been monitoring and there have been no further issues. This is now resolved

Read the full incident report →

Minor April 22, 2026 Instance D Performance Issues 1m Portal [Instance D]

Started Apr 22, 2026, 07:57 PM UTC· resolved Apr 22, 2026, 07:59 PM UTC

  1. investigating Apr 22, 2026, 07:57 PM UTC

    We have received reports of customers experiencing performance issues and logouts on Instance D. At this time the beta portal is not affected - beta.threatlocker.com can still be used

  2. resolved Apr 22, 2026, 07:59 PM UTC

    This is now resolved

Read the full incident report →

Minor March 12, 2026 EU1 Performance Issues 29m Portal [Instance EU1], API [Instance EU1]

Started Mar 12, 2026, 02:29 PM UTC· resolved Mar 12, 2026, 02:58 PM UTC

  1. investigating Mar 12, 2026, 02:29 PM UTC

    We have reports of some customers unable to log into instance EU1. We are currently investigating.

  2. resolved Mar 12, 2026, 02:58 PM UTC

    EU1 is now fully operational

Read the full incident report →

Major March 1, 2026 AE1 Data Center Interruption 71d 6h API [Instance AE1], Portal [Instance AE1]

Started Mar 01, 2026, 02:48 PM UTC· resolved May 11, 2026, 09:12 PM UTC

  1. monitoring Mar 01, 2026, 02:48 PM UTC

    We are aware of a power disruption at one of our data center locations in the Dubai region. It is not currently affecting the AE1 instance but we are closely monitoring

  2. resolved May 11, 2026, 09:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 25, 2026 LiveChat Outage 4h 38m LiveChat Chat Widget

Started Feb 25, 2026, 06:47 PM UTC· resolved Feb 25, 2026, 11:25 PM UTC

  1. investigating Feb 25, 2026, 05:09 PM UTC

    Our 3rd party chat service provider, LiveChat, have confirmed that they are currently experiencing an outage. https://status.livechat.com/incidents/01KJ9H5EV1126499GPNHCT9CVT ThreatLocker's Chat with a Cyber Hero service may be impacted by this outage. For urgent assistance please call +1 833-292-7732

  2. investigating Feb 25, 2026, 05:53 PM UTC

    LiveChat have stated 'While chats can be started, customers may experience delays or failures when sending messages.'

  3. monitoring Feb 25, 2026, 06:47 PM UTC

    LiveChat has stated that "Deployment of the fix is complete. We are monitoring the service to ensure full stability" ThreatLocker is going to continue monitoring as well before resolving this outage.

  4. resolved Feb 25, 2026, 11:25 PM UTC

    LiveChat remains to have this outage in a monitoring state at this time to ensure full stability. The ThreatLocker LiveChat widget has been stable for the last several hours with no noticeable issues. We will downgrade this outage at this time if you notice any issues with LiveChat please reach out to support through the available channels.

Read the full incident report →

Minor February 24, 2026 Slowness on the Applications page Instance G 9m Portal [Instance G]

Started Feb 24, 2026, 04:15 PM UTC· resolved Feb 24, 2026, 04:24 PM UTC

  1. investigating Feb 24, 2026, 04:15 PM UTC

    We are currently investigating and working on a remediation.

  2. resolved Feb 24, 2026, 04:24 PM UTC

    The cause of the performance degradation was quickly identified, and the implemented solution has resolved the issue. The incident has now been downgraded.

Read the full incident report →

Minor January 29, 2026 Performance Issues on Instance C 15m API [Instance C], Portal [Instance C]

Started Jan 29, 2026, 08:22 PM UTC· resolved Jan 29, 2026, 08:38 PM UTC

  1. investigating Jan 29, 2026, 08:22 PM UTC

    We are currently investigating reports of log in and performance issues affecting Instance C

  2. investigating Jan 29, 2026, 08:29 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 29, 2026, 08:30 PM UTC

    Instance C is now operational and we are monitoring

  4. resolved Jan 29, 2026, 08:38 PM UTC

    Instance C is now operational and the issue is resolved

Read the full incident report →