KaseyaOne - Unable to Access KaseyaOne

Incident Report for Kaseya Inc

Postmortem

Summary: 
Between 2026-02-07 8:23am UTC and 2026-02-07 4:40am UTC, some partners were unable to authenticate into KaseyaOne 

  

Root Cause:  

A power outage in a Microsoft datacenter caused downstream issues in the KaseyaOne application dependent on a Microsoft Azure service called Azure Cache for Redis. Azure Cache for Redis is used for caching login metadata and reducing page load times.

‌

Incident Timeline: Add any major milestones we should disclose publicly 

  • Identified: 2026-02-07 8:23am UTC   

  • Fix Implemented: 2026-02-07 9:31am UTC 

  • Resolved: 2026-02-07 9:40am UTC  

  • Public Notification to the Status Page: 2026-02-07 10:22am UTC  

  

Preventative Measures:  To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps:  

  • Enhancements to incident management and response: 
  1. KaseyaOne will be implementing a failover strategy to a US East datacenter in Azure to mitigate the impact of a power outage in the US West datacenters
Posted Feb 24, 2026 - 10:04 EST

Resolved

This incident has been resolved.
Posted Feb 07, 2026 - 17:22 EST

Monitoring

We were experiencing a service disruption for accessing KaseyaOne from 03:23 AM ET to 04:40 AM ET. Currently, KaseyaOne services are operational, and we are continuing to monitor this issue.

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

We apologize for any inconvenience.

- Kaseya Cloud Operations Team
Posted Feb 07, 2026 - 05:22 EST
This incident affected: KaseyaOne.