CompassMSP Services Status Page - Notice history

A fix has now been deployed across all supported platforms and is available to all customers. Our teams are actively monitoring the environment and platform telemetry to validate the effectiveness of the changes and ensure systems continue to operate as expected.

We encourage all customers to verify that their macOS devices are online and reporting successfully following the deployment of this fix. While many devices should recover normally, some macOS agents may remain offline and will require additional remediation including manual intervention by the end users. To assist with this process, we have prepared a step-by-step guide that will help you confirm agent status, identify devices requiring further assistance, and walk you through the recommended recovery steps: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm

We appreciate your patience, understanding, and partnership while we worked to investigate and resolve these issues.

Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

The Kaseya R&D team has developed a fix and will be rolling out the update to the MacOS agents tonight and tomorrow. We will post a maintenance window for each platform prior to the update.

To assist with updating macOS agents and verifying they are updated correctly, we have prepared a step-by-step guide available here: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm

Until the update is out on your platform the behaviors described in our previous posts remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.
• We continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here after all deployments are completed, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

Our teams are continuing to work on a resolution.

The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here by 7:00 PM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

We have identified the cause of the issue affecting the connectivity of Datto RMM macOS agents. Our teams are now working on a resolution.

The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here by 11:00 AM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved after monitoring overnight. As previously stated, this issue was fixed in the security intelligence update version 1.459.450.0, and should no longer occur on device's with this definition version or later. Please see the earlier communication for further details.

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

The Kaseya R&D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.1.1 Datto RMM version's cagservice.exe in a recent security intelligence update for Microsoft Defender Antivirus and other Microsoft antimalware.

This issue was fixed in the security intelligence update version 1.459.450.0, and the issue should no longer occur on device's with this definition version or later. Microsoft currently does not offer an automated way to revert the quarantining of a file, therefore manual action is required to bring affected devices back online in Datto RMM.

We recommend our partners to ensure that devices are updated with security intelligence version 1.459.450.0 or later to avoid the agent being falsely flagged as malicious by Microsoft antimalware.

Users can use the below commands and instructions to ensure that the latest security intelligence update is installed on the device to prevent the behavior:
Updating the security intelligence version:

• PowerShell: Update-MpSignature
• Command Prompt (CMD): MpCmdRun.exe -SignatureUpdate

After running the update, users can verify the installed version with the following command:

• Get-MpComputerStatus | Select-Object AntivirusSignatureVersion, AntivirusSignatureLastUpdated

Our team remains actively engaged with Microsoft to investigate reports of false-positive detections occurring after devices were updated to Datto RMM Agent version 15.1.1 and to support remediation efforts where needed. At this time, the issue appears to be related to a security detection classification and not confirmed as malicious activity within the Datto RMM agent. We will continue to share updates as additional information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved.

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

We have identified an issue affecting status reporting between Datto EDR, Datto AV, and Datto RMM. As a result, some devices may incorrectly generate alerts in Datto RMM indicating that Datto EDR requires attention or that Datto AV is not installed.

Our investigation has confirmed that Datto EDR and Datto AV remain installed and functioning properly on affected endpoints. Endpoint protection services continue to operate as expected. The issue is limited to the status information being reported and displayed within Datto RMM and does not indicate a loss of protection or a failure of the Datto EDR or Datto AV products.

Engineering teams have identified the underlying cause and are actively working on a resolution. We will continue to provide updates as additional information becomes available.

If you have questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

The issue affecting Activity Log performance on the Vidal Platform following the 15.1 release has been resolved.

The Kaseya Engineering Team implemented a fix and has confirmed that Activity Logs are loading as expected after monitoring the platform to ensure ongoing stability and performance.

Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved.

At this time, jobs and activity logs remain stable, and no further issues have been observed however we will continue to monitor the environment overnight.

A fix has been implemented for the Jobs and Activity Log on the Vidal platform and we are monitoring the results.

Scheduled and Quick Job functionality is restored, and the Engineering team is continuing to work on resolving the problem causing issues with the Activity Log loading in accounts.

The Engineering team is currently investigating and resolving issues flagged by internal alerting that led to the Activity Log loading and Job execution issues resurfacing.

Thank you for your patience!

A fix has been implemented for the Activity Log on the Vidal platform. The service has recovered and we are monitoring the results.

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

We have identified an issue with the Activity Log failing to load.

The Kaseya R&D team are working on a fix for the issue.

The Job queue has been cleared and Activity Logs continue to load as expected. We are continuing to monitor for any further issues.

A fix has been implemented for Activity Logs and they should be loading as expected.

A fix has also been implemented for Jobs not running, but delays are still expected as the platform works through all queued jobs. We will continue to monitor this queue and resolve this status page once it has cleared.

We are continuing to investigate this issue.