Datto Outage History

Started Mar 06, 2026, 08:45 PM UTC· resolved Mar 06, 2026, 10:04 PM UTC

1. investigating Mar 06, 2026, 08:45 PM UTC

   We are aware of a problem where Jobs and Audits are experiencing delays on the Zinfandel Platform. The Kaseya R&D Team Investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Mar 06, 2026, 09:04 PM UTC

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

3. resolved Mar 06, 2026, 10:04 PM UTC

   This incident has been resolved.

4. postmortem Mar 18, 2026, 10:18 AM UTC

   **Summary** Around **2026-03-06 9:40 AM EST,** partners on the Zinfandel platform started experiencing delays in both Quick and Scheduled Job execution. The issue was initially mitigated by 12:00 PM EST; however, the steps taken to restore service inadvertently caused the problem to reoccur later that afternoon at approximately 2:13 PM EST. The R&D and Operations teams fully resolved the issue by 2:47 PM EST. **Root Cause and Resolution** The initial incident was triggered by an unusually large-scale alert resolution operation, which created a significant backlog of processing tasks within the database. The high volume of queued work caused processing times to exceed the allowable execution window. This resulted in repeated retries, which continually saturated the database and prevented other operations from running normally. To alleviate the load, the task scheduling service was scaled down, and the queuing services were recycled, which reduced database pressure and restored normal operation by approximately 12:00 PM EST. However, at around 2:13 PM EST, these earlier mitigation steps produced an unintended side effect: they constrained the throughput of the service responsible for processing device audits. This limitation caused additional downstream delays in Job execution across the platform. The service was subsequently scaled back up to full capacity, and all services were confirmed healthy by **2:47 PM EST**. **Preventative Measures** To reduce the likelihood and impact of similar incidents in the future, the following steps are being taken: * **Resolution of Related Product Issues:**` `The R&D team has identified a backend software defect that contributed to the incident. A fix is scheduled for the **14.9 release**. * **Enhanced Monitoring, Alerting, and Response:**` `The Kaseya R&D team is reviewing additional monitoring capabilities to provide deeper insight into application performance at the component level for key services. * **Improved Incident Management and Response:**` `Global Kaseya teams will continue to receive training and coaching on Incident Management playbooks to ensure that all internal stakeholders are promptly informed and take coordinated action when events occur.

Read the full incident report →

Started Mar 05, 2026, 02:05 PM UTC· resolved Mar 05, 2026, 08:09 PM UTC

1. identified Mar 05, 2026, 02:05 PM UTC

   We are aware of a problem currently affecting Restores and Exports for Datto SaaS Protection that requires the Restore/Export service to be temporarily disabled. The Kaseya R&D Team has identified the issue and are actively working on a fix. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Mar 05, 2026, 04:18 PM UTC

   The Kaseya R&D team is actively testing a fix for this issue. We will provide additional updates on progress as they become available.

3. identified Mar 05, 2026, 05:10 PM UTC

   Testing of the fix was successful for V3 customers in all regions. Restore/Export services should now be functioning normally again for all V3 customers. The Kaseya R&D team is now actively working to apply the fix and test for all V2 customers. We will continue to provide additional updates as they become available.

4. identified Mar 05, 2026, 06:15 PM UTC

   The Kaseya R&D team is continuing to work on applying the fix for customers hosted on V2 nodes in all regions. SaaS Protection services for customers hosted on V3 pods in all regions continue to function normally.

5. monitoring Mar 05, 2026, 07:35 PM UTC

   The Kaseya R&D team has successfully deployed the fix to all V2 nodes in all regions and Restores and Exports were re-enabled. Restores and Exports for customers in all regions are functioning normally again. We will continue to monitor for any other issues.

6. resolved Mar 05, 2026, 08:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2026, 02:33 AM UTC· resolved Mar 04, 2026, 06:27 PM UTC

1. investigating Mar 04, 2026, 02:33 AM UTC

   We are aware of a problem where SaaS Protection customers hosted on node 'usw3-pod-1' are experiencing backup degradation. 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. monitoring Mar 04, 2026, 01:40 PM UTC

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

3. resolved Mar 04, 2026, 06:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2026, 01:44 AM UTC· resolved Mar 04, 2026, 07:43 AM UTC

1. investigating Mar 04, 2026, 01:44 AM UTC

   We are investigating an issue impacting AU5 partners where some DWP Report Files are not opening in browser or agent. Other regions are not affected. 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. resolved Mar 04, 2026, 07:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 04:35 PM UTC· resolved Mar 06, 2026, 02:31 PM UTC

1. investigating Mar 02, 2026, 04:35 PM UTC

   We are aware of a problem where Datto BCDR users associated with Server3935 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/

2. identified Mar 02, 2026, 06:15 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Mar 06, 2026, 02:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 27, 2026, 04:53 PM UTC· resolved Feb 27, 2026, 09:08 PM UTC

1. investigating Feb 27, 2026, 04:53 PM UTC

   We are aware of a problem where SaaS Protection customers hosted on node 'use1-bfyii-2378' are currently unreachable and are receiving an error when attempting to access their accounts. 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. monitoring Feb 27, 2026, 05:53 PM UTC

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

3. resolved Feb 27, 2026, 09:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 06:09 PM UTC· resolved Mar 02, 2026, 02:21 PM UTC

1. identified Feb 26, 2026, 06:09 PM UTC

   We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'aue1-saas-p0' are currently experiencing degraded backup performance for SharePoint and Teams 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 Feb 27, 2026, 07:05 PM UTC

   The Kaseya R&D team have implemented configuration changes on the pod to address the issue. Sharepoint and Teams success rates are improving and the Kaseya R&D team is actively monitoring.

3. resolved Mar 02, 2026, 02:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 02:11 PM UTC· resolved Mar 05, 2026, 08:10 PM UTC

1. identified Feb 26, 2026, 02:11 PM UTC

   We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' are currently experiencing degraded backup performance for SharePoint and Teams 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 Feb 26, 2026, 05:36 PM UTC

   While the Kaseya R&D team continue to address the issue they have temporarily decreased the daily backup frequency on pod 'des1-saas-p0' from 2x per day to 1x per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. The Kaseya R&D team is closely monitoring success rates after the configuration change and will increase backup frequency to 2x backups per day when it is safe and reliable for all customers hosted on the pod.

3. monitoring Feb 27, 2026, 07:05 PM UTC

   The Kaseya R&D team have implemented additional configuration changes on the pod to address the issue further. Sharepoint and Teams success rates are improving and the Kaseya R&D team is actively monitoring.

4. monitoring Mar 02, 2026, 01:40 PM UTC

   SharePoint and Teams success rates on the pod have stabilized and the Kaseya R&D team has increased backup frequency back to 2x backups per day. We are continuing to monitor.

5. monitoring Mar 03, 2026, 01:46 PM UTC

   Backup success rates for Teams and SharePoint services on pod 'des1-saas-p0' have stabilized at 2x backups per day. The Kaseya R&D team is continuing to monitor.

6. resolved Mar 05, 2026, 08:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 08:42 AM UTC· resolved Feb 26, 2026, 02:58 PM UTC

1. identified Feb 26, 2026, 08:42 AM UTC

   We are currently experiencing service disruption for US - VSA136, 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

2. monitoring Feb 26, 2026, 10:24 AM UTC

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

3. resolved Feb 26, 2026, 02:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 22, 2026, 11:13 AM UTC· resolved Feb 22, 2026, 12:30 PM UTC

1. investigating Feb 22, 2026, 11:13 AM UTC

   We are experiencing Partial Service Disruption on Liveconnect.me. Our team is working to restore functionality at this time. We apologize for any inconvenience. - Cloud Operations Team

2. monitoring Feb 22, 2026, 11:42 AM UTC

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

3. resolved Feb 22, 2026, 12:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 17, 2026, 10:39 PM UTC· resolved Feb 20, 2026, 02:07 PM UTC

1. investigating Feb 17, 2026, 10:39 PM UTC

   We are aware of a problem where Datto BCDR users paired to server5856 can experience degraded offsite capabilities. 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 Feb 18, 2026, 02:52 PM UTC

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

3. resolved Feb 20, 2026, 02:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 17, 2026, 01:31 PM UTC· resolved Feb 18, 2026, 09:39 PM UTC

1. investigating Feb 17, 2026, 01:31 PM UTC

   We are currently experiencing an issue with push notifications not working as expected. Our team is actively investigating and working on a resolution. You can still Login to KaseyaOne using 2FA Authenticator app by selecting 'Try Another Way" on the Approve Log In Push MFA screen. Thank you for your patience—we’ll provide updates as soon as we have more information.

2. monitoring Feb 18, 2026, 08:25 AM UTC

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

3. resolved Feb 18, 2026, 09:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 16, 2026, 01:48 PM UTC· resolved Feb 25, 2026, 03:19 PM UTC

1. investigating Feb 16, 2026, 01:48 PM UTC

   We are aware of a problem where Datto BCDR users paired to server3445 can experience degraded offsite capabilities. 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. identified Feb 18, 2026, 07:04 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Feb 18, 2026, 07:26 PM UTC

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

4. resolved Feb 25, 2026, 03:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2026, 06:56 PM UTC· resolved Feb 25, 2026, 03:17 PM UTC

1. identified Feb 11, 2026, 06:56 PM UTC

   We are aware of a problem where the assignment of loopback DNS on local interfaces disrupts networking connections on version 2.1.0.0 of Datto Secure Edge. 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. investigating Feb 12, 2026, 03:18 AM UTC

   Our engineering team has identified the root cause and released a hotfix Windows client release (v2.1.1.0) addressing the DNS configuration issue identified in the prior release. The hotfix automatically detects and corrects affected DNS settings upon startup, restoring internet connectivity and DNS functionality. The updated client can be installed directly over the impacted version and includes all prior improvements and fixes from v2.1.0.0. While initial assessment suggested some impacted endpoints might remain reachable via RMM, further validation confirms that RMM agents typically lose connectivity shortly after DNS failure, limiting remote remediation options. Due to dependency on DNS resolution for standard deployment mechanisms, remote push/install via RMM is not expected to be viable in most cases. We are actively evaluating alternative distribution methods that would allow customers to manually download and install the hotfix without relying on DNS. Any additional methods identified will be published as an update to this status page. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

3. monitoring Feb 12, 2026, 03:22 AM UTC

   Our engineering team has identified the root cause and released a hotfix Windows client release (v2.1.1.0) addressing the DNS configuration issue identified in the prior release. The hotfix automatically detects and corrects affected DNS settings upon startup, restoring internet connectivity and DNS functionality. The updated client can be installed directly over the impacted version and includes all prior improvements and fixes from v2.1.0.0. While initial assessment suggested some impacted endpoints might remain reachable via RMM, further validation confirms that RMM agents typically lose connectivity shortly after DNS failure, limiting remote remediation options. Due to dependency on DNS resolution for standard deployment mechanisms, remote push/install via RMM is not expected to be viable in most cases. We are actively evaluating alternative distribution methods that would allow customers to manually download and install the hotfix without relying on DNS. Any additional methods identified will be published as an update to this status page. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

4. resolved Feb 25, 2026, 03:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 02, 2026, 02:15 PM UTC· resolved Feb 24, 2026, 02:19 PM UTC

1. identified Feb 02, 2026, 02:15 PM UTC

   We are aware of a problem where BCDR users paired to server3861 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/

2. monitoring Feb 10, 2026, 06:19 PM UTC

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

3. resolved Feb 24, 2026, 02:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 27, 2026, 09:10 PM UTC· resolved Feb 18, 2026, 02:42 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jul 14, 2025, 01:29 PM UTC· resolved Jul 15, 2026, 03:03 PM UTC

1. investigating Jul 14, 2025, 01:29 PM UTC

   We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' may experience degraded SharePoint backup performance. The Kaseya R&D Team is currently investigating this issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Jul 14, 2025, 04:59 PM UTC

   The Kaseya R&D team has identified the issue and are actively working to resolve it.

3. monitoring Jul 16, 2025, 12:43 PM UTC

   Configuration changes have been implemented to address the issue and SharePoint backups are stable. The Kaseya R&D team is monitoring.

4. monitoring Jul 17, 2025, 01:11 PM UTC

   While the Kaseya R&D team continues to address the issue they have temporarily decreased the daily backup frequency on pod 'des1-saas-p0' from 3x per day to 2x per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Backup completion percentages remain stable, and we’re monitoring the situation closely. We will continue to review conditions daily and will restore 3x backups per day as soon as it’s safe and reliable for all customers hosted on the pod.

5. monitoring Oct 30, 2025, 01:45 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.

6. monitoring Mar 25, 2026, 07:54 PM UTC

   Daily backup cadence on pod ‘des1‑saas‑p0’ 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.

7. monitoring May 14, 2026, 07:23 PM UTC

   The backup cadence on pod 'des1‑saas‑p0' 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.

8. monitoring Jun 15, 2026, 03:27 PM UTC

   Our R&D team has increased the daily backup cadence on pod 'des1-saas-p0' from 2x daily backups to 3x daily backups and they are actively monitoring backup performance of all services on the pod.

9. monitoring Jul 02, 2026, 06:31 PM UTC

   Backup cadence on pod 'des1-saas-p0' 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.

10. resolved Jul 15, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Started May 30, 2025, 02:16 PM UTC· resolved Jul 15, 2026, 03:03 PM UTC

1. investigating May 30, 2025, 02:16 PM UTC

   We are currently aware of a problem where some Datto SaaS Protection customers hosted on pod 'cae1-saas-p0' are experiencing degraded backup performance for Teams services. 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 Jun 02, 2025, 12:18 PM UTC

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

3. monitoring Jun 02, 2025, 08:36 PM UTC

   Backup success rates for Teams services have improved and our R&D team is continuing to monitor.

4. monitoring Jun 05, 2025, 03:22 PM UTC

   Additional configuration changes have been made on the affected pod to further address the Teams backup performance degradation. The Kaseya R&D team is monitoring results.

5. monitoring Jun 06, 2025, 08:00 PM UTC

   The Kaseya R&D team is actively investigating additional changes to be implemented to address the continued Teams backup performance degradation affecting some customers hosted on the pod.

6. monitoring Jun 09, 2025, 12:37 PM UTC

   Teams backup success rates have stabilized on the pod. The Kaseya R&D team is continuing to investigate additional changes to address the issue further.

7. monitoring Jun 10, 2025, 07:32 PM UTC

   Degraded backup performance for Teams services has again been observed for some customers hosted on the pod. While the Kaseya R&D team continues to investigate they will be temporarily decreasing the daily Teams backup frequency from 3x per day to 2x per day to allow the service to stabilize.

8. monitoring Jun 18, 2025, 03:46 PM UTC

   Teams backup success rates have stabilized after the recent changes that were implemented. The Kaseya R&D team is monitoring.

9. monitoring Jul 01, 2025, 09:01 PM UTC

   To maintain high backup success rates amidst ongoing spikes in Microsoft throttling, the SaaS Protection team is continuing with 2x backups per day. Backup completion percentages remain stable, and we’re monitoring the situation closely. We will continue to review conditions daily and will restore 3x backups per day as soon as it’s safe and reliable for all customers hosted on the pod.

10. monitoring Oct 30, 2025, 01:46 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.

11. monitoring Mar 25, 2026, 07:54 PM UTC

    Daily backup cadence on pod ‘cae1‑saas‑p0’ 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.

12. monitoring May 14, 2026, 07:22 PM UTC

    The backup cadence on pod 'cae1‑saas‑p0' 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.

13. monitoring Jun 26, 2026, 12:44 PM UTC

    Our R&D team has increased the daily backup cadence on pod 'cae1-saas-p0' from 2x daily backups to 3x daily backups and they are actively monitoring backup performance of all services on the pod.

14. monitoring Jul 02, 2026, 06:31 PM UTC

    Backup cadence on pod 'cae1-saas-p0' 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.

15. resolved Jul 15, 2026, 03:03 PM UTC

    This incident has been resolved.

Read the full incident report →