Live / Kaseya / Incident
Kaseya: Datto BCDR - UK Region - Offsite Synchronization Failures Affecting a Subset of Devices
Kaseya · datto.comMinor incidentResolved2026-11-06 13:32 UTC
Public — what happened
Summary
Kaseya said some Datto BCDR customers in the UK region could see degraded offsite performance, which might affect synchronization, starting on 2026-11-03 at 18:58 UTC. The company said its engineers were investigating, and on 2026-11-04 it reported the problem had been identified and a fix was being put in place. On 2026-11-05 Kaseya said a fix was in place and it was monitoring the results, and the incident was marked resolved on 2026-11-06 at 13:32. Kaseya rated it minor.
Affected
Off-Site Synchronization
Timeline
- Started — 2026-11-03 18:58 UTC
- Investigating — 2026-11-03 18:58 UTC
- Identified — 2026-11-04 19:55 UTC
- Monitoring — 2026-11-05 14:15 UTC
- Resolved — 2026-11-06 13:32 UTC · 3 days 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.