Datto incident

Datto BCDR - Cloud Recovery - Cloud Operations Service Impact

Major Resolved View vendor source →

Datto experienced a major incident on September 2, 2026 affecting Off-Site Recovery, lasting 6d 6h. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 10:10 AM UTC
Resolved
Sep 08, 2026, 04:26 PM UTC
Duration
6d 6h
Detected by Pingoru
Sep 02, 2026, 10:10 AM UTC

Affected components

Off-Site Recovery

Update timeline

  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.