A third party vendor, ConnectWise, recently reported attempts of unauthorized access associated with the ConnectWise Cloud Backup environment. ConnectWise has initiated their incident response procedures, and have applied containment measures as they continue to investigate. At this time, according to ConnectWise there is no indication that ConnectWise partner backup data has been accessed. All additional updates related to this incident can be found on the ConnectWise Status Page at status.connectwise.com.
As part of our ongoing security monitoring efforts, the Kaseya Security Operations Center deployed additional detection measures on October 16, 2026, targeting publicly disclosed indicators of compromise. Activity matching these indicators is automatically designated as critical severity and promptly reviewed by our security analysts.
The Kaseya product team has also deployed a fortify action within SaaS Alerts and KSIEM environments to help mitigate this risk further. Please follow the steps below to apply the fortify action:
Action Name: Disable ConnectWise Cloud Backup and Cloud Management apps
Steps to Deploy within SaaS Alerts and KSIEM portal:
Within the left menu, under "Modules", select Fortify → Actions, then perform the following:
1. Set Select Product to Microsoft.
2. Set Select Organization to the customer's org (or leave it on All), and leave Select Actions on All.
3. Click Show Actions.
4. Search for Disable ConnectWise Cloud Backup and Cloud Management apps in the search box.
5. Under the action's buttons, click the wand icon labelled Apply.
If you feel you have been compromised due to this issue, please contact Kaseya support.
Datto Saas Protection- Partners Unable to Access Clients Hosted on Node isw1-bfyii-1134
The Kaseya R&D Team implemented a fix, and as a result, the clients hosted on the node are now accessible and full functionality is restored.
We are currently monitoring the health of the service and the progress with which the service is working through the queued backups.
The estimated time for full recovery is up to 8 hours.
investigating
We are aware of an issue where some Datto SaaS Protection Partners are unable to access customer accounts hosted on the isw1-bfyii-1134 node
The Kaseya Engineering Team is investigating the issue.
If you have any 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 the latest updates: https://status.kaseya.com/
Datto Workplace - AU5 - Agents/Portal are unable to connect
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where agents are unable to connect and portal users are unable to login in the AU region.
The Kaseya Engineering Team is currently investigating 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/
Datto Endpoint Backup for PC - Cloud Siris 296721 - US East - Degraded Cloud Operations
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto Endpoint Backup for PC users hosted on Cloud Siris 296721 in the US East region can experience degraded backup performance.
The Kaseya R&D Team is currently investigating the issue and working towards a resolution.
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/
DattoRMM - All Platforms - MacOS Agent Connectivity Issues
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.
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
identified
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/
identified
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/
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/
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/
Datto SaaS Protection - Service disruption for customers hosted on node 'aue1-bfyii-2213'
Our R&D team has resolved the issue and customers hosted on 'aue1-bfyii-2213' should now be accessible and accounts are functioning normally.
We are monitoring for any other issues.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where Datto SaaS Protection customers hosted on V2 node 'aue1-bfyii-2213' are experiencing a disruption to SaaS Protection services.
The Kaseya Engineering Team is currently investigating.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem in both BMS and Vorex where users are getting errors when generating batch invoices, using billing automations to send invoices, and issues using the "Post All" button when in the "Billing Review" stage.
The Kaseya Engineering Team is investigating the 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/
Kaseya Quote Manager - Intermittent Latency when navigating throughout the platform
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where users can experience extended latency when navigating throughout the Kaseya Quote Manager Platform.
The Kaseya Engineering Team are investigating the 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/
Following a recent platform update, some SaaS Protection environments across multiple regions experienced increased Microsoft 365 API throttling, resulting in backup performance degradation and delayed backup processing for a subset of customers. The underlying issue has been addressed, and backup success rates are already trending positively as affected environments work through the existing backlog. Performance is expected to continue improving as processing catches up, and Engineering teams are closely monitoring recovery efforts to ensure a return to normal operating levels for all customers.
monitoring
Backup success rates have largely returned to normal operating levels and remain stable across SaaS Protection environments. The vast majority of customer accounts are processing backups successfully, while ongoing optimization efforts continue to further improve consistency across the platform.
As part of these improvements, backup cadence has now been standardized across all Microsoft 365 workload types and environments to three backups per day.
Engineering teams will continue to monitor platform performance closely to ensure sustained stability and reliability.
monitoring
Backup success rates continue to trend positively and are returning to normal levels across SaaS Protection environments as additional post-Microsoft Graph migration improvements are deployed. Most customer accounts are now processing backups normally, and overall platform performance has continued to improve.
Engineering teams remain focused on implementing additional enhancements and monitoring performance closely to ensure continued improvements. We will provide further updates as progress continues.
monitoring
Backup success rates improved significantly over the weekend following the latest optimization efforts, and overall performance remains on a positive trend. The large majority of SaaS Protection customer accounts are processing backups normally, while engineering teams continue to implement additional post-Microsoft Graph migration improvements for environments that may still experience reduced backup performance across some Microsoft 365 services.
To help maintain high backup success rates as optimization efforts progress, backup cadence remains unchanged:
V2: All Microsoft 365 services back up three times daily.
V3: Exchange backs up three times daily; SharePoint, OneDrive, and Teams remain at one backup per day.
We will continue to monitor performance closely and provide further updates as additional improvements are implemented.
monitoring
Backup performance and success rates continue to improve as additional optimizations are deployed across Datto SaaS Protection environments. Current efforts are focused on further enhancing backup performance and reliability, including continued improvements to help mitigate the impact of Microsoft service throttling. Overall trends remain positive, and we expect continued improvements as optimization efforts progress.
Backup cadence remains unchanged:
V2: All Microsoft 365 services back up three times daily.
V3: Exchange backs up three times daily; SharePoint, OneDrive, and Teams remain at one backup per day while optimization efforts continue.
We will continue to monitor results closely and provide additional updates as further improvements are deployed.
monitoring
Microsoft Graph API migration has been completed across all Datto SaaS Protection environments, including customers utilizing in-place archive configurations. No further migration activities are expected to impact backup operations.
Some customers may continue to experience backup performance degradation while our engineering teams work to restore backup success rates to pre-migration levels. Multiple fixes and optimizations are being actively deployed across V2 and V3 environments, including improvements to Microsoft Graph API error handling and overall backup processing reliability. Teams continue to monitor the impact of each change as it is released.
Current Backup Cadence:
V2 environments: All Microsoft 365 services continue to back up three times per day.
V3 environments: Exchange continues to back up three times per day. SharePoint, OneDrive, and Teams remain on a reduced cadence of one backup per day while optimization efforts continue to maintain high backup success rates and mitigate Microsoft service throttling.
We do not currently have a fixed resolution date, as improvements are being delivered through ongoing remediation efforts rather than a single release. While performance is expected to continue improving, some customers may experience intermittent backup performance issues until all identified issues have been addressed. Based on current progress, we are cautiously optimistic that the remaining issues will be resolved over the coming days to weeks. We will continue providing updates as fixes are confirmed.
Customers who have not completed the required Microsoft 365 tenant reauthorization should follow the instructions here: https://saasprotection.datto.com/help/M365/Content/Troubleshooting/General/ews-to-graph.html
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/
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are currently experiencing service disruption for the below mentioned server, where administrators may be unable to login to UI.
Our team is actively working to restore functionality at this time.
We apologize for any inconvenience.
- Cloud Operations Team
Legacy Incident Archive
21 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
[INKY] - Email processing by INKY is being delayed
majorSource not attested
Last archived state: resolved
View archived record details
USEU
monitoring
Email delays are no longer being recorded and reported and we are monitoring the health of the service.
investigating
We are continuing to investigate the issue.
investigating
We have observed that the email processing by INKY is being delayed. We are aware of the issue and is being investigated
June 2026
Endpoint Backup v2 - A Subset of Endpoint Backup v2 Assets May Experience Backup Failures
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are aware of a problem where a subset of Endpoint Backup v2 assets can experience a backup failure due to error "system.ntfs_reparse_data: invalid argument".
The Kaseya R&D Team has identified the issue and is working towards a resolution.
In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237.
S...
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto Networking D200 devices may intermittently fail to check in, resulting in false‑positive offline email alerts.
Please note: The observed issue is cosmetic and does not affect the functionality or performance of the device.
The Kaseya R&D Team is investigating the issue and working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
April 2026
VSA10 - Degraded Performance - All regions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The root cause of the issue has been found. We believe that the issue will resolve itself as agents are allowed time to update.
If you are still experiencing issues performing Remote Takeovers, please contact our support team for help resolving the issue.
We will continue to monitor agent health and update here is the situation changes.
identified
We are still experiencing issues with subset of VSA10 customers unable to use Remote control feature. Our team is actively working to restore functionality on the affected instances.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
monitoring
Currently Application functionality for all the regions looks stable. We will continue to monitor the results and keep you posted accordingly.
We apologize for the inconvenience caused.
- Kaseya Cloud Operations Team
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Our team has identified an issue with the file transfer feature across all VSA10 regions. We are actively working to restore functionality on the affected instances.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
VSA10 - Partial Service Disruption - All regions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are experiencing issues with remote control on all VSA10 regions randomly, that may be resulting in impacting administrators ability to manage endpoints. Our team is working to restore functionality on the instance at this time.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
investigating
We are experiencing issues with remote control on APAC VSA10 that may be resulting in impacting administrators ability to manage endpoints. Our team is working to restore functionality on the instance at this time.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
Datto Backup for Microsoft Azure / Datto Endpoint Backup with Disaster Recovery - Devices Are Failing To Complete Registration
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where Datto Backup for Microsoft Azure and Datto Endpoint Backup with Disaster Recovery devices can experience registration failures.
The Kaseya R&D Team is currently investigating the issue and working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto RMM - Pinotage - Extended login times and login failures when attempting to access the UI
Source not attested
Last archived state: resolved
View archived record details
monitoring
The R&D team has identified and resolved the issue that was causing performance issues and failures when logging in to the UI on the Pinotage platform.
We are currently monitoring the health of the service.
A fix has been implemented and we are monitoring the results.
identified
We are aware of a problem where job execution is delayed on the Concord & Vidal platforms.
The Kaseya R&D Team have identified the issue and are working on implementing a fix.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Efforts to address the underlying issue remain in progress. Additional updates will be provided as they become available.
identified
The R&D team continues to actively work toward a resolution for this issue.
Additional information will be communicated as it becomes available.
identified
We are aware of a problem where BCDR assets paired to server1405 in the US-East region can experience degraded offsite performance.
The Kaseya R&D Team has identified the issue and is working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto RMM - Concord - Creating or saving Monitoring Policies fails with "could not execute statement" error
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Creating or saving Monitoring Policies fails with "could not execute statement" error.
The Kaseya R&D Team are investigating the issue.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
