Live / Incidents / Kaseya
Kaseya: Datto SaaS Protection - Backup performance degradation for M365 services affecting multiple pods/regions
Kaseya · datto.comImpact: majorResolved2026-09-28 20:10 UTC
Public — what happened
Summary
Post-migration validation and optimization activities following Microsoft Graph API enablement remain in progress.
Backup cadence remains unchanged, with all Microsoft 365 services in V2 environments continuing to back up three times per day. In V3 environments, Exchange backups continue at three times per day, while SharePoint, OneDrive, and Teams remain at one backup per day as optimization efforts continue to mitigate Microsoft service throttling and maintain high backup success rates.
Engineering teams continue to deploy enhancements and optimizations as part of ongoing post-migration validation efforts. Platform performance and stability remain under close monitoring. We appreciate yo
Timeline
- Started — 2026-08-05 19:40 UTC
- Last update — 2026-09-28 20:10 UTC
- Resolved — 2026-09-28 20:10 UTC
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 →