Live / Kaseya / Incident
Kaseya: KaseyaAssist Service Disruption
Kaseya · datto.comResolved2026-11-05 00:07 UTC
Public — what happened
Summary
Kaseya said KaseyaAssist, which is reached through its direct product portals, was disrupted starting at 20:07 UTC on 2026-11-04. It told customers they could still get support and billing help through helpdesk.kaseya.com in the meantime. Kaseya said its vendor was working on the problem, identified it by 21:31 UTC, and confirmed a fix was in place by 23:05 UTC, after which Kaseya kept monitoring. The incident was marked resolved at 00:07 UTC on 2026-11-05.
Timeline
- Started — 2026-11-04 20:07 UTC
- Investigating — 2026-11-04 20:07 UTC
- Identified — 2026-11-04 21:31 UTC
- Monitoring — 2026-11-04 23:05 UTC
- Resolved — 2026-11-05 00:07 UTC · 4h 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.