Datto incident

Datto Backup for Microsoft Azure / Datto Endpoint Backup with Disaster Recovery - Devices Are Failing To Complete Registration

Major Resolved View vendor source →

Datto experienced a major incident on April 9, 2026 affecting Device Registration and Device Registration, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Apr 09, 2026, 06:00 PM UTC
Resolved
Apr 10, 2026, 06:21 PM UTC
Duration
1d
Detected by Pingoru
Apr 09, 2026, 06:00 PM UTC

Affected components

Device RegistrationDevice Registration

Update timeline

  1. investigating Apr 09, 2026, 06:00 PM UTC

    We are aware of a problem where Datto Backup for Microsoft Azure and Datto Endpoint Backup with Disaster Recovery devices can experience registration failures. 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. identified Apr 10, 2026, 12:47 PM UTC

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

  3. monitoring Apr 10, 2026, 03:28 PM UTC

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

  4. resolved Apr 10, 2026, 06:21 PM UTC

    This incident has been resolved.

  5. postmortem Apr 16, 2026, 08:10 PM UTC

    **DBMA/EBDR - Device failing to register – 2026-04-09** **Summary:** Between 2026-04-09 11:00 AM UTC and 2026-04-10 12:30 PM UTC, Some partners experienced an issue where a subset of Datto Backup for Microsoft Azure and Datto Endpoint Backup with DR devices experienced registration failures. ‌ **Root Cause:** The issue was caused by a release configuration error in which a required system image was not properly marked for production use. As a result, the platform was unable to successfully create operating system disks when provisioning new virtual machines. ‌ **Incident Timeline:** * Identified: 2026-04-09 11:00 AM UTC * Public Notification: 2026-04-09 06:00 PM UTC * Resolved: 2026-04-10 12:30 PM UTC ‌ **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps: * To strengthen reliability going forward, we are introducing additional pre‑release validation steps * Enhancing real‑time monitoring and alerting around provisioning success * Conducting targeted training to improve rapid diagnosis and resolution of similar issues.