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.
July 2026
Datto SaaS Protection - Service disruption for customers hosted on node 'des1-bfyii-2985'
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our R&D team has implemented a fix to restore account access and have confirmed backups are running.
We are monitoring for any other issues.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where SaaS Protection customers hosted on node 'des1-bfyii-2985' are unable to access their accounts and are experiencing a disruption to their services.
The Kaseya R&D Team is actively investigating.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto SaaS Protection - Service disruption affecting customers hosted on pod 'gbe2-saas-p0'
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Our R&D team has implemented additional changes to address the intermittent account access issues that were still affecting some customers hosted on pod 'gbe2-saas-p0' and backups for all services are continuing to process.
We will be monitoring the pod closely for any other issues.
identified
Our R&D team is continuing to address the account access issues still affecting some SaaS Protection customers hosted on pod 'gbe2-saas-p0' as well as monitoring backup performance.
identified
Our R&D team has confirmed that backups are currently processing on pod 'gbe2-saas-p0' however they are continuing to address an issue affecting customer account access.
identified
Our R&D team is continuing to address the issue and fully restore SaaS Protection services on pod 'gbe2-saas-p0'.
identified
Our R&D team has applied a fix to address the issue and they are currently verifying restoration of all services on pod 'gbe2-saas-p0'.
identified
We are continuing to work on a fix for this issue.
identified
We are aware of an issue where Datto SaaS Protection customers hosted on pod 'gbe2-saas-p0' are experiencing a disruption to all SaaS Protection services.
The Kaseya Engineering Team has identified the issue and is actively working to restore service as quickly as possible.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Autotask - Multiple Regions - Inbound emails are not creating tickets
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 aware of a problem where tickets are not getting created from inbound emails.
The Kaseya Engineering Team is investigating the issue.
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/
Endpoint Backup v2 - UniView is exhibiting inconsistencies in backup reporting, resulting in inaccurate backup status visibility
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our R&D team has implemented a fix, and we're seeing improved performance across the affected systems. We're continuing to monitor the environment to ensure the improvements are sustained.
investigating
We are continuing to investigate this issue.
investigating
We are aware of a problem where Endpoint Backup v2 assets in UniView may incorrectly indicate backup failures despite successful backup completion, which can trigger unnecessary email notifications.
The Kaseya R&D Team is investigating the issue and working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'gbe2-saas-p2'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Backup success rate metrics for SharePoint/Teams services on pod 'gbe2-saas-p2' remain stable at normal levels.
Our R&D team is continuing to monitor.
monitoring
Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' are currently stable at normal levels.
Our R&D team is making additional adjustments to the configuration on the pod to further address the issue and will continue to monitor.
monitoring
Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' have returned to normal levels.
Our R&D team is continuing to monitor.
monitoring
Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' are improving after the changes made on the pod earlier today.
Our R&D team is continuing to monitor.
identified
Our R&D team has implemented changes on pod 'gbe2-saas-p2' to mitigate the backup performance issues affecting some SharePoint and Teams services.
identified
We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'gbe2-saas-p2' may be experiencing backup performance degradation affecting some SharePoint/Teams services.
The Kaseya Engineering Team has identified the issue and are actively working to resolve it.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto SaaS Protection - Service disruption for customers hosted on node 'use1-bfyii-2901'
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and the R&D team is actively working to resolve it.
investigating
We are aware of a problem where Datto SaaS Protection customers hosted on node 'use1-bfyii-2901' are experiencing a disruption to SaaS Protection services.
The Kaseya Engineering Team is currently investigating.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
VSAX - EMEA/APAC - Intermittent 500 errors and offline devices
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The Kaseya Engineering Team has developed a fix that will address this issue. The fix will be deployed after hours to our EMEA and APAC App Servers on the following schedule:
17:00 UTC APAC
20:00 UTC EMEA
Those that are online during this change will need to login again as they will be kicked out the system.
Should you have 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...
identified
We are aware of a problem where customers hosted on EMEA/APAC app servers may see intermediate service disruption, getting 500 - internal server error.
The Kaseya Engineering Team has identified the issue and working towards 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/
Intermittent 500 Errors in Datto Partner Portal for Backup Products.
criticalSource 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 an issue where customers are encountering 500 errors while accessing Backup products within the Datto Partner Portal (DPP).
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/
Microsoft Azure Outage in US West Impacting Multiple Kaseya Products
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented by Microsoft Azure and we are monitoring the results.
Please refer to the Microsoft Status page here: https://azure.status.microsoft/en-us/status for more details
identified
We have identified additional Kaseya Products that rely on Microsoft Azure Infrastructure that are affected by this issue.
Partners using Datto / Unitrends Backup for Microsoft Azure and Datto / Unitrends Endpoint Backup with Disaster Recovery in the US West region will experience issues with Device Check-In, Device Registration, and Back Up.
The Kaseya R&D team are continuing to work with the Microsoft Azure team to resolve this issue and we hope to have updates on a resolution as soon as ...
identified
Kaseya R&D are continuing to work closely with Microsoft Azure to resolve this issue affecting the KaseyaOne Portal.
identified
We have verified that the KaseyaOne Portal is being impacted by the Microsoft Azure Outage.
Please follow their Status Post as well for updates: https://azure.status.microsoft/en-us/status
investigating
We are aware of a problem where the KaseyaOne Portal is not accessible.
The Kaseya R&D Team is investigating the issue.
Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/phone
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
As a note; To ensure business continuity, for Kaseya modules using Require Log In with KaseyaOne, users must authenticate using their KaseyaOne Unif...
Datto Networking - Web Filtering Configuration Changes on DNA/D200 Devices Failed to Apply Successfully
majorSource not attested
Last archived state: resolved
View archived record details
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 web filtering configuration changes are not being successfully applied on the DNA and D200 appliances.
The Kaseya R&D Team has identified the issue and is working towards a resolution.
In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237.
Subscribe to the Kaseya Status Page for...
