Kaseya Outage History
Kaseya major outage · 2 active incidents View live status →Pingoru has recorded 157 incidents for Kaseya: 155 in the last 12 months and 88 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 12 | 695 of 720 (97%) |
| May 2026 | 20 | 697 of 744 (94%) |
| June 2026 | 15 | 695 of 720 (97%) |
| July 2026 | 29 | 690 of 744 (93%) |
| August 2026 | 26 | 719 of 744 (97%) |
| September 2026 | 37 | 584 of 720 (81%) |
| October 2026 | 14 | 575 of 590 (98%) |
Incidents, newest first
Notice July 3, 2026 Uniview - Uniview homepage and assets not currently loading 2d 19h Uniview Unified Backup Portal
Started Jul 03, 2026, 05:06 PM UTC· resolved Jul 06, 2026, 01:04 PM UTC
- investigating Jul 03, 2026, 05:06 PM UTC
We are currently aware of a problem where Uniview is not loading assets for some customers. The Kaseya R&D Team is actively investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Jul 03, 2026, 05:29 PM UTC
The Kaseya R&D team has found the problem and deployed a fix. They are closely monitoring the situation to confirm resolution.
- monitoring Jul 03, 2026, 05:29 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jul 03, 2026, 06:34 PM UTC
After monitoring the deployed fix, the Kaseya R&D team has observed that Uniview performance has returned to normal and is now reliably loading assets again. We believe this issue to be resolved but will continue monitoring over the weekend to ensure resolution.
- resolved Jul 06, 2026, 01:04 PM UTC
The Kaseya R&D team has completed monitoring and confirmed that Uniview performance remains stable. Assets are loading normally, and no further issues related to this incident have been observed. We consider this issue fully resolved at this time. If you experience any new issues, please contact our Chat Support so we can investigate promptly. For ongoing visibility into service status and communications, we encourage you to subscribe to the Kaseya Status Page: status.kaseya.com Thank you for your understanding and continued support.
Minor July 3, 2026 Autotask PSA - UK02 - Workflow Rule Delay and Latency 1h 49m
Started Jul 03, 2026, 01:58 PM UTC· resolved Jul 03, 2026, 03:47 PM UTC
- investigating Jul 03, 2026, 01:58 PM UTC
We are aware of an issue affecting Autotask users hosted in the UK02 zone, resulting in increased latency and delays in workflow rule processing. The Kaseya R&D Team is actively investigating this issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Jul 03, 2026, 03:05 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 03, 2026, 03:18 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 03, 2026, 03:47 PM UTC
This incident has been resolved.
Major July 1, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'des1-bfyii-1701' 26m
Started Jul 01, 2026, 08:18 PM UTC· resolved Jul 01, 2026, 08:45 PM UTC
- investigating Jul 01, 2026, 08:18 PM UTC
We are aware of a problem where customers hosted on node 'des1-bfyii-1701' are currently unable to access their accounts. The Kaseya R&D Team is currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Jul 01, 2026, 08:24 PM UTC
Our R&D team has identified the issue and have implemented a fix. The team is monitoring for any other issues.
- resolved Jul 01, 2026, 08:45 PM UTC
This incident has been resolved.
Minor June 30, 2026 Datto RMM - Intermittent Job Creation Failures on the Syrah (APAC) and Vidal (US East) platforms 15d
Started Jun 30, 2026, 01:26 PM UTC· resolved Jul 15, 2026, 02:25 PM UTC
- identified Jun 30, 2026, 01:26 PM UTC
The Kaseya R&D Team identified the cause of the issue where Jobs intermittently fail to be created in the Web UI. The fix for the problem is currently being tested, and it is planned to be deployed in the coming days.
- monitoring Jul 01, 2026, 10:20 AM UTC
The fix has been implemented on both the Syrah and Vidal platforms.
- resolved Jul 15, 2026, 02:25 PM UTC
The 15.0.1 version that included the fix for this issue is live on all production platforms.
Major June 29, 2026 Datto RMM - Syrah, Vidal - 15.0.1 Cagservice.exe being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint 15d 22h
Started Jun 29, 2026, 04:02 PM UTC· resolved Jul 15, 2026, 02:25 PM UTC
- investigating Jun 29, 2026, 04:02 PM UTC
We are aware of a problem where Datto RMM's 15.0.1 Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint. The Kaseya R&D Team are investigating this issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- investigating Jun 29, 2026, 04:07 PM UTC
We are continuing to investigate this issue.
- identified Jun 29, 2026, 07:36 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 29, 2026, 10:47 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 15, 2026, 02:25 PM UTC
This incident has been resolved.
Critical June 19, 2026 Datto Workplace - Service Issue Affecting EU Cell 4, Cell 7, and Cell 16 (404 Error) 1h 9m
Started Jun 19, 2026, 11:21 AM UTC· resolved Jun 19, 2026, 12:31 PM UTC
- investigating Jun 19, 2026, 08:51 AM UTC
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.
- investigating Jun 19, 2026, 08:56 AM UTC
We are continuing to investigate this issue.
- monitoring Jun 19, 2026, 09:01 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 19, 2026, 11:21 AM UTC
Customers may still experience a delay in email processing while the service is catching up with the queue that formed during the incidents.
- resolved Jun 19, 2026, 12:31 PM UTC
This incident has been resolved.
Major June 19, 2026 INKY - Internally sent emails are not getting delivered and emails to external recipients are getting delayed 3h 19m
Started Jun 19, 2026, 10:03 AM UTC· resolved Jun 19, 2026, 01:22 PM UTC
- investigating Jun 19, 2026, 10:03 AM UTC
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.
- identified Jun 19, 2026, 10:22 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 19, 2026, 10:30 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 19, 2026, 12:33 PM UTC
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.
- resolved Jun 19, 2026, 01:22 PM UTC
This incident has been resolved.
Minor June 17, 2026 Datto EDR - Issues Accessing Certain Applications Following Recent EDR Update 14d 5h
Started Jun 17, 2026, 03:27 PM UTC· resolved Jul 01, 2026, 08:46 PM UTC
- investigating Jun 17, 2026, 03:27 PM UTC
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.
- identified Jun 18, 2026, 07:39 PM UTC
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.
- monitoring Jun 19, 2026, 12:33 AM UTC
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. 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
- resolved Jul 01, 2026, 08:46 PM UTC
This incident has been resolved.
Minor June 15, 2026 Endpoint Backup v2 - Backup Failures 9d 4h
Started Jun 15, 2026, 02:12 PM UTC· resolved Jun 24, 2026, 06:44 PM UTC
- investigating Jun 15, 2026, 02:12 PM UTC
We are aware of a problem where a subset of Endpoint Backup v2 assets can experience a backup failure due to a "Errors writing to the AOF file: Input/output" error. 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/
- investigating Jun 15, 2026, 05:31 PM UTC
We are continuing to investigate this issue.
- identified Jun 16, 2026, 06:45 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jun 23, 2026, 05:53 PM UTC
We’re pleased to share that our team will begin rolling out the fix to non-U.S. regions on June 23, 2026 at 06:00 PM UTC, followed by deployment to U.S. regions on June 24, 2026 at 08:00 AM UTC. We appreciate your patience as we work to ensure a smooth and reliable update experience for all customers.
- monitoring Jun 24, 2026, 01:24 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 24, 2026, 06:44 PM UTC
This incident has been resolved.
Major June 12, 2026 Endpoint Backup v2 - A Subset of Endpoint Backup v2 Assets May Experience Backup Failures 2d 21h
Started Jun 12, 2026, 07:57 PM UTC· resolved Jun 15, 2026, 05:06 PM UTC
- identified Jun 12, 2026, 07:57 PM UTC
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/
- monitoring Jun 15, 2026, 01:29 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 15, 2026, 05:06 PM UTC
This incident has been resolved.
Critical June 10, 2026 Endpoint Backup v2 – Assets Reporting Offline; Backups and Restores Unavailable 1d 2h
Started Jun 10, 2026, 09:10 PM UTC· resolved Jun 11, 2026, 11:16 PM UTC
- investigating Jun 10, 2026, 09:10 PM UTC
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/
- identified Jun 11, 2026, 08:32 AM UTC
The R&D team identified the issue, and developed a fix. The change is currently being tested before proceeding with the rollout to production.
- identified Jun 11, 2026, 10:03 AM UTC
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.
- identified Jun 11, 2026, 11:32 AM UTC
We are continuing the rollout of the fixed agent version to production.
- identified Jun 11, 2026, 04:43 PM UTC
We are continuing to work on a fix for this issue.
- resolved Jun 11, 2026, 11:16 PM UTC
This incident has been resolved. The fixed agent version 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.
Minor June 10, 2026 Datto BCDR - Server5673 (Germany Region) - Degraded Node Functionality 4h 44m
Started Jun 10, 2026, 03:44 PM UTC· resolved Jun 10, 2026, 08:28 PM UTC
- identified Jun 10, 2026, 03:44 PM UTC
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/
- monitoring Jun 10, 2026, 06:59 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 10, 2026, 08:28 PM UTC
This incident has been resolved.
Major June 10, 2026 VSA9 - Partial Service Disruption - US-VSA146 3h 2m
Started Jun 10, 2026, 12:43 AM UTC· resolved Jun 10, 2026, 03:45 AM UTC
- investigating Jun 10, 2026, 12:43 AM UTC
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
- monitoring Jun 10, 2026, 02:04 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 10, 2026, 03:45 AM UTC
This incident has been resolved.
Minor June 8, 2026 Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'gbe2-saas-p1' 42d 3h
Started Jun 08, 2026, 01:31 PM UTC· resolved Jul 20, 2026, 05:00 PM UTC
- investigating Jun 08, 2026, 01:31 PM UTC
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/
- identified Jun 08, 2026, 03:37 PM UTC
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.
- identified Jun 09, 2026, 01:19 PM UTC
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.
- monitoring Jun 10, 2026, 12:48 PM UTC
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.
- monitoring Jun 10, 2026, 02:40 PM UTC
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.
- monitoring Jun 11, 2026, 07:46 PM UTC
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.
- monitoring Jun 15, 2026, 03:00 PM UTC
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.
- monitoring Jun 23, 2026, 06:31 PM UTC
The backup cadence for pod ‘gbe2‑saas‑p1’ is still temporarily set to 2x backups per day. Backups are running normally and backup success rates remain stable. Our R&D team will increase backup cadence to 3x backups per day once it’s safe and reliable for all customers on the pod.
- monitoring Jul 02, 2026, 06:31 PM UTC
The backup cadence for pod ‘gbe2‑saas‑p1’ is still temporarily set to 2x backups per day and backup success rates remain stable. Our R&D team has finished deploying additional improvements to further address the issue and they are actively monitoring the results. Backup cadence will be reverted to 3x daily backups as soon as it is safe and reliable for all customers hosted on the pod.
- monitoring Jul 17, 2026, 08:03 PM UTC
The backup cadence on pod 'gbe2-saas-p1' has been restored to 3x daily backups and all services are currently processing new backups normally. Our R&D team is closely monitoring for any issues.
- resolved Jul 20, 2026, 05:00 PM UTC
This incident has been resolved.
Major June 5, 2026 Datto SaaS Protection - New customer onboarding is unavailable 1h 19m
Started Jun 05, 2026, 02:38 PM UTC· resolved Jun 05, 2026, 03:58 PM UTC
- identified Jun 05, 2026, 02:38 PM UTC
We are aware of a problem where Datto SaaS Protection Partners are currently unable to onboard new customers within the Partner Portal and are receiving an error. The Kaseya R&D Team has identified the issue and they are actively working on a fix. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Jun 05, 2026, 03:19 PM UTC
A fix for this issue has been tested and is being prepared for release.
- monitoring Jun 05, 2026, 03:47 PM UTC
A fix for the issue has been deployed and the SaaS Protection onboarding service has been restored.
- resolved Jun 05, 2026, 03:58 PM UTC
This incident has been resolved.
Minor June 4, 2026 Autotask PSA - LR, UKLR, UK01, UK02, UK03, EU1, DE1 - Intermittent Error Messages 6h 5m
Started Jun 04, 2026, 07:55 AM UTC· resolved Jun 04, 2026, 02:00 PM UTC
- investigating Jun 04, 2026, 07:55 AM UTC
We are aware of a problem where error messages are being experienced when navigating the Autotask PSA UI. The Kaseya R&D Team is actively investigating this behaviour. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Jun 04, 2026, 10:04 AM UTC
The issue has been identified and a fix is being implemented.
- identified Jun 04, 2026, 10:35 AM UTC
Thank you for your patience while we continue to work on a fix for this issue. A workaround to prevent the error messages has been confirmed. If you navigate within Autotask to the top right-hand corner: My Account > My Settings > Reset Settings Please note that when applying this change, many of your current settings will be reset. This includes certain column choosers, notification template defaults, search grid default criteria, and default checkbox/radio button selections.
- monitoring Jun 04, 2026, 01:12 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 04, 2026, 02:00 PM UTC
This incident has been resolved.
Minor June 3, 2026 Datto Endpoint Backup for PC - Degraded Offsite Performance for Cloud Siris 246891 20d 23h
Started Jun 03, 2026, 01:42 PM UTC· resolved Jun 24, 2026, 01:32 PM UTC
- identified Jun 03, 2026, 01:42 PM UTC
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/
- identified Jun 15, 2026, 12:47 PM UTC
We are continuing to work on a fix for this issue.
- resolved Jun 24, 2026, 01:32 PM UTC
This incident has been resolved.
Critical June 3, 2026 Datto SaaS Protection - Onboarding new customers and Status page within the Partner Portal are unavailable 3h 7m
Started Jun 03, 2026, 11:25 AM UTC· resolved Jun 03, 2026, 02:32 PM UTC
- investigating Jun 03, 2026, 11:25 AM UTC
We are aware of a problem where customers are unable to onboard new tenants. The status page within the Datto Partner Portal is also unavailable and returning a 500 error. The Kaseya R&D Team is actively working to address the problem. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Jun 03, 2026, 12:42 PM UTC
Our R&D team has identified the issue and are actively working to deploy a fix.
- monitoring Jun 03, 2026, 01:51 PM UTC
A fix to restore access to the SaaS Protection Status Page within the Partner Portal and Onboarding functionality has been implemented. Our R&D team is actively monitoring for any other issues.
- resolved Jun 03, 2026, 02:32 PM UTC
This incident has been resolved.
Major May 29, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'use1-bfyii-126' 2d 18h
Started May 29, 2026, 06:14 PM UTC· resolved Jun 01, 2026, 12:25 PM UTC
- investigating May 29, 2026, 06:14 PM UTC
We are aware of a problem where customers hosted on node 'use1-bfyii-126' are experiencing a disruption to their SaaS Protection services. The Kaseya R&D Team is actively investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 29, 2026, 06:55 PM UTC
Our R&D team has implemented a fix to restore services on node 'use1-bfyii-126' and they are actively monitoring.
- resolved Jun 01, 2026, 12:25 PM UTC
This incident has been resolved.
Minor May 27, 2026 Endpoint Backup v2 - Last Backup Timestamp Is Not Updating Correctly, Which May Result in False-Positive Backup Threshold Alerts within UniView 1d 3h
Started May 27, 2026, 01:33 PM UTC· resolved May 28, 2026, 05:09 PM UTC
- identified May 27, 2026, 01:33 PM UTC
We are aware of a problem where the last backup timestamp for Endpoint Backup v2 assets can fail to update correctly, which may result in false-positive backup threshold alerts within UniView. Please note that this issue does not impact backup performance and is limited to a visual display anomaly only. 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/
- monitoring May 27, 2026, 08:22 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 28, 2026, 05:09 PM UTC
This incident has been resolved.
Minor May 26, 2026 DattoRMM - Vidal - Datto Continuity devices incorrectly reporting offline 23h 57m
Started May 26, 2026, 05:36 PM UTC· resolved May 27, 2026, 05:33 PM UTC
- identified May 26, 2026, 05:36 PM UTC
We are aware of a problem where online BCDR devices are reporting as offline through the Datto Continuity integration on our Vidal platform. The Kaseya R&D Team have identified the issue and are working on a fix Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified May 27, 2026, 10:33 AM UTC
We are continuing to work on a fix for this issue.
- monitoring May 27, 2026, 03:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 27, 2026, 05:33 PM UTC
This incident has been resolved.
Major May 24, 2026 Datto SaaS Protection - Service disruption for customers hosted on pod 'gbe2-saas-p1' 4d
Started May 24, 2026, 05:52 PM UTC· resolved May 28, 2026, 06:15 PM UTC
- investigating May 24, 2026, 05:52 PM UTC
We are aware of a problem causing a disruption to services for Datto SaaS Protection customers hosted on pod 'gbe2-saas-p1'. Our R&D team has identified the issue and is actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified May 26, 2026, 01:16 PM UTC
Our R&D team is continuing to address the current disruption to SaaS Protection services affecting customers hosted on pod 'gbe2-saas-p1'.
- monitoring May 26, 2026, 03:43 PM UTC
Our R&D team has implemented changes to address the issue affecting customers hosted on pod 'gbe2-saas-p1' and they are monitoring the results.
- monitoring May 26, 2026, 08:11 PM UTC
Backup success rate metrics on pod 'gbe2-saas-p1' are returning to normal. Our R&D team is continuing to monitor for any other issues.
- monitoring May 27, 2026, 03:32 PM UTC
Backup success rate metrics on pod 'gbe2-saas-p1' have returned to normal and our R&D team is continuing to monitor for any other issues.
- resolved May 28, 2026, 06:15 PM UTC
This incident has been resolved.
Major May 23, 2026 [Networking] - [DSE] - [DSE Safe Check Preventing users Access] 1h 13m
Started May 23, 2026, 06:51 PM UTC· resolved May 23, 2026, 08:04 PM UTC
- investigating May 23, 2026, 06:51 PM UTC
We are aware of a problem where DSE subscribers are being rejected from SafeCheck on May 23, 2026. This seems to be a trending outage with multiple partners due to an API issue. The Kaseya R&D Team are currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring May 23, 2026, 07:41 PM UTC
The Datto Networking R&D team has implemented a fix that is believed to have resolved the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- resolved May 23, 2026, 08:04 PM UTC
Original reporters have confirmed the issue has been resolved after Engineering fix
Major May 22, 2026 Issues with payment provider – KaseyaOne & Kaseya Store 1h 53m KaseyaOne, Kaseya Store
Started May 22, 2026, 09:37 AM UTC· resolved May 22, 2026, 11:30 AM UTC
- investigating May 22, 2026, 09:37 AM UTC
Our payment provider has flagged an ongoing issue that could potentially affect transaction processing. We are closely monitoring this and will post an update as soon as the situation is resolved or if any impact is detected. Thank you for your patience.
- identified May 22, 2026, 10:23 AM UTC
Vendor updated that they are currently experiencing American Express transaction failures due to maintenance activity within the American Express network, which extended beyond its planned duration. Vendor is actively working with the American Express team to minimize the impact and prevent additional processing failures while the maintenance is underway. Where possible, we recommend using alternative card brands for new transactions. Merchants may also retry failed American Express transactions after maintenance is complete. We will continue to monitor the situation closely and provide another update as soon as the issue is fully resolved.
- resolved May 22, 2026, 11:30 AM UTC
This incident has been resolved.
Major May 21, 2026 [Datto Workplace & Datto File Protection] Users are unable to login 5d 4h
Started May 21, 2026, 08:50 AM UTC· resolved May 26, 2026, 01:24 PM UTC
- investigating May 21, 2026, 08:50 AM UTC
Our R&D team is currently investigating the issue with the Datto Workplace and Datto File Protection portals in the US region being inaccessible at present. The top level URLs being currently inaccessible, customers in other regions can only access the login page through the subdomains. Please subscribe to this post to receive updates as our efforts to resolve this issue progresses. We apologise for the inconvenience caused!
- monitoring May 21, 2026, 09:05 AM UTC
The R&D team has successfully mitigated the issue and the previously affected pages are accessible again. We continue to monitor the health of the service while reviewing avenues to minimize the risk of the issue reoccurring.
- resolved May 26, 2026, 01:24 PM UTC
This incident has been resolved.