Live / Kaseya / Incident
Kaseya: Datto SAAS Protection - aue1-bfyii-2510 - Backups are not running and SaaS Protection Console is not accessible to perform recovery related functions
Kaseya · datto.comMajor incidentResolved2026-11-03 16:01 UTC
Public — what happened
Summary
Kaseya reported a major problem affecting its Datto SaaS Protection service on the aue1-bfyii-2510 system, where scheduled backups were not running and the console could not be opened to carry out recovery tasks. The company said it first became aware of the issue at 13:38 UTC on 2026-11-03 and its engineering team began investigating. By 14:06 UTC Kaseya said a fix was in place and it was watching the results, and it kept monitoring at 14:32 UTC. The incident was marked resolved at 16:01 UTC, and Kaseya did not state a cause in the text provided.
Affected
SaaS Protection Backups, SaaS Protection Console Login
Timeline
- Started — 2026-11-03 13:38 UTC
- Investigating — 2026-11-03 13:38 UTC
- Monitoring — 2026-11-03 14:06 UTC (2 updates)
- Resolved — 2026-11-03 16:01 UTC · 2h 23m 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 46, 2026, our weekly internet health report.