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
An update was deployed to Pinotage (EU1) over the weekend to restore standard device filter evaluation behavior.
Our internal testing confirms that filters are functioning as expected, and all automated tasks are running smoothly. We are actively monitoring platform performance across a full business day before marking this incident fully resolved.
If you paused any scheduled jobs or policies as a precaution, it is now safe to resume them. We will post our next update at the end of the business day.
identified
We are actively addressing an issue affecting device filters that utilize compound criteria, such as "does not contain" combined with nested logical operators.
Engineering is preparing an update to restore previous filter evaluation behavior. The build is currently being validated in our staging environment, and we will provide an update once the production release window is confirmed.
Recommended Actions:
Filters: No action is needed on your existing device filters. Existing configurations will evaluate as expected once the update is deployed.
Automations: As a precaution, partners may choose to temporarily pause or defer non-critical scheduled jobs or policies that target dynamic filters until the update is complete.
We will post our next update once staging validation concludes.
identified
We are aware of a issue affecting device filters that combine negative query conditions, such as “does not contain,” with an embedded AND/OR operator within the filter criteria.
A change with how these conditions are evaluated was made to correct these queries however it was not communicated as expected and may cause some existing filters to return different results than previously anticipated.
We are considering reverting this change, if you believe your filters may be affected, please contact Support for assistance reviewing your configuration and guidance on next steps.
investigating
We are aware of a issue affecting device filters that combine negative query conditions, such as “does not contain,” with an embedded AND/OR operator within the filter criteria.
A change with how these conditions are evaluated was made to correct these queries however it was not communicated as expected and may cause some existing filters to return different results than previously anticipated.
We are considering reverting this change, if you believe your filters may be affected, please contact Support for assistance reviewing your configuration and guidance on next steps.
Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-1555'
Customers hosted on node 'gbe2-bfyii-1555' are accessible again and backups are running normally.
Our R&D team is 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 Datto SaaS Protection customers hosted on 'gbe2-bfyii-1555' 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/
PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619): Kaseya status - Investigation and Remediation
Kaseya is aware of two critical vulnerabilities in PHP: CVE-2026-109618 and CVE-2026-109619.
CVE-2026-109618 involves a remote code execution vulnerability where handling out-of-memory errors via longjmp() leaves request memory uninitialized due to improper control flow management, potentially allowing attackers to achieve remote code execution using out-of-memory (OOM) triggers.
CVE-2026-109619 describes a remote code execution vulnerability where longjmp() fatal error handling leaves global memory pointing to freed memory regions. These regions can later be accessed during subsequent requests, potentially enabling arbitrary code execution.
Kaseya has completed an evaluation of its product portfolio regarding these vulnerabilities. A summary of the current status across impacted products and services is provided in the table below. As our investigation and remediation efforts continue, we will keep the following list updated with the latest information.
Here is what each status means:
<b>Fully Patched:</b> The fix has been applied.
<b>Compensating Controls:</b> We have put controls in place to reduce exposure and potential impact while we work on remediation.
<b>Unaffected:</b> The product is not affected by these vulnerabilities.
Product Status:
AudIT - Unaffected
Autotask PSA - Fully Patched
Datto Backup for Azure Files + Blob Storage - Unaffected
BMS/Vorex - Fully patched
ConnectBooster - Unaffected
Datto Backup For Azure - Unaffected
Datto BCDR - Compensating Controls
Datto Direct to Cloud Products - Compensating Controls
Datto EDR - Unaffected
Datto Networking - Compensating Controls
Datto Partner Portal - Compensating Controls
Datto RMM - Fully Patched
Datto SaaS Defense - Unaffected
Datto SaaS Protection + Backupify - Compensating Controls
Datto Workplace + File Protect - Fully Patched
Endpoint Backup V2 - Fully Patched
Graphus - Unaffected
ID Agent - Fully Patched
Inky - Unaffected
IT Glue - Unaffected
Kaseya One - Unaffected
Kaseya Quote Manager - Fully Patched
Kaseya MDM - Unaffected
Microsoft Entra Backup - Unaffected
MyITProcess - Unaffected
Passly - Unaffected
RapidFire Tools - Fully Patched
RocketCyber - Fully Patched
SaaS Alerts -Unaffected
Secure Payments - Fully Patched
Spanning - Fully Patched
Unitrends - Fully Patched
UniView - Unaffected
vPenTest - Fully Patched
VSA 10 On Prem - Unaffected
VSA 10 Cloud - Fully Patched
VSA 9 On Prem - Unaffected
VSA 9 Cloud - Fully Patched
Please note that Unitrends customers will need to take an additional action as outlined in our Knowledgebase: https://help.unitrends.kaseya.com/help/Content/Satori/release-notes/release-notes-11-2-0-3.htm
We will continue to provide updates as additional information becomes available.
For additional questions, please create a ticket with our Support team here: https://helpdesk.kaseya.com/hc/en-gb#/contact
<b>Changelog Last Update: 11/12/2026 - Spanning - Moved from Compensating Controls to Fully Patched</b>
investigating
Two critical vulnerabilities were disclosed in third-party PHP libraries that allow unauthenticated remote code execution. Kaseya security teams are assessing all Kaseya systems and products and applying fixes as they become available.
This page is the source of truth for Kaseya status and guidance.
Product Status:
All products: Customer action: none
Kaseya corporate infrastructure: Customer action: none
Third-party components in Kaseya products: Customer action: none
RocketCyber - EU Region - Pages loading slow or not at all
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where RocketCyber partners, in the EU region, are experiencing web pages loading slow or not at all, within the platform.
The Kaseya Engineering Team is currently 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/
A third party vendor, ConnectWise, recently reported attempts of unauthorized access associated with the ConnectWise Cloud Backup environment. ConnectWise has initiated their incident response procedures, and have applied containment measures as they continue to investigate. At this time, according to ConnectWise there is no indication that ConnectWise partner backup data has been accessed. All additional updates related to this incident can be found on the ConnectWise Status Page at status.connectwise.com.
As part of our ongoing security monitoring efforts, the Kaseya Security Operations Center deployed additional detection measures on October 16, 2026, targeting publicly disclosed indicators of compromise. Activity matching these indicators is automatically designated as critical severity and promptly reviewed by our security analysts.
The Kaseya product team has also deployed a fortify action within SaaS Alerts and KSIEM environments to help mitigate this risk further. Please follow the steps below to apply the fortify action:
Action Name: Disable ConnectWise Cloud Backup and Cloud Management apps
Steps to Deploy within SaaS Alerts and KSIEM portal:
Within the left menu, under "Modules", select Fortify → Actions, then perform the following:
1. Set Select Product to Microsoft.
2. Set Select Organization to the customer's org (or leave it on All), and leave Select Actions on All.
3. Click Show Actions.
4. Search for Disable ConnectWise Cloud Backup and Cloud Management apps in the search box.
5. Under the action's buttons, click the wand icon labelled Apply.
If you feel you have been compromised due to this issue, please contact Kaseya support.
Datto Saas Protection- Partners Unable to Access Clients Hosted on Node isw1-bfyii-1134
The Kaseya R&D Team implemented a fix, and as a result, the clients hosted on the node are now accessible and full functionality is restored.
We are currently monitoring the health of the service and the progress with which the service is working through the queued backups.
The estimated time for full recovery is up to 8 hours.
investigating
We are aware of an issue where some Datto SaaS Protection Partners are unable to access customer accounts hosted on the isw1-bfyii-1134 node
The Kaseya Engineering Team is investigating the issue.
If you have any 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 the latest updates: https://status.kaseya.com/
Datto Workplace - AU5 - Agents/Portal are unable to connect
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where agents are unable to connect and portal users are unable to login in the AU region.
The Kaseya Engineering Team is currently investigating this 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/
Datto Endpoint Backup for PC - Cloud Siris 296721 - US East - Degraded Cloud Operations
A fix has been implemented and we are monitoring the results.
investigating
We are aware of a problem where Datto Endpoint Backup for PC users hosted on Cloud Siris 296721 in the US East region can experience degraded backup performance.
The Kaseya R&D Team is currently investigating the issue and 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 - All Platforms - MacOS Agent Connectivity Issues
The Kaseya R&D team will be releasing a new Datto RMM agent build across all platforms. This release includes a new agent version number, making it easier for partners distinguish between agents that have been updated and those that may still require attention.
Deployment of the updated agent build will follow the published platform maintenance schedule. We encourage partners to review the release notes for detailed deployment information, platform rollout timing, and guidance regarding the updated agent version.
Release notes: https://rmm.datto.com/help/en/Content/0HOME/ReleaseNotes/2026/ReleaseNotesDattoRMMv15.1.4.htm
We continue to actively monitor the rollout and its results across all platforms. Partners should verify that their devices remain online following the update. If any macOS devices remain offline or require additional remediation, please refer to the available guidance and contact Support if further assistance is needed.
monitoring
A fix has now been deployed across all supported platforms and is available to all customers. Our teams are actively monitoring the environment and platform telemetry to validate the effectiveness of the changes and ensure systems continue to operate as expected.
We encourage all customers to verify that their macOS devices are online and reporting successfully following the deployment of this fix. While many devices should recover normally, some macOS agents may remain offline and will require additional remediation including manual intervention by the end users. To assist with this process, we have prepared a step-by-step guide that will help you confirm agent status, identify devices requiring further assistance, and walk you through the recommended recovery steps: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm
We appreciate your patience, understanding, and partnership while we worked to investigate and resolve these issues.
Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact
identified
The Kaseya R&D team has developed a fix and will be rolling out the update to the MacOS agents tonight and tomorrow. We will post a maintenance window for each platform prior to the update.
To assist with updating macOS agents and verifying they are updated correctly, we have prepared a step-by-step guide available here: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm
Until the update is out on your platform the behaviors described in our previous posts remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.
• We continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.
We will post our next update here after all deployments are completed, or sooner if more information becomes available.
We apologize for the inconvenience and appreciate your patience while we work to resolve this 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/
identified
Our teams are continuing to work on a resolution.
The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.
Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.
We will post our next update here by 7:00 PM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.
We apologize for the inconvenience and appreciate your patience while we work to resolve this 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/
identified
We have identified the cause of the issue affecting the connectivity of Datto RMM macOS agents. Our teams are now working on a resolution.
The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.
Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.
We will post our next update here by 11:00 AM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.
We apologize for the inconvenience and appreciate your patience while we work to resolve this 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/
investigating
We are aware of a problem affecting the connectivity of Datto RMM macOS agents.
At this time, we have identified the following behaviors:
- Newly installed macOS agent installations are unable to establish connectivity.
- Existing macOS agents, that are currently in production environments, should remain online; however, our investigation is ongoing to determine whether additional scenarios may cause agents to go offline.
- Initial testing shows that if a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.
Our teams are actively investigating the root cause with Apple and working to develop a resolution. We will provide additional updates as more information becomes available.
Until further notice, we recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.
We apologize for the inconvenience and appreciate your patience while we work to resolve this 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/
Datto SaaS Protection - Service disruption for customers hosted on node 'aue1-bfyii-2213'
Our R&D team has resolved the issue and customers hosted on 'aue1-bfyii-2213' should now be accessible and accounts are functioning normally.
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 Datto SaaS Protection customers hosted on V2 node 'aue1-bfyii-2213' 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/
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...
