Liongard Outage History

Started Oct 15, 2026, 06:57 PM UTC· resolved Oct 16, 2026, 02:03 PM UTC

1. investigating Oct 15, 2026, 06:57 PM UTC

   We are currently experiencing a service interruption on US7. Some users may receive an “Internal Server Error” message when attempting to log in. Our team is currently investigating.

2. monitoring Oct 15, 2026, 07:20 PM UTC

   Our team has implemented a fix for the issue affecting US7, and initial testing indicates that service has been restored. We have successfully verified login functionality across multiple accounts and have not observed any further issues. We are moving this incident to **Monitoring** and will continue to monitor the instance to ensure stability.

3. resolved Oct 16, 2026, 02:03 PM UTC

   The issue affecting the US7 instance has been resolved. Following the implementation of a fix, we have continued monitoring the instance and have not observed any further issues. Login functionality has been restored, and services are operating normally. We are marking this incident as resolved. Thank you for your patience.

Read the full incident report →

Started Aug 03, 2026, 03:32 PM UTC· resolved Aug 18, 2026, 07:02 PM UTC

1. investigating Aug 03, 2026, 03:32 PM UTC

   US5 is currently experiencing platform slowness and intermittent 400 errors caused by database connection exhaustion. Our teams are actively investigating the issue and working to restore normal performance. We will provide additional updates as they become available.

2. monitoring Aug 03, 2026, 03:37 PM UTC

   We have deployed a change that should improve performance in US5. Our teams are monitoring the environment to confirm continued improvement.

3. monitoring Aug 06, 2026, 04:23 PM UTC

   We've deployed an additional fix to US5 to resolve the recurring database performance issue. Performance has returned to normal, and we're continuing to monitor closely. Our upcoming August release includes further improvements that will reduce the risk of this recurring issue.

4. monitoring Aug 18, 2026, 06:53 PM UTC

   This has been resolved.

5. resolved Aug 18, 2026, 07:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 22, 2026, 10:12 PM UTC· resolved Jun 30, 2026, 09:26 PM UTC

1. monitoring Jun 22, 2026, 10:12 PM UTC

   Liongard recently began a phased release of Agent version 5.4.0 on June 9. The release was terminated on June 16 after issues were identified. The 5.4.0 agent release was made available to partners on the following instances: US1, US2, US3, US7, AUS1, CA1, EU1, IND1, and UK1. Partners on all other instances should be unaffected. For some partners who upgraded to Agent version 5.4.0, the agent upgrade completed successfully, but affected agents were unable to send heartbeats to the Liongard platform and returned 503 errors. As a result, some inspections associated with affected agents may not have run as expected. During our investigation, we also identified a separate certificate-related issue with the 5.4.0 agent release. Due to these issues, Liongard has removed Agent 5.4.0 from the static download URL and agent updater path. Agent version 5.3.1 has been relisted as the current available version. Our development team has implemented a fix to address the heartbeat 503 issue, and that fix is expected to become visible within the next couple of hours. In parallel, the team is working on Agent version 5.4.1 to address the certificate-related issue. Version 5.4.1 will be made available once it has been fully tested and validated. We will provide additional updates as more information becomes available.

2. monitoring Jun 24, 2026, 01:18 PM UTC

   Liongard has released Agent version 5.4.1 through the agent auto-updater path to address the certificate-related issue identified in the Agent 5.4.0 release. Agent version 5.4.1 is currently available only on the instances that received the Agent 5.4.0 release: US1, US2, US3, US7, AUS1, CA1, EU1, IND1, and UK1. Partners on all other instances should be unaffected. Agent version 5.4.0 remains removed from the static download URL and agent updater path. Agent version 5.3.1 remains the current version available when downloading the agent from the Liongard platform UI. We are continuing to monitor agent recovery as affected agents update. Partners may continue to see some agents appear offline until those agents successfully update through the agent auto-updater path or are otherwise remediated. Once we have confirmed continued recovery, Agent version 5.4.1 will be made available to additional instances through a phased release. We will provide another update once more information is available.

3. resolved Jun 30, 2026, 09:26 PM UTC

   Jun 30, 16:26 CDT - Liongard has fully released Agent version 5.4.1 to all partner instances. Agent version 5.4.1 is now available through the Liongard platform UI when downloading an agent, as well as through the agent updater path. Agent version 5.4.1 addresses the issues identified with Agent version 5.4.0. We have observed agent health recovery for affected agents after updating to version 5.4.1. Agents that were previously unable to run as expected or communicate successfully with the Liongard platform have resumed normal functionality after updating. At this time, we are not seeing a continued pattern of issues related to Agent version 5.4.1, and this incident is now considered resolved. If you experience any issues with Agent version 5.4.1, please contact Liongard Support for assistance.

Read the full incident report →

Started Mar 09, 2026, 01:39 PM UTC· resolved Mar 13, 2026, 04:24 PM UTC

1. investigating Mar 09, 2026, 01:39 PM UTC

   We are currently investigating an issue causing an outage for one of our service instances. Our engineering team is actively working to determine the root cause and restore service as quickly as possible. At this time, we have not yet identified the underlying cause and do not have an estimated time for resolution. We will continue to provide updates as soon as more information becomes available. We appreciate your patience and understanding while we work to resolve this issue.

2. monitoring Mar 09, 2026, 03:49 PM UTC

   The fix has been deployed and we are monitoring currently.

3. monitoring Mar 09, 2026, 04:59 PM UTC

   The fix has been deployed and we are monitoring currently.

4. resolved Mar 13, 2026, 04:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 25, 2025, 11:05 PM UTC· resolved Dec 18, 2025, 06:47 PM UTC

1. identified Nov 25, 2025, 11:05 PM UTC

   --Executive Summary Liongard recently deployed an update to the Liongard Agent that unintentionally introduced instability in some partner environments. The update included a new Nmap-based enhancement for Network Discovery, but the way this capability was packaged and distributed resulted in several endpoint protection platforms—most notably SentinelOne—flagging legitimate components as malicious. This issue was not due to a security compromise, but rather to how the Nmap integration was implemented in the agent. Some security solutions interpreted the bundled Nmap installer as a threat, leading to quarantines and—in more severe cases—temporary loss of network connectivity on protected endpoints. Liongard takes full responsibility for the disruption this caused. To immediately mitigate partner impact, we are releasing Agent version 5.1.1, which removes the Nmap integration entirely and clears existing Nmap files from the Liongard Agent directory. This rollback will temporarily pause Network Discovery functionality until it is reintroduced with a more compatible, rigorously validated design in version 5.1.2. --Detailed Technical Analysis --What Happened Agent versions 5.0.4 through 5.1.0 introduced Nmap to expand Network Discovery capabilities. Although secure and intentional, the method of bundling this tool resulted in some EDR/AV vendors misidentifying it as a “Hacking Tool.” Because of this misalignment between our packaging approach and security vendor expectations, certain policies responded aggressively, quarantining files or disabling network adapters entirely. --Root Cause The issue originated from how the Nmap installer was included and delivered within the Liongard Agent. While Nmap itself is widely used and trusted, our deployment approach triggered behavior- and signature-based detections in several protection platforms. This was a preventable integration challenge on our part, and we are taking action to ensure it does not recur. --Immediate Remediation: Agent 5.1.1 To stabilize partner environments, Agent 5.1.1 will: · Fully remove the Nmap installer from the agent · Remove any existing Nmap files from previously installed versions · Prevent further EDR false positives related to this release · Temporarily suspend Network Discovery Inspector functionality Work is already underway on Agent 5.1.2, which will restore Network Discovery using an approach that aligns with modern EDR expectations and vendor security criteria. --Moving Forward: Improvements & Preventive Measures Liongard is committed to learning from this event and improving both our release processes and our diligence around security vendor compatibility. 1. Strengthened Pre-Release Testing With Security Vendors We are expanding testing and validation across multiple EDR/AV vendors—including SentinelOne, CrowdStrike, and Microsoft Defender—to ensure future changes are recognized as safe before release. 2. Enhanced Packaging & Architecture Review Before introducing utilities or scanning tools like Nmap, our engineering teams will now perform deeper compatibility reviews tailored to how EDRs evaluate installers, command-line utilities, and network-scanning behaviors. 3. Earlier & More Detailed Partner Communication Future architectural updates will be accompanied by: · Clear technical preparation steps · Updated EDR allowlisting guidance · Early communication for partners with strict security postures 4. Expanded Internal Validation We are enhancing our release pipeline to include: · Multi-vendor false-positive testing · Behavior-based security scanning These steps are designed to prevent similar disruptions and ensure future enhancements are introduced with the necessary rigor and validation. --Closing Statement We acknowledge the disruption this incident caused and take responsibility for the impact on your operations. Our team is fully committed to resolving the issue, restoring full functionality, and implementing the improvements needed to prevent this from happening again. Thank you for your continued partnership and patience as we work through this with urgency and care. If you have any questions or need support with affected endpoints, please reach out to Liongard Support. https://support.liongard.com/en/articles/12936905-incident-review-liongard-agent-update-sentinelone-false-positive

2. identified Nov 25, 2025, 11:06 PM UTC

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

3. monitoring Nov 26, 2025, 02:20 PM UTC

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

4. resolved Dec 18, 2025, 06:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 26, 2025, 11:22 PM UTC· resolved Nov 25, 2025, 09:47 PM UTC

1. investigating Jun 26, 2025, 11:22 PM UTC

   We are currently investigating performance issues affecting IT Glue Flexible Assets. Our team is actively working with Kaseya IT Glue to identify and resolve the root cause of the issue. In the meantime, we recommend partners leverage IT Glue Pro Sync, which utilizes Core Assets to provide a more stable experience. This feature is now available in Preview for all Liongard Partners for a limited time. Click here for more information on how to enable this feature: https://docs.liongard.com/docs/core-asset-configuration-syncing-it-glue We will provide updates as we learn more.

2. identified Jul 17, 2025, 11:40 PM UTC

   Kaseya IT Glue has identified the issues impacting our IT Glue Flexible Asset integration. They have provided an initial resolution for part of the issue, and we are actively working with them to get to a complete resolution. In the meantime, we recommend partners leverage IT Glue Pro Sync, which utilizes Core Assets to provide a more stable experience. This feature is now available in Preview for all Liongard Partners for a limited time. Click here for more information on how to enable this feature: https://docs.liongard.com/docs/core-asset-configuration-syncing-it-glue

3. identified Jul 23, 2025, 10:13 PM UTC

   Update on IT Glue Flexible Asset Integration Issue KaseyaIT Glue is taking further steps to fully resolve the IT Glue Flexible Asset integration issue. They plan to release a hotfix on July 31 to address the issue. In the meantime, we continue to recommend that partners use IT Glue Pro Sync, which leverages Core Assets for a more stable experience. This feature is available in Preview for all Liongard partners for a limited time. For details on enabling Pro Sync, please visit: https://docs.liongard.com/docs/core-asset-configuration-syncing-it-glue

4. resolved Nov 25, 2025, 09:47 PM UTC

   The incident has been resolved.

Read the full incident report →