Kaseya Outage History

Started Sep 17, 2026, 07:33 AM UTC· resolved Sep 17, 2026, 09:34 AM UTC

1. investigating Sep 17, 2026, 07:33 AM UTC

   We are experiencing a service disruption on remotecarece3, where administrators may be unable to login to Ui. Our team is working to restore the functionality on the affected instances at this time. We apologize for any inconvenience. - Cloud Operations Team

2. monitoring Sep 17, 2026, 07:59 AM UTC

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

3. resolved Sep 17, 2026, 09:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 07:39 PM UTC· resolved Sep 18, 2026, 02:56 PM UTC

1. investigating Sep 16, 2026, 07:39 PM UTC

   We are aware of a problem where Datto Endpoint Backup for PC users paired to Cloud Device 299242 can experience degraded backup and recovery performance. The Kaseya Engineering Team is currently investigating the issue and working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Sep 16, 2026, 11:01 PM UTC

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

3. resolved Sep 18, 2026, 02:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 01:14 PM UTC· resolved Sep 16, 2026, 04:28 PM UTC

1. investigating Sep 16, 2026, 01:14 PM UTC

   We are aware of a problem where a subset of Datto Endpoint Backup and Datto Endpoint Backup for PCs nodes in the UK region are currently experiencing intermittent connectivity issues, which may impact backup and recovery operations. The Kaseya Engineering Team is currently investigating the issue and working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Sep 16, 2026, 01:56 PM UTC

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

3. resolved Sep 16, 2026, 04:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 09:06 AM UTC· resolved Sep 16, 2026, 03:20 PM UTC

1. identified Sep 16, 2026, 09:06 AM UTC

   We are currently experiencing a partial service disruption affecting some KaseyaOne and Kaseya Store functionality. Customers may experience issues when viewing or managing Subscriptions and when accessing the Professional Services page. This disruption is related to an ongoing global Salesforce service disruption. Our Engineering team is actively monitoring the situation and its impact on KaseyaOne and Kaseya Store services. We will provide further updates as more information becomes available. Thank you for your patience and understanding.

2. identified Sep 16, 2026, 10:31 AM UTC

   We continue to monitor the status of the Salesforce service disruption and its effects on our services. The Kaseya Store appears to have recovered, however, some KaseyaOne functionalities are still impacted by the issue.

3. monitoring Sep 16, 2026, 01:02 PM UTC

   The Engineering team confirmed that we no longer see issues related to either KaseyaOne or Kaseya Store functionality; both services are healthy now. We continue to monitor the situation to ensure we promptly detect and advise of any regressions, should they occur, while the Salesforce Service Status is not marked as fully resolved.

4. resolved Sep 16, 2026, 03:20 PM UTC

   After continued monitoring, KaseyaOne and Kaseya Store services have remained healthy. This issue is resolved.

Read the full incident report →

Started Sep 15, 2026, 01:02 PM UTC· resolved Sep 15, 2026, 03:38 PM UTC

1. investigating Sep 15, 2026, 01:02 PM UTC

   We are aware of a problem where Datto BCDR users paired to Server3188 in the Canada region are experiencing degraded offsite capabilities. The Kaseya Engineering Team is currently investigating the issue and working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. resolved Sep 15, 2026, 03:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 04:53 PM UTC· resolved Sep 14, 2026, 07:58 PM UTC

1. investigating Sep 14, 2026, 04:53 PM UTC

   We are aware of a problem where Spanning customers hosted in the CA and AP regions are currently unable to login to their accounts. 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 Sep 14, 2026, 06:34 PM UTC

   Following the identification of issues affecting customer account access in the Canada and Asia-Pacific regions, further investigation determined that customers in the US region were also impacted. A fix has been deployed, and full access to Spanning accounts has been restored across all affected regions. Our R&D team is monitoring for any other issues.

3. resolved Sep 14, 2026, 07:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 03:05 PM UTC· resolved Sep 14, 2026, 06:47 PM UTC

1. investigating Sep 14, 2026, 03:05 PM UTC

   We are aware of a problem where US-based users are currently unable to authenticate to US-hosted cells. The Kaseya R&D Team is currently investigating the issue and working towards a resolution. 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 here: 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 14, 2026, 03:20 PM UTC

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

3. resolved Sep 14, 2026, 06:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 12:56 PM UTC· resolved Sep 14, 2026, 02:03 PM UTC

1. investigating Sep 14, 2026, 12:56 PM UTC

   We are aware of a problem where Datto Networking users are currently unable to create Fabric Tunnels through Network Manager. 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 14, 2026, 02:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 12:46 PM UTC· resolved Sep 14, 2026, 05:53 PM UTC

1. investigating Sep 14, 2026, 12:46 PM UTC

   We are aware of a problem where Datto SaaS Protection Partners are unable to access their customer accounts due to the SaaS Protection Status Page within the Datto Partner Portal not loading customer details. The Kaseya Engineering Team is actively 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. investigating Sep 14, 2026, 02:30 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 14, 2026, 02:51 PM UTC

   Our R&D team has identified the issue and have deployed configuration changes to allow the SaaS Protection Status Page within the Datto Partner Portal to load customer details again as well as restore customer account access for all affected partners. The team is closely monitoring the results of the changes made.

4. monitoring Sep 14, 2026, 04:40 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Sep 14, 2026, 05:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 09:21 AM UTC· resolved Sep 14, 2026, 11:57 AM UTC

1. identified Sep 14, 2026, 09:21 AM UTC

   We are aware of a problem where the inbound email parser is not creating items in the target Autotask PSA database on the DE1 and EU1 zones. The Kaseya Engineering Team is working on resolving 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 Sep 14, 2026, 10:40 AM UTC

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

3. monitoring Sep 14, 2026, 11:23 AM UTC

   The system is currently working through items that queued up during this issue, therefore incoming email processing may still be delayed.

4. resolved Sep 14, 2026, 11:57 AM UTC

   The system finished processing the remaining items in the queue, and the Incoming Email Processing is currently creating designated items in real time. This incident is resolved.

Read the full incident report →

Started Sep 10, 2026, 09:38 AM UTC· resolved Sep 23, 2026, 03:08 PM UTC

1. monitoring Sep 10, 2026, 09:38 AM UTC

   The Kaseya R&D Team responded to alerts related to the eu.rocketcyber.com site. The incident lasted for about 30 minutes during which Rocketcyber customers hosted in the EU region were not able to access the product. The issue is now resolved, and we are currently monitoring the health of the service.

2. resolved Sep 23, 2026, 03:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 12:51 PM UTC· resolved Sep 29, 2026, 07:45 PM UTC

1. investigating Sep 09, 2026, 12:51 PM UTC

   We are experiencing service disruption on PHILKAS01 Server, which may impact administrators ability to manage endpoints. We are aware of the issue, and our team is actively working to resolve the same. We apologize for any inconvenience. - Kaseya Cloud Operations Team

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

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

3. identified Sep 09, 2026, 05:04 PM UTC

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

4. monitoring Sep 09, 2026, 08:17 PM UTC

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

5. monitoring Sep 09, 2026, 11:23 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring Sep 14, 2026, 01:47 PM UTC

   We are experiencing service disruption on PHILKAS01 Server, which may impact administrators ability to manage endpoints. We are aware of the issue, and our team is actively working to resolve the same. We apologize for any inconvenience. - Kaseya Cloud Operations Team

7. resolved Sep 29, 2026, 07:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2026, 07:43 PM UTC· resolved Sep 09, 2026, 12:54 PM UTC

1. investigating Sep 08, 2026, 07:43 PM UTC

   We are aware of a problem where Datto BCDR users paired to Server5465 can experience degraded offsite performance. 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/

2. monitoring Sep 08, 2026, 08:11 PM UTC

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

3. resolved Sep 09, 2026, 12:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2026, 07:10 PM UTC· resolved Sep 17, 2026, 02:30 PM UTC

1. investigating Sep 08, 2026, 07:10 PM UTC

   We are aware of a problem where Datto BCDR users paired to Server2214 can experienced degraded offsite performance. 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/

2. identified Sep 09, 2026, 12:54 PM UTC

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

3. resolved Sep 17, 2026, 02:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2026, 12:43 PM UTC· resolved Sep 04, 2026, 07:40 PM UTC

1. identified Sep 04, 2026, 12:43 PM UTC

   We are aware of a problem where users on UK01 and UK02 who use Outlook as their email service are not having their Emails be sent and received. The Kaseya Engineering Team have identified the issue and are working with Microsoft to resolve it. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. resolved Sep 04, 2026, 07:40 PM UTC

   Microsoft has fixed the issue with receiving email from external domains. We have verified that emails are now getting processed without issue. This incident is resolved.

Read the full incident report →

Started Sep 03, 2026, 07:20 PM UTC· resolved Sep 04, 2026, 02:06 PM UTC

1. investigating Sep 03, 2026, 07:20 PM UTC

   We are aware of a problem where Datto Endpoint Backup for PC users hosted on Cloud Siris 299242 may experience degraded backup and recovery performance.. 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/

2. monitoring Sep 04, 2026, 12:11 PM UTC

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

3. resolved Sep 04, 2026, 02:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 09:11 PM UTC· resolved Sep 02, 2026, 11:17 PM UTC

1. identified Sep 02, 2026, 09:11 PM UTC

   We're aware of an issue preventing Secure Edge administrators from viewing recent usage information within Datto Network Manager. We've identified the root cause of the issue. Queued data has resumed processing and we're expecting metrics to become available again within a few hours. We will update this post as we continue to monitor and work through the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. resolved Sep 02, 2026, 11:17 PM UTC

   The issue preventing Secure Edge administrators from viewing recent usage information within Datto Network Manager has been resolved. Queued data has finished processing, and usage metrics are now available as expected. We appreciate your patience while we worked through this issue. Subscribe to the Kaseya Status Page for up to date information at https://status.kaseya.com/

Read the full incident report →

Started Sep 02, 2026, 08:33 PM UTC· resolved Sep 11, 2026, 03:06 PM UTC

1. investigating Sep 02, 2026, 08:33 PM UTC

   We are aware of a problem where some customers hosted on pod 'aue1-saas-p0' are currently experiencing degraded backup performance for Exchange services. 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. identified Sep 02, 2026, 08:56 PM UTC

   Our R&D team has identified the issue and have started deploying changes to mitigate the Exchange backup performance issues for customers hosted on pod 'aue1-saas-p0'

3. identified Sep 03, 2026, 01:40 PM UTC

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

4. identified Sep 03, 2026, 07:31 PM UTC

   Following the recent changes deployed by our R&D team, we are seeing improvements in Exchange backup success rates for customers hosted on pod 'aue1-saas-p0'. Our team remains actively engaged and continues to work on further improvements while closely monitoring the environment.

5. monitoring Sep 04, 2026, 04:47 PM UTC

   Following additional changes deployed by our R&D team, we are seeing continued improvement in Exchange backup success rates for customers hosted on pod 'aue1-saas-p0'. Our team is closely monitoring the environment as backup processing and success rates continue to recover.

6. resolved Sep 11, 2026, 03:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 10:10 AM UTC· resolved Sep 08, 2026, 04:26 PM UTC

1. investigating Sep 02, 2026, 10:10 AM UTC

   We are aware of a problem where Cloud Virtualizations are hindered for some of our partners due to not being able to change power states on virtual machines in Datto BCDR. 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. investigating Sep 02, 2026, 11:27 AM UTC

   We are continuing to investigate this issue.

3. investigating Sep 02, 2026, 12:32 PM UTC

   The Kaseya Systems Engineering Team is continuing to investigate the issue.

4. identified Sep 02, 2026, 01:10 PM UTC

   The Kaseya Systems Engineering Team identified the issue and they are working on resolving the problem.

5. identified Sep 03, 2026, 02:42 PM UTC

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

6. identified Sep 03, 2026, 02:51 PM UTC

   The remediation has been identified and is currently being deployed to the affected nodes in a phased rollout to ensure a controlled and efficient resolution.

7. identified Sep 04, 2026, 02:19 PM UTC

   The majority of BCDR servers have been successfully restored and are operating normally. A limited number of servers remain under remediation, and Engineering teams are actively working to complete recovery efforts and return all impacted systems to full operational status.

8. monitoring Sep 04, 2026, 06:44 PM UTC

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

9. resolved Sep 08, 2026, 04:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 06:00 AM UTC· resolved Sep 02, 2026, 10:11 AM UTC

1. investigating Sep 02, 2026, 06:00 AM UTC

   We are aware of an issue where customers are encountering 500 errors while accessing Backup & RMM products within the Datto Partner Portal (DPP). The Kaseya R&D Team is investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Sep 02, 2026, 07:30 AM UTC

   We are pleased to inform you that the recent service incident experienced by our BCDR AND DRMM partners where users experienced difficulties logging into the Datto Partner Portal has now been successfully resolved. We understand the impact that such problems can have on your business operations, and we sincerely apologize for any inconvenience caused during this time. Our team has been diligently working to identify the root cause of the problem. Our goal is to not only address the immediate concern but also to minimize the risk of similar incidents in the future. By analyzing the underlying factors, we aim to enhance our systems and processes, ensuring a more robust and reliable experience for all our partners. Thank you for your patience and understanding. We remain committed to delivering exceptional service and continuous improvement.

3. monitoring Sep 02, 2026, 08:40 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Sep 02, 2026, 10:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 09:49 PM UTC· resolved Sep 02, 2026, 04:51 PM UTC

1. monitoring Sep 01, 2026, 09:49 PM UTC

   A recent degradation with Intuit's QuickBooks Online has been reported by Intuit. This is currently affecting API calls which may result in sync failures causing delays in data syncing to and from QBO and ConnectBooster. Our team is currently monitoring the status of this from Intuit's Status Page which can be found here: https://status.developer.intuit.com/ At this time, a valid workaround is not available, and we recommend that you subscribe to Intuit's Status Page for immediate updates. Our team will continue to provide status updates as they are received to the status page. Thank you,

2. monitoring Sep 02, 2026, 03:00 AM UTC

   Intuit has updated their status page stating that this is a Major Outage within the Intuit system. They are still investigating the issue. This is currently affecting API calls resulting in sync failures causing delays in data syncing to and from QBO and ConnectBooster. Our team is continuing to monitor the status of this from Intuit's Status Page which can be found here: https://status.developer.intuit.com/ At this time, a valid workaround is not available, and we recommend that you subscribe to Intuit's Status Page for immediate updates. Our team will continue to provide status updates as they are received to the status page

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

   Intuit has reported that API functionality has returned, and calls should be completing as expected. Our internal teams have confirmed that syncs are running now running as expected. We advise Partners to compare data between ConnectBooster, and QuickBooks Online to ensure the data is up to date, and if not, to set their sync date back to 9/1/2026 - 1pm which was prior to the outage being reported by Intuit and allow for an accounting package sync to take place. Thank you,

4. resolved Sep 02, 2026, 04:51 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 12:13 PM UTC· resolved Sep 01, 2026, 01:27 PM UTC

1. investigating Sep 01, 2026, 12:13 PM UTC

   We are aware of a problem where the Datto SaaS Protection Status Page is not loading details for some of our users. 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 Sep 01, 2026, 12:52 PM UTC

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

3. resolved Sep 01, 2026, 01:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 11:37 AM UTC· resolved Sep 01, 2026, 03:56 PM UTC

1. investigating Sep 01, 2026, 11:37 AM UTC

   We are aware of a problem where users are unable to access the Vidal platform The Kaseya Engineering Team is actively investigating and we will provide updates as more information becomes available. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. monitoring Sep 01, 2026, 12:35 PM UTC

   The Kaseya Engineering Team has issued a fix. Service has been restored, and we are monitoring the environment to ensure continued stability.

3. resolved Sep 01, 2026, 03:56 PM UTC

   The issue affecting access to the Datto RMM Vidal platform has been resolved.

Read the full incident report →

Started Aug 31, 2026, 04:01 PM UTC· resolved Aug 31, 2026, 05:34 PM UTC

1. investigating Aug 31, 2026, 04:01 PM UTC

   We are aware of a problem where Datto Workplace users in the U.S. region hosted on Cells 1, 6, and 15 may experience intermittent service connectivity disruptions, resulting in degraded access to Workplace services. The Kaseya Engineering Team is 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 Aug 31, 2026, 04:12 PM UTC

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

3. resolved Aug 31, 2026, 05:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 28, 2026, 05:13 PM UTC· resolved Aug 28, 2026, 06:23 PM UTC

1. investigating Aug 28, 2026, 05:13 PM UTC

   We are experiencing service disruption on EU - VSA114 Server, which may impact administrators ability to manage endpoints. We are aware of the issue, and our team is actively working to resolve the same. We apologize for any inconvenience. - Kaseya Cloud Operations Team

2. investigating Aug 28, 2026, 05:16 PM UTC

   We are continuing to investigate this issue.

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

   This incident has been resolved.

Read the full incident report →