Live  /  Kaseya  /  Incident

Kaseya: Datto SaaS Protection - Service disruption for customers hosted on node 'aue1-bfyii-1533'

Kaseya · datto.comMajor incidentResolved2026-10-26 20:02 UTC
Public — what happened

Summary

Kaseya said that Datto SaaS Protection customers hosted on one specific server node had their service disrupted starting at 14:17 UTC on 2026-10-26, and some may have seen a '500 Internal Server Error' when opening their accounts. The company's engineering team began investigating, and at 18:01 UTC it said its R&D team had identified the issue and put a fix in place. Kaseya reported that accounts on the affected node were accessible again and working normally while it kept monitoring, and the incident was marked resolved at 20:02 UTC.

Affected

SaaS Protection Backups, SaaS Protection Console Login, SaaS Protection Seat Management, SaaS Protection Restores/Exports

As listed on Kaseya’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 45, 2026, our weekly internet health report.

The full archive is on the Kaseya status & history page.

Related: Kaseya status & history. SquidGrid is not affiliated with Kaseya.