New Multi-region uptime checks and custom-domain status pages

Kaseya Inc Outage History

Daily provider-status observations and published incident history for Kaseya Inc.

Under maintenance

Kaseya Inc is reporting under maintenance. 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

Aug 18Nov 15

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 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

November 2026
Datto BCDR - US Region - Server5582 Not Accessible
minor Observed active window 2h 27m

View incident details and source

Started:

Off-Site Synchronization Off-Site Recovery
monitoring
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
major

View incident details and source

Started:

monitoring
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
major Observed active window 48m

View incident details and source

Started:

North America Primary Application Services
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 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
major Observed active window 14h 41m

View incident details and source

Started:

Portal
monitoring
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
minor Observed active window 25h 54m

View incident details and source

Started:

Syrah (APAC)
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 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>.
Google Brotli Vulnerability (CVE-2026-111497)

View incident details and source

Started:

identified
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
critical Observed active window 3h 3m

View incident details and source

Started:

Login
identified
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>.
Security Advisory: N-able Integration Paused

View incident details and source

Started:

monitoring
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
minor Observed active window 8m

View incident details and source

Started:

Limited Release America East America East 3 America West 2 America West 3 UK 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>.
Datto RMM - Version 15.2.0 (Pinotage, Syrah, Zinfandel, Concord) - Autotask Integration Device Sync Delays
major Observed active window 175h 20m

View incident details and source

Started:

Pinotage (EU1) Zinfandel (US West) Concord (US East) Syrah (APAC)
monitoring
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
Germany Data Center Infrastructure - Service Performance Degradation Impacting Offsite Capabilities.
critical Source not attested
Last archived state: resolved
View archived record details
Agent Registration SaaS Protection Backups Backup Backup SaaS Protection Console Login Backup Verification SaaS Protection Seat Management Verification Recovery Recovery Off-Site Synchronization SaaS Protection Restores/Exports Off-Site Recovery
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We are aware of a problem where customers in the Germany region using Datto BCDR, Datto SaaS Protection, and Datto Endpoint Backup are currently experiencing service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is 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...
Datto SaaS Protection - Backup and Restore issues affecting customers in multiple regions
minor Source not attested
Last archived state: resolved
View archived record details
SaaS Protection Backups SaaS Protection Restores/Exports
monitoring
Backup success rates have returned to normal levels and restoration functions have resumed. Our R&D team is continuing to monitor.
identified
Our R&D team has begun deploying changes to the affected regions to address the issue.
identified
Our R&D team is actively preparing to deploy changes to address the issue.
identified
We are aware of a problem where some Datto SaaS Protection customers hosted in multiple regions are experiencing backup and restore failures. Export services are not affected. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. 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...
SaaS Protection - isw1-bfyii-1131 - Backup Performance Degradation
major Source not attested
Last archived state: resolved
View archived record details
SaaS Protection Backups
monitoring
Backups continue to process normally for customers hosted on node 'isw1-bfyii-1131' and our R&D team is monitoring for any other issues.
identified
The Engineering team has performed the necessary steps to resolve the issue, and are observing that related errors have stopped and backup metrics are improving as the service is recovering.
identified
We are aware of a problem where backups are not successful for customers hosted on isw1-bfyii-1131 The Kaseya Engineering Team is currently responding to the issue, and we will provide updates on this thread as information becomes available. 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 RMM - Vidal - Post 15.1.0 Release - Activity Log Issues
minor Source not attested
Last archived state: resolved
View archived record details
Vidal (US East)
monitoring
At this time, jobs and activity logs remain stable, and no further issues have been observed however we will continue to monitor the environment overnight.
monitoring
A fix has been implemented for the Jobs and Activity Log on the Vidal platform and we are monitoring the results.
identified
Scheduled and Quick Job functionality is restored, and the Engineering team is continuing to work on resolving the problem causing issues with the Activity Log loading in accounts.
identified
The Engineering team is currently investigating and resolving issues flagged by internal alerting that led to the Activity Log loading and Job execution issues resurfacing. Thank you for your patience!
monitoring
A fix has been implemented for the Activity Log on the Vidal platform. The service has recovered and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We have identified an issue with the Activity Log failing to load. The Kaseya R&D team are working on a fix for the issue.
monitoring
The Job queue has been cleared and Activity Logs continue to load as expected. We are continuing to monitor for any further issues.
monitoring
A fix has been implemented for Activity Logs and they should be loading as expected. A fix has also been implemented for Jobs not running, but delays are still expected as the platform works through all queued jobs. We will continue to monitor this queue and resolve this status page once it has cleared.
investigating
We are continuing to investigate this issue.
investigating
We are aware of a problem on Datto RMM's Vidal Platform where Jobs are not running and the Activity log can be slow to load. The Kaseya Engineering Team are 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/
[Kaseya Store] - [Kaseya Store] - [Kaseya Store inaccessible]
critical Source not attested
Last archived state: resolved
View archived record details
Kaseya Store
investigating
We are continuing to investigate this issue.
investigating
We are aware of a problem where the Kaseya Store is not accessible. 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/
Datto RMM - Merlot (EMEA) - Job Service Failures
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and we are currently monitoring the results.
investigating
We are aware of an issue affecting the Merlot platform where Quick Jobs and Scheduled Jobs are failing to run. The Kaseya Engineering Team is actively 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 Workplace - Degraded Performance in US Regions
minor Source 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 investigating reports of slow loading times affecting Workplace, the web portal, and agent connectivity for partners hosted in our US regions. A small number of users may also see intermittent connection errors when opening a project or folder. Our engineering 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/
Inky Dashboard partial outage
major Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
A database issue is causing a partial outage on the US Inky dashboard. Email processing is unaffected but settings will not be able to be changed while we correct the issue. The issue has been identified and a fix is being implemented.
DattoRMM - Vidal - ConnectWise Integration is inaccessible
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are no longer seeing errors related to the ConnectWise Integration. We are continuing to monitor the services at this time.
investigating
We are aware of a problem where the ConnectWise integration is returning an error on our Vidal platform. Users may see errors while viewing the integration page and ticketing can be affected. 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 SaaS protection - Backups currently paused des1-bfyii-1127
minor Source 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 Kaseya R&D Team has implemented a fix to alleviate backups for customers hosted on the node des1-bfyii-1127. Backups success rates will be monitored for improvement
identified
We are aware of a problem where SaaS Protection customers hosted on node ‘des1-bfyii-1127' are experiencing degraded backup performance for some services. The Kaseya R&D Team has identified the issue and are working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Get alerts for Kaseya Inc Subscribe to the provider incident feed Browse all services