Datto incident

Datto Networking - Web Filtering Configuration Changes on DNA/D200 Devices Failed to Apply Successfully

Major Resolved View vendor source →

Datto experienced a major incident on July 23, 2026 affecting Routers, lasting 4d 1h. The incident has been resolved; the full update timeline is below.

Started
Jul 23, 2026, 01:37 PM UTC
Resolved
Jul 27, 2026, 02:45 PM UTC
Duration
4d 1h
Detected by Pingoru
Jul 23, 2026, 01:37 PM UTC

Affected components

Routers

Update timeline

  1. identified Jul 23, 2026, 01:37 PM UTC

    We are aware of a problem where web filtering configuration changes are not being successfully applied on the DNA and D200 appliances. The Kaseya R&D Team has identified the issue and is working towards a resolution. In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jul 24, 2026, 03:49 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jul 27, 2026, 12:33 PM UTC

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

  4. resolved Jul 27, 2026, 02:45 PM UTC

    This incident has been resolved.

  5. postmortem Aug 03, 2026, 03:27 PM UTC

    **Datto Networking- Web filtering policy changes fail to deploy to DNA and D200 appliances – 2026-07-17** **Summary:** Between **2026-07-17 10:37 PM UTC** and **2026-07-27 02:45 PM UTC**, **Datto Networking** customers experienced an issue where web filtering configuration changes were not being successfully applied on the DNA and D200 appliances. **Root Cause:** The issue was traced to an application integration change that resulted in processing errors and prevented certain configuration updates from being applied successfully. An additional issue affecting the application of category-based configuration changes was also identified. Remediation for both issues was developed promptly. **Incident Timeline:** * Identified: **2026-07-17 10:37 PM UTC** * Public Notification: **2026-07-23 02:37 PM UTC** * Resolved: **2026-07-27 02:45 PM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * Improve monitoring and alerting effectiveness to accelerate issue identification, streamline triage activities, and support service reliability. * Complete the transition away from legacy infrastructure dependencies to improve platform resilience, reduce operational risk, and prevent similar issues from recurring.