- Detected by Pingoru
- May 14, 2026, 03:20 PM UTC
- Resolved
- May 15, 2026, 05:52 PM UTC
- Duration
- 1d 2h
Affected: 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]Portal [Instance CA1]Portal [Instance EU1]Portal [Instance SA1]
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.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 05:56 PM UTC
- Resolved
- May 13, 2026, 06:21 PM UTC
- Duration
- 25m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 08:45 PM UTC
- Resolved
- May 11, 2026, 09:08 PM UTC
- Duration
- 22m
Affected: 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.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 05:35 PM UTC
- Resolved
- May 11, 2026, 08:33 PM UTC
- Duration
- 2h 58m
Affected: 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]Portal [Instance CA1]Portal [Instance EU1]Portal [Instance SA1]
Timeline · 4 updates
-
investigating May 11, 2026, 05:35 PM UTC
We are aware of an issue affecting logins to the portal and are currently investigating
-
investigating May 11, 2026, 06:32 PM UTC
We are continuing to actively investigate this issue.
-
monitoring May 11, 2026, 07:52 PM UTC
Access has been restored and we are currently monitoring
-
resolved May 11, 2026, 08:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 12:48 PM UTC
- Resolved
- May 08, 2026, 06:06 PM UTC
- Duration
- 5h 18m
Affected: Portal [Instance EU1]
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Apr 30, 2026, 08:00 PM UTC
- Resolved
- May 01, 2026, 12:22 AM UTC
- Duration
- 4h 22m
Affected: Portal [Instance C]
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Apr 22, 2026, 07:57 PM UTC
- Resolved
- Apr 22, 2026, 07:59 PM UTC
- Duration
- 1m
Affected: Portal [Instance D]
Timeline · 2 updates
-
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
-
resolved Apr 22, 2026, 07:59 PM UTC
This is now resolved
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 02:29 PM UTC
- Resolved
- Mar 12, 2026, 02:58 PM UTC
- Duration
- 29m
Affected: Portal [Instance EU1]API [Instance EU1]
Timeline · 2 updates
-
investigating Mar 12, 2026, 02:29 PM UTC
We have reports of some customers unable to log into instance EU1. We are currently investigating.
-
resolved Mar 12, 2026, 02:58 PM UTC
EU1 is now fully operational
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 02:48 PM UTC
- Resolved
- May 11, 2026, 09:12 PM UTC
- Duration
- 71d 6h
Affected: API [Instance AE1]Portal [Instance AE1]
Timeline · 2 updates
-
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
-
resolved May 11, 2026, 09:12 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 25, 2026 - Detected by Pingoru
- Feb 25, 2026, 06:47 PM UTC
- Resolved
- Feb 25, 2026, 11:25 PM UTC
- Duration
- 4h 38m
Affected: LiveChat Chat Widget
Timeline · 4 updates
-
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
-
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.'
-
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.
-
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 →
- Detected by Pingoru
- Feb 24, 2026, 04:15 PM UTC
- Resolved
- Feb 24, 2026, 04:24 PM UTC
- Duration
- 9m
Affected: Portal [Instance G]
Timeline · 2 updates
-
investigating Feb 24, 2026, 04:15 PM UTC
We are currently investigating and working on a remediation.
-
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 →
- Detected by Pingoru
- Jan 29, 2026, 08:22 PM UTC
- Resolved
- Jan 29, 2026, 08:38 PM UTC
- Duration
- 15m
Affected: API [Instance C]Portal [Instance C]
Timeline · 4 updates
-
investigating Jan 29, 2026, 08:22 PM UTC
We are currently investigating reports of log in and performance issues affecting Instance C
-
investigating Jan 29, 2026, 08:29 PM UTC
We are continuing to investigate this issue.
-
monitoring Jan 29, 2026, 08:30 PM UTC
Instance C is now operational and we are monitoring
-
resolved Jan 29, 2026, 08:38 PM UTC
Instance C is now operational and the issue is resolved
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 12:15 PM UTC
- Resolved
- Jan 24, 2026, 12:00 AM UTC
- Duration
- 11h 45m
Timeline · 4 updates
-
investigating Jan 23, 2026, 12:15 PM UTC
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.
-
identified Jan 23, 2026, 01:42 PM UTC
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.
-
monitoring Jan 23, 2026, 03:27 PM UTC
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.
-
resolved Jan 24, 2026, 12:00 AM UTC
The issue has been confirmed as resolved. All systems are up and running and functioning as intended.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 05:08 PM UTC
- Resolved
- Nov 24, 2025, 10:40 PM UTC
- Duration
- 5h 32m
Affected: Portal [Instance G]
Timeline · 2 updates
-
identified Nov 24, 2025, 05:08 PM UTC
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.
-
resolved Nov 24, 2025, 10:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 02:13 PM UTC
- Resolved
- Nov 24, 2025, 02:43 PM UTC
- Duration
- 30m
Affected: Portal [Instance G]
Timeline · 2 updates
-
investigating Nov 24, 2025, 02:13 PM UTC
We have had reports of slowness on Instance G. We are currently investigating.
-
resolved Nov 24, 2025, 02:43 PM UTC
The slowness issues on instance G have now been resolved
Read the full incident report →
- Detected by Pingoru
- Nov 20, 2025, 01:44 PM UTC
- Resolved
- Nov 24, 2025, 02:44 PM UTC
- Duration
- 4d 1h
Affected: Portal [Instance G]Portal [Instance H]
Timeline · 8 updates
-
identified Nov 20, 2025, 01:44 PM UTC
We have identified an issue affecting a small number of customers logging in to Portal Instance H. We are currently working to resolve this.
-
identified Nov 20, 2025, 02:44 PM UTC
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
-
monitoring Nov 20, 2025, 03:43 PM UTC
We've restored portal login functionality and are currently monitoring to ensure that the issue is completely resolved.
-
monitoring Nov 20, 2025, 05:33 PM UTC
We've observed degraded portal login performance on instance G and are working on restoring performance.
-
monitoring Nov 20, 2025, 05:44 PM UTC
We have restored login performance on instance G and are continuing to monitor its performance.
-
identified Nov 21, 2025, 01:44 PM UTC
We are aware of some performance issues on instance H this morning affecting some customers. This is currently being addressed
-
monitoring Nov 21, 2025, 03:10 PM UTC
All systems are fully operational at this time. We are continuing to monitor.
-
resolved Nov 24, 2025, 02:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2025, 08:30 PM UTC
- Resolved
- Nov 21, 2025, 03:11 PM UTC
- Duration
- 1d 18h
Affected: API [Instance A]Portal [Instance A]API [Instance B]Portal [Instance B]API [Instance C]Portal [Instance C]API [Instance D]Apps APIsPortal [Instance D]API [Instance E]Portal [Instance E]API [Instance F]Portal [Instance F]API [Instance G]Portal [Instance G]API [Instance H]Portal [Instance H]API [Instance AE1]API [Instance AU1]Portal [Instance AE1]Portal [Instance AU1]Portal [Instance CA1]API [Instance CA1]Portal [Instance EU1]API [Instance EU1]Portal [Instance SA1]API [Instance SA1]Portal [Instance FedRAMP]
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 03:23 PM UTC
- Resolved
- Nov 07, 2025, 08:49 PM UTC
- Duration
- 1d 5h
Affected: Portal [Instance A]API [Instance B]Portal [Instance B]API [Instance C]Portal [Instance C]API [Instance D]Portal [Instance D]API [Instance E]Portal [Instance E]API [Instance F]Portal [Instance F]API [Instance G]Portal [Instance G]API [Instance H]Portal [Instance H]
Timeline · 24 updates
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 02:20 PM UTC
- Resolved
- Oct 21, 2025, 09:04 PM UTC
- Duration
- 6h 44m
Affected: API [Instance B]API [Instance C]API [Instance D]API [Instance G]
Timeline · 6 updates
-
investigating Oct 21, 2025, 02:20 PM UTC
We are currently investigating this issue.
-
investigating Oct 21, 2025, 02:28 PM UTC
We are continuing to investigate this issue.
-
investigating Oct 21, 2025, 03:34 PM UTC
We are continuing to investigate this issue. Instance D APIs are back operational.
-
identified Oct 21, 2025, 04:38 PM UTC
The issue has been identified. APIs for Instance B & C have been resolved. APIs for Instance G are currently working through a backlog.
-
monitoring Oct 21, 2025, 05:52 PM UTC
Instance G APIs are back operational. We will continue to monitor this issue.
-
resolved Oct 21, 2025, 09:04 PM UTC
This Incident has been resolved, we are now downgrading this outage.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 01:59 PM UTC
- Resolved
- Oct 02, 2025, 02:07 PM UTC
- Duration
- 8m
Affected: API [Instance F]API [Instance G]
Timeline · 4 updates
-
investigating Oct 02, 2025, 01:59 PM UTC
We are aware of disruption affecting our APIs. Some online machines may show offline. This is currently being investigated.
-
identified Oct 02, 2025, 02:02 PM UTC
We have identified the issue and a fix is being applied
-
monitoring Oct 02, 2025, 02:06 PM UTC
A fix has been implemented and we are now monitoring
-
resolved Oct 02, 2025, 02:07 PM UTC
This incident has now been resolved
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2025, 12:52 PM UTC
- Resolved
- Sep 24, 2025, 01:03 PM UTC
- Duration
- 11m
Affected: Portal [Instance H]
Timeline · 2 updates
-
investigating Sep 24, 2025, 12:52 PM UTC
User experience might be impacted. Any issues or assistance you might need, please reach out to support via LiveChat. We'll make sure to update this status page as we progress through this issue and towards its resolution. Thank you for your ongoing patience.
-
resolved Sep 24, 2025, 01:03 PM UTC
Accessibility into the Portal has been successfully restored. At this time, the outage has been officially downgraded. If anyone experiences new issues in logging into the portal, please reach out to Support via LiveChat. Thank you again for your patience and cooperation throughout this outage.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 05:29 AM UTC
- Resolved
- Aug 21, 2025, 05:30 PM UTC
- Duration
- 12h 1m
Affected: Portal [Instance AU1]
Timeline · 5 updates
-
investigating Aug 21, 2025, 05:29 AM UTC
We are currently investigating this issue.
-
investigating Aug 21, 2025, 09:54 AM UTC
We are continuing to Investigate this issue, It has been identified that the routing issue is applying to other international locations as well.
-
monitoring Aug 21, 2025, 02:03 PM UTC
Due to the inconsistent nature of the issue, it has only been observed internally thus far. We're not currently aware of any customers that are impacted by this issue.
-
monitoring Aug 21, 2025, 03:48 PM UTC
This is now resolved. It was not customer impacting.
-
resolved Aug 21, 2025, 05:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2025, 01:45 PM UTC
- Resolved
- Aug 13, 2025, 02:09 PM UTC
- Duration
- 24m
Affected: Portal [Instance E]
Timeline · 2 updates
-
investigating Aug 13, 2025, 01:45 PM UTC
We are aware of performance and login issues on Instance E
-
resolved Aug 13, 2025, 02:09 PM UTC
The issues with performance on Instance E have now been resolved
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2025, 02:12 PM UTC
- Resolved
- Jul 14, 2025, 11:11 PM UTC
- Duration
- 8h 58m
Affected: Portal [Instance FedRAMP]
Timeline · 2 updates
-
investigating Jul 14, 2025, 02:12 PM UTC
We are currently investigating performance issues on the FedRAMP Instance
-
resolved Jul 14, 2025, 11:11 PM UTC
The FedRAMP Instance is now fully functional
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2025, 02:14 PM UTC
- Resolved
- Jun 26, 2025, 05:18 PM UTC
- Duration
- 3h 3m
Affected: Portal [Instance H]
Timeline · 3 updates
-
investigating Jun 26, 2025, 02:14 PM UTC
We have received reports of slowness and logouts on Instance H. We are currently investigating
-
monitoring Jun 26, 2025, 02:47 PM UTC
We have implemented a fix and are currently monitoring
-
resolved Jun 26, 2025, 05:18 PM UTC
We have been monitoring and things have stabilized and the issue is now resolved
Read the full incident report →
