Daily provider-status observations and published incident history for Kaseya Inc.
Unknown
Current status for Kaseya Inc cannot be verified right now. Verified .
Official provider source.
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>.
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>.
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>.
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>.
We are aware of a problem where automated syncing of devices from Datto RMM to Autotask PSA configuration items is interrupted following the Datto RMM v15.2.0 update. Please note that this issue is isolated to device synchronization; Site to Company mapping is unaffected and remains functional. As a result of this interruption, newly onboarded devices, as well as recent updates or deletions to existing devices in Datto RMM, may not automatically sync to Autotask.
The Kaseya Engineering Team has identified the root cause and we are working to restore device sync functionality. We will provide another update as soon as more information becomes available. We apologize for any disruption this may cause to your workflow.
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>.
Datto Endpoint Backup for PC - US Region Cloud Siris 279760 - Degraded Backup Functionality
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto Endpoint Backup for PC assets paired with Cloud Siris 279760 may experience degraded backup functionality.
The Kaseya Engineering Team is 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>.
BMS - US - Multiple Customers Experiencing Resource Unavailable / Record Not Found Errors Across Modules
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 Multiple customers in the BMS US region are reporting issues accessing various modules, including Service Desk, CRM, and Admin (Support Users).
The Kaseya Engineering Team is actively 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>.
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
Autotask PSA - UK02 - Workflow Rule Delay and Latency
minorSource 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 a fix is being implemented.
investigating
We are aware of an issue affecting Autotask users hosted in the UK02 zone, resulting in increased latency and delays in workflow rule processing.
The Kaseya R&D Team is actively investigating this issue.
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 'des1-bfyii-1701'
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our R&D team has identified the issue and have implemented a fix. The team is monitoring for any other issues.
investigating
We are aware of a problem where customers hosted on node 'des1-bfyii-1701' are currently unable to access their accounts.
The Kaseya R&D Team is currently investigating.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
June 2026
Datto RMM - Intermittent Job Creation Failures on the Syrah (APAC) and Vidal (US East) platforms
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented on both the Syrah and Vidal platforms.
identified
The Kaseya R&D Team identified the cause of the issue where Jobs intermittently fail to be created in the Web UI.
The fix for the problem is currently being tested, and it is planned to be deployed in the coming days.
Datto RMM - Syrah, Vidal - 15.0.1 Cagservice.exe being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
The Kaseya R&D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.0 Datto RMM version's cagservice.exe in a recent security intelligence update for Microsoft Defender Antivirus and other Microsoft antimalware.
This issue was fixed in the security intelligence update version 1.453.344.0, and the issue should no longer occur as long as the device is on this definition version or la...
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are aware of a problem where Datto RMM's 15.0.1 Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint.
The Kaseya R&D Team are investigating this issue.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
INKY - Internally sent emails are not getting delivered and emails to external recipients are getting delayed
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The service has caught up with processing through items queued in INKY, and the R&D team is reviewing individual examples of residual issues .
Please work with our support team and provide them with message IDs for review if the issue appears to still persist.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
The INKY R&D Team is investigating the issue where emails to internal recipients filtered through INKY are not showing up in INKY and not getting delivered to recipients.
Emails to external recipients, while also not appearing in INKY, successfully get delivered but with a noticeable delay.
Please subscribe to this incident to receive update notifications as they become available.
Datto Workplace - Service Issue Affecting EU Cell 4, Cell 7, and Cell 16 (404 Error)
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Customers may still experience a delay in email processing while the service is catching up with the queue that formed during the incidents.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue where partners are unable to access the Workplace portal.
Partners in EU Cell 4, EU Cell 7, and EU Cell 16 are experiencing service disruptions and may receive a 404 Error when attempting to access the portal.
Our engineering team is actively investigating the issue and working to restore service as quickly as possible.
Datto EDR - Issues Accessing Certain Applications Following Recent EDR Update
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We’re pleased to inform you that our Engineering team has released a Hotfix for the Datto AMSI module remaining on devices:
UI 15272
Agent #3.17.1.5552
Fixes:
This release addresses an issue where the Datto AMSI provider remained actively registered on a device after having the AMSI module disabled.
The AMSI module remains disabled globally and will be reintroduced through a controlled rollout.
This change does not disable overall EDR protection. It is a temporary mitigation specif...
identified
If you are still experiencing issues after rebooting, please contact Kaseya Support to receive a script that can be run on affected endpoints to resolve the issue. A hotfix agent update is in progress and will be released shortly. We will update this page once it is available.
investigating
We are aware that some customers are continuing to experience difficulty accessing certain applications, including Microsoft Teams, following a recent Datto EDR update. We are actively investigating and treating this as a priority.
What we currently know:
A recent Datto EDR update enabled additional behavioral monitoring on affected endpoints. We have identified this change as a contributing factor to the issue and are working on a resolution.
What you can do right now:
A reboot of the af...
Endpoint Backup v2 - Backup Failures
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’re pleased to share that our team will begin rolling out the fix to non-U.S. regions on June 23, 2026 at 06:00 PM UTC, followed by deployment to U.S. regions on June 24, 2026 at 08:00 AM UTC.
We appreciate your patience as we work to ensure a smooth and reliable update experience for all customers.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are aware of a problem where a subset of Endpoint Backup v2 assets can experience backup failures due to EOF and AOF errors.
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/
We are continuing to work on a fix for this issue.
identified
We are continuing the rollout of the fixed agent version to production.
identified
The hotfixed agent version is being rolled out to production following successful testing and validation that the changes implemented by the R&D team resolves the issue.
We are deploying the upgrade in batches to mitigate any risks to the health of the infrastructure.
identified
The R&D team identified the issue, and developed a fix.
The change is currently being tested before proceeding with the rollout to production.
investigating
We are investigating an issue causing Endpoint Backup v2 assets to appear offline in UniView. While this issue is ongoing, scheduled backups are not running, recovery points may show as unavailable, and backup, restore, and BMR operations are failing. All regions are affected.
There is no workaround available at this time. The Kaseya R&D team is engaged and actively investigating, and we will provide updates as more information becomes available.
Subscribe to the Kaseya Status Page for up-t...
A fix has been implemented and we are monitoring the results.
identified
We are aware of a problem where BCDR users paired to Server5673 can experience degraded offsite capabilities.
The Kaseya R&D Team has identified the issue and is working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
