Datto (Kaseya) Outage History
Uptime record, past incidents, and downtime history for Datto (Kaseya).
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 0% | 25 | 25 |
| April 2026 | 0% | 30 | 30 |
| March 2026 | 0% | 31 | 31 |
| February 2026 | 0% | 5 | 5 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Datto SaaS Protection - Service disruption for customers hosted on pod 'gbe2-saas-p1'
Started: May 24, 5:52 PM
SaaS Protection Backups
investigating
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/
May 24, 5:52 PM
Endpoint Backup v2 - Last Backup Timestamp Is Not Updating Correctly, Which May Result in False-Positive Backup Threshold Alerts within UniView
Started: May 22, 3:15 PM
Backup
identified
We are aware of a problem where 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.
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/
May 22, 3:15 PM
[Datto Workplace & Datto File Protection] Users are unable to login
Started: May 21, 8:50 AM
US8
US1
US9
US6
US17
US15
monitoring
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.
May 21, 9:05 AM
investigating
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!
May 21, 8:50 AM
Datto RMM - Cagservice.exe being flagged as malicious by Antivirus Software due to a Microsoft Defender Definition update misclassifying the executable
Started: May 20, 10:51 PM
Pinotage (EU1)
Merlot (EU2)
Zinfandel (US West)
Concord (US East)
Syrah (APAC)
Vidal (US East)
monitoring
The Kaseya R&D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.0 Datto RMM version's cagservice.exe in a recent security intelligence update for Microsoft Defender Antivirus and other Microsoft antimalware.
This issue was fixed in the security intelligence update version 1.451.15.0, and the issue should no longer occur as long as the device is on this definition version or later.
Microsoft currently does not offer an automated way to rev...
May 21, 3:40 PM
identified
The R&D team continues to work with Microsoft counterparts on a path to restore the erroneously quarantined assets, and restore RMM connectivity to affected devices.
May 21, 9:35 AM
investigating
In collaboration with Microsoft, an update has been made to Microsoft Defender Antivirus and other Microsoft antimalware's security intelligence to prevent these false positive alerts on the cagservice.exe for devices running Microsoft antimalware solutions.
Devices running security intelligence version 1.451.15.0 and above have the updated detection logic. If you receive an alert for the cagservice.exe and your device is on version 1.451.15.0 and above, please reach out to our support team...
May 20, 10:51 PM
investigating
The RMM agent underwent an update, causing some devices with antivirus software, mainly Microsoft Defender for Endpoint, to alert on the update behavior and quarantine "cagservice.exe". This alert has been identified as a false positive.
To prevent these alerts on Microsoft Defender for Endpoint for this new RMM agent, please follow these steps:
1. Go to the Security Portal
2. Go to Settings
3. Go to Endpoints
4. Under "Rules" click on "Indicators"
5. Under the file hashes, add the indicat...
May 20, 7:05 PM
investigating
We are aware of a problem where the Datto RMM's "cagservice.exe" is being flagged as malicious by some antivirus software, causing it to be quarantined.
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/
May 20, 4:28 PM
Datto Networking - Intermittent Check‑In Failures Observed on Datto Networking D200 Devices
Started: May 4, 5:24 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 5, 1:07 PM
investigating
We are aware of a problem where Datto Networking D200 devices may intermittently fail to check in, resulting in false‑positive offline email alerts.
Please note: The observed issue is cosmetic and does not affect the functionality or performance of the device.
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/
May 4, 5:24 PM
April 2026
VSA10 - Degraded Performance - All regions
Started: Apr 10, 8:57 AM
monitoring
The root cause of the issue has been found. We believe that the issue will resolve itself as agents are allowed time to update.
If you are still experiencing issues performing Remote Takeovers, please contact our support team for help resolving the issue.
We will continue to monitor agent health and update here is the situation changes.
Apr 10, 9:29 PM
identified
We are still experiencing issues with subset of VSA10 customers unable to use Remote control feature. Our team is actively working to restore functionality on the affected instances.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
Apr 10, 4:54 PM
monitoring
Currently Application functionality for all the regions looks stable. We will continue to monitor the results and keep you posted accordingly.
We apologize for the inconvenience caused.
- Kaseya Cloud Operations Team
Apr 10, 10:23 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 10, 9:43 AM
investigating
Our team has identified an issue with the file transfer feature across all VSA10 regions. We are actively working to restore functionality on the affected instances.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
Apr 10, 8:57 AM
VSA10 - Partial Service Disruption - All regions
Started: Apr 10, 3:46 AM
monitoring
We are continuing to monitor for any further issues.
Apr 10, 8:39 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 10, 8:38 AM
investigating
We are experiencing issues with remote control on all VSA10 regions randomly, that may be resulting in impacting administrators ability to manage endpoints. Our team is working to restore functionality on the instance at this time.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
Apr 10, 6:20 AM
investigating
We are experiencing issues with remote control on APAC VSA10 that may be resulting in impacting administrators ability to manage endpoints. Our team is working to restore functionality on the instance at this time.
We apologize for any disruption this may cause.
- Kaseya Cloud Operations Team
Apr 10, 3:46 AM
Datto Backup for Microsoft Azure / Datto Endpoint Backup with Disaster Recovery - Devices Are Failing To Complete Registration
Started: Apr 9, 6:00 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 10, 3:28 PM
identified
The issue has been identified and a fix is being implemented.
Apr 10, 12:47 PM
investigating
We are aware of a problem where Datto Backup for Microsoft Azure and Datto Endpoint Backup with Disaster Recovery devices can experience registration failures.
The Kaseya R&D Team is currently investigating the issue and working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Apr 9, 6:00 PM
Datto RMM - Pinotage - Extended login times and login failures when attempting to access the UI
Started: Apr 9, 9:39 AM
monitoring
The R&D team has identified and resolved the issue that was causing performance issues and failures when logging in to the UI on the Pinotage platform.
We are currently monitoring the health of the service.
Apr 9, 9:39 AM
Datto RMM - Concord & Vidal - Delayed Job Execution
Started: Apr 6, 3:48 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 6, 4:06 PM
identified
We are aware of a problem where job execution is delayed on the Concord & Vidal platforms.
The Kaseya R&D Team have identified the issue and are working on implementing a fix.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Apr 6, 3:48 PM
March 2026
Datto BCDR - Server1405 - Degraded Offsite Performance
Started: Mar 26, 7:26 PM
identified
Efforts to address the underlying issue remain in progress. Additional updates will be provided as they become available.
Apr 8, 7:09 PM
identified
The R&D team continues to actively work toward a resolution for this issue.
Additional information will be communicated as it becomes available.
Mar 31, 4:58 PM
identified
We are aware of a problem where BCDR assets paired to server1405 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/
Mar 26, 7:26 PM
Datto RMM - Concord - Creating or saving Monitoring Policies fails with "could not execute statement" error
Started: Mar 26, 3:21 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 26, 3:39 PM
investigating
We are aware of a problem where Creating or saving Monitoring Policies fails with "could not execute statement" error.
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/
Mar 26, 3:21 PM
Datto BCDR - Server5856 - Degraded Offsite Performance
Started: Mar 25, 2:43 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 27, 1:18 PM
identified
We are aware of a problem where BCDR users paired to server5856 in the US-East region 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/
Mar 25, 2:43 PM
Datto Endpoint Backup for PC - Degraded Offsite Capabilities for Cloud Siris use1-dtc-server-143
Started: Mar 24, 11:44 PM
investigating
We are aware of an issue where Datto Endpoint Backup for PC users paired with Cloud Siris 'use1-dtc-server-143' may experience degraded performance, which can result in slower-than-average backup and restore speeds.
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/
Mar 24, 11:44 PM
Datto Endpoint Backup for PC - Degraded Capabilities on 'gbe2-dtc-server-157' in UK Region
Started: Mar 24, 2:24 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 24, 4:04 PM
identified
We are aware of a problem where users paired to server 'gbe2-dtc-server-157' in the UK 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/
Mar 24, 2:24 PM
Datto RMM - Merlot and Pinotage - Device Filter results are not able to be returned
Started: Mar 23, 4:39 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 23, 6:31 PM
investigating
We are aware of a problem where some device filters on Merlot and Pinotage are failing to load with an error pop-up saying: "Device Filter results were not able to be returned."
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/
Mar 23, 4:39 PM
Datto SaaS Protection - Backup performance degradation on pods 'use1-saas-p7' and 'use1-saas-p8'
Started: Mar 20, 11:39 AM
monitoring
Backups success rates for both pods 'use1-saas-p7' and 'use1-saas-p8' have returned to normal levels.
Our R&D team is continuing to monitor for any other issues.
Mar 22, 7:20 PM
monitoring
Backups success rates for pod 'use1-saas-p7' have returned to normal levels and remain stable.
Customer backups on pod 'use1-saas-p8' are continuing to process normally and our R&D team is monitoring recovery as backup success rates improve.
Mar 20, 7:09 PM
identified
Our R&D team has implemented a fix to address the backup issues affecting pod 'use1-saas-p8' and backups have started to process normally again.
Mar 20, 5:53 PM
identified
Our R&D team is continuing to implement changes to address the backup issues affecting customers hosted on pod 'use1-saas-p8'
Backups continue to process normally on pod 'use1-saas-p7' and backup success rates should fully recover in the next couple of hours.
Mar 20, 5:37 PM
identified
Backups are processing normally again on pod 'use1-saas-p7' and backup success rate metrics are improving.
The R&D team has identified another issue still affecting backups on pod 'use1-saas-p8' and they are actively working to resolve it.
Mar 20, 2:16 PM
identified
The R&D team identified the root cause of the problem and they are working on resolving the issue.
Mar 20, 12:05 PM
investigating
We are currently investigating an issue affecting some customers hosted on pods 'use1-saas-p7' and 'use1-saas-p8', where performance degradation has been observed affecting all backups.
The Kaseya R&D team has identified the root cause and is actively working on a resolution. Further updates will be provided as progress is made.
Mar 20, 11:39 AM
Datto RMM - Merlot - Agent-based alerts are not being raised on the platform
Started: Mar 20, 10:48 AM
monitoring
The R&D team identified the cause of the issue and implemented a fix.
New alerts are now creating on the platform in real time, and previous alerts impacted by this issue are being processed and will be raised in the accounts within the next 2 hours.
Mar 20, 12:21 PM
investigating
We are aware of a problem where Agent-based alerts are not being raised on the platform for Datto RMM on the Merlot platform
The Kaseya R&D Team are aware of the issue and are investigating the root cause.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Mar 20, 10:48 AM
Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'use1-saas-p5'
Started: Mar 18, 10:49 AM
monitoring
Backups are processing normally and backup success rates continue to improve.
Our R&D team is continuing to monitor.
Mar 18, 2:07 PM
monitoring
We are seeing continued improvement in backup performance on pod use1-saas-p5.
The R&D team will continue monitoring the environment until full recovery is confirmed.
Mar 18, 12:30 PM
identified
We are currently investigating an issue affecting some customers hosted on pod use1-saas-p5, where backup performance degradation has been observed for certain SharePoint services.
The Kaseya R&D team has identified the root cause and is actively working on a resolution. Further updates will be provided as progress is made.
Mar 18, 10:49 AM
Endpoint Backup v2 - Registration, Backup and Restore Requests Are Not Initiating Successfully
Started: Mar 16, 3:16 PM
investigating
We are aware of a problem where Endpoint Backup v2 registration, backup, restore requests are not initiating successfully.
The Kaseya R&D Team is currently investigating the issue and working towards a resolution.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Mar 16, 3:16 PM
Datto SaaS Protection - Backup performance degradation on pod 'use1-saas-p9'
Started: Mar 16, 11:08 AM
monitoring
Operations have been restored by the R&D team.
We are continuing to monitor the service to ensure full recovery.
Mar 16, 11:47 AM
identified
We are aware of an issue affecting backup performance for some customers hosted on pod use1-saas-p9.
Our R&D team is actively working to restore the service to full capacity. In the meantime, backup processing may be delayed, but the team is working to ensure daily backups are completed within the 24-hour window.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Mar 16, 11:08 AM
Datto Networking - Dynamic DNS records for Datto Networking DNA devices are temporarily resolving to an incorrect private IP address
Started: Mar 11, 1:33 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 11, 2:35 PM
identified
We are aware of a problem where Datto Networking DNA devices' dynamic DNS addresses have been inadvertently configured with an incorrect private IP address.
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/
Mar 11, 1:33 PM
Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'des1-saas-p1'
Started: Mar 10, 3:29 PM
SaaS Protection Backups
monitoring
The backup cadence on pod 'des1‑saas‑p1' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. R&D is continuing to develop improvements, targeted for release Q2 2026. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.
May 14, 7:24 PM
monitoring
After monitoring over the weekend, all services are backing up normally at 2x backup per day again. Our R&D teams are continuing to develop and test improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
Apr 20, 12:47 PM
monitoring
We are aware of additional reports of backup performance degradation affecting SharePoint services on pod 'des1-saas-p1'. Our R&D team has implemented changes to address the issue and are monitoring.
Apr 17, 2:03 PM
monitoring
Daily backup cadence on pod ‘des1‑saas‑p1’ remains temporarily set to 2x backups per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Our R&D teams are actively developing and testing improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
Mar 25, 7:55 PM
monitoring
Backup frequency on this pod is still set to 2x backups per day to maintain high backup success rates while the R&D team continues to develop and test improvements to address the issue. The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod. Backup success rates remain stable and the R&D team is continuing to monitor.
Mar 18, 7:32 PM
identified
Backups remain stable at 2x backups per day and our R&D team is continuing to monitor closely. The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod.
Mar 16, 6:35 PM
identified
Backups continue to process normally at 2x backups per day and success rates remain stable. Our R&D team will continue to monitor backup performance on the pod closely over the weekend as they prepare to increase backup frequency to 3x backups per day early next week.
Mar 13, 4:03 PM
identified
Backup frequency on the pod was increased to 2 backups per day again and our R&D team is monitoring closely as backup success rates continue to improve.
Mar 12, 8:01 PM
identified
The R&D team has successfully restored pod stability, and backups are now processing in real time.
They are working to resume the schedule of two backups per day, beginning with the next backup window.
Additional capacity is also being added to maintain continued pod stability, and to enable increasing the backup cadence to 3 backups per day in the near future.
Mar 12, 11:26 AM
identified
Recent changes made to improve SharePoint and Teams backup performance did not produce the expected results. Our R&D team will be implementing additional mitigation measures over the next 24 hours to further stabilize SharePoint and Teams backups for customers on the pod. As part of this work, we will be temporarily reducing backup frequency for customers from 2x backups per day to 1x backups per day. These adjustments are intended to improve overall system reliability while long‑term enhan...
Mar 11, 8:27 PM
identified
Issues affecting Teams backup performance have been identified and our R&D team is continuing to address the underlying problem affecting SharePoint/Teams backup performance for some customers hosted on the pod.
Mar 11, 4:52 PM
identified
After the changes implemented yesterday, the Kaseya R&D team is working to deploy additional improvements to further address the degraded backup performance affecting some customers hosted on pod 'des1-saas-p1'.
Mar 11, 3:08 PM
monitoring
The Kaseya R&D team has implemented additional changes to help address the issue and are monitoring the results closely.
Mar 10, 7:28 PM
identified
We are aware of a problem where some customers hosted on pod 'des1-saas-p1' are experiencing backup performance degradation for some SharePoint services.
The Kaseya R&D Team has identified the issue and are actively working to resolve it.
In the meantime, the R&D team has temporarily decreased the daily backup frequency on pod 'des1-saas-p1' from 3x per day to 2x per day to help maintain high backup success rates amidst ongoing spikes in Microsoft throttling.
Subscribe to the Kaseya Status...
Mar 10, 3:29 PM
Datto BCDR - Germany Region (Server 3818) - Degraded Offsite Performance
Started: Mar 9, 7:17 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 16, 5:13 PM
identified
We are aware of a problem where Datto BCDR users in the Germany region associated with server3818 may experience reduced 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/
Mar 9, 7:17 PM
July 2025
Datto SaaS Protection - Backup performance degradation for SharePoint services on pod 'des1-saas-p0'
Started: Jul 14, 1:29 PM
SaaS Protection Backups
monitoring
The backup cadence on pod 'des1‑saas‑p0' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. R&D is continuing to develop improvements, targeted for release Q2 2026. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.
May 14, 7:23 PM
monitoring
Daily backup cadence on pod ‘des1‑saas‑p0’ remains temporarily set to 2x backups per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Our R&D teams are actively developing and testing improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
Mar 25, 7:54 PM
monitoring
Backup frequency on this pod is still set to 2x backups per day to maintain high backup success rates while the R&D team continues to develop and test improvements to address the issue.
The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod.
Backup success rates remain stable and the R&D team is continuing to monitor.
Oct 30, 1:45 PM
monitoring
While the Kaseya R&D team continues to address the issue they have temporarily decreased the daily backup frequency on pod 'des1-saas-p0' from 3x per day to 2x per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling.
Backup completion percentages remain stable, and we’re monitoring the situation closely.
We will continue to review conditions daily and will restore 3x backups per day as soon as it’s safe and reliable for all customers hosted on the pod.
Jul 17, 1:11 PM
monitoring
Configuration changes have been implemented to address the issue and SharePoint backups are stable.
The Kaseya R&D team is monitoring.
Jul 16, 12:43 PM
identified
The Kaseya R&D team has identified the issue and are actively working to resolve it.
Jul 14, 4:59 PM
investigating
We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' may experience degraded SharePoint backup performance.
The Kaseya R&D Team is currently investigating this issue.
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
Jul 14, 1:29 PM
May 2025
Datto SaaS Protection - Backup performance degradation for Teams services on pod 'cae1-saas-p0'
Started: May 30, 2:16 PM
SaaS Protection Backups
monitoring
The backup cadence on pod 'cae1‑saas‑p0' remains temporarily set to 2x daily backups to maintain high success rates amid Microsoft throttling. R&D is continuing to develop improvements, targeted for release Q2 2026. The 3x daily backup cadence will be restored once it is stable and reliable for all customers.
May 14, 7:22 PM
monitoring
Daily backup cadence on pod ‘cae1‑saas‑p0’ remains temporarily set to 2x backups per day to maintain high backup success rates amidst ongoing spikes in Microsoft throttling. Our R&D teams are actively developing and testing improvements to address the issue, with a targeted release in Q2 2026. We will restore the 3x daily backup cadence when it is safe and reliable for all customers on the pod.
Mar 25, 7:54 PM
monitoring
Backup frequency on this pod is still set to 2x backups per day to maintain high backup success rates while the R&D team continues to develop and test improvements to address the issue.
The backup frequency will be increased to 3x backups per day when it is safe and reliable for all customers hosted on the pod.
Backup success rates remain stable and the R&D team is continuing to monitor.
Oct 30, 1:46 PM
monitoring
To maintain high backup success rates amidst ongoing spikes in Microsoft throttling, the SaaS Protection team is continuing with 2x backups per day.
Backup completion percentages remain stable, and we’re monitoring the situation closely.
We will continue to review conditions daily and will restore 3x backups per day as soon as it’s safe and reliable for all customers hosted on the pod.
Jul 1, 9:01 PM
monitoring
Teams backup success rates have stabilized after the recent changes that were implemented.
The Kaseya R&D team is monitoring.
Jun 18, 3:46 PM
monitoring
Degraded backup performance for Teams services has again been observed for some customers hosted on the pod.
While the Kaseya R&D team continues to investigate they will be temporarily decreasing the daily Teams backup frequency from 3x per day to 2x per day to allow the service to stabilize.
Jun 10, 7:32 PM
monitoring
Teams backup success rates have stabilized on the pod.
The Kaseya R&D team is continuing to investigate additional changes to address the issue further.
Jun 9, 12:37 PM
monitoring
The Kaseya R&D team is actively investigating additional changes to be implemented to address the continued Teams backup performance degradation affecting some customers hosted on the pod.
Jun 6, 8:00 PM
monitoring
Additional configuration changes have been made on the affected pod to further address the Teams backup performance degradation.
The Kaseya R&D team is monitoring results.
Jun 5, 3:22 PM
monitoring
Backup success rates for Teams services have improved and our R&D team is continuing to monitor.
Jun 2, 8:36 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 2, 12:18 PM
investigating
We are currently aware of a problem where some Datto SaaS Protection customers hosted on pod 'cae1-saas-p0' are experiencing degraded backup performance for Teams 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/
May 30, 2:16 PM