Datto Outage History

Datto RMM experienced delayed job execution on the Concord and Vidal platforms for 1.8 hours. The Kaseya R&D team identified the root cause and implemented a fix. The incident was resolved after a monitoring period to confirm the fix was effective.

Datto RMM experienced a major incident where certificate errors prevented the RMM agent from being installed across all platforms. The issue affected users' ability to deploy new RMM agents for approximately 18 hours. The problem was resolved after Kaseya's R&D team implemented a fix and monitored the results.

Datto's antivirus behavioral detection component was incorrectly quarantining legitimate files during endpoint startup before policy settings were fully applied, with quarantined files not generating console alerts and unable to be restored directly from the portal. The issue had low probability but affected customer environments when it occurred. Datto deployed a fix on April 2nd that was applied to agents during their next maintenance window, resolving the 44.6-hour incident.

Datto RMM filters on the Vidal platform were failing to load due to an "Out of sort memory" error. The issue prevented users from accessing filter functionality within the RMM platform. The Kaseya R&D team implemented a fix and resolved the incident after 42 minutes of monitoring.

Datto BCDR assets paired to server1405 in the US-East region experienced degraded offsite performance over a 13-day period. The issue affected backup and disaster recovery operations for customers using that specific server. The Kaseya R&D team identified and resolved the underlying performance problem.

Datto RMM experienced a database issue that prevented users from creating or saving Monitoring Policies, displaying a "could not execute statement" error. The problem affected the Concord region and lasted approximately 2.7 hours. Kaseya's R&D team implemented a fix and monitored the results before confirming full resolution.

Datto BCDR users paired to server5856 in the US-East region experienced degraded offsite backup capabilities for approximately 48 hours. The Kaseya R&D team identified and implemented a fix to restore normal offsite performance. The incident was resolved after monitoring confirmed the fix was successful.

Datto Endpoint Backup for PC users paired with Cloud Siris 'use1-dtc-server-143' experienced degraded performance that resulted in slower-than-average backup and restore speeds. The issue affected offsite backup capabilities for users connected to this specific server. The incident was resolved after 15 hours of investigation and remediation by the Kaseya R&D Team.

Datto Endpoint Backup for PC experienced degraded offsite performance for users connected to server 'gbe2-dtc-server-157' in the UK region. The Kaseya R&D team identified the root cause and implemented a fix after 3.4 hours of service degradation. 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. The incident was resolved after 3 hours when Kaseya's R&D team implemented a fix and confirmed the service was restored.