Datto incident

Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'gbe2-saas-p1'

Minor Resolved View vendor source →

Datto experienced a minor incident on June 8, 2026 affecting SaaS Protection Backups, lasting 42d 3h. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2026, 01:31 PM UTC
Resolved
Jul 20, 2026, 05:00 PM UTC
Duration
42d 3h
Detected by Pingoru
Jun 08, 2026, 01:31 PM UTC

Affected components

SaaS Protection Backups

Update timeline

  1. investigating Jun 08, 2026, 01:31 PM UTC

    We are aware of a problem where some customers hosted on pod 'gbe2-saas-p1' are experiencing backup performance degradation for some SharePoint services. The Kaseya R&D Team is actively Investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jun 08, 2026, 03:37 PM UTC

    The backup cadence on pod 'gbe2‑saas‑p1' has been temporarily set to 2x daily backups to maintain high success rates. The 3x daily backup cadence will be restored once it is stable and reliable for all customers. The Kaseya R&D Team will continue to monitor pod performance.

  3. identified Jun 09, 2026, 01:19 PM UTC

    Backup success rate metrics for SharePoint and Teams services on pod 'gbe2-saas-p1' are improving and our R&D team is continuing to monitor pod performance as it recovers.

  4. monitoring Jun 10, 2026, 12:48 PM UTC

    Backup success rate metrics for SharePoint and Teams services on pod 'gbe2-saas-p1' have returned to normal and our R&D team is continuing to monitor for any other issues.

  5. monitoring Jun 10, 2026, 02:40 PM UTC

    All backups continue to process normally on pod 'gbe2‑saas‑p1' while the backup cadence remains temporarily set to 2x daily backups to maintain high backup success rates. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.

  6. monitoring Jun 11, 2026, 07:46 PM UTC

    SharePoint and Teams backup success rates on pod 'gbe2-saas-p1' continue to remain stable at 2x backups per day. Our R&D team is continuing to monitor and the 3x daily backup cadence will be restored once it is stable and reliable for all customers.

  7. monitoring Jun 15, 2026, 03:00 PM UTC

    The backup cadence on pod 'gbe2‑saas‑p1' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. Backups are running normally and success rate metrics remain stable. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.

  8. monitoring Jun 23, 2026, 06:31 PM UTC

    The backup cadence for pod ‘gbe2‑saas‑p1’ is still temporarily set to 2x backups per day. Backups are running normally and backup success rates remain stable. Our R&D team will increase backup cadence to 3x backups per day once it’s safe and reliable for all customers on the pod.

  9. monitoring Jul 02, 2026, 06:31 PM UTC

    The backup cadence for pod ‘gbe2‑saas‑p1’ is still temporarily set to 2x backups per day and backup success rates remain stable. Our R&D team has finished deploying additional improvements to further address the issue and they are actively monitoring the results. Backup cadence will be reverted to 3x daily backups as soon as it is safe and reliable for all customers hosted on the pod.

  10. monitoring Jul 17, 2026, 08:03 PM UTC

    The backup cadence on pod 'gbe2-saas-p1' has been restored to 3x daily backups and all services are currently processing new backups normally. Our R&D team is closely monitoring for any issues.

  11. resolved Jul 20, 2026, 05:00 PM UTC

    This incident has been resolved.