Kaseya Outage History
Kaseya major outage · 2 active incidents View live status →Pingoru has recorded 157 incidents for Kaseya: 155 in the last 12 months and 88 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 12 | 695 of 720 (97%) |
| May 2026 | 20 | 697 of 744 (94%) |
| June 2026 | 15 | 695 of 720 (97%) |
| July 2026 | 29 | 690 of 744 (93%) |
| August 2026 | 26 | 719 of 744 (97%) |
| September 2026 | 37 | 584 of 720 (81%) |
| October 2026 | 14 | 579 of 594 (98%) |
Incidents, newest first
Major May 20, 2026 Datto RMM - v15.0 Cagservice.exe being flagged as malicious by Antivirus Software due to a Microsoft Defender Definition update misclassifying the executable 12d 11h
Started May 20, 2026, 10:51 PM UTC· resolved Jun 02, 2026, 10:29 AM UTC
- investigating May 20, 2026, 04:28 PM UTC
We are aware of a problem where the Datto RMM's "cagservice.exe" is being flagged as malicious by some antivirus software, causing it to be quarantined. 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/
- investigating May 20, 2026, 07:05 PM UTC
The RMM agent underwent an update, causing some devices with antivirus software, mainly Microsoft Defender for Endpoint, to alert on the update behavior and quarantine "cagservice.exe". This alert has been identified as a false positive. To prevent these alerts on Microsoft Defender for Endpoint for this new RMM agent, please follow these steps: 1. Go to the Security Portal 2. Go to Settings 3. Go to Endpoints 4. Under "Rules" click on "Indicators" 5. Under the file hashes, add the indicator with the SHA256 Hash: "91774f1195ba7042293bba1152afc334052d6c235a90e715f8c5c5fc8f27b089", and set the expiration to never, and the action to "Allow" 6. Allow time for the indicator to sync to endpoints. For more information on these steps, please see this Microsoft article: https://learn.microsoft.com/en-us/defender-endpoint/indicator-manage?source=recommendations The Kaseya R&D team is continuing to investigate this issue.
- investigating May 20, 2026, 10:51 PM UTC
In collaboration with Microsoft, an update has been made to Defender for Endpoint's security intelligence to prevent these false positive alerts on the cagservice.exe for devices running Microsoft's Defender for Endpoint. Devices running security intelligence version 1.451.15.0 and above have the updated detection logic. If you receive an alert for the cagservice.exe and your device is on version 1.451.150 and above, please reach out to our support team so we can continue to troubleshoot the issue. The Kaseya R&D Team is now investigating how to restore devices taken offline by the quarantine of the cagservice.exe.
- identified May 21, 2026, 09:35 AM UTC
The R&D team continues to work with Microsoft counterparts on a path to restore the erroneously quarantined assets, and restore RMM connectivity to affected devices.
- monitoring May 21, 2026, 03:40 PM UTC
The Kaseya R&D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.0 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.451.15.0, and the issue should no longer occur as long as the device is on 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.451.15.0 or later to avoid the v15.0 agent being falsely flagged as malicious by Microsoft antimalware. The 15.0 release deployment is scheduled to finish on the 1st June with the Pinotage (EU2) platform. 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
- resolved Jun 02, 2026, 10:29 AM UTC
With the general availability of the 15.0 release version of Datto RMM, we're resolving this informational post.
Minor May 20, 2026 Datto Workplace / Datto File Protection - US Cells - U.S. Based Agents Are Experiencing Connectivity failures, and Portal Access is Intermittently Unavailable 2h 4m
Started May 20, 2026, 03:53 PM UTC· resolved May 20, 2026, 05:57 PM UTC
- investigating May 20, 2026, 03:53 PM UTC
We are aware of a problem where U.S. based Datto Workplace and Datto File Protection agents can experience intermittent connectivity failures and degraded access to the Portal. The Kaseya R&D Team is currently investigating the issue and working towards a resolution. Please note: File access and file downloads can be obtained through the File Explorer option. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 20, 2026, 05:43 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 20, 2026, 05:57 PM UTC
This incident has been resolved.
Minor May 18, 2026 Datto SaaS Protection - Backup performance degradation for SharePoint/Teams services on pod 'des1-saas-p0' 2d 17h
Started May 18, 2026, 08:15 PM UTC· resolved May 21, 2026, 01:22 PM UTC
- identified May 18, 2026, 08:15 PM UTC
We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' may experience degraded SharePoint/Teams backup performance. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 18, 2026, 10:25 PM UTC
Our R&D team has implemented changes to address the SharePoint/Teams backup performance degradation affecting some customers on pod 'des1-saas-p0' and they are monitoring the results.
- monitoring May 19, 2026, 12:32 PM UTC
Backup success rate metrics for SharePoint/Teams services on pod 'des1-saas-p0' have returned to normal. Our R&D team is continuing to monitor.
- resolved May 21, 2026, 01:22 PM UTC
This incident has been resolved.
Minor May 18, 2026 Datto BCDR - Server3921 (US-East) - Degraded Node Functionality 21h 45m
Started May 18, 2026, 03:15 PM UTC· resolved May 19, 2026, 01:01 PM UTC
- identified May 18, 2026, 03:15 PM UTC
We are aware of a problem where BCDR users paired to Server3921 in the US-East region are experiencing degraded performance in offsite operations. 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/
- monitoring May 18, 2026, 07:46 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 19, 2026, 01:01 PM UTC
This incident has been resolved.
Major May 15, 2026 Datto Workplace - AU5 - Some files are unable to be accessed through local agents and the Workplace Online 3d 1h
Started May 15, 2026, 09:36 AM UTC· resolved May 18, 2026, 11:28 AM UTC
- investigating May 15, 2026, 09:36 AM UTC
The R&D Team is currently investigating the issue where users receive an error through the local agent or in Workplace Online when attempting to access certain files on the AU5 cell.
- monitoring May 15, 2026, 02:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 18, 2026, 11:28 AM UTC
This incident has been resolved.
Major May 11, 2026 Datto SaaS Protection - Service disruption for customers hosted on pod 'usw3-saas-p0' 1d 20h
Started May 11, 2026, 05:39 PM UTC· resolved May 13, 2026, 02:14 PM UTC
- investigating May 11, 2026, 05:39 PM UTC
We are aware of a problem where customers hosted on pod 'usw3-saas-p0' are experiencing a disruption to Backup and Recovery services for Datto SaaS Protection. The Kaseya R&D Team is actively Investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 11, 2026, 06:50 PM UTC
Our R&D team has implemented a fix to resolve the Backup and Recovery affecting customers on pod 'usw3-saas-p0' and are actively monitoring for any other issues.
- identified May 11, 2026, 10:11 PM UTC
Our R&D team has identified another issue affecting Backup and Recovery services for customers hosted on pod 'usw3-saas-p0' and are actively working to address it.
- monitoring May 11, 2026, 10:46 PM UTC
Our R&D team has resolved the issue and Backup and Recovery services are functioning normally again for customers on pod 'usw3-saas-p0'. We are continuing to monitor.
- monitoring May 12, 2026, 08:30 PM UTC
Backup success rates on pod 'usw3-saas-p0' remain stable at normal levels. Our R&D team is continuing to monitor.
- resolved May 13, 2026, 02:14 PM UTC
This incident has been resolved.
Critical May 11, 2026 SaaS Alerts Microsoft Manage Service Interruption 2d 8h
Started May 11, 2026, 05:42 AM UTC· resolved May 13, 2026, 01:51 PM UTC
- investigating May 11, 2026, 05:42 AM UTC
We are aware of the ongoing service interruption issue in SaaS Alerts Microsoft Manage Integration. Our team is investigating the issue and working towards a resolution.
- investigating May 11, 2026, 07:01 AM UTC
Kaseya R&D team is continuing to investigate the issue and working towards a resolution.
- investigating May 11, 2026, 10:30 AM UTC
Kaseya R&D team is continuing to investigate the issue and working towards a resolution.
- investigating May 11, 2026, 02:39 PM UTC
We are continuing to investigate this issue.
- identified May 11, 2026, 03:12 PM UTC
The issue has been identified. One of the endpoints from Microsoft is responding properly sometimes and others is throwing an error. We have implemented retry functionality for that endpoint and are clearing all errors. We will continue to work on this until all impacted Microsoft connections are stable.
- monitoring May 11, 2026, 06:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 13, 2026, 01:51 PM UTC
We have observed that the Microsoft endpoint is performing as expected. This incident is now closed.
Minor May 8, 2026 Datto Workplace / Datto File Protection - US Cells - SSO login is currently unavailable for users based in the United States 2d 20h
Started May 08, 2026, 04:12 PM UTC· resolved May 11, 2026, 12:47 PM UTC
- investigating May 08, 2026, 04:12 PM UTC
We are aware of a problem where a subset of US Datto Workplace and Datto File Protection users cannot login via Portal SSO. Agent login access remains unaffected, and users continue to have full access. The Kaseya R&D Team is investigating the issue and working towards a resolution. Workaround: Please ensure your local region is specified when utilizing direct login: EX: eu.workplace.datto.com EX: us.workplace.datto.com If assistance is needed, our Technical Support team can assist. Note: Users for most cells can login directly to Datto Workplace and Datto File Protection. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 08, 2026, 07:28 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 11, 2026, 12:47 PM UTC
This incident has been resolved.
Major May 5, 2026 Datto Workplace AU5 - Agents are unable to connect and sync data; files cannot be created and/or saved in Workplace Online 1d 4h
Started May 05, 2026, 08:27 AM UTC· resolved May 06, 2026, 12:45 PM UTC
- investigating May 05, 2026, 08:27 AM UTC
We are currently investigating an issue impacting partners on AU5 cell, where connections and data syncs are failing. Affected partners may see server errors in applications, no files appearing on the VFS agent, or connection failures on the V8 agent. At this time, other regions are not affected. Subscribe to the Kaseya Status Page for up to date information at https://status.kaseya.com/
- investigating May 05, 2026, 11:14 AM UTC
The R&D and Infrastructure teams are continuing to investigate the cause of the issue.
- monitoring May 05, 2026, 01:50 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 06, 2026, 12:45 PM UTC
This incident has been resolved.
Minor May 4, 2026 Datto Networking - Intermittent Check‑In Failures Observed on Datto Networking D200 Devices 1d 2h
Started May 04, 2026, 05:24 PM UTC· resolved May 05, 2026, 07:34 PM UTC
- investigating May 04, 2026, 05:24 PM UTC
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/
- monitoring May 05, 2026, 01:07 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2026, 07:34 PM UTC
This incident has been resolved.
Major May 4, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'Gbe2-saas-p0-app-2' 1d
Started May 04, 2026, 11:52 AM UTC· resolved May 05, 2026, 12:19 PM UTC
- investigating May 04, 2026, 11:52 AM UTC
We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection services. Backups are still operational, but the platform is unable to be accessed. The Kaseya R&D Team is investigating the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 04, 2026, 01:07 PM UTC
The Kaseya R&D team has implemented changes to help address the issue and are monitoring the results closely.
- resolved May 05, 2026, 12:19 PM UTC
This incident has been resolved.
Critical April 30, 2026 Datto SaaS Protection - Service disruption for customers hosted on pod 'cae1-saas-p1' 16h 52m
Started Apr 30, 2026, 10:31 PM UTC· resolved May 01, 2026, 03:24 PM UTC
- identified Apr 30, 2026, 10:31 PM UTC
We are aware of a problem where customers hosted on pod 'cae1-pod-1' are experiencing a disruption to their SaaS Protection services. Our R&D team is performing maintenance on pod 'cae1-pod-1' to resolve an issue that was identified. The estimated down time is up to 8 hours. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 01, 2026, 05:17 AM UTC
Our R&D team has implemented a fix to address the issue impacting the pod. We are actively monitoring the node for any other issues.
- monitoring May 01, 2026, 06:32 AM UTC
Backup success rates have improved since a fix has been implemented. Our R&D continues to monitor the health of the pod until expected levels are reached.
- monitoring May 01, 2026, 12:36 PM UTC
Backup success rates on the pod have returned to normal and remain stable. Our R&D team is continuing to monitor.
- resolved May 01, 2026, 03:24 PM UTC
This incident has been resolved.
Minor April 30, 2026 Datto SaaS Protection - Backup performance and access issues for customers hosted on node 'gbe2-bfyii-1225' 19h 54m
Started Apr 30, 2026, 04:38 PM UTC· resolved May 01, 2026, 12:33 PM UTC
- identified Apr 30, 2026, 04:38 PM UTC
We are aware of a problem where customers hosted on node 'gbe2-bfyii-1225' are experiencing degraded backup performance for SharePoint/Teams services as well as receiving 504 errors when attempting to access their SaaS Protection accounts. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Apr 30, 2026, 07:36 PM UTC
Our R&D team has implemented a fix to address the SaaS Protection account access issues and customers should no longer receive a 504 error when logging in. We are actively monitoring the node for any other issues.
- resolved May 01, 2026, 12:33 PM UTC
This incident has been resolved.
Minor April 29, 2026 Datto SaaS Protection - Backup performance degradation for M365 services on pod 'usw3-saas-p1' 22h 29m
Started Apr 29, 2026, 02:30 PM UTC· resolved Apr 30, 2026, 12:59 PM UTC
- identified Apr 29, 2026, 02:30 PM UTC
We are currently aware of a problem where some Datto SaaS Protection customers hosted on pod 'usw3-saas-p1' are experiencing degraded backup performance for some M365 services. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Apr 29, 2026, 04:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 30, 2026, 12:59 PM UTC
This incident has been resolved.
Major April 28, 2026 Datto RMM - Zinfandel - Agents going offline 10h 28m
Started Apr 28, 2026, 09:47 PM UTC· resolved Apr 29, 2026, 08:16 AM UTC
- investigating Apr 28, 2026, 09:47 PM UTC
We are aware of a problem where Datto RMM agents, within the Zinfandel platform going offline. The Kaseya R&D Team is aware and currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Apr 28, 2026, 10:15 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 29, 2026, 08:16 AM UTC
This incident has been resolved.
Minor April 28, 2026 Datto RMM - Zinfandel: Delayed Jobs 1h 18m
Started Apr 28, 2026, 04:12 PM UTC· resolved Apr 28, 2026, 05:31 PM UTC
- investigating Apr 28, 2026, 04:12 PM UTC
We are aware of a problem where Jobs on Datto RMM's Zinfandel platform are delayed 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/
- monitoring Apr 28, 2026, 04:36 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 28, 2026, 05:31 PM UTC
This incident has been resolved.
Minor April 28, 2026 VSA10 - Service Degradation for subset of VSA10-US customers 2d 9h
Started Apr 28, 2026, 03:10 PM UTC· resolved May 01, 2026, 12:58 AM UTC
- investigating Apr 28, 2026, 03:10 PM UTC
Subset of VSA10 US customers may be experiencing degraded performance intermittently, which may impact administrators ability to manage endpoints. We are aware of the issue and our team is actively working to resolve the same. We apologize for any inconvenience caused. - Cloud Operations Team
- monitoring Apr 29, 2026, 07:10 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 29, 2026, 07:59 AM UTC
We are continuing to monitor for any further issues.
- resolved May 01, 2026, 12:58 AM UTC
This incident has been resolved.
Major April 24, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-327' 26d 17h
Started Apr 24, 2026, 07:30 PM UTC· resolved May 21, 2026, 01:23 PM UTC
- investigating Apr 24, 2026, 01:20 PM UTC
We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection services. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Apr 24, 2026, 02:15 PM UTC
Our R&D team is continuing to address this issue.
- identified Apr 24, 2026, 07:30 PM UTC
Our R&D team is performing maintenance on node 'gbe2-bfyii-327' over the weekend to repair a hardware issue that was identified. There is still currently no ETA on when services will be fully restored. We will provide more updates from the team as they become available.
- identified Apr 27, 2026, 12:45 PM UTC
Maintenance on node 'gbe2-bfyii-327' is still in progress. We will continue to provide updates as they become available.
- identified Apr 29, 2026, 02:00 PM UTC
Maintenance is still in progress to address a hardware issue found on node 'gbe2-bfyii-327'. We will continue to provide updates from the team as the maintenance progresses.
- monitoring May 01, 2026, 12:29 PM UTC
Maintenance on node 'gbe2-bfyii-327' has been completed and the node is back online. All customer accounts are accessible and backups are running. Our R&D team is continuing to monitor.
- identified May 08, 2026, 04:22 PM UTC
Our R&D team is aware of some customers hosted on node 'gbe2-bfyii-327' experiencing backup performance issues after the maintenance was completed and the team is working to address it.
- identified May 13, 2026, 05:50 PM UTC
Customer accounts hosted on node 'gbe2-bfyii-327' remain functional and our R&D team is continuing to address the backup performance issues affecting some services.
- identified May 14, 2026, 07:30 PM UTC
Our R&D team is continuing to address the backup performance issues affecting a small subset of customer's services on the node and backup success rates are improving.
- monitoring May 19, 2026, 04:13 PM UTC
Our R&D team has implemented changes to address the backup issues affecting a small subset of customer's services on node 'gbe2-bfyii-327' and will be monitoring for any other issues.
- monitoring May 19, 2026, 08:25 PM UTC
Backup success rate metrics for node 'gbe2-bfyii-327' have returned to normal levels. Our R&D team is continuing to monitor.
- resolved May 21, 2026, 01:23 PM UTC
This incident has been resolved.
Major April 23, 2026 VSA9 - Partial Service Disruption - liveconnect.me 4h 55m VSA 9
Started Apr 23, 2026, 03:58 PM UTC· resolved Apr 23, 2026, 08:54 PM UTC
- investigating Apr 23, 2026, 03:58 PM UTC
We are currently experiencing a partial service disruption affecting a subset of customers using VSA9 LiveConnect (liveconnect.me). Customers may notice issues accessing LiveConnect on-demand services. Our team is working to restore the functionality on the affected instances at this time. We apologize for any inconvenience. - Cloud Operations Team
- monitoring Apr 23, 2026, 08:00 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 23, 2026, 08:00 PM UTC
We are continuing to monitor for any further issues.
- resolved Apr 23, 2026, 08:54 PM UTC
This incident has been resolved.
Minor April 22, 2026 Datto AV - Agent is unable to perform actions on MacOS devices 1d 22h Datto AV
Started Apr 22, 2026, 03:34 PM UTC· resolved Apr 24, 2026, 02:18 PM UTC
- investigating Apr 22, 2026, 03:34 PM UTC
We are aware of a problem where Datto AV is unable to perform any actions on a MacOS device. The Datto AV Team is currently investigating this issue and is working to deploy a hotfix to correct this behavior. This is our highest priority issue. Unfortunately, there is no workaround that can be applied at this time. Please contact support and they can provide further details as well as add your case to the investigation.
- identified Apr 22, 2026, 06:01 PM UTC
We have identified the root cause of the issue affecting Datto AV actions on macOS devices and are currently validating the fix. Our team plans to deploy this update during the scheduled US maintenance window at 23:00 CST tonight and will actively monitor the rollout to ensure stability. We will provide confirmation once the release is completed and fully validated. We appreciate your patience as we work to fully resolve this issue.
- identified Apr 22, 2026, 07:51 PM UTC
We have identified the root cause of the issue affecting Datto AV actions on macOS devices and are continuing validation of the fix. During final testing, we identified an additional issue that needs to be addressed before release. As a result, we are postponing the deployment and now plan to target the next maintenance window tomorrow (April 23rd). We appreciate your patience as we work to fully resolve this issue.
- resolved Apr 24, 2026, 02:18 PM UTC
This incident has been resolved. Once the devices receive the update, during the maintenance window, they will need to be rebooted for the update to be applied.
Notice April 20, 2026 Service Disruption - BMS US & UK 2h 6m
Started Apr 20, 2026, 03:14 PM UTC· resolved Apr 20, 2026, 05:20 PM UTC
- monitoring Apr 20, 2026, 03:14 PM UTC
We were experiencing service disruption for BMS US and UK from 10:15 AM ET. The services are back operational from 10:39 AM ET. We are currently monitoring this issue. We Apologize for any inconvenience caused. -Cloud Operations Team
- resolved Apr 20, 2026, 05:20 PM UTC
This incident has been resolved.
Notice April 17, 2026 Incident Update – Datto EDR Portal Access (US Region) 2d 23h
Started Apr 17, 2026, 02:36 PM UTC· resolved Apr 20, 2026, 02:06 PM UTC
- monitoring Apr 17, 2026, 02:36 PM UTC
We experienced a brief issue where some customers in the US region were unable to access the Datto EDR portal. This was due to a temporary service disruption that lasted a few minutes. The issue has been identified and resolved, and access is now restored. We are continuing to monitor the system to ensure stability. We apologize for the disruption and appreciate your patience.
- monitoring Apr 17, 2026, 06:12 PM UTC
We are continuing to monitor. Some partners may still experience a temporary error when attempting to log in or navigate the Datto EDR platform. While service may return to normal on its own after some time, please contact our support team and they can apply a backend workaround that may assist with resolving the issue.
- monitoring Apr 17, 2026, 08:10 PM UTC
Following our earlier update, we are continuing to monitor the environment and have identified additional infrastructure-related pressure contributing to intermittent latency. We are seeing elevated system load driven by increased telemetry and system activity, which can create short-lived performance impacts as services recover. Our team is actively implementing changes to reduce this load and stabilize the platform. We are taking a controlled approach to these changes to avoid further disruption, and performance is trending in the right direction. We will continue to provide updates as we make progress. Thank you again for your patience.
- monitoring Apr 17, 2026, 11:31 PM UTC
We have identified the primary contributor to the recent performance issues and have a mitigation in place that will be deployed during the upcoming maintenance window. The update reduces unnecessary system activity that was creating elevated load and impacting portal responsiveness. Once deployed, this is expected to significantly improve stability. We are also continuing work on additional infrastructure improvements to ensure the platform can handle increased load more efficiently and prevent recurrence. We will provide another update once the mitigation is fully deployed. Thank you for your continued patience.
- resolved Apr 20, 2026, 02:06 PM UTC
This incident has been resolved.
Major April 8, 2026 Datto Workplace - Latency Issues Affecting Users on US Cells 36d 5h
Started Apr 08, 2026, 02:12 PM UTC· resolved May 14, 2026, 07:50 PM UTC
- investigating Apr 01, 2026, 03:45 PM UTC
We are aware of a problem where Datto Workplace users are reporting elevated latency impacting multiple projects within the U.S. region. 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/
- investigating Apr 02, 2026, 01:02 PM UTC
We are continuing to investigate this issue.
- identified Apr 03, 2026, 01:32 PM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 03, 2026, 05:06 PM UTC
We have identified the root cause of the slow file downloads impacting large projects. The issue is isolated to the server side and does not impact data integrity. A corrective solution is currently under evaluation, and we anticipate providing an updated status early next week.
- identified Apr 08, 2026, 02:12 PM UTC
Our engineering team has provided a temporary solution to mitigate the latency issue affecting Datto Workplace. If you wish to implement this workaround, please contact our Technical Support team for assistance with its application.
- identified Apr 10, 2026, 02:58 PM UTC
The Kaseya R&D team continues to actively work toward resolving this issue. Please note that any latency impact is limited to VFS/V10 agents.
- identified Apr 15, 2026, 05:38 PM UTC
Our engineering team is continuing to investigate a permanent resolution.
- identified Apr 23, 2026, 08:28 PM UTC
Our engineering team is actively working on a permanent resolution. We’ll provide updates as progress continues.
- resolved May 14, 2026, 07:50 PM UTC
This incident has been resolved.
Minor March 24, 2026 Datto BCDR - Local Virtualization and Verification Will Not Execute Successfully on Windows 2003 and Windows XP 32‑bit Systems 50d 23h
Started Mar 24, 2026, 08:11 PM UTC· resolved May 14, 2026, 07:41 PM UTC
- investigating Mar 24, 2026, 08:11 PM UTC
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.
- identified Mar 25, 2026, 04:24 PM UTC
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.
- resolved May 14, 2026, 07:41 PM UTC
We’re pleased to inform you that our Engineering team has released a fix that should resolve the problem where BCDR Agents operating on 32-bit versions of Windows Server 2003 and Windows XP are experiencing failures with screenshot verification, and local virtualization processes are not successfully initializing. If the problem is still occurring, please make sure your device is fully up to date on the latest OS version. Please note, we have started to roll out the update to devices on 05/11/2026 and the release will complete for all devices by 05/28/2026. Thank you for your patience and understanding. We remain committed to delivering exceptional service and continuous improvement. Best regards,
Minor March 10, 2026 Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'des1-saas-p1' 126d 23h
Started Mar 10, 2026, 03:29 PM UTC· resolved Jul 15, 2026, 03:02 PM UTC
- identified Mar 10, 2026, 03:29 PM UTC
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 Page for up-to-date information at https://status.kaseya.com/
- monitoring Mar 10, 2026, 07:28 PM UTC
The Kaseya R&D team has implemented additional changes to help address the issue and are monitoring the results closely.
- identified Mar 11, 2026, 03:08 PM UTC
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'.
- identified Mar 11, 2026, 04:52 PM UTC
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 Mar 11, 2026, 08:27 PM UTC
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 enhancements continue.
- identified Mar 12, 2026, 11:26 AM UTC
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 Mar 12, 2026, 08:01 PM UTC
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 Mar 13, 2026, 04:03 PM UTC
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 Mar 16, 2026, 06:35 PM UTC
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.
- monitoring Mar 18, 2026, 07:32 PM UTC
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.
- monitoring Mar 25, 2026, 07:55 PM UTC
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 Apr 17, 2026, 02:03 PM UTC
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 Apr 20, 2026, 12:47 PM UTC
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 May 14, 2026, 07:24 PM UTC
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 Jun 15, 2026, 03:27 PM UTC
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 Jul 02, 2026, 06:31 PM UTC
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.
- resolved Jul 15, 2026, 03:02 PM UTC
This incident has been resolved.