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.
August 2026
Autotask PSA - Sydney Data Center Web Center and API - Unaccessaible
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
We are aware of a problem where some customers are unable to access Autotask within our Sydney Data Center
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/
Datto BCDR - Archived Agents May Generate Sync Completion Alerts for Points Marked for Offsite.
criticalSource not attested
Last archived state: resolved
View archived record details
Off-Site Synchronization
investigating
A known issue exists where archived agents may continue to generate sync completion alerts when associated local points are marked as offsite, despite the agents being in an archived state.
While a long-term solution is scheduled for implementation in a future release, assets affected before the fix is deployed will need to be corrected through manual intervention.
Customers seeking to implement this mitigation should submit a request through the Kaseya Help Desk Portal at https://helpd...
ConnectBooster - Unable to log in via Kaseya One
majorSource 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.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where Partners have reported the inability to log into the portal via Kaseya One
The Kaseya R&D Team is investigating the issue.
In the meantime, a workaround of logging directly into the ConnectBooster portal via the primary URL can allow you to log in without Kaseya One. please create a ticket with our Support team or contact them at 833-863-2237 if you need assistance with this process.
Subscribe to the Kaseya Status Page for up-to-date information at https://...
KaseyaOne & Kaseya Store - Issues with payment provider
minorSource not attested
Last archived state: resolved
View archived record details
identified
Our payment provider for KaseyaOne and Kaseya Store has identified intermittent connectivity issues with our fraud prevention provider that might cause increased authentication declines.
During this time, users may experience intermittent issues related to payment processing in KaseyaOne and Kaseya Store.
Core platform functionality outside of payment services will remain unaffected.
We recommend avoiding payment-related actions during this maintenance window where possible. We will monito...
Datto SaaS Protection - Backup performance degradation for some M365 services on Multiple Pods
majorSource not attested
Last archived state: resolved
View archived record details
identified
Significant improvement to backup success rate metrics has been observed across all regions after the latest changes were implemented.
Our R&D team is continuing to deploy configuration changes to further stabilize backup performance in all regions. Backup success rates will continue to be closely monitored as the team is actively working to develop additional improvements to address the API throttling related to the transition from EWS to Microsoft Graph APIs currently in progress.
identified
The latest changes have been deployed to SaaS Protection pods in multiple regions still experiencing backup performance issues.
Our R&D team is continuing to monitor as backup success rate metrics improve across the fleet.
identified
Our R&D team is currently implementing configuration changes in multiple regions to further mitigate the degraded backup performance still affecting some customers.
We will be closely monitoring the results of these changes as we continue to develop additional improvements to accelerate recovery for affected customers.
identified
After the changes made yesterday, we have observed some improvement to backup success rates however backups are currently still degraded for some M365 services across multiple regions due to API throttling related to the transition from EWS to Microsoft Graph APIs.
Our R&D team is continuing to develop additional improvements to address the backup performance issues.
identified
Our R&D team has completed deployment of the configuration changes to SaaS Protection pods in all regions.
Daily backup cadence is now temporarily set to 2x backups per day across the fleet to reduce API throttling and help stabilize backup success rate metrics during the transition from EWS to Microsoft Graph APIs.
Our R&D team is closely monitoring the effects of the changes and expect backup success rates to begin stabilizing over the next several hours.
identified
Our R&D team is continuing to deploy the configuration changes to adjust backup frequency from 3x backups per day to 2x backups per day on SaaS Protection pods in all regions and we are continuing to closely monitor backup success rate metrics.
identified
Our R&D team has begun deployment of the changes to reduce backup cadence on affected SaaS Protection pods across all regions to 2x backups per day to help stabilize backup success rates further. This change is expected to complete deployment by 20:00 ET (00:00 UTC).
Our R&D team is continuing to closely monitor backup performance as these additional changes are implemented.
identified
Our R&D team continues to address backup performance issues affecting some Microsoft 365 services across multiple SaaS Protection pods following the transition from EWS to Microsoft Graph APIs.
To help stabilize backup success rates and reduce API throttling during this migration, backup cadence on affected pods will be temporarily reduced from 3x backups per day to 2x backups per day.
identified
Our R&D team is continuing to address the backup performance issues affecting some M365 services on multiple SaaS Protection pods.
In the meantime, they are preparing to temporarily reduce backup cadence on affected pods from 3x backups per day to 2x backups per day to help stabilize backup success rates in all affected regions.
monitoring
Our R&D team has released a fix to address the backup performance degradation for some M365 services affecting customers hosted in multiple regions and they are closely monitoring.
identified
We are continuing to work on a fix for this issue.
identified
We are aware of an issue where some Datto SaaS Protection customers across multiple regions may experience degraded backup performance for some M365 services.
Affected regions:
AUE
CAE
DES
GBE
SG
USE
The Kaseya R&D team has identified the issue and is actively working to restore normal backup performance as quickly as possible.
For the latest updates, please subscribe to the Kaseya Status Page at https://status.kaseya.com/.
July 2026
Datto Endpoint Backup for PC - Service Disruption for Customers Hosted on Cloud Siris 215069
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 aware of a problem where customers using Datto Endpoint Backup for PC and paired with 'use1-dtc-server-5.datto.com' may encounter reduced performance or intermittent issues with 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/
Datto RMM (Syrah)-- Datto RMM Agent Detected as Malware Post 15.1.0
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We have reached out and shared the necessary technical indicators with our third party contact and have received confirmation that corrective actions have been implemented on their side. Based on the information provided to us, the issue should no longer occur with the current version of the agent.
We will continue to closely monitor the situation and provide additional updates if necessary.
Thank you for your patience and understanding.
investigating
Our R&D team is continuing its investigation into this issue and is working closely with a third-party provider to assist in identifying the root cause and resolution.
investigating
We are aware of a problem where, after the Datto RMM 15.1.0 update on the Syrah platform, some anti-virus software may flag the Datto RMM service as malicious.
The Kaseya Engineering Team is investigating this issue.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
DRMM (Syrah) -- Device Filter "Site Name" criterion ignored, returns devices from all sites
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 continuing to investigate this issue.
investigating
We are aware of the issue where Filters no longer respect the "Site Name" Criteria resulting in devices that should not be included in the Filter are included in the Filter that then affects Policy/Job targeting.
Datto SaaS Protection - Backup performance degradation for some Exchange services on pod 'aue1-saas-p1'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Exchange backup success rate metrics on pod 'aue1-saas-p1' have improved after the changes that were implemented.
Our R&D team is continuing to closely monitor backup performance on the pod.
identified
Our R&D team has implemented configuration changes on pod 'aue1-saas-p1' to help remediate the issue and they are actively monitoring backup performance.
identified
We are aware of a problem where some customers hosted on pod 'aue1-saas-p1' are experiencing backup performance degradation for Exchange 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 SaaS Protection - Backup performance degradation for some Teams/SharePoint services on pod 'gbe2-saas-p0'
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our R&D team has implemented additional changes to further address the issue and they are continuing to closely monitor backup performance on pod 'gbe2-saas-p0' as backup success rate metrics improve.
monitoring
Our R&D team has implemented a fix on pod 'gbe2-saas-p0' to address the backup performance degradation affecting some Teams/SharePoint services and we are closely monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of a problem where some customers hosted on pod 'gbe2-saas-p0' are experiencing backup performance degradation for some Teams/SharePoint services.
The Kaseya R&D Team is actively Investigating the issue.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
