Datto incident
Datto Workplace - AU5 - Some files are unable to be accessed through local agents and the Workplace Online
Datto experienced a major incident on May 15, 2026 affecting AU5, lasting 3d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 15, 2026, 09:36 AM UTC
The R&D Team is currently investigating the issue where users receive an error through the local agent or in Workplace Online when attempting to access certain files on the AU5 cell.
- monitoring May 15, 2026, 02:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 18, 2026, 11:28 AM UTC
This incident has been resolved.
- postmortem Jul 09, 2026, 04:02 PM UTC
**Datto Workplace - AU5 - Some Files Are Unable to be Accessed Through Local Agents and Workplace Online** **Summary:** Between May 5, 2026 at 08:00 AM UTC and May 18, 2026 at 11:28 AM UTC, some Datto Workplace customers hosted in the AU5 environment experienced issues accessing files. During the affected period, users experienced errors when attempting to access specific files hosted within the AU5 cell through either the local agent or Workplace Online. Additionally, intermittent connectivity disruptions occurred throughout the incident, resulting in periods of degraded service availability and access interruptions. **Root Cause:** The issue was caused by an outdated component that unintentionally remained in use following a recent service update. Over time, this component experienced degraded performance and eventually became unavailable, which disrupted connectivity for some users. Once identified, our engineering team promptly removed the outdated component and restored normal service. Connectivity was fully recovered on May 18, 2026, at 11:28 AM UTC. **Incident Timeline:** * Identified: **2026-05-05 08:00 AM UTC** * Public Notification: **2026-05-15 9:36 AM UTC** * Resolved: **2026-05-18 11:28 AM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * We are taking steps to ensure similar components are fully retired during future updates to prevent recurrence.