ThreatLocker had 39 outages in the last 2 years totaling 1992h 22m of downtime — averaging 1.6 incidents per month.
There were 39 ThreatLocker outages since June 2, 2025 totaling 1992h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
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.
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.
We are currently investigating login and performance issues on Instance CA1
This is now resolved
The issue has been identified and we are working on getting this resolved as quickly as possible
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
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.
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.
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)
This is now resolved
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.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
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.
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.
We are currently investigating an issue with machines not checking in on instance H
We are continuing to investigate this issue.
Infrastructure was able to identify the cause quickly and was able to resolve the check-in issue. Instance H is back to fully operational.
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
This incident has been resolved.
We are aware of an issue affecting logins to the portal and are currently investigating
We are continuing to actively investigate this issue.
Access has been restored and we are currently monitoring
This incident has been resolved.
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.
With the help of our engineers, we identified the root cause. The solution should be pushed out momentarily.
Solution has been implemented and the errors are fully resolved. Thank you for everyone's patience on the matter.
We have received reports of customers experiencing performance issues and logouts on Instance C. We are investigating.
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.
We have been monitoring and there have been no further issues. This is now resolved
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
This is now resolved
We have reports of some customers unable to log into instance EU1. We are currently investigating.
EU1 is now fully operational
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
This incident has been resolved.
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
LiveChat have stated 'While chats can be started, customers may experience delays or failures when sending messages.'
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.
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.
We are currently investigating and working on a remediation.
The cause of the performance degradation was quickly identified, and the implemented solution has resolved the issue. The incident has now been downgraded.
We are currently investigating reports of log in and performance issues affecting Instance C
We are continuing to investigate this issue.
Instance C is now operational and we are monitoring
Instance C is now operational and the issue is resolved
We’ve received reports that policies using Entra groups for user targeting have stopped working across multiple instances. We are actively investigating the root cause and will update this status as soon as possible. Thank you for your patience while we work through this issue.
The issue has been identified, and we are beginning to roll out the fixes for those impacted. Once again, we appreciate your patience while we work through this issue.
The solutions have been deployed to all impacted parties. We are actively reviewing and monitoring the situation throughout the day to confirm stability and functionality. This post will be updated once everything is confirmed to be fully operational and stable.
The issue has been confirmed as resolved. All systems are up and running and functioning as intended.
We have identified an issue with sending Application Requests, and a backlog in Unified Audit logging on Instance G. The cause has been identified and a fix is currently being pushed.
This incident has been resolved.
We have had reports of slowness on Instance G. We are currently investigating.
The slowness issues on instance G have now been resolved
We have identified an issue affecting a small number of customers logging in to Portal Instance H. We are currently working to resolve this.
If you are experiencing issues with machines not checking in, please reach out to our Cyber Hero support team with public IPs and we will get them added and prioritized
We've restored portal login functionality and are currently monitoring to ensure that the issue is completely resolved.
We've observed degraded portal login performance on instance G and are working on restoring performance.
We have restored login performance on instance G and are continuing to monitor its performance.
We are aware of some performance issues on instance H this morning affecting some customers. This is currently being addressed
All systems are fully operational at this time. We are continuing to monitor.
This incident has been resolved.