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.
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/
