Live / Kaseya / Incident
Kaseya: BMS - US - Multiple Customers Experiencing Resource Unavailable / Record Not Found Errors Across Modules
Kaseya · datto.comMajor incidentResolved2026-11-04 16:12 UTC
Public — what happened
Summary
Kaseya said multiple customers in the US region of its BMS product were having trouble accessing several modules, including Service Desk, CRM, and Admin for support users. The company reported the problem at 12:26 UTC on 2026-11-04 and said its engineering team was investigating, with an update at 14:32 UTC saying that work was continuing. At 15:07 UTC Kaseya said a fix had been put in place and it was monitoring the results, and the incident was marked resolved at 16:12. The company did not state a cause in the text provided.
Affected
US
Timeline
- Started — 2026-11-04 12:26 UTC
- Investigating — 2026-11-04 12:26 UTC (2 updates)
- Monitoring — 2026-11-04 15:07 UTC
- Resolved — 2026-11-04 16:12 UTC · 3h 46m 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.