Live / Kaseya / Incident
Kaseya: Multiple Products - Microsoft 365 Connection Issues
Kaseya · datto.comMajor incidentmonitoring2026-11-13 14:23 UTC
Public — what happened
Summary
Kaseya said several of its products could not connect to Microsoft 365 services, beginning at 18:54 UTC on 2026-11-12. The company said the cause was a current outage at Microsoft Exchange and pointed customers to Microsoft's status page for updates. On 2026-11-13 Kaseya said Microsoft was still working on the problem and that its own engineering teams were watching progress. At 14:23 UTC that day it reported affected services were recovering, and the incident is still listed as being monitored rather than resolved.
Timeline
- Started — 2026-11-12 18:54 UTC
- Investigating — 2026-11-12 18:54 UTC (2 updates)
- Identified — 2026-11-13 14:16 UTC
- Monitoring — 2026-11-13 14:23 UTC
- Ongoing at last check.
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 47, 2026, our weekly internet health report.