ThreatLocker Outage History

ThreatLocker experienced a service disruption where users encountered 417 errors when attempting to download Endpoint Detect policies from Community, affecting all portal instances globally. The issue persisted for 26.6 hours across multiple regions including North America, Europe, Australia, and South America. The problem was resolved by deploying a targeted solution that eliminated the 417 errors and restored policy download functionality.

ThreatLocker experienced a 29-minute service disruption where computers were unable to check in with Instance H, affecting both the API and Portal components. The infrastructure team quickly identified the root cause and restored full operational status to Instance H.

ThreatLocker experienced an issue where machines were unable to check in with the service on instances G and H, affecting the API components for both instances. This was a follow-up problem from an earlier incident that prevented proper machine communication with the ThreatLocker service. The issue was identified and resolved within 27 minutes.

ThreatLocker experienced a major incident affecting login functionality across all portal instances globally, preventing users from accessing the service for 3 hours. The company investigated and restored access, then monitored the system to ensure stability. The incident was fully resolved after confirming normal login operations were restored.

ThreatLocker's EU1 instance experienced 500 errors on portal.threatlocker.com for 5.3 hours, preventing users from accessing the main portal. Users were directed to use beta.threatlocker.com as a workaround until engineers identified the root cause and implemented a solution to fully resolve the errors.

ThreatLocker's Portal Instance C experienced performance issues that caused customers to face slow response times and unexpected logouts. The incident affected Portal Instance C operations for 7 minutes. The service team investigated the reported issues, though the resolution details were not specified in the incident record.

ThreatLocker's Instance D portal experienced performance issues and user logouts for 5 minutes on April 22, 2026. Customers reported difficulties accessing the main portal, though the beta portal remained unaffected and available as an alternative. The issue was resolved after investigation and monitoring.

ThreatLocker experienced login issues with their main Portal login page, preventing some customers from accessing their accounts. Users were directed to use the beta login page at beta.threatlocker.com as a workaround during the 15-minute outage. The issue was resolved and normal portal access was restored.

ThreatLocker experienced a power disruption at their Dubai data center that potentially affected the AE1 instance API and Portal components. While the disruption was initially not impacting the AE1 instance, it was classified as a major incident requiring close monitoring. The incident was resolved after approximately 71 days of monitoring and potential intermittent impacts.

ThreatLocker's "Chat with a Cyber Hero" service experienced a major outage for 6.3 hours due to their third-party chat provider LiveChat having service issues. Users could start chats but experienced delays or failures when sending messages through the LiveChat widget. The issue was resolved after LiveChat deployed a fix and both services monitored for stability before confirming full restoration.