Live / Kaseya / Incident
Kaseya: Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-1555'
Kaseya · datto.comMajor incidentResolved2026-10-22 18:26 UTC
Public — what happened
Summary
Kaseya reported a major service disruption affecting Datto SaaS Protection customers whose accounts are hosted on a specific server node, 'gbe2-bfyii-1555'. The company said the problem began at 09:28 UTC on 2026-10-22, and its engineers began investigating. By 14:54 UTC Kaseya said the issue had been identified and a fix was being put in place. At 17:55 UTC it said affected customers could access the service again and backups were running normally, and the incident was marked resolved at 18:26 after its R&D team monitored for further problems.
Affected
SaaS Protection Console Login
Timeline
- Started — 2026-10-22 09:28 UTC
- Investigating — 2026-10-22 09:28 UTC
- Identified — 2026-10-22 14:54 UTC
- Monitoring — 2026-10-22 17:55 UTC
- Resolved — 2026-10-22 18:26 UTC · 8h 59m 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 44, 2026, our weekly internet health report.