Kaseya incident

DattoRMM - Vidal - Datto Continuity devices incorrectly reporting offline

Minor Resolved View vendor source →

Kaseya experienced a minor incident on May 26, 2026, lasting 23h 57m. The incident has been resolved; the full update timeline is below.

Started
May 26, 2026, 05:36 PM UTC
Resolved
May 27, 2026, 05:33 PM UTC
Duration
23h 57m
Detected by Pingoru
May 26, 2026, 05:36 PM UTC

Update timeline

  1. identified May 26, 2026, 05:36 PM UTC

    We are aware of a problem where online BCDR devices are reporting as offline through the Datto Continuity integration on our Vidal platform. The Kaseya R&D Team have identified the issue and are working on a fix Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified May 27, 2026, 10:33 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring May 27, 2026, 03:34 PM UTC

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

  4. resolved May 27, 2026, 05:33 PM UTC

    This incident has been resolved.