Datto Outage History

Started May 18, 2026, 03:15 PM UTC· resolved May 19, 2026, 01:01 PM UTC

1. 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/

2. monitoring May 18, 2026, 07:46 PM UTC

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

3. resolved May 19, 2026, 01:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2026, 09:36 AM UTC· resolved May 18, 2026, 11:28 AM UTC

1. 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.

2. monitoring May 15, 2026, 02:08 PM UTC

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

3. resolved May 18, 2026, 11:28 AM UTC

   This incident has been resolved.

4. postmortem Jul 09, 2026, 04:02 PM UTC

   **Datto Workplace - AU5 - Some Files Are Unable to be Accessed Through Local Agents and Workplace Online** **Summary:** Between May 5, 2026 at 08:00 AM UTC and May 18, 2026 at 11:28 AM UTC, some Datto Workplace customers hosted in the AU5 environment experienced issues accessing files. During the affected period, users experienced errors when attempting to access specific files hosted within the AU5 cell through either the local agent or Workplace Online. Additionally, intermittent connectivity disruptions occurred throughout the incident, resulting in periods of degraded service availability and access interruptions. **Root Cause:** The issue was caused by an outdated component that unintentionally remained in use following a recent service update. Over time, this component experienced degraded performance and eventually became unavailable, which disrupted connectivity for some users. Once identified, our engineering team promptly removed the outdated component and restored normal service. Connectivity was fully recovered on May 18, 2026, at 11:28 AM UTC. **Incident Timeline:** * Identified: **2026-05-05 08:00 AM UTC** * Public Notification: **2026-05-15 9:36 AM UTC** * Resolved: **2026-05-18 11:28 AM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * We are taking steps to ensure similar components are fully retired during future updates to prevent recurrence.

Read the full incident report →

Started May 11, 2026, 05:39 PM UTC· resolved May 13, 2026, 02:14 PM UTC

1. 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/

2. 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.

3. 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.

4. 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.

5. 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.

6. resolved May 13, 2026, 02:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 11, 2026, 05:42 AM UTC· resolved May 13, 2026, 01:51 PM UTC

1. 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.

2. investigating May 11, 2026, 07:01 AM UTC

   Kaseya R&D team is continuing to investigate the issue and working towards a resolution.

3. investigating May 11, 2026, 10:30 AM UTC

   Kaseya R&D team is continuing to investigate the issue and working towards a resolution.

4. investigating May 11, 2026, 02:39 PM UTC

   We are continuing to investigate this issue.

5. 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.

6. monitoring May 11, 2026, 06:09 PM UTC

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

7. resolved May 13, 2026, 01:51 PM UTC

   We have observed that the Microsoft endpoint is performing as expected. This incident is now closed.

Read the full incident report →

Started May 08, 2026, 04:12 PM UTC· resolved May 11, 2026, 12:47 PM UTC

1. 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/

2. monitoring May 08, 2026, 07:28 PM UTC

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

3. resolved May 11, 2026, 12:47 PM UTC

   This incident has been resolved.

4. postmortem Jun 12, 2026, 05:49 PM UTC

   **Datto Workplace - US Users Unable to Log In via** [**workplace.datto.com**](http://workplace.datto.com) **– 2026-05-08** **Summary:** Between 2026**-05-08 08:48 AM UTC** and 2026**-05-08 07:28 PM UTC**, Datto Workplace customers **in the US region could not login via Datto Partner Portal SSO.** **Root Cause:** During the incident, a portion of checkout requests experienced errors, leading to a service disruption that primarily impacted users in the United States. To restore service, our teams performed a rebuild of the affected infrastructure components, which successfully resolved the issue. **Incident Timeline:** * Identified: 2026-05-08 08:48 AM UTC * Public Notification: 2026-05-08 04:12 PM UTC * Resolved: 2026-05-08 07:28 PM UTC **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * We have strengthened our drive replacement process to improve early detection and accelerate resolution, helping ensure a more reliable and consistent customer experience.

Read the full incident report →

Started May 05, 2026, 08:27 AM UTC· resolved May 06, 2026, 12:45 PM UTC

1. 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/

2. investigating May 05, 2026, 11:14 AM UTC

   The R&D and Infrastructure teams are continuing to investigate the cause of the issue.

3. monitoring May 05, 2026, 01:50 PM UTC

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

4. resolved May 06, 2026, 12:45 PM UTC

   This incident has been resolved.

5. postmortem Jun 25, 2026, 03:43 PM UTC

   **Datto Workplace - AU5 Clients agents are getting a "Server error" and is failing to connect to the cloud – 2026-05-05** **Summary:** Between May 5, 2026 at 08:00 UTC and May 6, 2026 at 09:30 PM UTC, some Datto Workplace customers hosted in the AU5 environment experienced issues accessing files. During this time, users may have seen a “Server error” message when using the Workplace desktop agent or Workplace Online, preventing access to certain files stored in the cloud. **Root Cause:** The issue was caused by an outdated component that unintentionally remained in use following a recent service update. Over time, this component experienced degraded performance and eventually became unavailable, which disrupted connectivity for some users. Once identified, our engineering team promptly removed the outdated component and restored normal service. Connectivity was fully recovered on May 6, 2026, at 09:30 PM UTC. **Incident Timeline:** * Identified: **2026-05-05 08:00 AM UTC** * Public Notification: **2026-05-05 9:27 PM UTC** * Resolved: **2026-05-06 09:30 PM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * We are taking steps to ensure similar components are fully retired during future updates to prevent recurrence.

Read the full incident report →

Started May 04, 2026, 05:24 PM UTC· resolved May 05, 2026, 07:34 PM UTC

1. investigating May 04, 2026, 05:24 PM UTC

   We are aware of a problem where Datto Networking D200 devices can fail to successfully check-in. 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/

2. monitoring May 05, 2026, 01:07 PM UTC

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

3. resolved May 05, 2026, 07:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 04, 2026, 11:52 AM UTC· resolved May 05, 2026, 12:19 PM UTC

1. 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/

2. 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.

3. resolved May 05, 2026, 12:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 10:31 PM UTC· resolved May 01, 2026, 03:24 PM UTC

1. 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/

2. 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.

3. 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.

4. 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.

5. resolved May 01, 2026, 03:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 04:38 PM UTC· resolved May 01, 2026, 12:33 PM UTC

1. 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/

2. 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.

3. resolved May 01, 2026, 12:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 29, 2026, 02:30 PM UTC· resolved Apr 30, 2026, 12:59 PM UTC

1. 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/

2. monitoring Apr 29, 2026, 04:37 PM UTC

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

3. resolved Apr 30, 2026, 12:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 28, 2026, 09:47 PM UTC· resolved Apr 29, 2026, 08:16 AM UTC

1. 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/

2. monitoring Apr 28, 2026, 10:15 PM UTC

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

3. resolved Apr 29, 2026, 08:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 28, 2026, 04:12 PM UTC· resolved Apr 28, 2026, 05:31 PM UTC

1. 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/

2. monitoring Apr 28, 2026, 04:36 PM UTC

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

3. resolved Apr 28, 2026, 05:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 28, 2026, 03:10 PM UTC· resolved May 01, 2026, 12:58 AM UTC

1. 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

2. monitoring Apr 29, 2026, 07:10 AM UTC

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

3. monitoring Apr 29, 2026, 07:59 AM UTC

   We are continuing to monitor for any further issues.

4. resolved May 01, 2026, 12:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 24, 2026, 07:30 PM UTC· resolved May 21, 2026, 01:23 PM UTC

1. 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/

2. identified Apr 24, 2026, 02:15 PM UTC

   Our R&D team is continuing to address this issue.

3. 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.

4. 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.

5. 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.

6. 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 functioning normally again. Our R&D team is continuing to monitor.

7. 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.

8. 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.

9. 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.

10. 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.

11. 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.

12. resolved May 21, 2026, 01:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Apr 23, 2026, 03:58 PM UTC· resolved Apr 23, 2026, 08:54 PM UTC

1. 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

2. monitoring Apr 23, 2026, 08:00 PM UTC

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

3. monitoring Apr 23, 2026, 08:00 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Apr 23, 2026, 08:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 03:34 PM UTC· resolved Apr 24, 2026, 02:18 PM UTC

1. 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.

2. 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.

3. 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.

4. 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.

Read the full incident report →

Started Apr 20, 2026, 03:14 PM UTC· resolved Apr 20, 2026, 05:20 PM UTC

1. 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

2. resolved Apr 20, 2026, 05:20 PM UTC

   This incident has been resolved.

3. postmortem Apr 22, 2026, 02:09 PM UTC

   **Summary:** Between 2026-04-20 14:15 UTC and 2026-04-20 14:39 UTC, some US and UK customers could not access their BMS portals due to a timeout error. **Root Cause:** An unexpected infrastructure event caused a subset of backend systems supporting the BMS portal to become temporarily unavailable. This resulted in timeout errors for some users in the US and UK while accessing the service. **Incident Timeline:** * Identified: 2026-04-20 14:20 UTC * Resolved: 2026-04-20 14:39 UTC * Backfill post to the Status Page: 2026-04-20 15:14 UTC **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: **Strengthened Change Management:** * Additional validation steps will be required to confirm maintenance timing and scope before any changes that could affect production systems. **Improved Monitoring and Alerting:** * Expanded monitoring to more quickly detect unexpected system restarts or availability issues. * Enhanced alerts to ensure faster awareness and response when critical systems are impacted. **Operational Readiness Improvements:** * Updated internal procedures and runbooks to support faster recovery during infrastructure-related incidents. * Regular reviews of incident response practices to ensure teams are prepared to handle similar scenarios efficiently.

Read the full incident report →

Started Apr 17, 2026, 02:36 PM UTC· resolved Apr 20, 2026, 02:06 PM UTC

1. 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.

2. 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.

3. 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.

4. 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.

5. resolved Apr 20, 2026, 02:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 15, 2026, 06:14 PM UTC· resolved Apr 16, 2026, 12:39 PM UTC

1. identified Apr 15, 2026, 06:14 PM UTC

   We are aware of a problem where Datto Workplace users will experience an issue where files become inaccessible following access, attributed to underlying latency conditions. 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/

2. monitoring Apr 15, 2026, 07:31 PM UTC

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

3. resolved Apr 16, 2026, 12:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 14, 2026, 03:27 PM UTC· resolved Apr 14, 2026, 05:11 PM UTC

1. investigating Apr 14, 2026, 03:27 PM UTC

   We are aware of a problem where a server Error message appearing when accessing quotes The Kaseya R&D Team is currently investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Apr 14, 2026, 04:27 PM UTC

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

3. resolved Apr 14, 2026, 05:11 PM UTC

   This incident has been resolved.

4. postmortem Apr 20, 2026, 06:00 PM UTC

   **Summary:** Between 2026-04-14 14:50 UTC and 2026-04-14 16:20 UTC, some customers experienced a “Server Error” while working with quotes. ‌ **Root Cause:** A recent configuration change led to unintended restrictions that interfered with normal request processing, resulting in intermittent errors for some customers. ‌ **Incident Timeline:** * Identified: 2026-04-14 14:55 UTC * Public Notification to the Status Page: 2026-04-14 15:27 UTC * Resolved: 2026-04-14 16:20 UTC ‌ **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: * Improving system monitoring and alerting to more quickly detect abnormal traffic patterns and service disruptions. * Refining our change management practices to further validate configuration updates before they are fully applied in production environments.

Read the full incident report →

Started Apr 14, 2026, 01:10 AM UTC· resolved Apr 14, 2026, 01:33 AM UTC

1. investigating Apr 14, 2026, 01:10 AM UTC

   We are aware of a problem where a subset of Datto BCDR devices cannot be accessed remotely through Relay via the UI or CLI, even though affected devices may still be checking in normally. The Kaseya R&D Team is currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com

2. investigating Apr 14, 2026, 01:11 AM UTC

   We are continuing to investigate this issue.

3. resolved Apr 14, 2026, 01:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 10, 2026, 08:57 AM UTC· resolved Apr 15, 2026, 08:16 AM UTC

1. investigating Apr 10, 2026, 08:57 AM UTC

   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

2. monitoring Apr 10, 2026, 09:43 AM UTC

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

3. monitoring Apr 10, 2026, 10:23 AM UTC

   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

4. identified Apr 10, 2026, 04:54 PM UTC

   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

5. monitoring Apr 10, 2026, 09:29 PM UTC

   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.

6. resolved Apr 15, 2026, 08:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 10, 2026, 07:56 AM UTC· resolved Apr 10, 2026, 03:12 PM UTC

1. investigating Apr 10, 2026, 07:56 AM UTC

   We are aware of an issue where Datto Endpoint Backup for PC users paired with Cloud Siris 'use1-dtc-server-328263' may experience degraded performance, which can result in slower-than-average backup and restore speeds. 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/

2. monitoring Apr 10, 2026, 01:42 PM UTC

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

3. resolved Apr 10, 2026, 03:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 10, 2026, 03:46 AM UTC· resolved Apr 10, 2026, 10:23 AM UTC

1. investigating Apr 10, 2026, 03:46 AM UTC

   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

2. investigating Apr 10, 2026, 06:20 AM UTC

   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

3. monitoring Apr 10, 2026, 08:38 AM UTC

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

4. monitoring Apr 10, 2026, 08:39 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Apr 10, 2026, 10:23 AM UTC

   This incident has been resolved.

Read the full incident report →