Datto Outage History

Started Nov 04, 2026, 08:07 PM UTC· resolved Nov 05, 2026, 12:07 AM UTC

1. investigating Nov 04, 2026, 08:07 PM UTC

   We are currently experiencing an issue impacting KaseyaAssist within our direct product portals. As a workaround, customers can continue to engage with Kaseya Support through helpdesk.kaseya.com for support inquiries and billing assistance. Our vendor is actively investigating the issue and working to restore service as quickly as possible. We apologize for any inconvenience and will provide updates as they become available.

2. identified Nov 04, 2026, 09:31 PM UTC

   Our vendor has identified and is in the process of implementing a fix - recovery to normal operations is expected to begin rolling out shortly

3. monitoring Nov 04, 2026, 11:05 PM UTC

   Our vendor confirmed that a fix has been implemented - We will continue to monitor and provide updates until full resolution has been confirmed

4. resolved Nov 05, 2026, 12:07 AM UTC

   All affected systems have made a full recovery. Incident is now resolved.

Read the full incident report →

Started Nov 04, 2026, 12:26 PM UTC· resolved Nov 04, 2026, 04:12 PM UTC

1. investigating Nov 04, 2026, 12:26 PM UTC

   We are aware of a problem where Multiple customers in the BMS US region are reporting issues accessing various modules, including Service Desk, CRM, and Admin (Support Users). The Kaseya Engineering Team is actively investigating. If you need any assistance, please contact our support team for assistance through the Kaseya Support Portal. To receive notifications about future maintenance events and service updates, subscribe to the Kaseya Status Page.

2. investigating Nov 04, 2026, 02:32 PM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 04, 2026, 03:07 PM UTC

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

4. resolved Nov 04, 2026, 04:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 03, 2026, 01:38 PM UTC· resolved Nov 03, 2026, 04:01 PM UTC

1. investigating Nov 03, 2026, 01:38 PM UTC

   We are aware of a problem where backups are not running and SaaS Protection Console is not accessible to perform recovery related functions. The Kaseya Engineering Team is investigating If you need any assistance, please contact our support team for assistance through the Kaseya Support Portal. To receive notifications about future maintenance events and service updates, subscribe to the Kaseya Status Page.

2. monitoring Nov 03, 2026, 02:06 PM UTC

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

3. monitoring Nov 03, 2026, 02:32 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 03, 2026, 04:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 02, 2026, 05:00 PM UTC· resolved Nov 02, 2026, 05:00 PM UTC

1. resolved Nov 02, 2026, 05:00 PM UTC

   The Kaseya Engineering Team resolved a problem where Batch Generating Invoices failed due to a "Failed to generate... Could not load file or assembly" error. If you are still experiencing this issue or need any assistance, please contact our support team for assistance through our helpdesk at: https://helpdesk.kaseya.com/hc/en-gb#/contact To receive notifications about future maintenance events and service updates, subscribe to https://status.kaseya.com/

Read the full incident report →

Started Nov 02, 2026, 04:58 PM UTC· resolved Nov 02, 2026, 08:20 PM UTC

1. identified Nov 02, 2026, 04:58 PM UTC

   We are aware of a problem where emails sent from Autotask PSA are delayed. The Kaseya Engineering Team has identified the issue and are working on a fix. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Nov 02, 2026, 07:32 PM UTC

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

3. resolved Nov 02, 2026, 08:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 02, 2026, 02:13 PM UTC· resolved Nov 02, 2026, 02:51 PM UTC

1. resolved Nov 02, 2026, 02:30 PM UTC

   The Kaseya Engineering Team resolved a problem where pages were failing to load with an error message: "Something went wrong! Please contact the system admin." If you are still experiencing this issue or need any assistance, please contact our support team for assistance through our helpdesk at: https://helpdesk.kaseya.com/hc/en-gb#/contact To receive notifications about future maintenance events and service updates, subscribe to https://status.kaseya.com/

2. postmortem Nov 03, 2026, 05:45 PM UTC

   # Summary Between 2026-11-02 14:13 UTC and 2026-11-02 14:51 UTC, some BMS EMEA customers experienced intermittent application errors when attempting to log in and perform certain actions, including ticket-related workflows. Affected users received an error message indicating that the requested action could not be completed. # Root Cause An application-level issue resulted in intermittent processing failures that affected login and ticketrelated workflows for some BMS EMEA customers. The application recovered successfully after a restart restored normal operation. ## Incident Timeline * Identified: 2026-11-02 14:13 UTC * Resolved: 2026-11-02 14:51 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 * Review existing monitoring coverage for application availability and application error conditions, with particular focus on login and ticket-related workflows. ## Enhancements to Incident Response and Recovery * Review and update operational recovery procedures for intermittent application failures. * Ensure recovery validation includes verification of critical workflows, including login functionality and ticket-related operations, following remediation activities.

Read the full incident report →

Started Oct 29, 2026, 07:57 PM UTC· resolved Nov 02, 2026, 08:31 PM UTC

1. investigating Oct 29, 2026, 07:57 PM UTC

   We are aware of a problem where Datto BCDR users in the UK region may experience degraded offsite performance, potentially impacting synchronization operations. The Kaseya Engineering Team is 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/

Read the full incident report →

Started Oct 29, 2026, 03:30 PM UTC· resolved Oct 29, 2026, 03:30 PM UTC

1. resolved Oct 29, 2026, 03:30 PM UTC

   The Kaseya Engineering Team resolved a problem where users in the US West region, hosted on storage server 'usw-backup-storage-0157' experienced degraded backup functionality. If you are still experiencing this issue or need any assistance, please contact our support team for assistance through our helpdesk at: https://helpdesk.kaseya.com/hc/en-gb#/contact To receive notifications about future maintenance events and service updates, subscribe to https://status.kaseya.com/

Read the full incident report →

Started Oct 28, 2026, 06:50 PM UTC· resolved Nov 03, 2026, 05:47 PM UTC

1. investigating Oct 28, 2026, 06:50 PM UTC

   We are aware of a problem where Datto AV is incorrectly flagging newly created .pdf files as PHISH/PDF, causing the files to be quarantined. The Kaseya R&D Team is currently investigating this 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. To work around this issue: Adding exclusions for the affected folders and files. Then restoring the affected files. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Oct 29, 2026, 03:13 PM UTC

   Our engineering team has identified the issue and is monitoring the fix. Some PDF files, were incorrectly flagged as PHISH/PDF.Agent. A specific detection rule has been disabled in VDF 8.21.8.130, deployed October 28, 2026. The rest of the PHISH detection category remains active. We are monitoring to confirm new false positives have stopped. Files that have already been quarantined must be restored manually.

3. resolved Nov 03, 2026, 05:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 26, 2026, 04:34 PM UTC· resolved Oct 26, 2026, 08:43 PM UTC

1. monitoring Oct 26, 2026, 04:34 PM UTC

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

2. resolved Oct 26, 2026, 08:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 26, 2026, 02:17 PM UTC· resolved Oct 26, 2026, 08:02 PM UTC

1. investigating Oct 26, 2026, 02:17 PM UTC

   We are aware of a problem where Datto SaaS Protection customers hosted on 'aue1-bfyii-1533' are experiencing a disruption to SaaS Protection services and may receive a '500 Internal Server Error' when attempting to access their accounts. The Kaseya Engineering Team is actively investigating. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Oct 26, 2026, 06:01 PM UTC

   Our R&D team has identified the issue and a fix has been implemented. All customers hosted on node 'aue1-bfyii-1533' are accessible again accounts are functioning normally. We are monitoring for any other issues.

3. resolved Oct 26, 2026, 08:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 26, 2026, 01:16 PM UTC· resolved Oct 26, 2026, 07:33 PM UTC

1. identified Oct 26, 2026, 01:16 PM UTC

   We are aware of a problem where customers hosted on pod 'aue2-saas-p2' are experiencing backup performance degradation affecting M365 and Google Workspace services. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. 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/

2. monitoring Oct 26, 2026, 06:17 PM UTC

   Our R&D team has implemented changes to address the issue and backup success rate metrics for customers hosted on pod 'aue2-saas-p2' have returned to normal levels. We are monitoring for any other issues.

3. resolved Oct 26, 2026, 07:33 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 24, 2026, 07:07 PM UTC· resolved Oct 26, 2026, 09:24 PM UTC

1. investigating Oct 24, 2026, 07:07 PM UTC

   We are aware of a problem where Node use1-dtc-server-118.datto.com is inaccessible preventing access to Backups/ Screenshots/ Restores. The Kaseya Engineering Team is investigating the situation 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 Oct 26, 2026, 09:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2026, 02:50 PM UTC· resolved Oct 26, 2026, 09:12 PM UTC

1. investigating Oct 23, 2026, 02:50 PM UTC

   We are aware of a issue affecting device filters that combine negative query conditions, such as “does not contain,” with an embedded AND/OR operator within the filter criteria. A change with how these conditions are evaluated was made to correct these queries however it was not communicated as expected and may cause some existing filters to return different results than previously anticipated. We are considering reverting this change, if you believe your filters may be affected, please contact Support for assistance reviewing your configuration and guidance on next steps.

2. identified Oct 23, 2026, 02:51 PM UTC

   We are aware of a issue affecting device filters that combine negative query conditions, such as “does not contain,” with an embedded AND/OR operator within the filter criteria. A change with how these conditions are evaluated was made to correct these queries however it was not communicated as expected and may cause some existing filters to return different results than previously anticipated. We are considering reverting this change, if you believe your filters may be affected, please contact Support for assistance reviewing your configuration and guidance on next steps.

3. identified Oct 23, 2026, 07:52 PM UTC

   We are actively addressing an issue affecting device filters that utilize compound criteria, such as "does not contain" combined with nested logical operators. Engineering is preparing an update to restore previous filter evaluation behavior. The build is currently being validated in our staging environment, and we will provide an update once the production release window is confirmed. Recommended Actions: Filters: No action is needed on your existing device filters. Existing configurations will evaluate as expected once the update is deployed. Automations: As a precaution, partners may choose to temporarily pause or defer non-critical scheduled jobs or policies that target dynamic filters until the update is complete. We will post our next update once staging validation concludes.

4. monitoring Oct 26, 2026, 10:12 AM UTC

   An update was deployed to Pinotage (EU1) over the weekend to restore standard device filter evaluation behavior. Our internal testing confirms that filters are functioning as expected, and all automated tasks are running smoothly. We are actively monitoring platform performance across a full business day before marking this incident fully resolved. If you paused any scheduled jobs or policies as a precaution, it is now safe to resume them. We will post our next update at the end of the business day.

5. resolved Oct 26, 2026, 09:12 PM UTC

   This incident is now resolved after the Kaseya R&D team restored prior device filter functionality with an update over the weekend If you paused any scheduled jobs or policies as a precaution, it is now safe to resume them.

Read the full incident report →

Started Oct 22, 2026, 09:28 AM UTC· resolved Oct 22, 2026, 06:26 PM UTC

1. investigating Oct 22, 2026, 09:28 AM UTC

   We are aware of a problem where Datto SaaS Protection customers hosted on 'gbe2-bfyii-1555' are experiencing a disruption to SaaS Protection services. The Kaseya Engineering Team is currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Oct 22, 2026, 02:54 PM UTC

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

3. monitoring Oct 22, 2026, 05:55 PM UTC

   Customers hosted on node 'gbe2-bfyii-1555' are accessible again and backups are running normally. Our R&D team is monitoring for any other issues.

4. resolved Oct 22, 2026, 06:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 21, 2026, 08:08 PM UTC· resolved Oct 22, 2026, 01:50 PM UTC

1. investigating Oct 21, 2026, 08:08 PM UTC

   We are aware of a problem where RocketCyber partners, in the EU region, are experiencing web pages loading slow or not at all, within the platform. 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. monitoring Oct 21, 2026, 09:00 PM UTC

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

3. resolved Oct 22, 2026, 01:50 PM UTC

   This incident has been resolved.

4. postmortem Oct 28, 2026, 04:34 PM UTC

   **RocketCyber - Service Degradation in EU Region – 2026-10-21** **Summary:** Between **2026-10-21 19:12 UTC** and **2026-10-21 21:45 UTC**, **RocketCyber** customers in the **EU region** experienced service degradation affecting portions of the platform. During this time, some users may have experienced delays or intermittent failures when interacting with RocketCyber services. Service functionality was fully restored once the underlying issue affecting a third-party cloud database provider was resolved. **Root Cause:** The incident was caused by a service disruption within a third-party cloud database provider in the EU region. Several RocketCyber services rely on this provider for authentication and database access. During the provider's outage, affected RocketCyber services were unable to successfully authenticate, resulting in degraded service availability until the provider restored normal operations. **Incident Timeline:** * **Identified:** 2026-10-21 19:42 UTC * **Public Notification:** 2026-10-21 19:42 UTC * **Resolved:** 2026-10-21 21:45 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** * Improve monitoring of critical third-party dependencies to provide faster visibility when an external provider experiences service disruptions. * Enhance alerting around authentication and database connectivity failures to accelerate identification and triage of dependency-related incidents. **Enhancements to Incident Management and Response** * Refine operational procedures for responding to third-party service interruptions, including improved communication workflows and escalation paths. * Improve correlation between internal service alerts and external provider status notifications to reduce investigation time during future incidents. **Enhancements to Infrastructure Resiliency** * Evaluate opportunities to further reduce dependency-related impact through application-level resiliency improvements where appropriate. * Review service dependency patterns and recovery procedures to improve platform resilience during external provider disruptions.

Read the full incident report →

Started Oct 19, 2026, 01:00 PM UTC· resolved Oct 19, 2026, 01:00 PM UTC

1. resolved Oct 19, 2026, 01:00 PM UTC

   We are aware of a problem where Datto Partner Portal users experienced an error when attempting to access the Datto Partner Portal. The Kaseya Engineering Team has implemented a resolution and user access has been restored. 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/

Read the full incident report →

Started Oct 15, 2026, 10:52 AM UTC· resolved Oct 23, 2026, 05:53 PM UTC

1. investigating Oct 15, 2026, 10:52 AM UTC

   We are aware of an issue where some Datto SaaS Protection Partners are unable to access customer accounts hosted on the isw1-bfyii-1134 node The Kaseya Engineering Team is investigating the issue. If you have any 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 the latest updates: https://status.kaseya.com/

2. monitoring Oct 15, 2026, 12:04 PM UTC

   The Kaseya R&D Team implemented a fix, and as a result, the clients hosted on the node are now accessible and full functionality is restored. We are currently monitoring the health of the service and the progress with which the service is working through the queued backups. The estimated time for full recovery is up to 8 hours.

3. resolved Oct 23, 2026, 05:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 05, 2026, 09:35 PM UTC· resolved Oct 06, 2026, 08:11 AM UTC

1. investigating Oct 05, 2026, 09:35 PM UTC

   We are aware of a problem where agents are unable to connect and portal users are unable to login in the AU region. 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 Oct 05, 2026, 11:09 PM UTC

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

3. resolved Oct 06, 2026, 08:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 05, 2026, 07:25 PM UTC· resolved Oct 06, 2026, 03:41 PM UTC

1. investigating Oct 05, 2026, 07:25 PM UTC

   We are aware of a problem where Datto Endpoint Backup for PC users hosted on Cloud Siris 296721 in the US East region can experience degraded backup performance. The Kaseya R&D 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 Oct 06, 2026, 12:59 PM UTC

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

3. resolved Oct 06, 2026, 03:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2026, 06:16 PM UTC· resolved Oct 21, 2026, 06:13 PM UTC

1. investigating Oct 02, 2026, 06:16 PM UTC

   We are aware of a problem affecting the connectivity of Datto RMM macOS agents. At this time, we have identified the following behaviors: - Newly installed macOS agent installations are unable to establish connectivity. - Existing macOS agents, that are currently in production environments, should remain online; however, our investigation is ongoing to determine whether additional scenarios may cause agents to go offline. - Initial testing shows that if a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM. Our teams are actively investigating the root cause with Apple and working to develop a resolution. We will provide additional updates as more information becomes available. Until further notice, we recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible. We apologize for the inconvenience and appreciate your patience while we work to resolve 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. identified Oct 02, 2026, 09:58 PM UTC

   We have identified the cause of the issue affecting the connectivity of Datto RMM macOS agents. Our teams are now working on a resolution. The behaviors described in our previous update remain unchanged: • Newly installed macOS agent installations are unable to establish connectivity. • Existing macOS agents that are currently in production environments should remain online. • If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM. Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible. We will post our next update here by 11:00 AM EDT on Saturday, October 3, 2026, or sooner if more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve 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/

3. identified Oct 03, 2026, 03:08 PM UTC

   Our teams are continuing to work on a resolution. The behaviors described in our previous update remain unchanged: • Newly installed macOS agent installations are unable to establish connectivity. • Existing macOS agents that are currently in production environments should remain online. • If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM. Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible. We will post our next update here by 7:00 PM EDT on Saturday, October 3, 2026, or sooner if more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve 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/

4. identified Oct 03, 2026, 11:00 PM UTC

   The Kaseya R&D team has developed a fix and will be rolling out the update to the MacOS agents tonight and tomorrow. We will post a maintenance window for each platform prior to the update. To assist with updating macOS agents and verifying they are updated correctly, we have prepared a step-by-step guide available here: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm Until the update is out on your platform the behaviors described in our previous posts remain unchanged: • Newly installed macOS agent installations are unable to establish connectivity. • Existing macOS agents that are currently in production environments should remain online. • If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM. • We continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible. We will post our next update here after all deployments are completed, or sooner if more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve 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/

5. monitoring Oct 04, 2026, 01:31 PM UTC

   A fix has now been deployed across all supported platforms and is available to all customers. Our teams are actively monitoring the environment and platform telemetry to validate the effectiveness of the changes and ensure systems continue to operate as expected. We encourage all customers to verify that their macOS devices are online and reporting successfully following the deployment of this fix. While many devices should recover normally, some macOS agents may remain offline and will require additional remediation including manual intervention by the end users. To assist with this process, we have prepared a step-by-step guide that will help you confirm agent status, identify devices requiring further assistance, and walk you through the recommended recovery steps: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm We appreciate your patience, understanding, and partnership while we worked to investigate and resolve these issues. Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

6. monitoring Oct 14, 2026, 07:48 PM UTC

   The Kaseya R&D team will be releasing a new Datto RMM agent build across all platforms. This release includes a new agent version number, making it easier for partners distinguish between agents that have been updated and those that may still require attention. Deployment of the updated agent build will follow the published platform maintenance schedule. We encourage partners to review the release notes for detailed deployment information, platform rollout timing, and guidance regarding the updated agent version. Release notes: https://rmm.datto.com/help/en/Content/0HOME/ReleaseNotes/2026/ReleaseNotesDattoRMMv15.1.4.htm We continue to actively monitor the rollout and its results across all platforms. Partners should verify that their devices remain online following the update. If any macOS devices remain offline or require additional remediation, please refer to the available guidance and contact Support if further assistance is needed.

7. resolved Oct 21, 2026, 06:13 PM UTC

   The Kaseya R&D team has completed the deployment of Datto RMM agent version 15.1.4 across all platforms. With the updated agent build now available across all platforms, we are marking this status page as Resolved. Some macOS agents may still require additional attention to complete the update or return to an online state. Partners should review the help article referenced in the 15.1.4 release notes for guidance on identifying and remediating affected agents. If additional assistance is required after following the recommended steps, please contact Support. Release notes: https://rmm.datto.com/help/en/Content/0HOME/ReleaseNotes/2026/ReleaseNotesDattoRMMv15.1.4.htm

Read the full incident report →

Started Oct 01, 2026, 07:58 PM UTC· resolved Oct 02, 2026, 02:22 PM UTC

1. investigating Oct 01, 2026, 07:58 PM UTC

   We are aware of a problem where Datto SaaS Protection customers hosted on V2 node 'aue1-bfyii-2213' are experiencing a disruption to SaaS Protection services. The Kaseya Engineering Team is currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Oct 01, 2026, 08:21 PM UTC

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

3. monitoring Oct 01, 2026, 08:47 PM UTC

   Our R&D team has resolved the issue and customers hosted on 'aue1-bfyii-2213' should now be accessible and accounts are functioning normally. We are monitoring for any other issues.

4. resolved Oct 02, 2026, 02:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2026, 05:55 PM UTC· resolved Oct 01, 2026, 08:10 PM UTC

1. investigating Oct 01, 2026, 05:55 PM UTC

   We are aware of a problem in both BMS and Vorex where users are getting errors when generating batch invoices, using billing automations to send invoices, and issues using the "Post All" button when in the "Billing Review" stage. 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. identified Oct 01, 2026, 06:06 PM UTC

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

3. resolved Oct 01, 2026, 08:10 PM UTC

   The Kaseya Engineering Team has fixed issues related to generating batch invoices and with using billing automation. The issue with the "Post All" button when on the "Billing Review" stage will be fixed at a later date. As a workaround, users can use the bulk select option to select multiple or all line items at once, then click "Post" instead of "Post All". This provides the same result by posting all selected line items, with just one additional step while we work on a permanent fix.

Read the full incident report →

Started Oct 01, 2026, 02:41 PM UTC· resolved Oct 01, 2026, 05:00 PM UTC

1. investigating Oct 01, 2026, 02:41 PM UTC

   We are aware of a problem where users can experience extended latency when navigating throughout the Kaseya Quote Manager Platform. 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. monitoring Oct 01, 2026, 02:55 PM UTC

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

3. resolved Oct 01, 2026, 05:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2026, 04:37 PM UTC· resolved Nov 02, 2026, 04:03 PM UTC

1. monitoring Sep 30, 2026, 04:37 PM UTC

   Microsoft Graph API migration has been completed across all Datto SaaS Protection environments, including customers utilizing in-place archive configurations. No further migration activities are expected to impact backup operations. Some customers may continue to experience backup performance degradation while our engineering teams work to restore backup success rates to pre-migration levels. Multiple fixes and optimizations are being actively deployed across V2 and V3 environments, including improvements to Microsoft Graph API error handling and overall backup processing reliability. Teams continue to monitor the impact of each change as it is released. Current Backup Cadence: V2 environments: All Microsoft 365 services continue to back up three times per day. V3 environments: Exchange continues to back up three times per day. SharePoint, OneDrive, and Teams remain on a reduced cadence of one backup per day while optimization efforts continue to maintain high backup success rates and mitigate Microsoft service throttling. We do not currently have a fixed resolution date, as improvements are being delivered through ongoing remediation efforts rather than a single release. While performance is expected to continue improving, some customers may experience intermittent backup performance issues until all identified issues have been addressed. Based on current progress, we are cautiously optimistic that the remaining issues will be resolved over the coming days to weeks. We will continue providing updates as fixes are confirmed. Customers who have not completed the required Microsoft 365 tenant reauthorization should follow the instructions here: https://saasprotection.datto.com/help/M365/Content/Troubleshooting/General/ews-to-graph.html 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/

2. monitoring Oct 02, 2026, 08:23 PM UTC

   Backup performance and success rates continue to improve as additional optimizations are deployed across Datto SaaS Protection environments. Current efforts are focused on further enhancing backup performance and reliability, including continued improvements to help mitigate the impact of Microsoft service throttling. Overall trends remain positive, and we expect continued improvements as optimization efforts progress. Backup cadence remains unchanged: V2: All Microsoft 365 services back up three times daily. V3: Exchange backs up three times daily; SharePoint, OneDrive, and Teams remain at one backup per day while optimization efforts continue. We will continue to monitor results closely and provide additional updates as further improvements are deployed.

3. monitoring Oct 05, 2026, 03:44 PM UTC

   Backup success rates improved significantly over the weekend following the latest optimization efforts, and overall performance remains on a positive trend. The large majority of SaaS Protection customer accounts are processing backups normally, while engineering teams continue to implement additional post-Microsoft Graph migration improvements for environments that may still experience reduced backup performance across some Microsoft 365 services. To help maintain high backup success rates as optimization efforts progress, backup cadence remains unchanged: V2: All Microsoft 365 services back up three times daily. V3: Exchange backs up three times daily; SharePoint, OneDrive, and Teams remain at one backup per day. We will continue to monitor performance closely and provide further updates as additional improvements are implemented.

4. monitoring Oct 07, 2026, 08:13 PM UTC

   Backup success rates continue to trend positively and are returning to normal levels across SaaS Protection environments as additional post-Microsoft Graph migration improvements are deployed. Most customer accounts are now processing backups normally, and overall platform performance has continued to improve. Engineering teams remain focused on implementing additional enhancements and monitoring performance closely to ensure continued improvements. We will provide further updates as progress continues.

5. monitoring Oct 13, 2026, 07:20 PM UTC

   Backup success rates have largely returned to normal operating levels and remain stable across SaaS Protection environments. The vast majority of customer accounts are processing backups successfully, while ongoing optimization efforts continue to further improve consistency across the platform. As part of these improvements, backup cadence has now been standardized across all Microsoft 365 workload types and environments to three backups per day. Engineering teams will continue to monitor platform performance closely to ensure sustained stability and reliability.

6. monitoring Oct 15, 2026, 06:49 PM UTC

   Following a recent platform update, some SaaS Protection environments across multiple regions experienced increased Microsoft 365 API throttling, resulting in backup performance degradation and delayed backup processing for a subset of customers. The underlying issue has been addressed, and backup success rates are already trending positively as affected environments work through the existing backlog. Performance is expected to continue improving as processing catches up, and Engineering teams are closely monitoring recovery efforts to ensure a return to normal operating levels for all customers.

7. monitoring Oct 20, 2026, 07:55 PM UTC

   Backup success rates have largely returned to expected operating levels following the recent increase in Microsoft 365 API throttling, and platform performance remains stable across SaaS Protection environments. The vast majority of customer accounts are processing backups successfully, while Engineering teams continue to implement platform optimizations and enhancements to further improve consistency, performance, and overall service reliability.

8. monitoring Oct 27, 2026, 07:50 PM UTC

   All Microsoft 365 workloads continue to be backed up three times per day across all SaaS Protection environments. Backup performance and success rates remain stable for the vast majority of customers as ongoing post-Microsoft Graph migration improvements continue to be deployed. Recent enhancements include improved handling of Microsoft 365 API throttling and additional optimizations to backup processing efficiency, helping to reduce failures, improve recovery from service limitations, and enhance overall backup reliability. These improvements are being rolled out across all environments. Engineering teams are also actively addressing several remaining issues affecting a subset of Microsoft 365 backups and continue to develop and deploy additional enhancements to further improve performance, consistency, and backup completion rates. While these improvements and optimizations continue to be implemented, a subset of customers across multiple regions may still experience delayed or missed backups, or backups that complete with some individual items not backed up. Recent changes have driven continued progress, and teams remain focused on further improving consistency, reliability, and overall platform performance.

9. resolved Nov 02, 2026, 04:03 PM UTC

   The Microsoft Graph API migration has now been completed across all Datto SaaS Protection environments. Following the migration, Engineering has implemented a series of improvements and optimizations that have significantly improved Microsoft 365 backup performance. All Microsoft 365 workloads (Exchange, OneDrive, SharePoint, and Teams) are currently backing as expected across all environments. While the vast majority of customers are experiencing expected backup performance, Engineering continues to investigate and address a subset of known issues that may still impact some customers. These issues are separate from the migration itself and include scenarios where backups may be delayed, missed, or complete with certain individual items not backed up. With the Microsoft Graph API migration now complete, we are closing this incident. Engineering continues to address the remaining known issues and deliver ongoing improvements and optimizations across the Datto SaaS Protection platform. If you continue to experience delayed or missed backups, items not backed up, or believe you may be encountering a new or different issue, please contact Support so our teams can review your environment and ensure any applicable cases are associated with the appropriate ongoing investigations: https://helpdesk.kaseya.com/hc/en-gb#/contact Customers who have not yet completed the required Microsoft 365 tenant reauthorization should follow the instructions available here: https://saasprotection.datto.com/help/M365/Content/Troubleshooting/General/ews-to-graph.html

Read the full incident report →