Datto incident
Datto SaaS Protection - Service disruption for customers hosted on pod 'gbe2-saas-p1'
Datto experienced a major incident on May 24, 2026 affecting SaaS Protection Backups and SaaS Protection Console Login and 1 more component, lasting 4d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 24, 2026, 05:52 PM UTC
We are aware of a problem causing a disruption to services for Datto SaaS Protection customers hosted on pod 'gbe2-saas-p1'. Our R&D team has identified the issue and is actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified May 26, 2026, 01:16 PM UTC
Our R&D team is continuing to address the current disruption to SaaS Protection services affecting customers hosted on pod 'gbe2-saas-p1'.
- monitoring May 26, 2026, 03:43 PM UTC
Our R&D team has implemented changes to address the issue affecting customers hosted on pod 'gbe2-saas-p1' and they are monitoring the results.
- monitoring May 26, 2026, 08:11 PM UTC
Backup success rate metrics on pod 'gbe2-saas-p1' are returning to normal. Our R&D team is continuing to monitor for any other issues.
- monitoring May 27, 2026, 03:32 PM UTC
Backup success rate metrics on pod 'gbe2-saas-p1' have returned to normal and our R&D team is continuing to monitor for any other issues.
- resolved May 28, 2026, 06:15 PM UTC
This incident has been resolved.