Datto incident
Endpoint Backup v2 - UniView is exhibiting inconsistencies in backup reporting, resulting in inaccurate backup status visibility
Datto experienced a minor incident on July 28, 2026 affecting Backup, lasting 1d 11h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 28, 2026, 12:52 PM UTC
We are aware of a problem where Endpoint Backup v2 assets in UniView may incorrectly indicate backup failures despite successful backup completion, which can trigger unnecessary email notifications. The Kaseya R&D Team is investigating the issue and working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- investigating Jul 28, 2026, 06:04 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 28, 2026, 11:59 PM UTC
Our R&D team has implemented a fix, and we're seeing improved performance across the affected systems. We're continuing to monitor the environment to ensure the improvements are sustained.
- resolved Jul 29, 2026, 11:59 PM UTC
This incident has been resolved. We will continue to monitor the environment to ensure ongoing stability. If you continue to experience any issues, please contact Kaseya Support. We sincerely apologize for the disruption and thank you for your patience while we worked to resolve this issue.
- postmortem Sep 02, 2026, 01:53 PM UTC
**Endpoint Backup v2 - Assets in UniView may inaccurately report backup failures despite successful backup completion – 2026-07-27** **Summary:** Between **2026-07-27 20:00 UTC and 2026-07-28 23:30 UTC**, Endpoint Backup v2 customers experienced an issue in which assets within UniView incorrectly reported backup failures, despite backups completing successfully. **Root Cause:** The incident was caused by a processing capacity constraint that delayed the synchronization of backup status information. As a result, recently completed backups were not reflected in the user interface in a timely manner, creating visibility issues for customers. Backup operations continued to complete successfully, and no backup data was impacted. **Incident Timeline:** * Identified: **2026-07-27 20:00 UTC** * Public Notification: **2026-07-28 13:52 UTC** * Resolved: **2026-07-28 23:30 UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * Implemented a more efficient data synchronization mechanism to reduce processing overhead, improve system performance, and accelerate the delivery of updated information across the platform.