Datto incident

Endpoint Backup v2 - Backup Failures

Minor Resolved View vendor source →

Datto experienced a minor incident on June 15, 2026 affecting Backup, lasting 9d 4h. The incident has been resolved; the full update timeline is below.

Started
Jun 15, 2026, 02:12 PM UTC
Resolved
Jun 24, 2026, 06:44 PM UTC
Duration
9d 4h
Detected by Pingoru
Jun 15, 2026, 02:12 PM UTC

Affected components

Backup

Update timeline

  1. investigating Jun 15, 2026, 02:12 PM UTC

    We are aware of a problem where a subset of Endpoint Backup v2 assets can experience a backup failure due to a "Errors writing to the AOF file: Input/output" error. 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. investigating Jun 15, 2026, 05:31 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 16, 2026, 06:45 PM UTC

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

  4. identified Jun 23, 2026, 05:53 PM UTC

    We’re pleased to share that our team will begin rolling out the fix to non-U.S. regions on June 23, 2026 at 06:00 PM UTC, followed by deployment to U.S. regions on June 24, 2026 at 08:00 AM UTC. We appreciate your patience as we work to ensure a smooth and reliable update experience for all customers.

  5. monitoring Jun 24, 2026, 01:24 PM UTC

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

  6. resolved Jun 24, 2026, 06:44 PM UTC

    This incident has been resolved.

  7. postmortem Jul 24, 2026, 02:21 PM UTC

    **Endpoint Backup v2 - Backup Failures Due To 'EOF' Error – 2026-06-15** ‌ **Summary:** Between **2026-06-15 12:30 PM UTC** and **2026-06-24 09:00 AM UTC**, a subset of Endpoint Backup V2 users experienced intermittent backup failures due to an “EOF” error. **Root Cause:** A rare compatibility issue within the underlying storage infrastructure caused some storage servers to become unresponsive, which in turn delayed or prevented backup operations from completing successfully. Engineering developed and deployed a targeted fix using a phased rollout approach to validate effectiveness and minimize risk. Following successful verification, the update was deployed across all affected storage servers, fully resolving the issue. **Incident Timeline:** * Identified: 2026-06-15 12:30 PM UTC * Public Notification: 2026-06-15 03:12 PM UTC * Resolved: 2026-06-24 09:00 AM UTC