DattoRMM - All Platforms - MacOS Agent Connectivity Issues

Incident Report for Kaseya Inc

Postmortem

Root Cause Analysis: Datto RMM macOS Agent and Web Remote Availability 

Summary

From October 2, 2026, at 08:53 UTC to October 21, 2026, at 18:13 UTC, customers experienced issues with the Datto RMM macOS agent and Web Remote. New macOS agent installations would fail. Some existing agents went offline after a device or agent service restart. Devices that went offline required the agent to be reinstalled, and macOS permissions to be re-authorized. Web Remote connectivity to macOS devices was also affected. 

We resolved the issue by re-signing the affected components with a valid code-signing certificate and deploying them to production. A follow-up agent update then moved the remaining devices to the newly signed components, fully restoring service. 

Root Cause

The certificate used to sign the macOS agent and Web Remote components was revoked after the associated account expired. macOS checks this certificate when an app is installed or launched, so the revocation blocked new installations and prevented some existing agents from restarting. 

In addition, the first re-signed build kept the same version number as the previous one, so devices already on that version did not automatically receive it. A further update was needed to complete the rollout. 

Preventative Measures 

  • Account and certificate management: Centralized tracking of developer accounts and signing certificates, with primary and backup owners and renewal tracking. 

  • Monitoring and alerting: Expiration alerts at set intervals, routine checks of production binary signatures, and scheduled tests confirming the macOS agent installs and launches successfully. 

  • Update practices: Builds with a new signing certificate will get a new version number, so online agents update automatically. Signatures will be validated before release. 

  • Recovery readiness: A documented, tested process for replacing signing certificates, including macOS permission profiles, MDM guidance, and options for devices that can’t update automatically. 

  • Incident response and resiliency: Faster validation when certificate or account issues are detected, and clearer incident communication

Posted Nov 16, 2026 - 15:27 EST

Resolved

The Kaseya R&D team has completed the deployment of Datto RMM agent version 15.1.4 across all platforms.

With the updated agent build now available across all platforms, we are marking this status page as Resolved. Some macOS agents may still require additional attention to complete the update or return to an online state.

Partners should review the help article referenced in the 15.1.4 release notes for guidance on identifying and remediating affected agents. If additional assistance is required after following the recommended steps, please contact Support.

Release notes: https://rmm.datto.com/help/en/Content/0HOME/ReleaseNotes/2026/ReleaseNotesDattoRMMv15.1.4.htm
Posted Oct 21, 2026 - 14:13 EDT

Update

The Kaseya R&D team will be releasing a new Datto RMM agent build across all platforms. This release includes a new agent version number, making it easier for partners distinguish between agents that have been updated and those that may still require attention.

Deployment of the updated agent build will follow the published platform maintenance schedule. We encourage partners to review the release notes for detailed deployment information, platform rollout timing, and guidance regarding the updated agent version.

Release notes: https://rmm.datto.com/help/en/Content/0HOME/ReleaseNotes/2026/ReleaseNotesDattoRMMv15.1.4.htm

We continue to actively monitor the rollout and its results across all platforms. Partners should verify that their devices remain online following the update. If any macOS devices remain offline or require additional remediation, please refer to the available guidance and contact Support if further assistance is needed.
Posted Oct 14, 2026 - 15:48 EDT

Monitoring

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
Posted Oct 04, 2026 - 09:31 EDT

Update

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/
Posted Oct 03, 2026 - 19:00 EDT

Update

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/
Posted Oct 03, 2026 - 11:08 EDT

Identified

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/
Posted Oct 02, 2026 - 17:58 EDT

Investigating

We are aware of a problem affecting the connectivity of Datto RMM macOS agents.

At this time, we have identified the following behaviors:

- Newly installed macOS agent installations are unable to establish connectivity.
- Existing macOS agents, that are currently in production environments, should remain online; however, our investigation is ongoing to determine whether additional scenarios may cause agents to go offline.
- Initial testing shows that if a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Our teams are actively investigating the root cause with Apple and working to develop a resolution. We will provide additional updates as more information becomes available.

Until further notice, we recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

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/
Posted Oct 02, 2026 - 14:16 EDT
This incident affected: Datto RMM (Pinotage (EU1), Merlot (EU2), Zinfandel (US West), Concord (US East), Syrah (APAC), Vidal (US East)).