Datto incident

Datto SaaS Protection - Service disruption for customers hosted on pod 'cae1-saas-p1'

Critical Resolved View vendor source →

Datto experienced a critical incident on April 30, 2026 affecting SaaS Protection Backups and SaaS Protection Console Login and 1 more component, lasting 16h 52m. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2026, 10:31 PM UTC
Resolved
May 01, 2026, 03:24 PM UTC
Duration
16h 52m
Detected by Pingoru
Apr 30, 2026, 10:31 PM UTC

Affected components

SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Client OnboardingSaaS Protection Report DeliverySaaS Protection Restores/Exports

Update timeline

  1. identified Apr 30, 2026, 10:31 PM UTC

    We are aware of a problem where customers hosted on pod 'cae1-pod-1' are experiencing a disruption to their SaaS Protection services. Our R&D team is performing maintenance on pod 'cae1-pod-1' to resolve an issue that was identified. The estimated down time is up to 8 hours. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 01, 2026, 05:17 AM UTC

    Our R&D team has implemented a fix to address the issue impacting the pod. We are actively monitoring the node for any other issues.

  3. monitoring May 01, 2026, 06:32 AM UTC

    Backup success rates have improved since a fix has been implemented. Our R&D continues to monitor the health of the pod until expected levels are reached.

  4. monitoring May 01, 2026, 12:36 PM UTC

    Backup success rates on the pod have returned to normal and remain stable. Our R&D team is continuing to monitor.

  5. resolved May 01, 2026, 03:24 PM UTC

    This incident has been resolved.