ThreatLocker had 40 outages in the last 2 years totaling 1848h 25m of downtime — averaging 1.6 incidents per month.
There were 40 ThreatLocker outages since July 14, 2025 totaling 1848h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.
Machines on D might appear as offline. However, devices should still be reporting and producing UA logs, accepting agent actions. We are currently investigating
We identified the cause and machines should show as checking in. Thank you
We have received reports of intermittent portal slowness on instance G. We are currently investigating thie issue.
This incident has been resolved.
This issue currently impacts both Portal and Beta. We are investigating.
This issue has been quickly Identified and performance returned shortly afterwards. We will continue to monitor to ensure stability. Proceeding to downgrade at this time.
We are currently investigating this issue.
We have identified the cause and working on bringing everything up to speed. Stay tuned
The Unified Audit is current and we are monitoring
This is now resolved
We are currently investigating this issue.
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.
We are currently investigating this issue.
We are continuing to investigate this issue.
Login issues are being addressed. Accessibility to the portal should be fine. We are monitoring this closely
Team was able to pinpoint the cause. Will continue to monitor this situation to ensure stability has fully been returned.
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
We are currently investigating this issue. Please use beta.threatlocker.com, if you are having any issues, please reach out to Support.
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
This incident has been resolved.
Please access the portal using beta.threatlocker.com while we investigate this issue. Device check-ins may also be affected.
We are continuing to investigate this issue. Device check-ins are returning to normal.
We are continuing to investigate this issue. Devices are now checking in as normal.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This is now resolved
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.