Kaseya Outage History

Kaseya degraded · 2 active incidents View live status →

Kaseya had 40 outages in the last 2 years totaling 3039h 47m of downtime — averaging 1.6 incidents per month.

There were 40 Kaseya outages since March 24, 2026 totaling 3039h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kaseya.net

Minor May 4, 2026

Datto Networking - Intermittent Check‑In Failures Observed on Datto Networking D200 Devices

Detected by Pingoru
May 04, 2026, 05:24 PM UTC
Resolved
May 05, 2026, 07:34 PM UTC
Duration
1d 2h
Timeline · 3 updates
  1. investigating May 04, 2026, 05:24 PM UTC

    We are aware of a problem where Datto Networking D200 devices may intermittently fail to check in, resulting in false‑positive offline email alerts. Please note: The observed issue is cosmetic and does not affect the functionality or performance of the device. The Kaseya R&D Team is 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 May 05, 2026, 01:07 PM UTC

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

  3. resolved May 05, 2026, 07:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 4, 2026

Datto SaaS Protection - Service disruption for customers hosted on node 'Gbe2-saas-p0-app-2'

Detected by Pingoru
May 04, 2026, 11:52 AM UTC
Resolved
May 05, 2026, 12:19 PM UTC
Duration
1d
Timeline · 3 updates
  1. investigating May 04, 2026, 11:52 AM UTC

    We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection services. Backups are still operational, but the platform is unable to be accessed. The Kaseya R&D Team is investigating the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 04, 2026, 01:07 PM UTC

    The Kaseya R&D team has implemented changes to help address the issue and are monitoring the results closely.

  3. resolved May 05, 2026, 12:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 30, 2026

Datto SaaS Protection - Service disruption for customers hosted on pod 'cae1-saas-p1'

Detected by Pingoru
Apr 30, 2026, 10:31 PM UTC
Resolved
May 01, 2026, 03:24 PM UTC
Duration
16h 52m
Timeline · 5 updates
  1. identified Apr 30, 2026, 10:31 PM UTC

    We are aware of a problem where customers hosted on pod 'cae1-pod-1' are experiencing a disruption to their SaaS Protection services. Our R&D team is performing maintenance on pod 'cae1-pod-1' to resolve an issue that was identified. The estimated down time is up to 8 hours. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 01, 2026, 05:17 AM UTC

    Our R&D team has implemented a fix to address the issue impacting the pod. We are actively monitoring the node for any other issues.

  3. monitoring May 01, 2026, 06:32 AM UTC

    Backup success rates have improved since a fix has been implemented. Our R&D continues to monitor the health of the pod until expected levels are reached.

  4. monitoring May 01, 2026, 12:36 PM UTC

    Backup success rates on the pod have returned to normal and remain stable. Our R&D team is continuing to monitor.

  5. resolved May 01, 2026, 03:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

Datto SaaS Protection - Backup performance and access issues for customers hosted on node 'gbe2-bfyii-1225'

Detected by Pingoru
Apr 30, 2026, 04:38 PM UTC
Resolved
May 01, 2026, 12:33 PM UTC
Duration
19h 54m
Timeline · 3 updates
  1. identified Apr 30, 2026, 04:38 PM UTC

    We are aware of a problem where customers hosted on node 'gbe2-bfyii-1225' are experiencing degraded backup performance for SharePoint/Teams services as well as receiving 504 errors when attempting to access their SaaS Protection accounts. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Apr 30, 2026, 07:36 PM UTC

    Our R&D team has implemented a fix to address the SaaS Protection account access issues and customers should no longer receive a 504 error when logging in. We are actively monitoring the node for any other issues.

  3. resolved May 01, 2026, 12:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

Datto SaaS Protection - Backup performance degradation for M365 services on pod 'usw3-saas-p1'

Detected by Pingoru
Apr 29, 2026, 02:30 PM UTC
Resolved
Apr 30, 2026, 12:59 PM UTC
Duration
22h 29m
Timeline · 3 updates
  1. identified Apr 29, 2026, 02:30 PM UTC

    We are currently aware of a problem where some Datto SaaS Protection customers hosted on pod 'usw3-saas-p1' are experiencing degraded backup performance for some M365 services. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Apr 29, 2026, 04:37 PM UTC

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

  3. resolved Apr 30, 2026, 12:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 28, 2026

Datto RMM - Zinfandel - Agents going offline

Detected by Pingoru
Apr 28, 2026, 09:47 PM UTC
Resolved
Apr 29, 2026, 08:16 AM UTC
Duration
10h 28m
Timeline · 3 updates
  1. investigating Apr 28, 2026, 09:47 PM UTC

    We are aware of a problem where Datto RMM agents, within the Zinfandel platform going offline. The Kaseya R&D Team is aware and currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Apr 28, 2026, 10:15 PM UTC

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

  3. resolved Apr 29, 2026, 08:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

Datto RMM - Zinfandel: Delayed Jobs

Detected by Pingoru
Apr 28, 2026, 04:12 PM UTC
Resolved
Apr 28, 2026, 05:31 PM UTC
Duration
1h 18m
Timeline · 3 updates
  1. investigating Apr 28, 2026, 04:12 PM UTC

    We are aware of a problem where Jobs on Datto RMM's Zinfandel platform are delayed 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 Apr 28, 2026, 04:36 PM UTC

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

  3. resolved Apr 28, 2026, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

VSA10 - Service Degradation for subset of VSA10-US customers

Detected by Pingoru
Apr 28, 2026, 03:10 PM UTC
Resolved
May 01, 2026, 12:58 AM UTC
Duration
2d 9h
Timeline · 4 updates
  1. investigating Apr 28, 2026, 03:10 PM UTC

    Subset of VSA10 US customers may be experiencing degraded performance intermittently, 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 caused. - Cloud Operations Team

  2. monitoring Apr 29, 2026, 07:10 AM UTC

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

  3. monitoring Apr 29, 2026, 07:59 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 01, 2026, 12:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 23, 2026

VSA9 - Partial Service Disruption - liveconnect.me

Detected by Pingoru
Apr 23, 2026, 03:58 PM UTC
Resolved
Apr 23, 2026, 08:54 PM UTC
Duration
4h 55m
Affected: VSA 9
Timeline · 4 updates
  1. investigating Apr 23, 2026, 03:58 PM UTC

    We are currently experiencing a partial service disruption affecting a subset of customers using VSA9 LiveConnect (liveconnect.me). Customers may notice issues accessing LiveConnect on-demand services. 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 Apr 23, 2026, 08:00 PM UTC

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

  3. monitoring Apr 23, 2026, 08:00 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Apr 23, 2026, 08:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Datto AV - Agent is unable to perform actions on MacOS devices

Detected by Pingoru
Apr 22, 2026, 03:34 PM UTC
Resolved
Apr 24, 2026, 02:18 PM UTC
Duration
1d 22h
Affected: Datto AV
Timeline · 4 updates
  1. investigating Apr 22, 2026, 03:34 PM UTC

    We are aware of a problem where Datto AV is unable to perform any actions on a MacOS device. The Datto AV Team is currently investigating this issue and is working to deploy a hotfix to correct this behavior. This is our highest priority issue. Unfortunately, there is no workaround that can be applied at this time. Please contact support and they can provide further details as well as add your case to the investigation.

  2. identified Apr 22, 2026, 06:01 PM UTC

    We have identified the root cause of the issue affecting Datto AV actions on macOS devices and are currently validating the fix. Our team plans to deploy this update during the scheduled US maintenance window at 23:00 CST tonight and will actively monitor the rollout to ensure stability. We will provide confirmation once the release is completed and fully validated. We appreciate your patience as we work to fully resolve this issue.

  3. identified Apr 22, 2026, 07:51 PM UTC

    We have identified the root cause of the issue affecting Datto AV actions on macOS devices and are continuing validation of the fix. During final testing, we identified an additional issue that needs to be addressed before release. As a result, we are postponing the deployment and now plan to target the next maintenance window tomorrow (April 23rd). We appreciate your patience as we work to fully resolve this issue.

  4. resolved Apr 24, 2026, 02:18 PM UTC

    This incident has been resolved. Once the devices receive the update, during the maintenance window, they will need to be rebooted for the update to be applied.

Read the full incident report →

Notice April 20, 2026

Service Disruption - BMS US & UK

Detected by Pingoru
Apr 20, 2026, 03:14 PM UTC
Resolved
Apr 20, 2026, 05:20 PM UTC
Duration
2h 6m
Timeline · 2 updates
  1. monitoring Apr 20, 2026, 03:14 PM UTC

    We were experiencing service disruption for BMS US and UK from 10:15 AM ET. The services are back operational from 10:39 AM ET. We are currently monitoring this issue. We Apologize for any inconvenience caused. -Cloud Operations Team

  2. resolved Apr 20, 2026, 05:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 17, 2026

Incident Update – Datto EDR Portal Access (US Region)

Detected by Pingoru
Apr 17, 2026, 02:36 PM UTC
Resolved
Apr 20, 2026, 02:06 PM UTC
Duration
2d 23h
Timeline · 5 updates
  1. monitoring Apr 17, 2026, 02:36 PM UTC

    We experienced a brief issue where some customers in the US region were unable to access the Datto EDR portal. This was due to a temporary service disruption that lasted a few minutes. The issue has been identified and resolved, and access is now restored. We are continuing to monitor the system to ensure stability. We apologize for the disruption and appreciate your patience.

  2. monitoring Apr 17, 2026, 06:12 PM UTC

    We are continuing to monitor. Some partners may still experience a temporary error when attempting to log in or navigate the Datto EDR platform. While service may return to normal on its own after some time, please contact our support team and they can apply a backend workaround that may assist with resolving the issue.

  3. monitoring Apr 17, 2026, 08:10 PM UTC

    Following our earlier update, we are continuing to monitor the environment and have identified additional infrastructure-related pressure contributing to intermittent latency. We are seeing elevated system load driven by increased telemetry and system activity, which can create short-lived performance impacts as services recover. Our team is actively implementing changes to reduce this load and stabilize the platform. We are taking a controlled approach to these changes to avoid further disruption, and performance is trending in the right direction. We will continue to provide updates as we make progress. Thank you again for your patience.

  4. monitoring Apr 17, 2026, 11:31 PM UTC

    We have identified the primary contributor to the recent performance issues and have a mitigation in place that will be deployed during the upcoming maintenance window. The update reduces unnecessary system activity that was creating elevated load and impacting portal responsiveness. Once deployed, this is expected to significantly improve stability. We are also continuing work on additional infrastructure improvements to ensure the platform can handle increased load more efficiently and prevent recurrence. We will provide another update once the mitigation is fully deployed. Thank you for your continued patience.

  5. resolved Apr 20, 2026, 02:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2026

Datto BCDR - Local Virtualization and Verification Will Not Execute Successfully on Windows 2003 and Windows XP 32‑bit Systems

Detected by Pingoru
Mar 24, 2026, 08:11 PM UTC
Resolved
May 14, 2026, 07:41 PM UTC
Duration
50d 23h
Timeline · 3 updates
  1. investigating Mar 24, 2026, 08:11 PM UTC

    We have identified an issue introduced in the latest device software release related to agents running 32 bit versions of Windows Server 2003 and Windows XP where screenshot verification and local virtualization fails to start. We are currently investigating the issue to determine the cause and potential fix. In the meantime, we have verified that cloud virtualizations are still functional for any DR scenarios. We will provide more information as it becomes available.

  2. identified Mar 25, 2026, 04:24 PM UTC

    Our R&D team has identified the underlying issue and is actively working toward a targeted resolution. The deployment window is projected to commence upon completion of the current major device release. In the interim, please utilize cloud‑based virtualization services to ensure continued operational continuity in the event of a Disaster Recovery scenario. Please note: This issue is currently impacting only a limited subset of the Datto Windows Agent fleet.

  3. resolved May 14, 2026, 07:41 PM UTC

    We’re pleased to inform you that our Engineering team has released a fix that should resolve the problem where BCDR Agents operating on 32-bit versions of Windows Server 2003 and Windows XP are experiencing failures with screenshot verification, and local virtualization processes are not successfully initializing. If the problem is still occurring, please make sure your device is fully up to date on the latest OS version. Please note, we have started to roll out the update to devices on 05/11/2026 and the release will complete for all devices by 05/28/2026. Thank you for your patience and understanding. We remain committed to delivering exceptional service and continuous improvement. Best regards,

Read the full incident report →