Live  /  Providers  /  Kaseya

Kaseya

datto.comReporting incidents

Independent assessment — SquidGrid is not affiliated with Kaseya. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Kaseya’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Kaseya is reporting

Current & recent incidents

monitoring

Datto SaaS Protection - Backup performance degradation for M365 services affecting multiple pods/regions

Major impact · 2026-09-28 20:10 UTC · still open per the provider’s page — may be stale

identified

BCDR - Server4715 US-EAST - Unscheduled Maintenance

Minor impact · 2026-09-21 17:21 UTC · still open per the provider’s page — may be stale

monitoring

[VSA9] - [PHILKAS01] - Intermittent Service Disruption

Major impact · 2026-09-14 13:47 UTC · still open per the provider’s page — may be stale

Resolved

ConnectBooster - Intermittent Sync and Access issues

Major impact · 2026-09-28 23:39 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Kaseya has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Kaseya runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Kaseya is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Kaseya.