Datto SaaS Protection - Backup performance degradation for some M365 services on Multiple Pods
Affected: SaaS Protection Backups
Datto Outage History
Datto partial outage · 2 active incidents View live status →Datto had 123 outages in the last 2 years totaling 1065h 22m of downtime — averaging 5.1 incidents per month.
There were 123 Datto outages since May 30, 2025 totaling 1065h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
Datto Endpoint Backup for PC - Service Disruption for Customers Hosted on Cloud Siris 215069
Affected: BackupRecovery
Timeline · 3 updates
- identified Jul 31, 2026, 05:44 PM UTC
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/
- monitoring Aug 05, 2026, 05:43 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 05, 2026, 06:06 PM UTC
This incident has been resolved.
Datto RMM (Syrah)-- Datto RMM Agent Detected as Malware Post 15.1.0
Affected: Syrah (APAC)
Timeline · 4 updates
- investigating Jul 31, 2026, 02:27 AM UTC
Antimalware suites are flagging the Datto RMM Agent update from 15.1.0 as malicious and raising alerts causing Partner distress.
- investigating Jul 31, 2026, 04:25 PM UTC
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.
- monitoring Jul 31, 2026, 06:43 PM UTC
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.
- resolved Aug 03, 2026, 04:04 PM UTC
This incident has been resolved.
DRMM (Syrah) -- Device Filter "Site Name" criterion ignored, returns devices from all sites
Affected: Syrah (APAC)
Timeline · 5 updates
Datto SaaS Protection - Backup performance degradation for some Exchange services on pod 'aue1-saas-p1'
Affected: SaaS Protection Backups
Timeline · 3 updates
- identified Jul 30, 2026, 04:34 PM UTC
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/
- identified Jul 30, 2026, 05:45 PM UTC
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.
- monitoring Jul 31, 2026, 03:55 PM UTC
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.
Datto SaaS Protection - Backup performance degradation for some Teams/SharePoint services on pod 'gbe2-saas-p0'
Affected: SaaS Protection Backups
Timeline · 4 updates
- investigating Jul 30, 2026, 03:11 PM UTC
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/
- identified Jul 30, 2026, 03:33 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 30, 2026, 06:33 PM UTC
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.
- monitoring Jul 31, 2026, 01:55 PM UTC
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.
Datto SaaS Protection - Service disruption for customers hosted on node 'des1-bfyii-2985'
Affected: SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Restores/Exports
Timeline · 4 updates
- investigating Jul 30, 2026, 01:44 PM UTC
We are aware of a problem where SaaS Protection customers hosted on node 'des1-bfyii-2985' are unable to access their accounts and are experiencing a disruption to their 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/
- identified Jul 30, 2026, 03:45 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 30, 2026, 04:26 PM UTC
Our R&D team has implemented a fix to restore account access and have confirmed backups are running. We are monitoring for any other issues.
- resolved Jul 30, 2026, 08:04 PM UTC
This incident has been resolved.
Datto SaaS Protection - Service disruption affecting customers hosted on pod 'gbe2-saas-p0'
Affected: SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Restores/Exports
Timeline · 8 updates
- identified Jul 29, 2026, 10:55 AM UTC
We are aware of an issue where Datto SaaS Protection customers hosted on pod gbe2-saas-p0 are experiencing a complete service disruption. The Kaseya Engineering Team has identified the issue and is actively working to restore service as quickly as possible. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Jul 29, 2026, 10:56 AM UTC
We are continuing to work on a fix for this issue.
- identified Jul 29, 2026, 12:23 PM UTC
Our R&D team has applied a fix to address the issue and they are currently verifying restoration of all services on pod 'gbe2-saas-p0'.
- identified Jul 29, 2026, 01:45 PM UTC
Our R&D team is continuing to address the issue and fully restore SaaS Protection services on pod 'gbe2-saas-p0'.
- identified Jul 29, 2026, 03:02 PM UTC
Our R&D team has confirmed that backups are currently processing normally on pod 'gbe2-saas-p0' however they are continuing to address an issue affecting customer account access.
- identified Jul 29, 2026, 04:38 PM UTC
Our R&D team is continuing to address the account access issues still affecting some SaaS Protection customers hosted on pod 'gbe2-saas-p0' as well as monitoring backup performance.
- monitoring Jul 29, 2026, 05:12 PM UTC
Our R&D team has implemented additional changes to address the intermittent account access issues that were still affecting some customers hosted on pod 'gbe2-saas-p0' and backups for all services are continuing to process. We will be monitoring the pod closely for any other issues.
- resolved Jul 29, 2026, 08:15 PM UTC
Backups continue to process and all customer accounts hosted on pod 'gbe2-saas-p0' are accessible and functioning normally. This incident is resolved.
Autotask - Multiple Regions - Inbound emails are not creating tickets
Affected: Limited ReleaseAmerica EastAmerica East 2America East 3America WestAmerica West 2America West 3Australia / New ZealandAustralia / New Zealand 2Spanish (Español)AT01
Timeline · 3 updates
- investigating Jul 28, 2026, 06:01 PM UTC
We are aware of a problem where tickets are not getting created from inbound emails. 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/
- monitoring Jul 28, 2026, 06:06 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 29, 2026, 07:04 AM UTC
This incident has been resolved. All inbound emails that occurred during the incident timeframe have been successfully reprocessed.
Endpoint Backup v2 - UniView is exhibiting inconsistencies in backup reporting, resulting in inaccurate backup status visibility
Affected: Backup
Timeline · 4 updates
- investigating Jul 28, 2026, 12:52 PM UTC
We are aware of a problem where Endpoint Backup v2 assets in UniView may incorrectly indicate backup failures despite successful backup completion, which can trigger unnecessary email notifications. 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 Jul 28, 2026, 06:04 PM UTC
We are continuing to investigate this issue.
- monitoring Jul 28, 2026, 11:59 PM UTC
Our R&D team has implemented a fix, and we're seeing improved performance across the affected systems. We're continuing to monitor the environment to ensure the improvements are sustained.
- resolved Jul 29, 2026, 11:59 PM UTC
This incident has been resolved. 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.
Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'gbe2-saas-p2'
Affected: SaaS Protection Backups
Timeline · 6 updates
- identified Jul 28, 2026, 12:47 PM UTC
We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'gbe2-saas-p2' may be experiencing backup performance degradation affecting some SharePoint/Teams services. The Kaseya Engineering 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/
- identified Jul 28, 2026, 06:02 PM UTC
Our R&D team has implemented changes on pod 'gbe2-saas-p2' to mitigate the backup performance issues affecting some SharePoint and Teams services.
- monitoring Jul 28, 2026, 08:07 PM UTC
Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' are improving after the changes made on the pod earlier today. Our R&D team is continuing to monitor.
- monitoring Jul 29, 2026, 03:20 PM UTC
Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' have returned to normal levels. Our R&D team is continuing to monitor.
- monitoring Jul 30, 2026, 03:48 PM UTC
Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' are currently stable at normal levels. Our R&D team is making additional adjustments to the configuration on the pod to further address the issue and will continue to monitor.
- monitoring Jul 31, 2026, 01:58 PM UTC
Backup success rate metrics for SharePoint/Teams services on pod 'gbe2-saas-p2' remain stable at normal levels. Our R&D team is continuing to monitor.
Datto SaaS Protection - Service disruption for customers hosted on node 'use1-bfyii-2901'
Affected: SaaS Protection Backups
Timeline · 4 updates
- investigating Jul 27, 2026, 05:35 PM UTC
We are aware of a problem where Datto SaaS Protection customers hosted on node 'use1-bfyii-2901' 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/
- identified Jul 27, 2026, 06:16 PM UTC
The issue has been identified and the R&D team is actively working to resolve it.
- monitoring Jul 27, 2026, 06:59 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 27, 2026, 08:00 PM UTC
This incident has been resolved.
VSAX - EMEA/APAC - Intermittent 500 errors and offline devices
Affected: APACEU
Timeline · 4 updates
- identified Jul 24, 2026, 01:27 PM UTC
We are aware of a problem where customers hosted on EMEA/APAC app servers may see intermediate service disruption, getting 500 - internal server error. The Kaseya Engineering Team has identified the issue and working towards 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/
- identified Jul 24, 2026, 03:46 PM UTC
The Kaseya Engineering Team has developed a fix that will address this issue. The fix will be deployed after hours to our EMEA and APAC App Servers on the following schedule: 17:00 UTC APAC 20:00 UTC EMEA Those that are online during this change will need to login again as they will be kicked out the system. Should you have 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/
- monitoring Jul 24, 2026, 08:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 24, 2026, 09:23 PM UTC
This incident has been resolved.
Intermittent 500 Errors in Datto Partner Portal for Backup Products.
Affected: Status Components
Timeline · 4 updates
Microsoft Azure Outage in US West Impacting Multiple Kaseya Products
Affected: Device RegistrationBackupDevice Check-inBackupDevice RegistrationKaseyaOne
Timeline · 6 updates
- investigating Jul 23, 2026, 03:15 PM UTC
We are aware of a problem where the KaseyaOne Portal is not accessible. The Kaseya R&D Team is investigating the issue. Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/phone Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ As a note; To ensure business continuity, for Kaseya modules using Require Log In with KaseyaOne, users must authenticate using their KaseyaOne Unified Login credentials. Users added as exceptions can still log in using local module-specific credentials. Details are available in this Knowledge Base article: https://help.one.kaseya.com/help/Content/1_Configuration/enable-require-login-with-K1.htm We recommend adding a small set of users to the override list to maintain access in the event of a future disruption or maintenance, helping ensure continuous business operations
- identified Jul 23, 2026, 03:49 PM UTC
We have verified that the KaseyaOne Portal is being impacted by the Microsoft Azure Outage. Please follow their Status Post as well for updates: https://azure.status.microsoft/en-us/status
- identified Jul 23, 2026, 05:06 PM UTC
Kaseya R&D are continuing to work closely with Microsoft Azure to resolve this issue affecting the KaseyaOne Portal.
- identified Jul 23, 2026, 06:26 PM UTC
We have identified additional Kaseya Products that rely on Microsoft Azure Infrastructure that are affected by this issue. Partners using Datto / Unitrends Backup for Microsoft Azure and Datto / Unitrends Endpoint Backup with Disaster Recovery in the US West region will experience issues with Device Check-In, Device Registration, and Back Up. The Kaseya R&D team are continuing to work with the Microsoft Azure team to resolve this issue and we hope to have updates on a resolution as soon as possible.
- monitoring Jul 23, 2026, 06:40 PM UTC
A fix has been implemented by Microsoft Azure and we are monitoring the results. Please refer to the Microsoft Status page here: https://azure.status.microsoft/en-us/status for more details
- resolved Jul 23, 2026, 09:19 PM UTC
This incident has been resolved.
Datto Networking - Web Filtering Configuration Changes on DNA/D200 Devices Failed to Apply Successfully
Affected: Routers
Timeline · 5 updates
Autotask PSA - UK03 - Error Messages Upon Navigating the UI
Affected: UK03 (United Kingdom)
Timeline · 3 updates
- investigating Jul 23, 2026, 08:22 AM UTC
We are aware of a problem where partners in our UK03 zone are receiving error messages when navigating the UI. The Kaseya R&D Team are investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Jul 23, 2026, 08:52 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 23, 2026, 09:24 AM UTC
This incident has been resolved.
Service Degradation - DES1 DC
Affected: DES01 - Munich, EU
Timeline · 4 updates
- investigating Jul 23, 2026, 04:17 AM UTC
We are currently experiencing service disruption in DES1 DC. Our team is working to restore the functionality on the affected instances at this time. We apologize for any inconvenience this may cause. - Kaseya Cloud Operations Team
- monitoring Jul 23, 2026, 04:29 AM UTC
Service has been restored. All targets in the DES1 data center are now accessible and fully operational. Apologies for the inconvenience caused. - Kaseya Cloud Operations Team.
- monitoring Jul 23, 2026, 04:30 AM UTC
We are continuing to monitor this.
- resolved Jul 23, 2026, 06:26 AM UTC
This incident has been resolved.
Datto SaaS Protection - Service disruption for customers hosted on node 'aue1-bfyii-2319'
Affected: SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Restores/Exports
Timeline · 3 updates
- investigating Jul 21, 2026, 06:05 PM UTC
We are aware of a problem where SaaS Protection customers hosted on node 'aue1-bfyii-2319' are unable to access their accounts and are experiencing a disruption to their 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 Jul 21, 2026, 06:29 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 21, 2026, 06:42 PM UTC
This incident has been resolved.
Datto RMM - Merlot - Slow loading pages across the Web Application, Audit attempts are unsuccessful
Affected: Merlot (EU2)
Timeline · 6 updates
Datto Partner Portal - Users Unable to Access Datto Partner Portal
Timeline · 2 updates
Datto RMM - Merlot - Agents going offline
Affected: Merlot (EU2)
Timeline · 5 updates
Endpoint Backup v2 - Subset of Endpoint Backup v2 assets are experiencing slow or incomplete backups due to 504 Gateway Timeout errors.
Affected: Backup
Timeline · 4 updates
Partial Service Disruption - KaseyaOne
Affected: KaseyaOne
Timeline · 2 updates
Datto SaaS Protection - Backup performance degradation for various services on pod multiple pods
Affected: SaaS Protection Backups
Timeline · 3 updates
- investigating Jul 11, 2026, 04:07 PM UTC
We are aware of a problem where some customers across multiple pods are experiencing backup performance degradation for various services. The affected pods and services are listed below. 'gbe2-pod-0' - SharePoint 'gbe2-pod-1' - SharePoint 'use1-pod-4' - SharePoint 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/
- monitoring Jul 12, 2026, 12:13 PM UTC
A fix has been implemented and we are monitoring the results. Several pods have shows signs of improvement.
- resolved Jul 13, 2026, 12:26 PM UTC
This incident has been resolved.