Datto Outage History

Datto degraded · 2 active incidents View live status →

There were 52 Datto outages since February 11, 2026 totaling 549h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.datto.com

Major February 16, 2026

Datto BCDR - Degraded Offsite Performance - server3445

Detected by Pingoru
Feb 16, 2026, 01:48 PM UTC
Resolved
Feb 25, 2026, 03:19 PM UTC
Duration
9d 1h
Affected: Off-Site Recovery
Timeline · 4 updates
  1. investigating Feb 16, 2026, 01:48 PM UTC

    We are aware of a problem where Datto BCDR users paired to server3445 can experience degraded offsite capabilities. 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/

  2. identified Feb 18, 2026, 07:04 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 18, 2026, 07:26 PM UTC

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

  4. resolved Feb 25, 2026, 03:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026

Datto Networking - Loopback DNS on Local Interfaces Disrupts Networking Connections

Detected by Pingoru
Feb 11, 2026, 06:56 PM UTC
Resolved
Feb 25, 2026, 03:17 PM UTC
Duration
13d 20h
Affected: Secure Edge
Timeline · 4 updates
  1. identified Feb 11, 2026, 06:56 PM UTC

    We are aware of a problem where the assignment of loopback DNS on local interfaces disrupts networking connections on version 2.1.0.0 of Datto Secure Edge. 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/

  2. investigating Feb 12, 2026, 03:18 AM UTC

    Our engineering team has identified the root cause and released a hotfix Windows client release (v2.1.1.0) addressing the DNS configuration issue identified in the prior release. The hotfix automatically detects and corrects affected DNS settings upon startup, restoring internet connectivity and DNS functionality. The updated client can be installed directly over the impacted version and includes all prior improvements and fixes from v2.1.0.0. While initial assessment suggested some impacted endpoints might remain reachable via RMM, further validation confirms that RMM agents typically lose connectivity shortly after DNS failure, limiting remote remediation options. Due to dependency on DNS resolution for standard deployment mechanisms, remote push/install via RMM is not expected to be viable in most cases. We are actively evaluating alternative distribution methods that would allow customers to manually download and install the hotfix without relying on DNS. Any additional methods identified will be published as an update to this status page. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  3. monitoring Feb 12, 2026, 03:22 AM UTC

    Our engineering team has identified the root cause and released a hotfix Windows client release (v2.1.1.0) addressing the DNS configuration issue identified in the prior release. The hotfix automatically detects and corrects affected DNS settings upon startup, restoring internet connectivity and DNS functionality. The updated client can be installed directly over the impacted version and includes all prior improvements and fixes from v2.1.0.0. While initial assessment suggested some impacted endpoints might remain reachable via RMM, further validation confirms that RMM agents typically lose connectivity shortly after DNS failure, limiting remote remediation options. Due to dependency on DNS resolution for standard deployment mechanisms, remote push/install via RMM is not expected to be viable in most cases. We are actively evaluating alternative distribution methods that would allow customers to manually download and install the hotfix without relying on DNS. Any additional methods identified will be published as an update to this status page. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  4. resolved Feb 25, 2026, 03:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Datto downtime and outages?

Pingoru polls Datto's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Datto reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Datto alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Datto for free

5 free monitors · No credit card required