Datto incident
Endpoint Backup v2 - Last Backup Timestamp Is Not Updating Correctly, Which May Result in False-Positive Backup Threshold Alerts within UniView
Datto experienced a minor incident on May 27, 2026 affecting Backup, lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 27, 2026, 01:33 PM UTC
We are aware of a problem 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. Please note that this issue does not impact backup performance and is limited to a visual display anomaly only. 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/
- monitoring May 27, 2026, 08:22 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 28, 2026, 05:09 PM UTC
This incident has been resolved.
- postmortem Jun 04, 2026, 06:29 PM UTC
**Endpoint Backup v2 - Last Backup Timestamp Is Not Updating Correctly, Which May Result in False-Positive Backup Threshold Alerts within UniView – 2026-05-27** **Summary:** Between **2026-05-27 13:36 UTC** and **2026-05-28 18:09 UTC**, Endpoint Backup v2 customers experienced an issue 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. **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-27 13:36 UTC * Public Notification: 2026-05-27 14:33 UTC * Resolved: 2026-05-28 18:09 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.