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.
May 2026
Datto Workplace / Datto File Protection - US Cells - SSO login is currently unavailable for users based in the United States
minorSource 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 a subset of US Datto Workplace and Datto File Protection users cannot login via Portal SSO. Agent login access remains unaffected, and users continue to have full access.
The Kaseya R&D Team is investigating the issue and working towards a resolution.
Workaround:
Please ensure your local region is specified when utilizing direct login:
EX: eu.workplace.datto.com
EX: us.workplace.datto.com
If assistance is needed, our Technical Support team can as...
Datto SaaS Protection - Backup performance degradation for SharePoint/Teams services on pod 'des1-saas-p0'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Backup success rate metrics for SharePoint/Teams services have returned to normal. Our R&D team is continuing to monitor.
monitoring
We are seeing improvement in backup success rate metrics for SharePoint/Teams services on 'des1-saas-p0'. Our R&D team is working to implement additional changes to address the issue further and is continuing to monitor.
monitoring
Our R&D team has implemented changes on pod 'des1-saas-p0' to address the backup performance degradation and they are monitoring the results.
identified
We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' may experience degraded SharePoint/Teams backup performance.
The Kaseya R&D 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 Workplace AU5 - Agents are unable to connect and sync data; files cannot be created and/or saved in Workplace Online
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
The R&D and Infrastructure teams are continuing to investigate the cause of the issue.
investigating
We are currently investigating an issue impacting partners on AU5 cell, where agent connections and file syncs are failing.
Affected partners may see server errors in the Workplace Agent with both versions.
Creating files in Workplace Online may fail with a 404 error.
Opening existing files with the Google Docs integration may fail with an error.
Saving changes to existing files through the Microsoft 365 integragration may silently fails.
Subscribe to the Kaseya Status Page for up to date ...
Datto SaaS Protection - Service disruption for customers hosted on node 'Gbe2-saas-p0-app-2'
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The Kaseya R&D team has implemented changes to help address the issue and are monitoring the results closely.
investigating
We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection services. Backups are still operational, but the platform is unable to be accessed.
The Kaseya R&D Team is investigating 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/
April 2026
Datto SaaS Protection - Service disruption for customers hosted on pod 'cae1-saas-p1'
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Backup success rates on the pod have returned to normal and remain stable. Our R&D team is continuing to monitor.
monitoring
Backup success rates have improved since a fix has been implemented. Our R&D continues to monitor the health of the pod until expected levels are reached.
monitoring
Our R&D team has implemented a fix to address the issue impacting the pod. We are actively monitoring the node for any other issues.
identified
We are aware of a problem where customers hosted on pod 'cae1-saas-p1' are experiencing a disruption to their SaaS Protection services.
Our R&D team is performing maintenance on pod 'cae1-saas-p1' to resolve an issue that was identified. The estimated down time is up to 8 hours.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto SaaS Protection - Backup performance and access issues for customers hosted on node 'gbe2-bfyii-1225'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our R&D team has implemented a fix to address the SaaS Protection account access issues and customers should no longer receive a 504 error when logging in. We are actively monitoring the node for any other issues.
identified
We are aware of a problem where customers hosted on node 'gbe2-bfyii-1225' are experiencing degraded backup performance for SharePoint/Teams services as well as receiving 504 errors when attempting to access their SaaS Protection accounts.
The Kaseya R&D 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 - Backup performance degradation for M365 services on pod 'usw3-saas-p1'
minorSource 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 currently aware of a problem where some Datto SaaS Protection customers hosted on pod 'usw3-saas-p1' are experiencing degraded backup performance for some M365 services.
The Kaseya R&D 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 RMM - Zinfandel - Agents going offline
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 Datto RMM agents, within the Zinfandel platform going offline.
The Kaseya R&D Team is aware and currently investigating.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Datto RMM - Zinfandel: Delayed Jobs
minorSource 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 Jobs on Datto RMM's Zinfandel platform are delayed
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/
VSA10 - Service Degradation for subset of VSA10-US customers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Subset of VSA10 US customers may be experiencing degraded performance intermittently, which may impact administrators ability to manage endpoints.
We are aware of the issue and our team is actively working to resolve the same.
We apologize for any inconvenience caused.
- Cloud Operations Team
