Datto SaaS Protection - Service disruption affecting customers hosted on pod 'gbe2-saas-p0'

Update timeline

1. identified Jul 29, 2026, 10:55 AM UTC

   We are aware of an issue where Datto SaaS Protection customers hosted on pod gbe2-saas-p0 are experiencing a complete service disruption. The Kaseya Engineering Team has identified the issue and is actively working to restore service as quickly as possible. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

2. identified Jul 29, 2026, 10:56 AM UTC

   We are continuing to work on a fix for this issue.

3. identified Jul 29, 2026, 12:23 PM UTC

   Our R&D team has applied a fix to address the issue and they are currently verifying restoration of all services on pod 'gbe2-saas-p0'.

4. identified Jul 29, 2026, 01:45 PM UTC

   Our R&D team is continuing to address the issue and fully restore SaaS Protection services on pod 'gbe2-saas-p0'.

5. identified Jul 29, 2026, 03:02 PM UTC

   Our R&D team has confirmed that backups are currently processing normally on pod 'gbe2-saas-p0' however they are continuing to address an issue affecting customer account access.

6. identified Jul 29, 2026, 04:38 PM UTC

   Our R&D team is continuing to address the account access issues still affecting some SaaS Protection customers hosted on pod 'gbe2-saas-p0' as well as monitoring backup performance.

7. monitoring Jul 29, 2026, 05:12 PM UTC

   Our R&D team has implemented additional changes to address the intermittent account access issues that were still affecting some customers hosted on pod 'gbe2-saas-p0' and backups for all services are continuing to process. We will be monitoring the pod closely for any other issues.

8. resolved Jul 29, 2026, 08:15 PM UTC

   Backups continue to process and all customer accounts hosted on pod 'gbe2-saas-p0' are accessible and functioning normally. This incident is resolved.