Kaseya incident

Datto SaaS Protection - Service disruption for customers hosted on pod 'usw3-saas-p0'

Major Resolved View vendor source →

Kaseya experienced a major incident on May 11, 2026, lasting 1d 20h. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 05:39 PM UTC
Resolved
May 13, 2026, 02:14 PM UTC
Duration
1d 20h
Detected by Pingoru
May 11, 2026, 05:39 PM UTC

Update timeline

  1. investigating May 11, 2026, 05:39 PM UTC

    We are aware of a problem where customers hosted on pod 'usw3-saas-p0' are experiencing a disruption to Backup and Recovery services for Datto SaaS Protection. The Kaseya R&D Team is actively Investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 11, 2026, 06:50 PM UTC

    Our R&D team has implemented a fix to resolve the Backup and Recovery affecting customers on pod 'usw3-saas-p0' and are actively monitoring for any other issues.

  3. identified May 11, 2026, 10:11 PM UTC

    Our R&D team has identified another issue affecting Backup and Recovery services for customers hosted on pod 'usw3-saas-p0' and are actively working to address it.

  4. monitoring May 11, 2026, 10:46 PM UTC

    Our R&D team has resolved the issue and Backup and Recovery services are functioning normally again for customers on pod 'usw3-saas-p0'. We are continuing to monitor.

  5. monitoring May 12, 2026, 08:30 PM UTC

    Backup success rates on pod 'usw3-saas-p0' remain stable at normal levels. Our R&D team is continuing to monitor.

  6. resolved May 13, 2026, 02:14 PM UTC

    This incident has been resolved.