Datto incident

Endpoint Backup v2 - Last Backup Timestamp Is Not Updating Correctly, Which May Result in False-Positive Backup Threshold Alerts within UniView

Minor Resolved View vendor source →

Datto experienced a minor incident on May 22, 2026 affecting Backup, lasting 3d 22h. The incident has been resolved; the full update timeline is below.

Started
May 22, 2026, 03:15 PM UTC
Resolved
May 26, 2026, 01:24 PM UTC
Duration
3d 22h
Detected by Pingoru
May 22, 2026, 03:15 PM UTC

Affected components

Backup

Update timeline

  1. identified May 22, 2026, 03:15 PM UTC

    We are aware of a problem where where the last backup timestamp for Endpoint Backup v2 assets can fail to update correctly, which may result in false-positive backup threshold alerts within UniView. The Kaseya R&D Team has identified the issue and is working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 26, 2026, 12:33 PM UTC

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

  3. resolved May 26, 2026, 01:24 PM UTC

    This incident has been resolved.

  4. postmortem Jun 04, 2026, 05:18 PM UTC

    **Endpoint Backup v2 - Last backup time not updating/UniView backup threshold alerts falsely triggering – 2026-05-21** **Summary:** Between **2026-05-22 14:28 UTC** and **2026-05-26 12:56 UTC**, **Endpoint Backup v2** customers experienced an issue where the last backup timestamp for Endpoint Backup v2 assets failed to update correctly, which resulted in false-positive backup threshold alerts within UniView. **Root Cause:** A large number of backup messages built up in the system faster than they could be processed. As a result, backup updates were delayed by several days. This caused outdated “last backup” timestamps and triggered incorrect backup alerts for multiple partners. **Incident Timeline:** * Identified: 2026-05-22 14:28 UTC * Public Notification: 2026-05-22 16:15 UTC * Resolved: 2026-05-26 12:56 UTC **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * Implemented configuration updates and performance improvements to better handle expected activity levels, moving beyond previous default settings to support a higher workload more effectively. * Enhanced our monitoring with improved alerts to quickly detect and address any unusual build-up in processing queues.