Live / Kaseya / Incident
Kaseya: Autotask - Multiple Zones - Integrations attempting to utilize the API are unable to connect to Autotask
Kaseya · datto.comMinor incidentResolved2026-11-06 23:41 UTC
Public — what happened
Summary
Kaseya said that connected tools trying to reach Autotask through its API were failing across multiple zones, with users receiving an internal server error. The problem began at 21:36 UTC on 2026-11-06, and Kaseya said its engineers had already identified the issue and were working on a fix. By 22:29 UTC the company said a fix was in place and it was monitoring the results, and the incident was marked resolved at 23:41. Kaseya rated it as minor.
Affected
Limited Release, America East, America East 3, America West 2, America West 3, UK 2 (United Kingdom), Australia / New Zealand
Timeline
- Started — 2026-11-06 21:36 UTC
- Identified — 2026-11-06 21:36 UTC
- Monitoring — 2026-11-06 22:29 UTC
- Resolved — 2026-11-06 23:41 UTC · 2h 05m 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.