New Multi-region uptime checks and custom-domain status pages

Kaseya Inc Outage History

Daily provider-status observations and published incident history for Kaseya Inc.

Degraded performance

Kaseya Inc is reporting degraded performance. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Kaseya Inc for future changes.

0% of 29 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

August 2026
Datto SaaS Protection - M365 Backup and Restore issues affecting customers in multiple regions
minor Observed active window 137h 5m

View incident details and source

Started:

SaaS Protection Backups SaaS Protection Restores/Exports
monitoring
Our R&D team has implemented additional changes to restore full functionality to affected customers and they are closely monitoring for any other issues.
identified
Our R&D team is continuing to address this issue and restore full functionality to the affected customers.
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We are aware of a problem where some Datto SaaS Protection customers hosted in multiple regions are experiencing backup and restore issues. Export services are not affected. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.k...
Datto BCDR - Server3824 (Germany Region) - Degraded Node Functionality
major Observed active window 216h 36m

View incident details and source

Started:

Off-Site Synchronization Off-Site Recovery
identified
We are aware of a problem where Datto BCDR users paired to Server3824 will experience a service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
DattoRMM - Vidal - Activity Log pages are slow to load
minor Observed active window 169h 27m

View incident details and source

Started:

Vidal (US East)
monitoring
We are aware of a problem where the Activity Logs on our Vidal Platform are slow to load after our 15.1 release. The Kaseya Engineering Team has applied a fix and is currently monitoring this closely. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto SaaS Protection - Backup performance degradation for M365 services affecting multiple pods/regions
major

View incident details and source

Started:

SaaS Protection Backups
monitoring
Post-migration validation and optimization activities following Microsoft Graph API enablement remain in progress. Backup cadence remains unchanged, with all Microsoft 365 services in V2 environments continuing to back up three times per day. In V3 environments, Exchange backups continue at three times per day, while SharePoint, OneDrive, and Teams remain at one backup per day as optimization efforts continue to mitigate Microsoft service throttling and maintain high backup success rates. Engineering teams continue to deploy enhancements and optimizations as part of ongoing post-migration validation efforts. Platform performance and stability remain under close monitoring. We appreciate your patience and will provide additional updates as progress continues.
monitoring
Microsoft Graph API enablement has now been completed across all V2 and V3 environments globally. To allow additional time for post-migration validation and optimization activities, the maintenance window has been extended. M365 backup cadence remains unchanged for V2 environments, with backups continuing at three times per day for all supported services. In V3 environments, Exchange backups remain at three times per day, while SharePoint, OneDrive, and Teams continue on a reduced cadence of one backup per day during ongoing optimization efforts. Engineering teams continue to closely monitor platform performance, address isolated performance issues, and implement targeted optimizations to ensure continued platform stability and reliability. We will continue to provide updates as progress is made and appreciate your patience while this work is completed.
monitoring
Microsoft Graph is enabled across all V3 environments globally and now is enabled on all V2 environments globally. Microsoft 365 backup cadence is unchanged for V2 environments. V3 environments have their Exchange Backups back to three a day while the rest remain on a reduced cadence. Engineering teams continue to monitor platform performance, address isolated issues, and implement ongoing optimizations.
monitoring
Microsoft Graph enablement remains active across all V3 environments globally, with rollout across V2 environments continuing to progress as planned. Graph has now been enabled in multiple V2 regions, with additional regions currently being onboarded. Microsoft 365 backup cadence remains unchanged for V2 environments at three backups per day. V3 environments remain on a reduced cadence of one backup per day to maintain high backup success rates while migration and optimization efforts continue. Engineering teams continue to monitor platform performance, address isolated issues, and implement ongoing optimizations. Graph enablement across the remaining V2 environments is expected to be completed in the coming days.
monitoring
Microsoft Graph enablement has been completed across all SaaS Protection V3 environments, with rollout across V2 environments continuing and expected to be completed in the coming days. To support service stability during the ongoing migration from EWS to Microsoft Graph, Microsoft 365 backup cadence remains adjusted in some environments. V3 environments are currently operating on a reduced backup schedule of one backup per day for M365 workloads to maintain high backup success rates during the transition. V2 environments continue to operate on the standard three backups per day schedule. Our engineering teams continue to closely monitor platform performance, address a small number of remaining service-specific issues, and implement ongoing optimizations. While migration activities remain in progress, some customers may continue to experience intermittent backup performance impacts for certain M365 workloads. Migration efforts continue to advance as planned and remain on track for completion by the end of September.
monitoring
Microsoft Graph API enablement has been completed across all SaaS Protection V3 pods globally, with V2 node rollout progressing and expected to finish this week. Our R&D team is actively monitoring performance, addressing issues impacting a small number of V3 pods, and implementing ongoing optimizations. Migration from EWS to Microsoft Graph continues to advance, with completion currently expected by the end of September. During this transition, some customers may continue to experience temporary backup performance degradation for M365 services while migration activities remain in progress.
monitoring
We continue to make steady progress on our migration efforts. Our teams are actively monitoring performance and stability as the rollout expands, and work remains ongoing to ensure a smooth transition while maintaining service reliability.
monitoring
Backup success rate metrics across M365 services in all regions have remained consistent as our R&D team continues migration-related optimization efforts and monitors overall service health and performance. While migration activities completed to date have delivered positive results, additional optimization work has been identified during ongoing monitoring efforts. To ensure these items are addressed appropriately, the maintenance window has been tentatively extended through Sunday, September 20, 2026. Some customers may continue to experience backup performance impacts affecting select Microsoft 365 services while this work remains ongoing. The R&D team remains actively engaged and focused on further improving backup performance and reliability while minimizing customer impact. We appreciate your continued patience and will provide further updates as work progresses.
monitoring
Backup success rate metrics continue to steadily improve across M365 services in all regions as our R&D team progresses migration efforts and implements additional optimizations. Service health and backup reliability continue to trend positively, with teams focused on further performance improvements and completing the Microsoft Graph migration while closely monitoring backup health and system performance across the environment.
monitoring
Our R&D team continues to make strong progress on the Microsoft 365 backup recovery effort and migration activities. Backup success rates have improved significantly across all Microsoft 365 services and regions. Migration and optimization efforts remain ongoing as teams focus on further improving performance and completing the remaining work. While some customers may still experience intermittent delays, overall service health and backup reliability continue to trend positively. Our teams remain actively engaged and will provide additional updates as progress continues.
monitoring
Our R&D team continues to make progress restoring and stabilizing Microsoft 365 backup operations. Additional Microsoft Graph API migrations have been completed across multiple regions, and recovery efforts continue to deliver improvements across affected services. To support recovery and maintain backup reliability, backup cadence remains temporarily adjusted for some Microsoft 365 workloads. In addition, changes have been implemented to distribute backup processing more evenly across regions, helping reduce peak load and improve overall system performance. As a result of these optimization efforts, some customers may continue to experience delayed backup start times or intermittent backup delays while processing is normalized across the environment. Backup operations remain active across all supported Microsoft 365 services. Many affected services and regions have stabilized, and recovery progress continues across the remaining environment. Our teams remain focused on completing the remaining work and are closely monitoring backup health and performance.
monitoring
Our R&D team has deployed additional changes to mitigate the issue affecting M365 backup operations. Since these changes were implemented, we have observed continued improvement in backup success rate metrics across affected regions. Our teams are closely monitoring backup health and performance as recovery progresses and will continue to evaluate the effectiveness of the recently deployed mitigations. While improvements have been observed, backup success rate metrics continue to recover, and some customers may still experience intermittent delays while the environment stabilizes.
identified
Our R&D team continues to actively address the issue as a top priority. Work is ongoing to implement corrective measures, while teams closely monitor service performance as recovery efforts progress. We will provide additional updates as more information becomes available.
identified
We are aware of degraded backup performance affecting Microsoft 365 services, including Exchange, OneDrive, SharePoint, and Teams, as ongoing maintenance and migration activities continue. Some customers may experience intermittent backup delays, reduced backup performance, or missed backup cycles while our R&D team works toward full service restoration. Our R&D team has identified the contributing factors and is actively implementing fixes while continuing the migration from Exchange Web Services (EWS) to Microsoft Graph APIs. This migration remains an important initiative to improve long-term platform performance, scalability, and reliability; however, we are currently seeing increased API throttling and processing delays affecting Microsoft 365 backup operations across multiple workloads. Our teams are closely monitoring backup health and performance across all regions and are deploying additional optimizations designed to reduce throttling, improve processing efficiency, and restore normal backup operations. Google Workspace services are not affected by this issue and continue to operate normally. We will continue to provide updates as additional information becomes available.
monitoring
As part of the ongoing migration effort, a planned maintenance window is scheduled for all regions to begin today Friday, September 4, 2026, and continue until Tuesday, September 8, 2026. During this period, our R&D team will be implementing additional changes and optimizations to further improve performance, reduce API throttling, and support the continued transition to Microsoft Graph APIs. Our teams will closely monitor backup health and performance throughout the maintenance window. While overall service stability remains strong, some customers may experience occasional backup delays, reduced backup performance, or missed backup cycles for Microsoft 365 services as migration and optimization activities continue. Our teams will continue to closely monitor backup health and performance throughout the maintenance window and provide additional updates as they become available.
monitoring
SaaS Protection backup performance remains strong across all regions and supported services. Backups for Google services, OneDrive, and SharePoint continue to run on the standard three-times-daily schedule. To support consistently high success rates during the ongoing transition from Exchange Web Services (EWS) to Microsoft Graph APIs, Exchange and Teams backups continue to operate on a temporary twice-daily cadence. Our R&D teams remain focused on the migration effort, making and refining configuration changes as needed while closely monitoring backup health and performance. Although overall system stability remains strong, some customers may continue to experience occasional backup delays or missed backup cycles due to API call throttling as migration and optimization activities progress. The migration from EWS to Microsoft Graph APIs is ongoing and is still projected for completion between late August and early September 2026.
monitoring
SaaS Protection backup success rates across all services and regions remain high. Google services, along with OneDrive and SharePoint, continue to process backups at the normal 3x daily cadence. Exchange and Teams backup cadence remains temporarily reduced to 2x daily backups to help maintain high backup success rates during the ongoing migration from Exchange Web Services (EWS) to Microsoft Graph APIs. Our R&D team continues to implement and refine configuration adjustments throughout the migration process and is actively monitoring backup performance across all regions. While overall performance remains stable, some customers may still experience intermittent backup delays or missed backups as optimization and migration efforts continue. The migration to Microsoft Graph APIs remains in progress and is currently expected to be completed between late August and early September.
monitoring
Backup operations remain healthy, with success rates staying high across all services and regions following the recent changes. Work on the EWS to Microsoft Graph API migration is ongoing, and our R&D team continues to monitor for any further issues.
monitoring
Our R&D team has completed deployment of the latest changes for the Graph API components as part of the ongoing migration and backup success rates for all services across all regions remain high. We are continuing to monitor.
monitoring
Backup success rate metrics for all services across all regions continue to remain stable at normal levels. Our R&D team is actively completing deployment of additional improvements to all regions and they are continuing to monitor.
monitoring
Backup success rate metrics for all services across all regions have recovered and remain stable at normal levels. Google services, along with OneDrive and SharePoint, continue to process 3x daily backups while Teams and Exchange services remain temporarily set to 2x daily backups to maintain high success rates as the migration to Microsoft Graph APIs progresses. Our R&D team is continuing to monitor.
identified
Our R&D team has deployed additional improvements, and backup cadence has now been restored to 3x daily backups for all Google services, OneDrive, and SharePoint across all regions. Exchange and Teams backup cadence remains temporarily set to 2x daily backups to help maintain high backup success rates during the ongoing transition to Microsoft Graph APIs. We have observed continued improvement in backup performance following these changes, and our R&D team is closely monitoring backup success rates across all affected regions. Additional performance enhancements are currently being deployed to further reduce API throttling, improve backup performance, and accelerate recovery. Deployment of these changes is expected to be completed early next week.
identified
Datto SaaS Protection is currently experiencing degraded backup performance and missed backups for some Microsoft 365 services across multiple regions. The issue has been linked to increased API activity and application-level throttling associated with the ongoing transition from Exchange Web Services (EWS) to Microsoft Graph APIs. Affected regions: US (USE/USW) Australia (AUE) Canada (CAE) Germany (DES) UK (GBE) Singapore (SG) Our R&D teams have identified the primary contributing factors and are actively working to restore full service functionality. Multiple mitigation measures have been implemented, including application performance optimizations, infrastructure and capacity improvements, deployment of configuration changes across affected SaaS Protection pods, and a temporary reduction in backup cadence from 3x daily backups to 2x daily backups to help reduce API demand and improve backup success rates during the transition. These actions have resulted in measurable improvement, with backup success rates increasing across all affected regions over the past 24 hours. While performance continues to stabilize, some customers may still experience backup delays or missed backups as remediation efforts continue. Additional software enhancements are scheduled for deployment this week to further reduce API throttling, improve backup performance, and accelerate recovery. Customer data protection remains the highest priority, and our R&D teams continue to closely monitor the environment while implementing further improvements. Updates will continue to be provided through the Kaseya Status Page as progress is made toward full service restoration.

Legacy Incident Archive

95 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

April 2026
Datto RMM - All Platforms - RMM Agent cannot be installed due to Certificate errors
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are aware of a problem where the Datto RMM agent cannot be installed due to Certificate errors. The Kaseya R&D Team are investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto AV – Behavioral Detection Update
Source not attested
Last archived state: resolved
View archived record details
identified
A fix has been developed and this will be released tonight, after 12am(EST) and applied during your next set maintenance window.
identified
We are aware of a low-frequency issue where certain legitimate files may be unexpectedly quarantined by a behavioral detection component. What’s happening In rare cases, a behavioral detection module may briefly activate during endpoint startup before policy settings are fully applied. During this short window, files that would normally be allowed may be flagged and quarantined. Customer impact Low probability, but non-zero Quarantined files may not generate alerts in the console Files can...
March 2026
Datto RMM - Vidal - Filter loading error "Out of sort memory"
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto RMM filters on the Vidal platform are failing to load with an "Out of sort memory" error message. The Kaseya R&D Team is investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto BCDR - Local Virtualization and Verification Will Not Execute Successfully on Windows 2003 and Windows XP 32‑bit Systems
minor Source not attested
Last archived state: resolved
View archived record details
identified
Our R&D team has identified the underlying issue and is actively working toward a targeted resolution. The deployment window is projected to commence upon completion of the current major device release. In the interim, please utilize cloud‑based virtualization services to ensure continued operational continuity in the event of a Disaster Recovery scenario. Please note: This issue is currently impacting only a limited subset of the Datto Windows Agent fleet.
investigating
We have identified an issue introduced in the latest device software release related to agents running 32 bit versions of Windows Server 2003 and Windows XP where screenshot verification and local virtualization fails to start. We are currently investigating the issue to determine the cause and potential fix. In the meantime, we have verified that cloud virtualizations are still functional for any DR scenarios. We will provide more information as it becomes available.
Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'des1-saas-p1'
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
Backup cadence on pod 'des1-saas-p1' remains at the normal 3x daily backups and our R&D team has deployed additional improvements to further address the issue. They are continuing to closely monitor backup performance of all services on the pod.
monitoring
Our R&D team has increased the daily backup cadence on pod 'des1-saas-p1' from 2x daily backups to 3x daily backups and they are actively monitoring backup performance of all services on the pod.
monitoring
The backup cadence on pod 'des1‑saas‑p1' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. R&D is continuing to develop improvements, targeted for release Q2 2026. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.
monitoring
After monitoring over the weekend, all services are backing up normally at 2x backup per day again. Our R&D teams are continuing to develop and test improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
monitoring
We are aware of additional reports of backup performance degradation affecting SharePoint services on pod 'des1-saas-p1'. Our R&D team has implemented changes to address the issue and are monitoring.
monitoring
Daily backup cadence on pod ‘des1‑saas‑p1’ remains temporarily set to 2x backups per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Our R&D teams are actively developing and testing improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
monitoring
Backup frequency on this pod is still set to 2x backups per day to maintain high backup success rates while the R&D team continues to develop and test improvements to address the issue. The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod. Backup success rates remain stable and the R&D team is continuing to monitor.
identified
Backups remain stable at 2x backups per day and our R&D team is continuing to monitor closely. The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod.
identified
Backups continue to process normally at 2x backups per day and success rates remain stable. Our R&D team will continue to monitor backup performance on the pod closely over the weekend as they prepare to increase backup frequency to 3x backups per day early next week.
identified
Backup frequency on the pod was increased to 2 backups per day again and our R&D team is monitoring closely as backup success rates continue to improve.
identified
The R&D team has successfully restored pod stability, and backups are now processing in real time. They are working to resume the schedule of two backups per day, beginning with the next backup window. Additional capacity is also being added to maintain continued pod stability, and to enable increasing the backup cadence to 3 backups per day in the near future.
identified
Recent changes made to improve SharePoint and Teams backup performance did not produce the expected results. Our R&D team will be implementing additional mitigation measures over the next 24 hours to further stabilize SharePoint and Teams backups for customers on the pod. As part of this work, we will be temporarily reducing backup frequency for customers from 2x backups per day to 1x backups per day. These adjustments are intended to improve overall system reliability while long‑term enhan...
identified
Issues affecting Teams backup performance have been identified and our R&D team is continuing to address the underlying problem affecting SharePoint/Teams backup performance for some customers hosted on the pod.
identified
After the changes implemented yesterday, the Kaseya R&D team is working to deploy additional improvements to further address the degraded backup performance affecting some customers hosted on pod 'des1-saas-p1'.
monitoring
The Kaseya R&D team has implemented additional changes to help address the issue and are monitoring the results closely.
identified
We are aware of a problem where some customers hosted on pod 'des1-saas-p1' are experiencing backup performance degradation for some SharePoint services. The Kaseya R&D Team has identified the issue and are actively working to resolve it. In the meantime, the R&D team has temporarily decreased the daily backup frequency on pod 'des1-saas-p1' from 3x per day to 2x per day to help maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Subscribe to the Kaseya Status...