Live / Kaseya / Incident
Kaseya: Datto Saas Protection- Partners Unable to Access Clients Hosted on Node isw1-bfyii-1134
Kaseya · datto.comMinor incidentResolved2026-10-23 17:53 UTC
Public — what happened
Summary
Kaseya said some Datto SaaS Protection partners could not reach customer accounts hosted on one particular node, and its engineering team began investigating on October 15 at 10:52 UTC. About an hour later, at 12:04 UTC, Kaseya said its R&D team had put a fix in place, so the affected clients were accessible again and full functionality was back. The company said it was then watching service health as queued backups were processed, with full recovery expected within up to 8 hours. Kaseya did not name a cause in the text provided, and the incident is marked resolved as of October 23 at 17:53.
Affected
SaaS Protection Console Login
Timeline
- Started — 2026-10-15 10:52 UTC
- Investigating — 2026-10-15 10:52 UTC
- Monitoring — 2026-10-15 12:04 UTC
- Resolved — 2026-10-23 17:53 UTC · 8 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 43, 2026, our weekly internet health report.