Is Liongard Down Right Now? Check if there is a current outage ongoing.

This issue has been resolved and Leo should be functioning normally.

We are currently experiencing an outage with Leo, our in-platform AI-powered support companion. As a result, Partners will experience longer than usual wait times for support. We are closely monitoring the issue and will provide an update once functionality has been restored.

On Thursday, May 23, 2024, our aus2 instance experienced a brief outage from 4:07 AM to 4:19 AM AEST. This outage was caused by an underlying AWS issue: some EC2 instances were unavailable in the ap-southeast-2 region. The issue has since been resolved, and systems are operating normally.

This fix has been confirmed and inspections are landing successfully and no further issues have been detected.

us4 instance has been up and running since 11:20am ET, we are continuing to monitor the inspections needing waiting to be processed.

Our fix has started to show it's effectiveness in landing successful inspections. However given the number of inspections needed to be processed we will be upsizing our infrastructure resources to ensure all inspections process successfully today. This will result in ~ 20 minute downtime starting at 11am ET.

A fix has been shipped to resolve the inspection timeout issues. We will be monitoring this issue as inspections start to land successfully throughout the day.

Today at 3pm ET we will be deploying a fix to resolve this issue. There will be an expected downtime between 3pm - 4 pm ET. As a result, you will not be able to access the Liongard platform during this time. We apologize for any inconvenience this has brought. Downtime extended until 4:30pm ET.

We are aware that inspections on our US4 instance have not been completing successfully due to timeouts. We have identified a fix for this issue and are actively working on it. We will update once the fix has been deployed and issue has been resolved.

We are currently experiencing issues with the Continuum RMM Inspector that are causing an increase in intermittent Inspector failures.  We have determined this to be an issue with the information being returned by the Continuum API. We have escalated the issue to ConnectWise and we are uncertain as to the future of this API as this product <a href="https://www.reddit.com/r/msp/comments/t8r91j/comment/hzubsqt/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button"> is being superseded by the newer ConnectWise RMM product</a>. In addition to the Liongard support request, we also suggest creating a support request with ConnectWise Support.

We are currently experiencing issues with the Continuum RMM Inspector that are causing an increase in intermittent Inspector failures.  We have determined this to be an issue with the information being returned by the Continuum API. We have escalated the issue to ConnectWise and we are uncertain as to the future of this API as this product is being superseded by the newer ConnectWise RMM product.In addition to the Liongard support request, we also suggest creating a support request with ConnectWise Support.

We're happy to report that the issue impacting Webroot child Inspectors has been resolved. According to Webroot, they have rolled back changes that were resulting in errors that were causing Liongard Webroot child Inspectors to fail: https://community.webroot.com/unity-api-forum-49/unity-api-skystatus-request-failed-no-parameterless-constructor-defined-for-type-of-system-string-355881 Once devices check-in to receive the update from Webroot, Inspections should complete successfully.

We are aware of an issue with our Webroot Inspector where child Inspectors are failing with the following error message: Inspection failed at https://unityapi.webrootcloudav.com/service/api/status/gsm/xxxx-xxxx-xxxx-xxxx-xxxx with status code 500: Request failed with status code 500 We have determined this is due to an issue with Webroot's API. See this link for more information: https://community.webroot.com/webroot-universal-reporter-130/skystatus-request-failed-no-parameterless-constructor-defined-355. We do not have an ETA for resolution, but we will update you as new information becomes available.

Microsoft 365 Inspectors are now completing successfully. We will continue to monitor this Inspector’s performance over the next few days.

We have identified an issue with the Microsoft 365 Inspectors failing. We pinpointed the issue down to the Graph API endpoints utilized to pull MailboxDetail and UserDetail reports. This appears to be a result Microsoft’s recent mitigation in response to the recent DDoS attack on Outlook services. We will continue to monitor this issue and investigate resolution options.

A successful fix for some inspections unable to complete successfully has been deployed and no further issues related to timeout inspections have been detected on US2.

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

We are aware that inspections on our US2 instance have not been completing successfully due to timeouts. We have identified a fix for this issue and are actively working on it. We will update once the fix has been deployed and issue has been resolved.

RESOLVED: ConnectWise PSA (formerly ConnectWise Manage) Integration Issue Resolved We’re happy to report that the issue impacting ConnectWise PSA has been resolved. Tickets closed in ConnectWise PSA are now automatically closing their corresponding Liongard Alerts. Thank you for your patience. If you have ticketing sync enabled, Liongard Alerts will automatically update ConnectWise PSA with minimal impact. However not all Alerts will close, check your open Alerts in Liongard to see if the corresponding ticket in ConnectWise PSA is open or closed. If they don’t match, you may want to go through your Alerts and close or update them as-needed.

We are aware of an issue with the ConnectWise PSA Integration. When a Liongard Partner closes a ticket in ConnectWise PSA, the associated alert in Liongard is not closing - it’s remaining open. Our Engineering team has investigated this and has opened a support case with ConnectWise’s Support team. We do not have an ETA for resolution right now, but will update you when we do. Note: This issue is limited to communication from ConnectWise PSA to Liongard. It is not impacting Liongard to ConnectWise PSA communications - Alerts closed in Liongard are closing associated tickets in ConnectWise PSA.