Looking for an update now? Check the current status, or follow Kaseya Inc for future changes.
0%of 73 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
October 2026
0%
31
31
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
November 2026
Datto BCDR - US Region - Server5582 Not Accessible
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto BCDR users paired to Server5582 in the US East region are experiencing degraded performance due to a node availability issue.
The Kaseya Engineering Team is currently investigating the issue and working towards a resolution.
If you need any assistance, please contact our support team for assistance through the <a href="https://helpdesk.kaseya.com/hc/en-gb#/contact">Kaseya Support Portal</a>.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
Multiple Products - Microsoft 365 Connection Issues
We are now seeing affected services recovering as Microsoft continues to address the issue.
For further details and the latest updates please visit the <a href="https://status.cloud.microsoft/m365/">Microsoft Status Page</a>
identified
Microsoft continues to address the issue with urgency until full mitigation and our R&D teams are monitoring progress closely.
Please see the latest updates on <a href="https://status.cloud.microsoft/m365/">Microsoft Status Page</a>
investigating
Please see the latest updates on <a href="https://status.cloud.microsoft/m365/">Microsoft Status Page</a>
investigating
We are aware of a problem with multiple products being unable to connect to Microsoft 365 services.
This is caused by the current outage being experienced by Microsoft Exchange. Please follow the <a href="https://status.cloud.microsoft/m365/">Microsoft Status Page</a> for updates.
IT Glue - North America - Intermittent 403 Errors when accessing IT Glue
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where users are receiving 403 errors when attempting to access IT Glue in North America.
The Kaseya Engineering Team is investigating this issue.
If you need any assistance, please contact our support team for assistance through the <a href="https://helpdesk.kaseya.com/hc/en-gb#/contact">Kaseya Support Portal</a>.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
ConnectBooster - Payment Failures due to Surcharge Settings Between ConnectBooster and NMI
Kaseya has deployed a fix to address the Transaction Failures through the NMI Gateway due to Surcharge settings.
We are currently monitoring the behavior and will provide future updates as they become available.
identified
We are aware of a problem where some users are experiencing transaction failures within ConnectBooster due to Surcharge settings between the ConnectBooster Portal and the NMI Gateway
The Kaseya Engineering Team have Identified the issue are working on a fix.
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/
DRMM - Syrah - Integration - ITGlue - 401 errors in Web Remote
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where an issue affecting the IT Glue Passwords feature within Datto RMM Web Remote.
Partners are encountering the following errors when attempting to access IT Glue passwords:
"Failed to load Organizations": "HttpStatusCode 401"
"Failed to load Configuration Matching": "HttpStatusCode 401"
The Kaseya Engineering Team is investigating
If you need any assistance, please contact our support team for assistance through the <a href="https://helpdesk.kaseya.com/hc/en-gb#/contact">Kaseya Support Portal</a>.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
Kaseya is aware of a critical vulnerability in Google Brotli: CVE-2026-111497
CVE-2026-111497 is a buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms and allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Customers should follow product-specific guidance for applicable updates and any required actions.
We are actively managing the Brotli decoder vulnerability and tracking product-specific impact and remediation. Compensating controls, where implemented, are intended to reduce exposure and potential impact while remediation progresses. Our Security and Product teams continue to monitor affected environments and address outstanding remediation. For additional questions, please create a ticket with our Support team here: https://helpdesk.kaseya.com/
Datto Partner Portal - Login - Unable to proceed past the Account Selection Page
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where Datto Partner Portal is inaccessible
The Kaseya Engineering Team is currently investigating the issue
If you need any assistance, please contact our support team for assistance through the <a href="https://helpdesk.kaseya.com/hc/en-gb#/contact">Kaseya Support Portal</a>.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
We are continuing to monitor for any further issues.
monitoring
Following <a href=https://uptime.n-able.com/event/202613/>N-able’s disclosure of a critical vulnerability</a> earlier this week, we temporarily inactivated Autotask and IT Glue API users tied to N-able integrations. These steps mirror N-able’s containment measures and protect credentials stored in N-able environments.
If you use the N-able integration with BMS, we recommend disabling it as well until you’ve completed the remediation steps in <a href="https://uptime.n-able.com/event/202580/">N-able’s advisory</a>.
We have no reason to believe Autotask, IT Glue, BMS or Kaseya systems were accessed. Only customers using an N-able integration with these products are affected.
<b>To restore your Autotask integration:</b>
- Complete the remediation in <a href="https://uptime.n-able.com/event/202580/">N-able’s advisory</a> for your environment.
- Have a System Admin reactivate the associated API user in Autotask; see this <a href=https://help.vsa10.kaseya.com/help/Content/1-Modules/integrations/autotask.htm>Autotask Integration KB</a> for reference.
<b>To restore your IT Glue integration:</b>
- Complete the remediation in<a href="https://uptime.n-able.com/event/202580/"> N-able’s advisory</a> for your environment
- Once the N-able remediation steps have been followed, proceed to this ITG KB under the section - <a href=https://help.itglue.kaseya.com/help/Content/1-admin/it-glue-api/getting-started-with-the-it-glue-api.html>Restart a paused API key </a>
<b>Disable your BMS N-able integration:</b>
- We recommend disabling the BMS API key for APIs that utilize N-able.
- Complete the remediation in <a href="https://uptime.n-able.com/event/202580/">N-able’s advisory</a> for your environment.
- Once the N-able remediation steps have been followed, proceed to this BMS KB under section - <a href=https://help.itglue.kaseya.com/help/Content/1-admin/psa-integrations/integrating-with-kaseya-bms.html?Highlight=bms%20api>Enable or Disable Sync</a>
We haven’t changed API keys or secrets, and rotation isn’t currently required. We’ll be updating this thread as more information comes through. For additional questions, please contact our <a href="https://helpdesk.kaseya.com/hc/en-gb">Kaseya Support</a> team.
Autotask - Multiple Zones - Integrations attempting to utilize the API are unable to connect to Autotask
Limited ReleaseAmerica EastAmerica East 3America West 2America West 3UK 2 (United Kingdom)Australia / New Zealand
identified
We are aware of a problem where Integrations attempting to utilize the API are unable to connect to Autotask. The error received is an "Internal Server Error" with the message "The server encountered an internal error or misconfiguration and was unable to complete your request"
The Kaseya Engineering Team have identified the issue and are working on a fix.
If you need any assistance, please contact our support team for assistance through the <a href="https://helpdesk.kaseya.com/hc/en-gb#/contact">Kaseya Support Portal</a>.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
The Kaseya Engineering team is continuing to monitor device sync queues and has observed positive recovery.
The Engineering team are going to continue to monitoring throughout the business day to ensure stability.
We will provide another update later today.
monitoring
The Kaseya Engineering team successfully deployed the fix to the Zinfandel platform during a scheduled after-hours maintenance yesterday. Since the deployments, both Pinotage and Zinfandel are no longer observing device sync backlogs, all other platforms continue to remain clear as well.
The Engineering team will continue monitoring queue throughput and overall system health throughout the day.
monitoring
The Kaseya Engineering team successfully deployed the fix to Pinotage (EU1) during scheduled after-hours maintenance yesterday. Since the deployment, we have observed a significant and steady reduction in the device sync backlog. We anticipate the remaining queue on Pinotage will be fully resolved by tomorrow morning (EMEA regional business hours).
The team is currently planning to deploy the same update to Zinfandel (US West) tonight, outside of standard regional business hours, to accelerate the processing of its remaining backlog.
We are also pleased to report that the sync delays on Concord (US East) and Syrah (APAC) have been successfully mitigated, and both platforms are actively processing as expected.
Our Engineering team will continue to closely monitor queue throughput and overall system health across all affected platforms. We will provide our next update tomorrow morning.
monitoring
The Kaseya Engineering team has developed a fix intended to address the device sync processing delays. Deployment to Pinotage is planned for after hours today.
Following the deployment, Engineering will monitor performance on Pinotage before determining the deployment schedule for the remaining affected platforms.
We will provide an additional update as significant progress is made.
monitoring
The Kaseya Engineering team continued monitoring device sync processing throughout the weekend. While the backlog has returned to normal levels on Syrah, processing of the backlogs has taken longer than anticipated on the other affected platforms and some device sync actions may continue to experience delays.
Engineering has developed an additional mitigation to accelerate processing of the remaining queues. The change is currently undergoing validation and, once complete, will be deployed to the affected platforms. We will continue monitoring system performance and sync processing throughout this work.
We will provide an additional update as significant progress is made.
To receive notifications about future maintenance events and service updates, subscribe to the Kaseya Status Page (https://status.kaseya.com)
monitoring
The Kaseya Engineering team has implemented mitigation measures, and all affected platforms are actively processing a backlog of device sync actions. We continue to see steady progress in reducing the queue; however, additional time is required to fully process the remaining backlog.
Our teams will continue monitoring system performance throughout the weekend and will provide updates as significant progress is made.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
identified
We are aware of a problem where Device Syncs for the Autotask integration on platforms upgraded to version 15.2.0 of Datto RMM are experiencing delays. This issue affects new and existing devices from syncing their data into Autotask, so changes in Datto RMM will not immediately be reflected in Autotask.
The Kaseya Engineering Team have identified the issue are are working on a fix.
If you need any assistance, please contact our support team for assistance through the <a href="https://helpdesk.kaseya.com/hc/en-gb#/contact">Kaseya Support Portal</a>.
To receive notifications about future maintenance events and service updates, subscribe to the <a href="https://status.kaseya.com/">Kaseya Status Page</a>.
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
majorSource 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...
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
minorSource 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'
minorSource 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...
