Kaseya Outage History

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, 09:51 PM UTC· resolved Oct 22, 2026, 06:35 PM UTC

1. investigating Oct 21, 2026, 09:51 PM UTC

   Two critical vulnerabilities in PHP 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

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.

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:47 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 17, 2026, 08:28 PM UTC· resolved Oct 22, 2026, 03:30 PM UTC

1. monitoring Oct 17, 2026, 08:28 PM UTC

   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.

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:15 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, 12:03 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 Oct 01, 2026, 07:10 AM 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/

Read the full incident report →

Started Sep 30, 2026, 02:51 PM UTC· resolved Sep 30, 2026, 05:03 PM UTC

1. investigating Sep 30, 2026, 02:51 PM UTC

   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

2. investigating Sep 30, 2026, 02:58 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 30, 2026, 03:30 PM UTC

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

4. monitoring Sep 30, 2026, 03:31 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Sep 30, 2026, 05:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2026, 12:25 AM UTC· resolved Sep 30, 2026, 01:03 AM UTC

1. investigating Sep 30, 2026, 12:25 AM UTC

   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/

2. resolved Sep 30, 2026, 01:03 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 04:18 PM UTC· resolved Sep 28, 2026, 11:39 PM UTC

1. identified Sep 28, 2026, 04:18 PM UTC

   We are aware of a problem where some users are experiencing intermittent sync and access issues within their ConnectBooster portals. The Kaseya Engineering Team have Identified the issue are 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 Sep 28, 2026, 10:56 PM UTC

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

3. resolved Sep 28, 2026, 11:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 03:11 PM UTC· resolved Sep 29, 2026, 02:55 PM UTC

1. investigating Sep 28, 2026, 03:11 PM UTC

   We are aware of a problem where Datto RMM's 15.1.1 Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint. The Kaseya Engineering Team is investigating this issue with Microsoft. 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 Sep 28, 2026, 07:40 PM UTC

   Our team remains actively engaged with Microsoft to investigate reports of false-positive detections occurring after devices were updated to Datto RMM Agent version 15.1.1 and to support remediation efforts where needed. At this time, the issue appears to be related to a security detection classification and not confirmed as malicious activity within the Datto RMM agent. We will continue to share updates as additional 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/

3. monitoring Sep 28, 2026, 10:10 PM UTC

   A fix has been implemented and we are monitoring the results. The Kaseya R&D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.1.1 Datto RMM version's cagservice.exe in a recent security intelligence update for Microsoft Defender Antivirus and other Microsoft antimalware. This issue was fixed in the security intelligence update version 1.459.450.0, and the issue should no longer occur on device's with this definition version or later. Microsoft currently does not offer an automated way to revert the quarantining of a file, therefore manual action is required to bring affected devices back online in Datto RMM. We recommend our partners to ensure that devices are updated with security intelligence version 1.459.450.0 or later to avoid the agent being falsely flagged as malicious by Microsoft antimalware. Users can use the below commands and instructions to ensure that the latest security intelligence update is installed on the device to prevent the behavior: Updating the security intelligence version: - PowerShell: Update-MpSignature - Command Prompt (CMD): MpCmdRun.exe -SignatureUpdate After running the update, users can verify the installed version with the following command: - Get-MpComputerStatus | Select-Object AntivirusSignatureVersion, AntivirusSignatureLastUpdated

4. resolved Sep 29, 2026, 02:55 PM UTC

   This incident has been resolved after monitoring overnight. As previously stated, this issue was fixed in the security intelligence update version 1.459.450.0, and should no longer occur on device's with this definition version or later. Please see the earlier communication for further details.

Read the full incident report →

Started Sep 28, 2026, 01:28 PM UTC· resolved Sep 28, 2026, 06:17 PM UTC

1. investigating Sep 28, 2026, 01:28 PM UTC

   We are aware of a problem where LiveMobile is inaccessible on Android devices across all regions. 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 Sep 28, 2026, 02:39 PM UTC

   The issue has been identified and a fix is being implemented. When logging into Autotask on the web, to ensure the best connectivity to your Autotask instance, please double check your configuration to ensure that the zone specific (ww# or ww##) URL is being used.

3. monitoring Sep 28, 2026, 03:34 PM UTC

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

4. monitoring Sep 28, 2026, 05:08 PM UTC

   Monitoring post release detected an issue with the Autotask and Datto RMM integration. This issue caused tickets to fail to create from Datto RMM, prevented access to the Autotask integration settings in Datto RMM, and prevented new monitor creation in Datto RMM when the option to "Create a Ticket" was set. A new fix has been deployed to correct these issues and we will continue to monitor the results.

5. resolved Sep 28, 2026, 06:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 09:06 AM UTC· resolved Sep 28, 2026, 12:55 PM UTC

1. investigating Sep 28, 2026, 09:06 AM UTC

   We are aware of a problem where Quotes and Sales Orders created in Kaseya Quote Manager are not syncing over to Autotask. The Kaseya Engineering Team are aware of the issue and are currently investigating further. 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 Sep 28, 2026, 11:27 AM UTC

   The Engineering Team identified the issue that caused the sync requests for both the Autotask PSA and ConnectWise PSA integrations to queue up. Mitigation measures have been applied to increase the throughput to help with processing the queue.

3. monitoring Sep 28, 2026, 12:02 PM UTC

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

4. resolved Sep 28, 2026, 12:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 07:21 AM UTC· resolved Sep 24, 2026, 09:34 AM UTC

1. investigating Sep 24, 2026, 07:21 AM UTC

   We are aware of a problem where latency and error messages are being observed when navigating the Autotask UI. The Kaseya Engineering Team is aware of this behaviour and is currently 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. identified Sep 24, 2026, 08:11 AM UTC

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

3. monitoring Sep 24, 2026, 08:37 AM UTC

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

4. resolved Sep 24, 2026, 09:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 22, 2026, 07:51 PM UTC· resolved Sep 23, 2026, 03:00 PM UTC

1. investigating Sep 22, 2026, 07:51 PM UTC

   We are aware of a problem where RocketCyber users, who attempt to switch Organizations are encountering the following error, preventing users from being able to switch Organizations: Access Blocked [Organization name] does not have SSO enabled for this KaseyaOne Tenant To access this account, login directly at https://app.rocketcyber.com(US) or https://eu.rocketcyber.com(EU) RocketCyber's monitoring capabilities are unaffected and will continue to gather and send data to the RocketCyber platform. The Kaseya R&D Team is currently investigating and we will provide an update as soon as we have more information.

2. monitoring Sep 22, 2026, 11:47 PM UTC

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

3. resolved Sep 23, 2026, 03:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 05:21 PM UTC· resolved Sep 23, 2026, 02:04 PM UTC

1. identified Sep 21, 2026, 05:21 PM UTC

   We are aware of a problem where Server4715 is undergoing unscheduled maintenance. The Kaseya Engineering Team has identified the problem and are replacing faulted hardware. During this time offsite synchronization and virtual machine performance will be impacted. 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 07, 2026, 01:26 PM UTC

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

3. monitoring Oct 12, 2026, 01:02 PM UTC

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

4. resolved Oct 12, 2026, 04:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 05:40 AM UTC· resolved Sep 21, 2026, 08:01 PM UTC

1. investigating Sep 21, 2026, 05:40 AM UTC

   We are aware of a problem where Datto SaaS Protection Partners were receiving a 500 error when attempting to access the SaaS Protection Status Page within the Datto Partner Portal. The Kaseya Engineering Team has been involved and they are investigating the issue.

2. identified Sep 21, 2026, 08:47 AM UTC

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

3. monitoring Sep 21, 2026, 08:55 AM UTC

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

4. identified Sep 21, 2026, 09:25 AM UTC

   The system is recovering after the R&D team took steps to resolve the issue. Some customer may still experience issues accessing the SaaS Protection Status Page while the system is recovering.

5. monitoring Sep 21, 2026, 06:56 PM UTC

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

6. resolved Sep 21, 2026, 08:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 20, 2026, 01:33 PM UTC· resolved Sep 21, 2026, 12:52 PM UTC

1. investigating Sep 20, 2026, 01:33 PM UTC

   We are aware of a problem where Datto BCDR users associated with Server5465 may experience disruptions affecting offsite synchronization and offsite restore operations. The Kaseya R&D Team is currently investigating the issue and working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Sep 20, 2026, 03:42 PM UTC

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

3. resolved Sep 21, 2026, 12:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 17, 2026, 04:05 PM UTC· resolved Sep 18, 2026, 03:39 PM UTC

1. investigating Sep 17, 2026, 04:05 PM UTC

   We are aware of a problem where Datto Networking users are experiencing throttling despite the network's pooled data cap remaining below the configured threshold. The Kaseya Engineering Team is currently investigating this 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 Sep 17, 2026, 08:57 PM UTC

   We have identified the root cause of the issue regarding Datto Networking users experiencing throttling despite the network's pooled data cap remaining below the configured threshold. We are currently monitoring for any new individual cases, however the issue is currently resolved. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

3. resolved Sep 18, 2026, 03:39 PM UTC

   This incident has been resolved.

Read the full incident report →