Datto incident
Endpoint Backup v2 - Subset of Endpoint Backup v2 assets are experiencing slow or incomplete backups due to 504 Gateway Timeout errors.
Datto experienced a minor incident on July 16, 2026 affecting Backup, lasting 1d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 16, 2026, 01:59 PM UTC
We are aware of a problem where Endpoint Backup v2 assets can experience slow or failed backups due to a "504 Gateway Timeout" error. 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/
- monitoring Jul 17, 2026, 03:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 17, 2026, 06:05 PM UTC
This incident has been resolved.
- postmortem Jul 30, 2026, 01:24 PM UTC
**Endpoint Backup v2 - Backup delays and failures were caused by 504 Gateway Timeout errors – 2026-07-16** **Summary:** Between **2026-07-16 09:00 AM UTC** and **2026-07-17 03:30 PM UTC**, Endpoint Backup v2 customers experienced slow or failed backups due to a "504 Gateway Timeout" error. **Root Cause:** Increased activity and maintenance across multiple storage systems created higher-than-normal demand on infrastructure resources, resulting in backup performance issues for some customers. **Incident Timeline:** * Identified: **2026-07-16 09:00 AM UTC** * Public Notification: **2026-07-16 02:59 PM UTC** * Resolved: **2026-07-17 03:30 PM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * We are implementing performance improvements, enhancing monitoring and alerting capabilities for faster issue detection, and adding safeguards to better manage demand and maintain service stability during periods of increased activity.