Live / Kaseya / Incident
Kaseya: Datto SaaS Protection - M365 Backup Performance Degradation - Post-Graph Migration
Kaseya · datto.comMajor incidentResolved2026-11-02 16:03 UTC
Public — what happened
Summary
Kaseya said its Datto SaaS Protection service had slower and less reliable Microsoft 365 backups after a move to Microsoft's Graph API, which it reported finished on 2026-09-30. It said some customers saw delayed or missed backups, and for a time some Microsoft 365 services in one environment type ran only once a day instead of three times. Kaseya reported steady improvement through October, including a second dip around 2026-10-15 that it linked to a platform update and increased Microsoft throttling, which it said it addressed. By 2026-10-13 it had set all backups to three per day, and the incident was marked resolved on 2026-11-02, though its last update noted some customers could still see occasional delays or missed items.
Affected
SaaS Protection Backups
Timeline
- Started — 2026-09-30 16:37 UTC
- Monitoring — 2026-09-30 16:37 UTC (8 updates)
- Resolved — 2026-11-02 16:03 UTC · 33 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Kaseya against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Kaseya: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Kaseya report →
More from Kaseya
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.