We are aware of a problem where Kaseya Quote Manager users get a 504 Azure Front Door error, and potential slowness if able to access KQM.
The Kaseya Engineering Team is currently 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/
ConnectBooster - Intermittent Sync and Access issues
A fix has been implemented and we are monitoring the results.
identified
We are aware of a problem where some users are experiencing intermittent sync and access issues within their ConnectBooster portals.
The Kaseya Engineering Team have Identified the issue are are working on a fix.
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 - Syrah/Vidal - Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint.
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
investigating
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/
investigating
We are aware of a problem where Datto RMM's 15.1.1 Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint.
The Kaseya Engineering Team is investigating this issue with Microsoft.
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/
Autotask - All Regions - LiveMobile inaccessible on Android Devices, https://autotask.net Certificate Error, and Datto RMM Integration Errors
Limited ReleaseAmerica EastAmerica East 2America East 3America WestAmerica West 2America West 3Australia / New Zealand 4UK Limited Release (United Kingdom)UK (United Kingdom)UK 2 (United Kingdom)UK03 (United Kingdom)EU1 (English Europe and Asia)Australia / New ZealandAustralia / New Zealand 2Australia/ New Zealand 3 (Sydney Datacenter)German (Deutsch)Spanish (Español)Report Data WarehouseAT01
monitoring
Monitoring post release detected an issue with the Autotask and Datto RMM integration.
This issue caused tickets to fail to create from Datto RMM, prevented access to the Autotask integration settings in Datto RMM, and prevented new monitor creation in Datto RMM when the option to "Create a Ticket" was set.
A new fix has been deployed to correct these issues and we will continue to monitor the results.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
When logging into Autotask on the web, to ensure the best connectivity to your Autotask instance, please double check your configuration to ensure that the zone specific (ww# or ww##) URL is being used.
investigating
We are aware of a problem where LiveMobile is inaccessible on Android devices across all regions.
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 - Quotes and Sales Orders Not Syncing to Autotask or ConnectWise
A fix has been implemented and we are monitoring the results.
identified
The Engineering Team identified the issue that caused the sync requests for both the Autotask PSA and ConnectWise PSA integrations to queue up.
Mitigation measures have been applied to increase the throughput to help with processing the queue.
investigating
We are aware of a problem where Quotes and Sales Orders created in Kaseya Quote Manager are not syncing over to Autotask.
The Kaseya Engineering Team are aware of the issue and are currently investigating further.
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/
Autotask PSA - UK01, UK02, UK03, EU1, DE1 - Latency and Errors Observed Within the UI
UK (United Kingdom)UK 2 (United Kingdom)UK03 (United Kingdom)EU1 (English Europe and Asia)German (Deutsch)
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 latency and error messages are being observed when navigating the Autotask UI.
The Kaseya Engineering Team is aware of this behaviour and is currently investigating.
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/
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where RocketCyber users, who attempt to switch Organizations are encountering the following error, preventing users from being able to switch Organizations:
Access Blocked
[Organization name] does not have SSO enabled for this KaseyaOne Tenant
To access this account, login directly at https://app.rocketcyber.com(US) or https://eu.rocketcyber.com(EU)
RocketCyber's monitoring capabilities are unaffected and will continue to gather and send data to the RocketCyber platform.
The Kaseya R&D Team is currently investigating and we will provide an update as soon as we have more information.
We are aware of a problem where Server4715 is undergoing unscheduled maintenance.
The Kaseya Engineering Team has identified the problem and are replacing faulted hardware. During this time offsite synchronization and virtual machine performance will be impacted.
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 - 500 Error When Accessing SaaS Protection Status Page in Datto Partner Portal
A fix has been implemented and we are monitoring the results.
identified
The system is recovering after the R&D team took steps to resolve the issue.
Some customer may still experience issues accessing the SaaS Protection Status Page while the system is recovering.
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 SaaS Protection Partners were receiving a 500 error when attempting to access the SaaS Protection Status Page within the Datto Partner Portal.
The Kaseya Engineering Team has been involved and they are investigating the issue.
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto BCDR users associated with Server5465 may experience disruptions affecting offsite synchronization and offsite restore operations.
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/
Legacy Incident Archive
95 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.
April 2026
Datto RMM - All Platforms - RMM Agent cannot be installed due to Certificate errors
majorSource 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 continuing to investigate this issue.
investigating
We are aware of a problem where the Datto RMM agent cannot be installed due to Certificate errors.
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/
Datto AV – Behavioral Detection Update
Source not attested
Last archived state: resolved
View archived record details
identified
A fix has been developed and this will be released tonight, after 12am(EST) and applied during your next set maintenance window.
identified
We are aware of a low-frequency issue where certain legitimate files may be unexpectedly quarantined by a behavioral detection component.
What’s happening
In rare cases, a behavioral detection module may briefly activate during endpoint startup before policy settings are fully applied. During this short window, files that would normally be allowed may be flagged and quarantined.
Customer impact
Low probability, but non-zero
Quarantined files may not generate alerts in the console
Files can...
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto RMM filters on the Vidal platform are failing to load with an "Out of sort memory" error message.
The Kaseya R&D Team is investigating the issue.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto BCDR - Local Virtualization and Verification Will Not Execute Successfully on Windows 2003 and Windows XP 32‑bit Systems
minorSource not attested
Last archived state: resolved
View archived record details
identified
Our R&D team has identified the underlying issue and is actively working toward a targeted resolution.
The deployment window is projected to commence upon completion of the current major device release.
In the interim, please utilize cloud‑based virtualization services to ensure continued operational continuity in the event of a Disaster Recovery scenario.
Please note: This issue is currently impacting only a limited subset of the Datto Windows Agent fleet.
investigating
We have identified an issue introduced in the latest device software release related to agents running 32 bit versions of Windows Server 2003 and Windows XP where screenshot verification and local virtualization fails to start.
We are currently investigating the issue to determine the cause and potential fix.
In the meantime, we have verified that cloud virtualizations are still functional for any DR scenarios. We will provide more information as it becomes available.
Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'des1-saas-p1'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Backup cadence on pod 'des1-saas-p1' remains at the normal 3x daily backups and our R&D team has deployed additional improvements to further address the issue. They are continuing to closely monitor backup performance of all services on the pod.
monitoring
Our R&D team has increased the daily backup cadence on pod 'des1-saas-p1' from 2x daily backups to 3x daily backups and they are actively monitoring backup performance of all services on the pod.
monitoring
The backup cadence on pod 'des1‑saas‑p1' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. R&D is continuing to develop improvements, targeted for release Q2 2026. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.
monitoring
After monitoring over the weekend, all services are backing up normally at 2x backup per day again. Our R&D teams are continuing to develop and test improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
monitoring
We are aware of additional reports of backup performance degradation affecting SharePoint services on pod 'des1-saas-p1'. Our R&D team has implemented changes to address the issue and are monitoring.
monitoring
Daily backup cadence on pod ‘des1‑saas‑p1’ remains temporarily set to 2x backups per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Our R&D teams are actively developing and testing improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
monitoring
Backup frequency on this pod is still set to 2x backups per day to maintain high backup success rates while the R&D team continues to develop and test improvements to address the issue. The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod. Backup success rates remain stable and the R&D team is continuing to monitor.
identified
Backups remain stable at 2x backups per day and our R&D team is continuing to monitor closely. The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod.
identified
Backups continue to process normally at 2x backups per day and success rates remain stable. Our R&D team will continue to monitor backup performance on the pod closely over the weekend as they prepare to increase backup frequency to 3x backups per day early next week.
identified
Backup frequency on the pod was increased to 2 backups per day again and our R&D team is monitoring closely as backup success rates continue to improve.
identified
The R&D team has successfully restored pod stability, and backups are now processing in real time.
They are working to resume the schedule of two backups per day, beginning with the next backup window.
Additional capacity is also being added to maintain continued pod stability, and to enable increasing the backup cadence to 3 backups per day in the near future.
identified
Recent changes made to improve SharePoint and Teams backup performance did not produce the expected results. Our R&D team will be implementing additional mitigation measures over the next 24 hours to further stabilize SharePoint and Teams backups for customers on the pod. As part of this work, we will be temporarily reducing backup frequency for customers from 2x backups per day to 1x backups per day. These adjustments are intended to improve overall system reliability while long‑term enhan...
identified
Issues affecting Teams backup performance have been identified and our R&D team is continuing to address the underlying problem affecting SharePoint/Teams backup performance for some customers hosted on the pod.
identified
After the changes implemented yesterday, the Kaseya R&D team is working to deploy additional improvements to further address the degraded backup performance affecting some customers hosted on pod 'des1-saas-p1'.
monitoring
The Kaseya R&D team has implemented additional changes to help address the issue and are monitoring the results closely.
identified
We are aware of a problem where some customers hosted on pod 'des1-saas-p1' are experiencing backup performance degradation for some SharePoint services.
The Kaseya R&D Team has identified the issue and are actively working to resolve it.
In the meantime, the R&D team has temporarily decreased the daily backup frequency on pod 'des1-saas-p1' from 3x per day to 2x per day to help maintain high backup success rates amidst ongoing spikes in Microsoft throttling.
Subscribe to the Kaseya Status...
