Datto incident
Datto SaaS Protection - Backup performance degradation for SharePoint and Teams services on pod 'des1-saas-p0'
Datto experienced a minor incident on February 26, 2026 affecting SaaS Protection Backups, lasting 7d 5h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 26, 2026, 02:11 PM UTC
We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' are currently experiencing degraded backup performance for SharePoint and Teams services. The Kaseya R&D team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Feb 26, 2026, 05:36 PM UTC
While the Kaseya R&D team continue to address the issue they have temporarily decreased the daily backup frequency on pod 'des1-saas-p0' from 2x per day to 1x per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. The Kaseya R&D team is closely monitoring success rates after the configuration change and will increase backup frequency to 2x backups per day when it is safe and reliable for all customers hosted on the pod.
- monitoring Feb 27, 2026, 07:05 PM UTC
The Kaseya R&D team have implemented additional configuration changes on the pod to address the issue further. Sharepoint and Teams success rates are improving and the Kaseya R&D team is actively monitoring.
- monitoring Mar 02, 2026, 01:40 PM UTC
SharePoint and Teams success rates on the pod have stabilized and the Kaseya R&D team has increased backup frequency back to 2x backups per day. We are continuing to monitor.
- monitoring Mar 03, 2026, 01:46 PM UTC
Backup success rates for Teams and SharePoint services on pod 'des1-saas-p0' have stabilized at 2x backups per day. The Kaseya R&D team is continuing to monitor.
- resolved Mar 05, 2026, 08:10 PM UTC
This incident has been resolved.