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.

Source: status.kaseya.net

157incidents recorded
155last 12 months
88last 90 days
4 daystypical duration
Incidents per month
02040AprMayJunJulAugSepOct14
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct98%
Pingoru began tracking Kaseya in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202612695 of 720 (97%)
May 202620697 of 744 (94%)
June 202615695 of 720 (97%)
July 202629690 of 744 (93%)
August 202626719 of 744 (97%)
September 202637584 of 720 (81%)
October 202614574 of 589 (98%)

Incidents, newest first

Critical July 31, 2026 Datto RMM (Syrah)-- Datto RMM Agent Detected as Malware Post 15.1.0 3d 13h

Started Jul 31, 2026, 02:27 AM UTC· resolved Aug 03, 2026, 04:04 PM UTC

  1. 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.

  2. 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.

  3. 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.

  4. resolved Aug 03, 2026, 04:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 31, 2026 DRMM (Syrah) -- Device Filter "Site Name" criterion ignored, returns devices from all sites 2h 37m

Started Jul 31, 2026, 12:48 AM UTC· resolved Jul 31, 2026, 03:26 AM UTC

  1. investigating Jul 31, 2026, 12:48 AM UTC

    We are aware of the issue where Filters no longer respect the "Site Name" Criteria resulting in devices that should not be included in the Filter are included in the Filter that then affects Policy/Job targeting.

  2. investigating Jul 31, 2026, 02:04 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 31, 2026, 02:30 AM UTC

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

  4. resolved Jul 31, 2026, 03:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2026 Datto SaaS Protection - Backup performance degradation for some Exchange services on pod 'aue1-saas-p1' 3d 16h

Started Jul 30, 2026, 04:34 PM UTC· resolved Aug 03, 2026, 09:22 AM UTC

  1. 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/

  2. 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.

  3. 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.

Read the full incident report →

Minor July 30, 2026 Datto SaaS Protection - Backup performance degradation for some Teams/SharePoint services on pod 'gbe2-saas-p0' 1d 12h

Started Jul 30, 2026, 03:11 PM UTC· resolved Aug 01, 2026, 04:05 AM UTC

  1. 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/

  2. identified Jul 30, 2026, 03:33 PM UTC

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

  3. 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.

  4. 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.

Read the full incident report →

Major July 30, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'des1-bfyii-2985' 6h 19m

Started Jul 30, 2026, 01:44 PM UTC· resolved Jul 30, 2026, 08:04 PM UTC

  1. 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/

  2. identified Jul 30, 2026, 03:45 PM UTC

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

  3. 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.

  4. resolved Jul 30, 2026, 08:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 29, 2026 Datto SaaS Protection - Service disruption affecting customers hosted on pod 'gbe2-saas-p0' 9h 19m

Started Jul 29, 2026, 10:55 AM UTC· resolved Jul 29, 2026, 08:15 PM UTC

  1. 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/

  2. identified Jul 29, 2026, 10:56 AM UTC

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

  3. 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'.

  4. 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'.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

Read the full incident report →

Major July 28, 2026 Autotask - Multiple Regions - Inbound emails are not creating tickets 13h 2m

Started Jul 28, 2026, 06:01 PM UTC· resolved Jul 29, 2026, 07:04 AM UTC

  1. 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/

  2. monitoring Jul 28, 2026, 06:06 PM UTC

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

  3. 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.

Read the full incident report →

Minor July 28, 2026 Endpoint Backup v2 - UniView is exhibiting inconsistencies in backup reporting, resulting in inaccurate backup status visibility 1d 11h

Started Jul 28, 2026, 12:52 PM UTC· resolved Jul 29, 2026, 11:59 PM UTC

  1. 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/

  2. investigating Jul 28, 2026, 06:04 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

Read the full incident report →

Minor July 28, 2026 Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'gbe2-saas-p2' 1d 12h

Started Jul 28, 2026, 12:47 PM UTC· resolved Jul 30, 2026, 01:12 AM UTC

  1. 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/

  2. 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.

  3. 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.

  4. 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.

Read the full incident report →

Major July 27, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'use1-bfyii-2901' 2h 25m

Started Jul 27, 2026, 05:35 PM UTC· resolved Jul 27, 2026, 08:00 PM UTC

  1. 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/

  2. identified Jul 27, 2026, 06:16 PM UTC

    The issue has been identified and the R&D team is actively working to resolve it.

  3. monitoring Jul 27, 2026, 06:59 PM UTC

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

  4. resolved Jul 27, 2026, 08:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 24, 2026 VSAX - EMEA/APAC - Intermittent 500 errors and offline devices 7h 56m

Started Jul 24, 2026, 01:27 PM UTC· resolved Jul 24, 2026, 09:23 PM UTC

  1. 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/

  2. 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/

  3. monitoring Jul 24, 2026, 08:25 PM UTC

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

  4. resolved Jul 24, 2026, 09:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 24, 2026 Intermittent 500 Errors in Datto Partner Portal for Backup Products. 1h 42m

Started Jul 24, 2026, 08:47 AM UTC· resolved Jul 24, 2026, 10:29 AM UTC

  1. investigating Jul 24, 2026, 08:47 AM UTC

    We are aware of an issue where customers are encountering 500 errors while accessing Backup products within the Datto Partner Portal (DPP). The Kaseya R&D Team is investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Jul 24, 2026, 10:06 AM UTC

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

  3. resolved Jul 24, 2026, 10:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 23, 2026 Microsoft Azure Outage in US West Impacting Multiple Kaseya Products 6h 4m KaseyaOne

Started Jul 23, 2026, 03:15 PM UTC· resolved Jul 23, 2026, 09:19 PM UTC

  1. 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

  2. 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

  3. 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.

  4. 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.

  5. 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

  6. resolved Jul 23, 2026, 09:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2026 Datto Networking - Web Filtering Configuration Changes on DNA/D200 Devices Failed to Apply Successfully 4d 1h

Started Jul 23, 2026, 01:37 PM UTC· resolved Jul 27, 2026, 02:45 PM UTC

  1. identified Jul 23, 2026, 01:37 PM UTC

    We are aware of a problem where web filtering configuration changes are not being successfully applied on the DNA and D200 appliances. 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/

  2. identified Jul 24, 2026, 03:49 PM UTC

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

  3. monitoring Jul 27, 2026, 12:33 PM UTC

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

  4. resolved Jul 27, 2026, 02:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2026 Autotask PSA - UK03 - Error Messages Upon Navigating the UI 1h 2m

Started Jul 23, 2026, 08:22 AM UTC· resolved Jul 23, 2026, 09:24 AM UTC

  1. 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/

  2. monitoring Jul 23, 2026, 08:52 AM UTC

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

  3. resolved Jul 23, 2026, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2026 Service Degradation - DES1 DC 2h 8m

Started Jul 23, 2026, 04:17 AM UTC· resolved Jul 23, 2026, 06:26 AM UTC

  1. 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

  2. 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.

  3. monitoring Jul 23, 2026, 04:30 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jul 23, 2026, 06:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 21, 2026 Datto SaaS Protection - Service disruption for customers hosted on node 'aue1-bfyii-2319' 36m

Started Jul 21, 2026, 06:05 PM UTC· resolved Jul 21, 2026, 06:42 PM UTC

  1. 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/

  2. monitoring Jul 21, 2026, 06:29 PM UTC

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

  3. resolved Jul 21, 2026, 06:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 21, 2026 Datto RMM - Merlot - Slow loading pages across the Web Application, Audit attempts are unsuccessful 1d 2h

Started Jul 21, 2026, 08:55 AM UTC· resolved Jul 22, 2026, 11:51 AM UTC

  1. investigating Jul 21, 2026, 08:55 AM UTC

    The Kaseya R&D Team is currently investigating reported issues on the Merlot platform with pages across the Datto RMM Web Application loading slowly or failing to load. Device audit attempts have also been observed to be consistently unsuccessful. Thank you for your patience while we are working on identifying and resolving the issue. Please subscribe to this incident to receive notifications when an update is posted.

  2. monitoring Jul 21, 2026, 10:06 AM UTC

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

  3. investigating Jul 21, 2026, 03:09 PM UTC

    The Kaseya R&D Team is currently investigating additional reports on the Merlot platform where pages and functions across the Datto RMM Web Application may load slowly or fail to load. Thank you for your patience while we are working on identifying and resolving the issue. Please subscribe to this incident to receive notifications when an update is posted.

  4. monitoring Jul 21, 2026, 05:14 PM UTC

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

  5. resolved Jul 22, 2026, 11:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 20, 2026 Datto Partner Portal - Users Unable to Access Datto Partner Portal –

Started Jul 20, 2026, 01:00 PM UTC· resolved Jul 20, 2026, 01:00 PM UTC

  1. resolved Jul 20, 2026, 02:06 PM UTC

    We are pleased to inform you that the recent service incident experienced by our BCDR partners where users experienced difficulties logging into the Datto Partner Portal has now been successfully resolved. We understand the impact that such problems can have on your business operations, and we sincerely apologize for any inconvenience caused during this time. Our team has been diligently working to identify the root cause of the problem. Our goal is to not only address the immediate concern but also to minimize the risk of similar incidents in the future. By analyzing the underlying factors, we aim to enhance our systems and processes, ensuring a more robust and reliable experience for all our partners. Thank you for your patience and understanding. We remain committed to delivering exceptional service and continuous improvement. Best regards,

Read the full incident report →

Major July 20, 2026 Datto RMM - Merlot - Agents going offline 21h 12m

Started Jul 20, 2026, 12:54 PM UTC· resolved Jul 21, 2026, 10:06 AM UTC

  1. investigating Jul 20, 2026, 12:54 PM UTC

    We are currently receiving reports of Merlot agents appearing as offline. We are aware of this and we are investigating.

  2. investigating Jul 20, 2026, 03:22 PM UTC

    Investigation efforts are ongoing as our teams continue to work diligently on this issue.

  3. monitoring Jul 20, 2026, 04:48 PM UTC

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

  4. resolved Jul 21, 2026, 10:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2026 Endpoint Backup v2 - Subset of Endpoint Backup v2 assets are experiencing slow or incomplete backups due to 504 Gateway Timeout errors. 1d 4h

Started Jul 16, 2026, 01:59 PM UTC· resolved Jul 17, 2026, 06:05 PM UTC

  1. investigating Jul 16, 2026, 01:59 PM UTC

    We are aware of a problem where Endpoint Backup v2 assets can experience slow or failed backups due to a "504 Gateway Timeout" error. 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/

  2. monitoring Jul 17, 2026, 03:58 PM UTC

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

  3. resolved Jul 17, 2026, 06:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 15, 2026 Partial Service Disruption - KaseyaOne – KaseyaOne

Started Jul 15, 2026, 08:56 AM UTC· resolved Jul 15, 2026, 08:56 AM UTC

  1. resolved Jul 15, 2026, 08:56 AM UTC

    We experienced a partial service disruption affecting access to KaseyaOne from 02:55 AM ET to 03:30 AM ET. KaseyaOne services are now fully operational, and we are continuing to monitor the environment to ensure stability. We apologize for any inconvenience this may have caused. - Kaseya Cloud Operations Team

Read the full incident report →

Critical July 11, 2026 Datto SaaS Protection - Backup performance degradation for various services on pod multiple pods 1d 20h

Started Jul 11, 2026, 04:07 PM UTC· resolved Jul 13, 2026, 12:26 PM UTC

  1. 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/

  2. 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.

  3. resolved Jul 13, 2026, 12:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 8, 2026 Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'gbe2-saas-p0' 14d 1h

Started Jul 08, 2026, 12:37 PM UTC· resolved Jul 22, 2026, 02:18 PM UTC

  1. investigating Jul 08, 2026, 12:37 PM UTC

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

  2. monitoring Jul 08, 2026, 02:05 PM UTC

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

  3. monitoring Jul 09, 2026, 12:24 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jul 13, 2026, 07:55 PM UTC

    Our R&D team has implemented additional changes to further address this issue. SharePoint services have recovered and our R&D team continues to monitor as Teams backup success rates improve.

  5. monitoring Jul 17, 2026, 02:12 PM UTC

    Backup success rates for Teams have returned to normal. All other services continue to backup normally. Our R&D team is continuing to monitor for any other issues.

  6. resolved Jul 22, 2026, 02:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 6, 2026 Datto SaaS Protection - Pod 'aue1-bfyii-2746' is Inaccessible 23h 33m

Started Jul 06, 2026, 01:33 PM UTC· resolved Jul 07, 2026, 01:06 PM UTC

  1. identified Jul 06, 2026, 01:33 PM UTC

    We are aware of a problem where Pod 'aue1-bfyii-2746' is inaccessible. The Kaseya R&D Team has identified the problem and are working toward a fix. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Jul 07, 2026, 12:38 PM UTC

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

  3. resolved Jul 07, 2026, 01:06 PM UTC

    This incident has been resolved.

Read the full incident report →