Kaseya incident

Datto Workplace - Latency Issues Affecting Users on US Cells

Major Resolved View vendor source →

Kaseya experienced a major incident on April 8, 2026, lasting 36d 5h. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2026, 02:12 PM UTC
Resolved
May 14, 2026, 07:50 PM UTC
Duration
36d 5h
Detected by Pingoru
Apr 08, 2026, 02:12 PM UTC

Update timeline

  1. investigating Apr 01, 2026, 03:45 PM UTC

    We are aware of a problem where Datto Workplace users are reporting elevated latency impacting multiple projects within the U.S. region. 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. investigating Apr 02, 2026, 01:02 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 03, 2026, 01:32 PM UTC

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

  4. identified Apr 03, 2026, 05:06 PM UTC

    We have identified the root cause of the slow file downloads impacting large projects. The issue is isolated to the server side and does not impact data integrity. A corrective solution is currently under evaluation, and we anticipate providing an updated status early next week.

  5. identified Apr 08, 2026, 02:12 PM UTC

    Our engineering team has provided a temporary solution to mitigate the latency issue affecting Datto Workplace. If you wish to implement this workaround, please contact our Technical Support team for assistance with its application.

  6. identified Apr 10, 2026, 02:58 PM UTC

    The Kaseya R&D team continues to actively work toward resolving this issue. Please note that any latency impact is limited to VFS/V10 agents.

  7. identified Apr 15, 2026, 05:38 PM UTC

    Our engineering team is continuing to investigate a permanent resolution.

  8. identified Apr 23, 2026, 08:28 PM UTC

    Our engineering team is actively working on a permanent resolution. We’ll provide updates as progress continues.

  9. resolved May 14, 2026, 07:50 PM UTC

    This incident has been resolved.