Live / Kaseya / Incident
Kaseya: Datto SaaS Protection - Backup Performance Degradation For Customers Hosted On Pod 'aue2-saas-p2'
Kaseya · datto.comMinor incidentResolved2026-10-26 19:33 UTC
Public — what happened
Summary
Kaseya said customers whose Datto SaaS Protection accounts are hosted on one server group, called pod 'aue2-saas-p2', saw slower and less reliable backups of Microsoft 365 and Google Workspace data. The company rated the problem minor and said it began around 13:16 UTC on 2026-10-26, when its engineers had already identified the issue. By 18:17 UTC Kaseya said its R&D team had made changes and backup success rates were back to normal, and it kept watching for further problems. The incident was marked resolved at 19:33 UTC.
Affected
SaaS Protection Backups
Timeline
- Started — 2026-10-26 13:16 UTC
- Identified — 2026-10-26 13:16 UTC
- Monitoring — 2026-10-26 18:17 UTC
- Resolved — 2026-10-26 19:33 UTC · 6h 17m 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 45, 2026, our weekly internet health report.