Datto Outage History

Started Aug 26, 2026, 02:40 PM UTC· resolved Aug 28, 2026, 06:18 PM UTC

1. investigating Aug 26, 2026, 02:40 PM UTC

   We are aware of a problem where Datto Endpoint Backup for PC users in the Germany region, paired to 'des1-dtc-server-30', 'des1-dtc-server-32' and 'des1-dtc-server-33' will experience degraded offsite performance, which may affect backup and recovery operations. The Kaseya Engineering Team is currently investigating the issue and working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Aug 26, 2026, 03:58 PM UTC

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

3. resolved Aug 28, 2026, 06:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2026, 08:39 PM UTC· resolved Aug 31, 2026, 01:43 PM UTC

1. identified Aug 25, 2026, 08:39 PM UTC

   We are aware of a problem where some Datto SaaS Protection customers hosted in multiple regions are experiencing backup and restore issues. Export services are not affected. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. 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/

2. identified Aug 25, 2026, 09:48 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Aug 25, 2026, 11:57 PM UTC

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

4. monitoring Aug 26, 2026, 12:03 PM UTC

   We are continuing to monitor for any further issues.

5. identified Aug 26, 2026, 05:06 PM UTC

   Our R&D team is continuing to address this issue and restore full functionality to the affected customers.

6. monitoring Aug 26, 2026, 07:44 PM UTC

   Our R&D team has implemented additional changes to restore full functionality to affected customers and they are closely monitoring for any other issues.

7. resolved Aug 31, 2026, 01:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2026, 04:09 PM UTC· resolved Sep 03, 2026, 04:44 PM UTC

1. identified Aug 25, 2026, 04:09 PM UTC

   We are aware of a problem where Datto BCDR users paired to Server3824 will experience a service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. resolved Sep 03, 2026, 04:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 24, 2026, 03:46 PM UTC· resolved Aug 25, 2026, 04:34 PM UTC

1. identified Aug 24, 2026, 03:46 PM UTC

   We are aware of a problem where customers in the Germany region using Datto BCDR, Datto SaaS Protection, and Datto Endpoint Backup are currently experiencing service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Aug 24, 2026, 05:15 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Aug 25, 2026, 04:05 PM UTC

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

4. resolved Aug 25, 2026, 04:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 21, 2026, 06:22 PM UTC· resolved Aug 22, 2026, 02:50 PM UTC

1. identified Aug 21, 2026, 06:22 PM UTC

   We are aware of a problem where some Datto SaaS Protection customers hosted in multiple regions are experiencing backup and restore failures. Export services are not affected. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. 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/

2. identified Aug 21, 2026, 07:54 PM UTC

   Our R&D team is actively preparing to deploy changes to address the issue.

3. identified Aug 21, 2026, 08:46 PM UTC

   Our R&D team has begun deploying changes to the affected regions to address the issue.

4. monitoring Aug 22, 2026, 12:53 AM UTC

   Backup success rates have returned to normal levels and restoration functions have resumed. Our R&D team is continuing to monitor.

5. resolved Aug 22, 2026, 02:50 PM UTC

   Changes made by the Kaseya R&D team have proven successful and full functionality has been restored. The issue is now considered resolved.

Read the full incident report →

Started Aug 21, 2026, 05:17 PM UTC· resolved Aug 28, 2026, 06:43 PM UTC

1. monitoring Aug 21, 2026, 05:17 PM UTC

   We are aware of a problem where the Activity Logs on our Vidal Platform are slow to load after our 15.1 release. The Kaseya Engineering Team has applied a fix and is currently monitoring this closely. 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/

2. resolved Aug 28, 2026, 06:43 PM UTC

   The issue affecting Activity Log performance on the Vidal Platform following the 15.1 release has been resolved. The Kaseya Engineering Team implemented a fix and has confirmed that Activity Logs are loading as expected after monitoring the platform to ensure ongoing stability and performance. Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

Read the full incident report →

Started Aug 19, 2026, 11:25 AM UTC· resolved Aug 19, 2026, 08:08 PM UTC

1. identified Aug 19, 2026, 11:25 AM UTC

   We are aware of a problem where backups are not successful for customers hosted on isw1-bfyii-1131 The Kaseya Engineering Team is currently responding to the issue, and we will provide updates on this thread as 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/

2. identified Aug 19, 2026, 12:29 PM UTC

   The Engineering team has performed the necessary steps to resolve the issue, and are observing that related errors have stopped and backup metrics are improving as the service is recovering.

3. monitoring Aug 19, 2026, 01:00 PM UTC

   Backups continue to process normally for customers hosted on node 'isw1-bfyii-1131' and our R&D team is monitoring for any other issues.

4. resolved Aug 19, 2026, 08:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 02:15 PM UTC· resolved Aug 20, 2026, 12:38 PM UTC

1. investigating Aug 18, 2026, 02:15 PM UTC

   We are aware of a problem on Datto RMM's Vidal Platform where Jobs are not running and the Activity log can be slow to load. The Kaseya Engineering Team are investigating the issue. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. investigating Aug 18, 2026, 02:52 PM UTC

   We are continuing to investigate this issue.

3. monitoring Aug 18, 2026, 02:58 PM UTC

   A fix has been implemented for Activity Logs and they should be loading as expected. A fix has also been implemented for Jobs not running, but delays are still expected as the platform works through all queued jobs. We will continue to monitor this queue and resolve this status page once it has cleared.

4. monitoring Aug 18, 2026, 03:48 PM UTC

   The Job queue has been cleared and Activity Logs continue to load as expected. We are continuing to monitor for any further issues.

5. identified Aug 18, 2026, 05:13 PM UTC

   We have identified an issue with the Activity Log failing to load. The Kaseya R&D team are working on a fix for the issue.

6. identified Aug 18, 2026, 07:48 PM UTC

   We are continuing to work on a fix for this issue.

7. monitoring Aug 19, 2026, 07:49 AM UTC

   A fix has been implemented for the Activity Log on the Vidal platform. The service has recovered and we are monitoring the results.

8. identified Aug 19, 2026, 12:46 PM UTC

   The Engineering team is currently investigating and resolving issues flagged by internal alerting that led to the Activity Log loading and Job execution issues resurfacing. Thank you for your patience!

9. identified Aug 19, 2026, 01:01 PM UTC

   Scheduled and Quick Job functionality is restored, and the Engineering team is continuing to work on resolving the problem causing issues with the Activity Log loading in accounts.

10. monitoring Aug 19, 2026, 01:53 PM UTC

    A fix has been implemented for the Jobs and Activity Log on the Vidal platform and we are monitoring the results.

11. monitoring Aug 19, 2026, 09:01 PM UTC

    At this time, jobs and activity logs remain stable, and no further issues have been observed however we will continue to monitor the environment overnight.

12. resolved Aug 20, 2026, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 03:46 AM UTC· resolved Aug 18, 2026, 02:13 PM UTC

1. investigating Aug 18, 2026, 03:46 AM UTC

   We have observed that the email processing by INKY is being delayed. We are aware of the issue and is being investigated

2. investigating Aug 18, 2026, 07:30 AM UTC

   We are continuing to investigate the issue.

3. monitoring Aug 18, 2026, 09:42 AM UTC

   Email delays are no longer being recorded and reported and we are monitoring the health of the service.

4. resolved Aug 18, 2026, 02:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 01:53 AM UTC· resolved Aug 18, 2026, 04:26 AM UTC

1. investigating Aug 18, 2026, 01:53 AM UTC

   We are aware of a problem where the Kaseya Store is not accessible. 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/

2. investigating Aug 18, 2026, 01:54 AM UTC

   We are continuing to investigate this issue.

3. resolved Aug 18, 2026, 04:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2026, 09:24 AM UTC· resolved Aug 14, 2026, 07:32 PM UTC

1. investigating Aug 13, 2026, 09:24 AM UTC

   We are aware of an issue affecting the Merlot platform where Quick Jobs and Scheduled Jobs are failing to run. The Kaseya Engineering Team is actively 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/

2. monitoring Aug 13, 2026, 09:52 AM UTC

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

3. resolved Aug 14, 2026, 07:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2026, 09:56 PM UTC· resolved Aug 14, 2026, 12:14 PM UTC

1. identified Aug 12, 2026, 09:56 PM UTC

   We are investigating reports of slow loading times affecting Workplace, the web portal, and agent connectivity for partners hosted in our US regions. A small number of users may also see intermittent connection errors when opening a project or folder. Our engineering 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 Aug 13, 2026, 08:27 AM UTC

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

3. resolved Aug 14, 2026, 12:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 12, 2026, 01:48 AM UTC· resolved Aug 12, 2026, 11:55 AM UTC

1. identified Aug 12, 2026, 01:48 AM UTC

   A database issue is causing a partial outage on the US Inky dashboard. Email processing is unaffected but settings will not be able to be changed while we correct the issue. The issue has been identified and a fix is being implemented.

2. monitoring Aug 12, 2026, 02:24 AM UTC

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

3. resolved Aug 12, 2026, 11:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 11, 2026, 05:35 PM UTC· resolved Aug 12, 2026, 07:33 PM UTC

1. investigating Aug 11, 2026, 05:35 PM UTC

   We are aware of a problem where the ConnectWise integration is returning an error on our Vidal platform. Users may see errors while viewing the integration page and ticketing can be affected. The Kaseya Engineering Team is currently Investigating this issue Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Aug 11, 2026, 06:30 PM UTC

   We are no longer seeing errors related to the ConnectWise Integration. We are continuing to monitor the services at this time.

3. resolved Aug 12, 2026, 07:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 08, 2026, 05:15 PM UTC· resolved Aug 10, 2026, 01:23 PM UTC

1. identified Aug 08, 2026, 05:15 PM UTC

   We are aware of a problem where SaaS Protection customers hosted on node ‘des1-bfyii-1127' are experiencing degraded backup performance for some services. The Kaseya R&D Team has identified the issue and are working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Aug 08, 2026, 08:55 PM UTC

   The Kaseya R&D Team has implemented a fix to alleviate backups for customers hosted on the node des1-bfyii-1127. Backups success rates will be monitored for improvement

3. monitoring Aug 08, 2026, 09:04 PM UTC

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

4. monitoring Aug 09, 2026, 01:38 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Aug 10, 2026, 01:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 07, 2026, 10:59 PM UTC· resolved Aug 07, 2026, 11:48 PM UTC

1. investigating Aug 07, 2026, 10:59 PM UTC

   We are aware of a problem where some customers are unable to access Autotask within our Sydney Data Center 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/

2. resolved Aug 07, 2026, 11:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 06, 2026, 05:51 PM UTC· resolved Aug 24, 2026, 06:02 PM UTC

1. investigating Aug 06, 2026, 05:51 PM UTC

   A known issue exists where archived agents may continue to generate sync completion alerts when associated local points are marked as offsite, despite the agents being in an archived state. While a long-term solution is scheduled for implementation in a future release, assets affected before the fix is deployed will need to be corrected through manual intervention. Customers seeking to implement this mitigation should submit a request through the Kaseya Help Desk Portal at https://helpdesk.kaseya.com/hc/en-gb. Our Support team will assist with the required remediation activities. Thank you for your understanding and continued support.

2. resolved Aug 24, 2026, 06:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 06, 2026, 02:15 PM UTC· resolved Aug 06, 2026, 09:28 PM UTC

1. investigating Aug 06, 2026, 02:15 PM UTC

   We are aware of a problem where Partners have reported the inability to log into the portal via Kaseya One The Kaseya R&D Team is investigating the issue. In the meantime, our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Aug 06, 2026, 04:01 PM UTC

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

3. monitoring Aug 06, 2026, 05:19 PM UTC

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

4. monitoring Aug 06, 2026, 05:19 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Aug 06, 2026, 09:28 PM UTC

   This incident has been resolved.

6. postmortem Sep 03, 2026, 02:24 PM UTC

   # Summary: Between 2026-08-06 05:41 UTC and 2026-08-06 18:03 UTC, ConnectBooster customers were unable to login to ConnectBooster using KaseyaOne Single-Sign-On \(SSO\). # Root Cause: An unexpected failure in a dependency used by the SSO login process caused login attempts to fail. ## Incident Timeline: • Identified: 2026-08-06 13:30 UTC • Public Notification: 2026-08-06 14:15 UTC • Resolved: 2026-08-06 18:03 UTC # Preventative Measures: To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. ## Enhancements to Monitoring and Alerting: * Enhance login workflow logging to provide improved visibility into authentication performance and failures across all login methods. * Implement monitoring and alerting for login workflows using request, error, and performance metrics, enabling the team to quickly identify and respond to authentication issues. ## Enhancements to Infrastructure Resiliency: * Streamline services within the SSO login workflow so that authentication can continue successfully even if related supporting services are unavailable.

Read the full incident report →

Started Aug 06, 2026, 01:41 PM UTC· resolved Aug 06, 2026, 04:56 PM UTC

1. identified Aug 06, 2026, 01:41 PM UTC

   Our payment provider for KaseyaOne and Kaseya Store has identified intermittent connectivity issues with our fraud prevention provider that might cause increased authentication declines. During this time, users may experience intermittent issues related to payment processing in KaseyaOne and Kaseya Store. Core platform functionality outside of payment services will remain unaffected. We recommend avoiding payment-related actions during this maintenance window where possible. We will monitor the situation and provide updates if necessary.

2. resolved Aug 06, 2026, 04:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 05, 2026, 07:40 PM UTC· resolved Sep 30, 2026, 04:40 PM UTC

1. identified Aug 05, 2026, 07:40 PM UTC

   Datto SaaS Protection is currently experiencing degraded backup performance and missed backups for some Microsoft 365 services across multiple regions. The issue has been linked to increased API activity and application-level throttling associated with the ongoing transition from Exchange Web Services (EWS) to Microsoft Graph APIs. Affected regions: US (USE/USW) Australia (AUE) Canada (CAE) Germany (DES) UK (GBE) Singapore (SG) Our R&D teams have identified the primary contributing factors and are actively working to restore full service functionality. Multiple mitigation measures have been implemented, including application performance optimizations, infrastructure and capacity improvements, deployment of configuration changes across affected SaaS Protection pods, and a temporary reduction in backup cadence from 3x daily backups to 2x daily backups to help reduce API demand and improve backup success rates during the transition. These actions have resulted in measurable improvement, with backup success rates increasing across all affected regions over the past 24 hours. While performance continues to stabilize, some customers may still experience backup delays or missed backups as remediation efforts continue. Additional software enhancements are scheduled for deployment this week to further reduce API throttling, improve backup performance, and accelerate recovery. Customer data protection remains the highest priority, and our R&D teams continue to closely monitor the environment while implementing further improvements. Updates will continue to be provided through the Kaseya Status Page as progress is made toward full service restoration.

2. identified Aug 06, 2026, 03:33 PM UTC

   Our R&D team has deployed additional improvements, and backup cadence has now been restored to 3x daily backups for all Google services, OneDrive, and SharePoint across all regions. Exchange and Teams backup cadence remains temporarily set to 2x daily backups to help maintain high backup success rates during the ongoing transition to Microsoft Graph APIs. We have observed continued improvement in backup performance following these changes, and our R&D team is closely monitoring backup success rates across all affected regions. Additional performance enhancements are currently being deployed to further reduce API throttling, improve backup performance, and accelerate recovery. Deployment of these changes is expected to be completed early next week.

3. monitoring Aug 07, 2026, 04:08 PM UTC

   Backup success rate metrics for all services across all regions have recovered and remain stable at normal levels. Google services, along with OneDrive and SharePoint, continue to process 3x daily backups while Teams and Exchange services remain temporarily set to 2x daily backups to maintain high success rates as the migration to Microsoft Graph APIs progresses. Our R&D team is continuing to monitor.

4. monitoring Aug 10, 2026, 04:25 PM UTC

   Backup success rate metrics for all services across all regions continue to remain stable at normal levels. Our R&D team is actively completing deployment of additional improvements to all regions and they are continuing to monitor.

5. monitoring Aug 11, 2026, 03:02 PM UTC

   Our R&D team has completed deployment of the latest changes for the Graph API components as part of the ongoing migration and backup success rates for all services across all regions remain high. We are continuing to monitor.

6. monitoring Aug 12, 2026, 07:44 PM UTC

   Backup operations remain healthy, with success rates staying high across all services and regions following the recent changes. Work on the EWS to Microsoft Graph API migration is ongoing, and our R&D team continues to monitor for any further issues.

7. monitoring Aug 18, 2026, 07:30 PM UTC

   SaaS Protection backup success rates across all services and regions remain high. Google services, along with OneDrive and SharePoint, continue to process backups at the normal 3x daily cadence. Exchange and Teams backup cadence remains temporarily reduced to 2x daily backups to help maintain high backup success rates during the ongoing migration from Exchange Web Services (EWS) to Microsoft Graph APIs. Our R&D team continues to implement and refine configuration adjustments throughout the migration process and is actively monitoring backup performance across all regions. While overall performance remains stable, some customers may still experience intermittent backup delays or missed backups as optimization and migration efforts continue. The migration to Microsoft Graph APIs remains in progress and is currently expected to be completed between late August and early September.

8. monitoring Aug 26, 2026, 03:59 PM UTC

   SaaS Protection backup performance remains strong across all regions and supported services. Backups for Google services, OneDrive, and SharePoint continue to run on the standard three-times-daily schedule. To support consistently high success rates during the ongoing transition from Exchange Web Services (EWS) to Microsoft Graph APIs, Exchange and Teams backups continue to operate on a temporary twice-daily cadence. Our R&D teams remain focused on the migration effort, making and refining configuration changes as needed while closely monitoring backup health and performance. Although overall system stability remains strong, some customers may continue to experience occasional backup delays or missed backup cycles due to API call throttling as migration and optimization activities progress. The migration from EWS to Microsoft Graph APIs is ongoing and is still projected for completion between late August and early September 2026.

9. monitoring Sep 04, 2026, 04:59 PM UTC

   As part of the ongoing migration effort, a planned maintenance window is scheduled for all regions to begin today Friday, September 4, 2026, and continue until Tuesday, September 8, 2026. During this period, our R&D team will be implementing additional changes and optimizations to further improve performance, reduce API throttling, and support the continued transition to Microsoft Graph APIs. Our teams will closely monitor backup health and performance throughout the maintenance window. While overall service stability remains strong, some customers may experience occasional backup delays, reduced backup performance, or missed backup cycles for Microsoft 365 services as migration and optimization activities continue. Our teams will continue to closely monitor backup health and performance throughout the maintenance window and provide additional updates as they become available.

10. identified Sep 09, 2026, 03:14 PM UTC

    We are aware of degraded backup performance affecting Microsoft 365 services, including Exchange, OneDrive, SharePoint, and Teams, as ongoing maintenance and migration activities continue. Some customers may experience intermittent backup delays, reduced backup performance, or missed backup cycles while our R&D team works toward full service restoration. Our R&D team has identified the contributing factors and is actively implementing fixes while continuing the migration from Exchange Web Services (EWS) to Microsoft Graph APIs. This migration remains an important initiative to improve long-term platform performance, scalability, and reliability; however, we are currently seeing increased API throttling and processing delays affecting Microsoft 365 backup operations across multiple workloads. Our teams are closely monitoring backup health and performance across all regions and are deploying additional optimizations designed to reduce throttling, improve processing efficiency, and restore normal backup operations. Google Workspace services are not affected by this issue and continue to operate normally. We will continue to provide updates as additional information becomes available.

11. identified Sep 09, 2026, 08:53 PM UTC

    Our R&D team continues to actively address the issue as a top priority. Work is ongoing to implement corrective measures, while teams closely monitor service performance as recovery efforts progress. We will provide additional updates as more information becomes available.

12. monitoring Sep 10, 2026, 12:44 PM UTC

    Our R&D team has deployed additional changes to mitigate the issue affecting M365 backup operations. Since these changes were implemented, we have observed continued improvement in backup success rate metrics across affected regions. Our teams are closely monitoring backup health and performance as recovery progresses and will continue to evaluate the effectiveness of the recently deployed mitigations. While improvements have been observed, backup success rate metrics continue to recover, and some customers may still experience intermittent delays while the environment stabilizes.

13. monitoring Sep 10, 2026, 06:33 PM UTC

    Our R&D team continues to make progress restoring and stabilizing Microsoft 365 backup operations. Additional Microsoft Graph API migrations have been completed across multiple regions, and recovery efforts continue to deliver improvements across affected services. To support recovery and maintain backup reliability, backup cadence remains temporarily adjusted for some Microsoft 365 workloads. In addition, changes have been implemented to distribute backup processing more evenly across regions, helping reduce peak load and improve overall system performance. As a result of these optimization efforts, some customers may continue to experience delayed backup start times or intermittent backup delays while processing is normalized across the environment. Backup operations remain active across all supported Microsoft 365 services. Many affected services and regions have stabilized, and recovery progress continues across the remaining environment. Our teams remain focused on completing the remaining work and are closely monitoring backup health and performance.

14. monitoring Sep 11, 2026, 03:04 PM UTC

    Our R&D team continues to make strong progress on the Microsoft 365 backup recovery effort and migration activities. Backup success rates have improved significantly across all Microsoft 365 services and regions. Migration and optimization efforts remain ongoing as teams focus on further improving performance and completing the remaining work. While some customers may still experience intermittent delays, overall service health and backup reliability continue to trend positively. Our teams remain actively engaged and will provide additional updates as progress continues.

15. monitoring Sep 11, 2026, 08:00 PM UTC

    Backup success rate metrics continue to steadily improve across M365 services in all regions as our R&D team progresses migration efforts and implements additional optimizations. Service health and backup reliability continue to trend positively, with teams focused on further performance improvements and completing the Microsoft Graph migration while closely monitoring backup health and system performance across the environment.

16. monitoring Sep 14, 2026, 06:23 PM UTC

    Backup success rate metrics across M365 services in all regions have remained consistent as our R&D team continues migration-related optimization efforts and monitors overall service health and performance. While migration activities completed to date have delivered positive results, additional optimization work has been identified during ongoing monitoring efforts. To ensure these items are addressed appropriately, the maintenance window has been tentatively extended through Sunday, September 20, 2026. Some customers may continue to experience backup performance impacts affecting select Microsoft 365 services while this work remains ongoing. The R&D team remains actively engaged and focused on further improving backup performance and reliability while minimizing customer impact. We appreciate your continued patience and will provide further updates as work progresses.

17. monitoring Sep 15, 2026, 08:51 PM UTC

    We continue to make steady progress on our migration efforts. Our teams are actively monitoring performance and stability as the rollout expands, and work remains ongoing to ensure a smooth transition while maintaining service reliability.

18. monitoring Sep 16, 2026, 08:21 PM UTC

    Microsoft Graph API enablement has been completed across all SaaS Protection V3 pods globally, with V2 node rollout progressing and expected to finish this week. Our R&D team is actively monitoring performance, addressing issues impacting a small number of V3 pods, and implementing ongoing optimizations. Migration from EWS to Microsoft Graph continues to advance, with completion currently expected by the end of September. During this transition, some customers may continue to experience temporary backup performance degradation for M365 services while migration activities remain in progress.

19. monitoring Sep 17, 2026, 05:49 PM UTC

    Microsoft Graph enablement has been completed across all SaaS Protection V3 environments, with rollout across V2 environments continuing and expected to be completed in the coming days. To support service stability during the ongoing migration from EWS to Microsoft Graph, Microsoft 365 backup cadence remains adjusted in some environments. V3 environments are currently operating on a reduced backup schedule of one backup per day for M365 workloads to maintain high backup success rates during the transition. V2 environments continue to operate on the standard three backups per day schedule. Our engineering teams continue to closely monitor platform performance, address a small number of remaining service-specific issues, and implement ongoing optimizations. While migration activities remain in progress, some customers may continue to experience intermittent backup performance impacts for certain M365 workloads. Migration efforts continue to advance as planned and remain on track for completion by the end of September.

20. monitoring Sep 18, 2026, 08:12 PM UTC

    Microsoft Graph enablement remains active across all V3 environments globally, with rollout across V2 environments continuing to progress as planned. Graph has now been enabled in multiple V2 regions, with additional regions currently being onboarded. Microsoft 365 backup cadence remains unchanged for V2 environments at three backups per day. V3 environments remain on a reduced cadence of one backup per day to maintain high backup success rates while migration and optimization efforts continue. Engineering teams continue to monitor platform performance, address isolated issues, and implement ongoing optimizations. Graph enablement across the remaining V2 environments is expected to be completed in the coming days.

21. monitoring Sep 23, 2026, 04:31 PM UTC

    Microsoft Graph is enabled across all V3 environments globally and now is enabled on all V2 environments globally. Microsoft 365 backup cadence is unchanged for V2 environments. V3 environments have their Exchange Backups back to three a day while the rest remain on a reduced cadence. Engineering teams continue to monitor platform performance, address isolated issues, and implement ongoing optimizations.

22. monitoring Sep 25, 2026, 08:26 PM UTC

    Microsoft Graph API enablement has now been completed across all V2 and V3 environments globally. To allow additional time for post-migration validation and optimization activities, the maintenance window has been extended. M365 backup cadence remains unchanged for V2 environments, with backups continuing at three times per day for all supported services. In V3 environments, Exchange backups remain at three times per day, while SharePoint, OneDrive, and Teams continue on a reduced cadence of one backup per day during ongoing optimization efforts. Engineering teams continue to closely monitor platform performance, address isolated performance issues, and implement targeted optimizations to ensure continued platform stability and reliability. We will continue to provide updates as progress is made and appreciate your patience while this work is completed.

23. monitoring Sep 28, 2026, 08:10 PM UTC

    Post-migration validation and optimization activities following Microsoft Graph API enablement remain in progress. Backup cadence remains unchanged, with all Microsoft 365 services in V2 environments continuing to back up three times per day. In V3 environments, Exchange backups continue at three times per day, while SharePoint, OneDrive, and Teams remain at one backup per day as optimization efforts continue to mitigate Microsoft service throttling and maintain high backup success rates. Engineering teams have identified a small number of isolated issues and are actively implementing targeted fixes while continuing to monitor platform performance and stability. We appreciate your patience and will provide additional updates as progress continues.

Read the full incident report →

Started Aug 03, 2026, 09:12 AM UTC· resolved Aug 05, 2026, 07:46 PM UTC

1. identified Aug 03, 2026, 09:12 AM UTC

   We are aware of an issue where some Datto SaaS Protection customers may experience degraded backup performance for Exchange and Teams services. The Kaseya R&D team has identified the issue and is actively working to restore normal backup performance as quickly as possible. For the latest updates, please subscribe to the Kaseya Status Page at https://status.kaseya.com/.

2. identified Aug 03, 2026, 12:31 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Aug 03, 2026, 01:30 PM UTC

   Our R&D team has released a fix to address the backup performance degradation for some M365 services affecting customers hosted in multiple regions and they are closely monitoring.

4. identified Aug 03, 2026, 02:46 PM UTC

   Our R&D team is continuing to address the backup performance issues affecting some M365 services on multiple SaaS Protection pods. In the meantime, they are preparing to temporarily reduce backup cadence on affected pods from 3x backups per day to 2x backups per day to help stabilize backup success rates in all affected regions.

5. identified Aug 03, 2026, 03:33 PM UTC

   Our R&D team continues to address backup performance issues affecting some Microsoft 365 services across multiple SaaS Protection pods following the transition from EWS to Microsoft Graph APIs. To help stabilize backup success rates and reduce API throttling during this migration, backup cadence on affected pods will be temporarily reduced from 3x backups per day to 2x backups per day.

6. identified Aug 03, 2026, 05:34 PM UTC

   Our R&D team has begun deployment of the changes to reduce backup cadence on affected SaaS Protection pods across all regions to 2x backups per day to help stabilize backup success rates further. This change is expected to complete deployment by 20:00 ET (00:00 UTC). Our R&D team is continuing to closely monitor backup performance as these additional changes are implemented.

7. identified Aug 03, 2026, 08:05 PM UTC

   Our R&D team is continuing to deploy the configuration changes to adjust backup frequency from 3x backups per day to 2x backups per day on SaaS Protection pods in all regions and we are continuing to closely monitor backup success rate metrics.

8. identified Aug 03, 2026, 09:52 PM UTC

   Our R&D team has completed deployment of the configuration changes to SaaS Protection pods in all regions. Daily backup cadence is now temporarily set to 2x backups per day across the fleet to reduce API throttling and help stabilize backup success rate metrics during the transition from EWS to Microsoft Graph APIs. Our R&D team is closely monitoring the effects of the changes and expect backup success rates to begin stabilizing over the next several hours.

9. identified Aug 04, 2026, 02:29 PM UTC

   After the changes made yesterday, we have observed some improvement to backup success rates however backups are currently still degraded for some M365 services across multiple regions due to API throttling related to the transition from EWS to Microsoft Graph APIs. Our R&D team is continuing to develop additional improvements to address the backup performance issues.

10. identified Aug 04, 2026, 05:26 PM UTC

    Our R&D team is currently implementing configuration changes in multiple regions to further mitigate the degraded backup performance still affecting some customers. We will be closely monitoring the results of these changes as we continue to develop additional improvements to accelerate recovery for affected customers.

11. identified Aug 04, 2026, 08:09 PM UTC

    The latest changes have been deployed to SaaS Protection pods in multiple regions still experiencing backup performance issues. Our R&D team is continuing to monitor as backup success rate metrics improve across the fleet.

12. identified Aug 05, 2026, 02:02 PM UTC

    Significant improvement to backup success rate metrics has been observed across all regions after the latest changes were implemented. Our R&D team is continuing to deploy configuration changes to further stabilize backup performance in all regions. Backup success rates will continue to be closely monitored as the team is actively working to develop additional improvements to address the API throttling related to the transition from EWS to Microsoft Graph APIs currently in progress.

Read the full incident report →

Started Jul 31, 2026, 05:44 PM UTC· resolved Aug 05, 2026, 06:06 PM UTC

1. identified Jul 31, 2026, 05:44 PM UTC

   We are aware of a problem where customers using Datto Endpoint Backup for PC and paired with 'use1-dtc-server-5.datto.com' may encounter reduced performance or intermittent issues with offsite capabilities. 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 Aug 05, 2026, 05:43 PM UTC

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

3. resolved Aug 05, 2026, 06:06 PM UTC

   This incident has been resolved.

4. postmortem Aug 19, 2026, 03:27 PM UTC

   **\[Datto Endpoint Backup for PC\]** **A performance degradation event affected the Datto Endpoint Backup for PC Server service, impacting service responsiveness and availability – 2026-07-31** ‌ **Summary:** Between **2026-07-31 05:30 PM UTC** and **2026-08-05 07:30 PM UTC**, Datto Endpoint Backup for PC customers hosted on Cloud Siris 215069 encountered reduced performance and intermittent issues with offsite capabilities. **Root Cause:** The service interruption resulted from a hardware failure. Recovery activities were conducted with a focus on maintaining service integrity and minimizing potential impact. Following restoration of service, a review was completed and improvement actions have been identified to further enhance recovery processes. **Incident Timeline:** * Identified: **2026-07-31 05:30 PM UTC** * Public Notification: **2026-07-31 05:34 PM UTC** * Resolved: **2026-08-05 07:30 PM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * Create standardized documentation for system restoration workflows and conduct process reviews with key technical and operational teams to ensure effective execution, knowledge sharing, and continuous improvement. * Establish a centralized and well-documented catalog of monitoring alerts and designated response teams to improve operational visibility, accountability, and incident management.

Read the full incident report →

Started Jul 31, 2026, 02:27 AM UTC· resolved Aug 03, 2026, 04:04 PM UTC

1. investigating Jul 31, 2026, 02:27 AM UTC

   Antimalware suites are flagging the Datto RMM Agent update from 15.1.0 as malicious and raising alerts causing Partner distress.

2. investigating Jul 31, 2026, 04:25 PM UTC

   Our R&D team is continuing its investigation into this issue and is working closely with a third-party provider to assist in identifying the root cause and resolution.

3. monitoring Jul 31, 2026, 06:43 PM UTC

   We have reached out and shared the necessary technical indicators with our third party contact and have received confirmation that corrective actions have been implemented on their side. Based on the information provided to us, the issue should no longer occur with the current version of the agent. We will continue to closely monitor the situation and provide additional updates if necessary. Thank you for your patience and understanding.

4. resolved Aug 03, 2026, 04:04 PM UTC

   This incident has been resolved.

5. postmortem Aug 12, 2026, 07:46 PM UTC

   **Root Cause Analysis – DRMM Agent Services Incorrectly Flagged by Endpoint Security Software** **Summary** Between **2026-07-30 17:00 UTC and 2026-07-31 18:43 UTC**, some Datto RMM customers on the Syrah platform experienced issues following the deployment of agent version **15.1.0**. The issue affected endpoints utilizing **Sophos**, where certain DRMM agent services were identified as malicious. In affected environments, agent files were quarantined or removed, causing the Datto RMM agent to become non-functional until remediation actions were completed. The issue affected a subset of customers and was resolved after coordination with the security vendor. **Root Cause** Following the deployment of DRMM agent version 15.1.0, certain agent components were incorrectly identified as malicious by a third-party endpoint security vendor. The detection was a false positive and was not the result of malware or unauthorized code within the DRMM agent. Investigation determined that the detection was likely related to changes in the digital signing reputation of the agent files, which caused the security tool to classify legitimate agent activity as suspicious. **Incident Timeline** * **Identified:** 2026-07-30 21:00 UTC * **Public Notification:** 2026-07-31 02:27 UTC * **Resolved:** 2026-07-31 18:43 UTC **Preventative Measures** To reduce the likelihood and impact of similar incidents in the future, we are implementing the following improvements: **Enhancements to Release Validation** * Further strengthen our pre-release validation by incorporating a broader set of security and threat-intelligence platforms before agent updates are broadly deployed. * Broaden third-party endpoint security testing to further improve early detection of potential false-positive classifications before release. **Enhancements to Vendor Coordination** * Expand the existing file reputation submission process to include additional security providers to further improve coordination and response options, reducing reliance on a single vendor path. * Establish more formalized engagement processes with security vendors to facilitate faster review and resolution of false-positive detections. **Enhancements to Agent Deployment Practices** * Evaluate staged agent rollout capabilities that would allow updates to be gradually deployed to a subset of endpoints before broader distribution limiting the scope of impact when issues are detected. * Use phased deployments to identify unexpected environmental interactions earlier and further reduce potential customer impact. **Enhancements to Agent Update Architecture** * Review and improve elements of the agent update mechanism to reduce the likelihood that normal update activities are misinterpreted by security software. * Continue refining update workflows to improve compatibility with modern endpoint protection technologies to further reduce the risk of false positive classifications

Read the full incident report →

Started Jul 31, 2026, 12:48 AM UTC· resolved Jul 31, 2026, 03:26 AM UTC

1. investigating Jul 31, 2026, 12:48 AM UTC

   We are aware of the issue where Filters no longer respect the "Site Name" Criteria resulting in devices that should not be included in the Filter are included in the Filter that then affects Policy/Job targeting.

2. investigating Jul 31, 2026, 02:04 AM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 31, 2026, 02:30 AM UTC

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

4. resolved Jul 31, 2026, 03:26 AM UTC

   This incident has been resolved.

5. postmortem Aug 05, 2026, 12:53 PM UTC

   **Datto RMM - Global Filters Using Site Criteria Returned Incorrect Results – 2026-07-30** **Summary** Between **2026-07-30 18:10 UTC** and **2026-07-31 02:30 UTC**, some **Datto RMM** customers experienced an issue where **Global Filters using Site specific criteria, including Site Name**, **Site Description**, or **Site is On-Demand,** and **excluding “does not contain”** criteria, returned broader-than-expected device results. As a result, customers using the affected filter configurations may have seen devices incorrectly included in filter results, creating a risk of inaccurate device targeting for downstream automation, policies, or jobs that ran during the exposure window. The time required to fully restore service was extended because a rollback path for the release was not available. As a result, mitigation required the issue to be diagnosed, a software fix to be developed, tested, and deployed before the incident could be resolved. Engineering isolated the regression, developed a corrective code change, validated the fix, and deployed it to restore expected filter behavior. ‌ **Root Cause** A software defect introduced during a performance optimization of site-based filtering logic caused certain filter criteria to be processed incorrectly. Under specific filter configurations, portions of the filtering logic were not applied as intended, resulting in broader device selection results than expected. A corrective code change was validated and deployed to restore expected filter behavior. ‌ **Incident Timeline** **Identified:** 2026-07-31 00:30 UTC **Public Notification:** 2026-07-31 01:48 UTC **Resolved:** 2026-07-31 02:30 UTC ‌ **Preventative Measures** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: **Enhancements to Release Management Practices** * Expand unit test coverage for code changes to improve validation of functionality affected by application changes. * Expand automated regression test coverage across filter functionality, including historical defect scenarios and previously identified filter-related use cases. * Increase automated test coverage for critical customer workflows and core platform functionality to improve release readiness validation. * Execute automated regression testing as part of both development and release validation processes. * Evaluate additional release strategies such as customer beta testing, canary deployments, and blue/green deployments to enhance existing release strategies and further reduce risk, improve early issue detection, and minimize customer impact during software releases. **Enhancements to Quality Assurance and Detection** * Implement additional automated regression testing for filter functionality and related workflows. * Additional scope will be added to automated Regression testing that covers functional completeness and accuracy to cover critical customer workflow validation * Expand monitoring and alerting around post-deployment validation activities to accelerate identification of release-related issues. * Establish automated validation of key customer workflows following deployment to improve early detection of functional regressions during QA testing. **Enhancements to Incident Recovery Capabilities** * Implement automated post-deployment validation of critical workflows and use resulting signals to accelerate mitigation decisions when issues are detected post-release. * Develop rollback capabilities to enable restoration to a known good release version when appropriate. * Assess rollback mechanisms that align with future deployment strategy improvements, including staged deployment and service-based release models. These improvements are intended to strengthen release validation, improve early detection of functional regressions, reduce restoration time during incidents, and limit the potential impact of future release-related issues.

Read the full incident report →

Started Jul 30, 2026, 04:34 PM UTC· resolved Aug 05, 2026, 07:46 PM UTC

1. identified Jul 30, 2026, 04:34 PM UTC

   We are aware of a problem where some customers hosted on pod 'aue1-saas-p1' are experiencing backup performance degradation for Exchange 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 Jul 30, 2026, 05:45 PM UTC

   Our R&D team has implemented configuration changes on pod 'aue1-saas-p1' to help remediate the issue and they are actively monitoring backup performance.

3. monitoring Jul 31, 2026, 03:55 PM UTC

   Exchange backup success rate metrics on pod 'aue1-saas-p1' have improved after the changes that were implemented. Our R&D team is continuing to closely monitor backup performance on the pod.

Read the full incident report →