Live / Kaseya / Incident
Kaseya: Datto BCDR - US Region - Server5582 Not Accessible
Kaseya · datto.comMinor incidentResolved2026-11-13 17:47 UTC
Public — what happened
Summary
Kaseya said that Datto BCDR users paired to Server5582 in its US East region were seeing slower, degraded performance, which the company linked to a node availability problem. The report was posted at 15:22 UTC on 2026-11-13, when its engineering team was investigating and working toward a fix. Kaseya rated the incident minor and marked it resolved at 17:47.
Affected
Off-Site Synchronization, Off-Site Recovery
Timeline
- Started — 2026-11-13 15:22 UTC
- Investigating — 2026-11-13 15:22 UTC
- Resolved — 2026-11-13 17:47 UTC · 2h 24m 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 47, 2026, our weekly internet health report.