Kaseya Inc Status

On Monday, June 22nd, maintenance is scheduled on Kaseya Store, between 05:00 AM to 08:00 AM EDT. During this maintenance, we will be deploying the new version of Kaseya Store. However, we do not anticipate any interruption to the service. We apologize for any inconvenience this may cause. - Cloud Operations Team

This incident has been resolved.

The service has caught up with processing through items queued in INKY, and the R&D team is reviewing individual examples of residual issues . Please work with our support team and provide them with message IDs for review if the issue appears to still persist.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

The INKY R&D Team is investigating the issue where emails to internal recipients filtered through INKY are not showing up in INKY and not getting delivered to recipients. Emails to external recipients, while also not appearing in INKY, successfully get delivered but with a noticeable delay. Please subscribe to this incident to receive update notifications as they become available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating an issue where partners are unable to access the Workplace portal. Partners in EU Cell 4, EU Cell 7, and EU Cell 16 are experiencing service disruptions and may receive a 404 Error when attempting to access the portal. Our engineering team is actively investigating the issue and working to restore service as quickly as possible.

We’re pleased to inform you that our Engineering team has released a Hotfix for the Datto AMSI module remaining on devices: UI 15272 Agent #3.17.1.5552 Fixes: This release addresses an issue where the Datto AMSI provider remained actively registered on a device after having the AMSI module disabled. The AMSI module remains disabled globally and will be reintroduced through a controlled rollout. This change does not disable overall EDR protection. It is a temporary mitigation specific to the AMSI module. The hotfix will be applied during your next scheduled maintenance window. This page provides information to assist with determining the agent version on a device: https://edr.datto.com/help/Content/troubleshooting/confirming-ui-version.htm

If you are still experiencing issues after rebooting, please contact Kaseya Support to receive a script that can be run on affected endpoints to resolve the issue. A hotfix agent update is in progress and will be released shortly. We will update this page once it is available.

We are aware that some customers are continuing to experience difficulty accessing certain applications, including Microsoft Teams, following a recent Datto EDR update. We are actively investigating and treating this as a priority. What we currently know: A recent Datto EDR update enabled additional behavioral monitoring on affected endpoints. We have identified this change as a contributing factor to the issue and are working on a resolution. What you can do right now: A reboot of the affected endpoint may resolve the issue in some cases. Our team is also working on a scripted remediation and a hotfix — we will update this page as those become available. What we are doing: Our engineering team is actively working on a fix. Subscribe to updates at status.kaseya.com to be notified as our investigation progresses.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are aware of a problem where a subset of Endpoint Backup v2 assets can experience backup failures due to EOF and AOF errors. The Kaseya R&D Team is investigating the issue and working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are aware of a problem where a subset of Endpoint Backup v2 assets can experience a backup failure due to error "system.ntfs_reparse_data: invalid argument". The Kaseya R&D Team has identified the issue and is working towards a resolution. In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

The backup cadence on pod 'gbe2‑saas‑p1' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. Backups are running normally and success rate metrics remain stable. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.

SharePoint and Teams backup success rates on pod 'gbe2-saas-p1' continue to remain stable at 2x backups per day. Our R&D team is continuing to monitor and the 3x daily backup cadence will be restored once it is stable and reliable for all customers.

All backups continue to process normally on pod 'gbe2‑saas‑p1' while the backup cadence remains temporarily set to 2x daily backups to maintain high backup success rates. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.

Backup success rate metrics for SharePoint and Teams services on pod 'gbe2-saas-p1' have returned to normal and our R&D team is continuing to monitor for any other issues.

Backup success rate metrics for SharePoint and Teams services on pod 'gbe2-saas-p1' are improving and our R&D team is continuing to monitor pod performance as it recovers.

The backup cadence on pod 'gbe2‑saas‑p1' has been temporarily set to 2x daily backups to maintain high success rates. The 3x daily backup cadence will be restored once it is stable and reliable for all customers. The Kaseya R&D Team will continue to monitor pod performance.

We are aware of a problem where some customers hosted on pod 'gbe2-saas-p1' are experiencing backup performance degradation for some 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/

We are continuing to work on a fix for this issue.

We are aware of a problem where Datto Endpoint Backup for PC users paired to Cloud Siris 246891 in the US East region can experience degraded offsite performance. 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 Workplace - US Users Unable to Log In via** [**workplace.datto.com**](http://workplace.datto.com) **– 2026-05-08**     **Summary:**   Between 2026**-05-08 08:48 AM UTC** and 2026**-05-08 07:28 PM UTC**, Datto Workplace customers **in the US region could not login via Datto Partner Portal SSO.**      **Root Cause:**   During the incident, a portion of checkout requests experienced errors, leading to a service disruption that primarily impacted users in the United States. To restore service, our teams performed a rebuild of the affected infrastructure components, which successfully resolved the issue.     **Incident Timeline:** * Identified: 2026-05-08 08:48 AM UTC * Public Notification: 2026-05-08 04:12 PM UTC * Resolved: 2026-05-08 07:28 PM UTC       **Preventative Measures:**   To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * We have strengthened our drive replacement process to improve early detection and accelerate resolution, helping ensure a more reliable and consistent customer experience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are aware of a problem where a subset of US Datto Workplace and Datto File Protection users cannot login via Portal SSO. Agent login access remains unaffected, and users continue to have full access. The Kaseya R&D Team is investigating the issue and working towards a resolution. Workaround: Please ensure your local region is specified when utilizing direct login: EX: eu.workplace.datto.com EX: us.workplace.datto.com If assistance is needed, our Technical Support team can assist. Note: Users for most cells can login directly to Datto Workplace and Datto File Protection. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved. The fixed agent version (v1.14.12) has been rolled out to production, and Endpoint Backup v2 services have been restored. Assets are reporting correctly in UniView, and backup, restore, BMR, and agent registration operations are functioning as expected. Scheduled backups have resumed and will run at their next scheduled time. We will continue to monitor the environment to ensure ongoing stability. If you continue to experience any issues, please contact Kaseya Support. We sincerely apologize for the disruption and thank you for your patience while we worked to resolve this issue.

We are continuing to work on a fix for this issue.

We are continuing the rollout of the fixed agent version to production.

The hotfixed agent version is being rolled out to production following successful testing and validation that the changes implemented by the R&D team resolves the issue. We are deploying the upgrade in batches to mitigate any risks to the health of the infrastructure.

The R&D team identified the issue, and developed a fix. The change is currently being tested before proceeding with the rollout to production.

We are investigating an issue causing Endpoint Backup v2 assets to appear offline in UniView. While this issue is ongoing, scheduled backups are not running, recovery points may show as unavailable, and backup, restore, and BMR operations are failing. All regions are affected. There is no workaround available at this time. The Kaseya R&D team is engaged and actively investigating, and we will provide updates as more information becomes available. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are aware of a problem where BCDR users paired to Server5673 can experience degraded offsite capabilities. The Kaseya R&D Team has identified the issue and is working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are experiencing a issues with outbound email on US-VSA146. Our team is working to restore functionality on the instance at this time. We apologize for any inconvenience. - Kaseya Cloud Operations Team