Kaseya Outage History

Kaseya's Datto BCDR service experienced degraded offsite capabilities for users paired to server5856 in the US-East region over a 47.6-hour period. The issue affected backup and disaster recovery offsite functions for users connected to that specific server. The Kaseya R&D team identified and implemented a fix, with the incident fully resolved after monitoring confirmed the solution was effective.

Kaseya's Datto Endpoint Backup for PC service experienced degraded performance for users paired with Cloud Siris server 'use1-dtc-server-143', resulting in slower-than-average backup and restore speeds. The issue affected offsite backup capabilities and lasted approximately 15 hours before being resolved by the R&D team.

Kaseya's Datto Endpoint Backup for PC experienced degraded offsite performance on server 'gbe2-dtc-server-157' in the UK region, affecting users paired to that specific server. The R&D team identified the root cause and implemented a fix after 3.4 hours. The incident was resolved after a monitoring period to ensure the fix was effective.

Datto RMM experienced a major incident where device filters on the Merlot and Pinotage platforms failed to load, displaying "Device Filter results were not able to be returned" error messages. The issue prevented users from accessing filtered device results within the RMM platform. Kaseya's R&D team implemented a fix and resolved the incident after 2.9 hours of monitoring.

Kaseya's Datto SaaS Protection service experienced backup performance degradation affecting customers on pods 'use1-saas-p7' and 'use1-saas-p8', with all backups showing reduced success rates. The R&D team identified the root cause and implemented fixes, with pod 'use1-saas-p7' recovering first followed by pod 'use1-saas-p8'. The incident was fully resolved after 74.6 hours with backup success rates returning to normal levels on both pods.

Datto RMM on the Merlot platform experienced a major incident where agent-based alerts were not being raised on the platform for 3.2 hours. The Kaseya R&D team identified the root cause and implemented a fix, restoring real-time alert creation. Previously impacted alerts were processed and raised within 2 hours of the resolution.

Kaseya's Datto SaaS Protection service experienced backup performance degradation for SharePoint and Teams services on pod 'use1-saas-p5', affecting some customers hosted on that infrastructure. The R&D team identified the root cause and implemented a fix, with backup success rates gradually improving over the monitoring period. The incident was fully resolved after 26.4 hours with normal backup processing restored.

Kaseya's Endpoint Backup v2 service experienced a major outage where registration, backup, and restore requests failed to initiate successfully. The incident affected all core backup functionality for users of the v2 service. The Kaseya R&D team resolved the issue after 1.3 hours of investigation and remediation work.

Kaseya's Datto SaaS Protection service experienced backup performance degradation on pod 'use1-saas-p9', causing delayed backup processing for affected customers. The R&D team worked to ensure daily backups were still completed within the 24-hour window while addressing the underlying performance issue. The incident was resolved after 9.1 hours with operations restored and continued monitoring to ensure full recovery.

Datto Networking DNA devices experienced a configuration issue where their dynamic DNS records were resolving to incorrect private IP addresses instead of the proper addresses. This affected network connectivity and device accessibility for users with these networking devices. The issue was identified by the Kaseya R&D team, a fix was implemented and monitored, and the incident was fully resolved after 27.6 hours.