Datto outage history

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

This incident has been resolved.

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/

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.

This incident has been resolved.

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/

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.

This incident has been resolved.

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/

This incident has been resolved.

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.

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.

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.

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.

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.

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/

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

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.

This incident has been resolved.

Two critical vulnerabilities were disclosed in third-party PHP libraries that allow unauthenticated remote code execution. Kaseya security teams are assessing all Kaseya systems and products and applying fixes as they become available. This page is the source of truth for Kaseya status and guidance. Product Status: All products: Customer action: none Kaseya corporate infrastructure: Customer action: none Third-party components in Kaseya products: Customer action: none

Kaseya is aware of two critical vulnerabilities in PHP: CVE-2026-109618 and CVE-2026-109619. CVE-2026-109618 involves a remote code execution vulnerability where handling out-of-memory errors via longjmp() leaves request memory uninitialized due to improper control flow management, potentially allowing attackers to achieve remote code execution using out-of-memory (OOM) triggers. CVE-2026-109619 describes a remote code execution vulnerability where longjmp() fatal error handling leaves global memory pointing to freed memory regions. These regions can later be accessed during subsequent requests, potentially enabling arbitrary code execution. Kaseya has completed an evaluation of its product portfolio regarding these vulnerabilities. A summary of the current status across impacted products and services is provided in the table below. As our investigation and remediation efforts continue, we will keep the following list updated with the latest information. Here is what each status means: Fully Patched: The fix has been applied. Compensating Controls: The product is impacted, protective controls are in place, and we are working to remediate. Unaffected: The product is not affected by these vulnerabilities. Product Status: AudIT - Unaffected Autotask PSA - Fully Patched Datto Backup for Azure Files + Blob Storage - Unaffected BMS - Fully patched Connect Booster - Unaffected Datto Backup For Azure - Unaffected Datto BCDR - Compensating Controls Datto Direct to Cloud Products - Compensating Controls Datto EDR - Unaffected Datto Networking - Compensating Controls Datto Partner Portal - Compensating Controls Datto RMM - Fully Patched Datto SaaS Defense - Unaffected Datto SaaS Protection + Backupify - Compensating Controls Datto Workplace + File Protect - Compensating Controls Endpoint Backup V2 - Fully Patched Graphus - Unaffected ID Agent - Compensating Controls Inky - Unaffected IT Glue - Unaffected Kaseya One - Unaffected Kaseya Quote Manager - Compensating Controls Kaseya MDM - Unaffected Microsoft Entra Backup - Unaffected MyITProcess - Unaffected Passly - Unaffected RapidFire Tools - Compensating Controls RocketCyber - Compensating Controls SaaS Alerts -Unaffected Secure Payments - Compensating Controls Spanning - Compensating Controls Unitrends - Compensating Controls UniView - Unaffected vPenTest - Fully Patched VSA 10 - Fully Patched VSA 9 - Compensating Controls We will continue to provide updates as additional information becomes available. For additional questions, please create a ticket with our Support team here: https://helpdesk.kaseya.com/hc/en-gb#/contact

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/

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

This incident has been resolved.

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/

A third party vendor, ConnectWise, recently reported attempts of unauthorized access associated with the ConnectWise Cloud Backup environment. ConnectWise has initiated their incident response procedures, and have applied containment measures as they continue to investigate. At this time, according to ConnectWise there is no indication that ConnectWise partner backup data has been accessed. All additional updates related to this incident can be found on the ConnectWise Status Page at status.connectwise.com. As part of our ongoing security monitoring efforts, the Kaseya Security Operations Center deployed additional detection measures on October 16, 2026, targeting publicly disclosed indicators of compromise. Activity matching these indicators is automatically designated as critical severity and promptly reviewed by our security analysts. The Kaseya product team has also deployed a fortify action within SaaS Alerts and KSIEM environments to help mitigate this risk further. Please follow the steps below to apply the fortify action: Action Name: Disable ConnectWise Cloud Backup and Cloud Management apps Steps to Deploy within SaaS Alerts and KSIEM portal: Within the left menu, under "Modules", select Fortify → Actions, then perform the following: 1. Set Select Product to Microsoft. 2. Set Select Organization to the customer's org (or leave it on All), and leave Select Actions on All. 3. Click Show Actions. 4. Search for Disable ConnectWise Cloud Backup and Cloud Management apps in the search box. 5. Under the action's buttons, click the wand icon labelled Apply. If you feel you have been compromised due to this issue, please contact Kaseya support.

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/

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.

This incident has been resolved.

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/

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

This incident has been resolved.

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/

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

This incident has been resolved.

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/

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/

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/

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/

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

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.

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

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/

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

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.

This incident has been resolved.

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/

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

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.

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/

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

This incident has been resolved.

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/

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.

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.

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.

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.

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.

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.

We are currently experiencing service disruption for the below mentioned server, where administrators may be unable to login to UI. Our team is actively working to restore functionality at this time. We apologize for any inconvenience. - Cloud Operations Team

We are continuing to investigate this issue.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

We are aware of a problem where Kaseya Quote Manager users get a 504 Azure Front Door error, and potential slowness if able to access KQM. 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/

This incident has been resolved.