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 202614577 of 592 (98%)

Incidents, newest first

Minor August 28, 2026 Datto RMM / Datto EDR / Datto AV – Integration – Datto RMM Reporting Datto EDR and Datto AV Products as Not Detected 3d 3h Datto AV

Started Aug 28, 2026, 10:30 AM UTC· resolved Aug 31, 2026, 01:40 PM UTC

  1. investigating Aug 28, 2026, 10:30 AM UTC

    We are investigating an issue affecting status reporting between Datto RMM, Datto EDR, and Datto AV. Some devices may generate alerts in Datto RMM reporting that Datto EDR or Datto AV is not detected. Datto EDR and Datto AV remain installed and are operating normally on affected endpoints. This issue is limited to how their status is communicated to and displayed within Datto RMM and does not indicate a loss of endpoint protection. Our Engineering teams are investigating this issue with high priority. We will provide further updates as more information becomes available. 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 Aug 28, 2026, 12:59 PM UTC

    We have identified an issue affecting status reporting between Datto EDR, Datto AV, and Datto RMM. As a result, some devices may incorrectly generate alerts in Datto RMM indicating that Datto EDR requires attention or that Datto AV is not installed. Our investigation has confirmed that Datto EDR and Datto AV remain installed and functioning properly on affected endpoints. Endpoint protection services continue to operate as expected. The issue is limited to the status information being reported and displayed within Datto RMM and does not indicate a loss of protection or a failure of the Datto EDR or Datto AV products. Engineering teams have identified the underlying cause and are actively working on a resolution. We will continue to provide updates as additional information becomes available. If you have 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 Aug 28, 2026, 08:33 PM UTC

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

  4. resolved Aug 31, 2026, 01:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2026 Datto SaaS Protection - Backup performance degradation for Exchange services on pod 'use1-saas-p7' 4d 5h

Started Aug 27, 2026, 02:52 PM UTC· resolved Aug 31, 2026, 08:11 PM UTC

  1. investigating Aug 27, 2026, 02:52 PM UTC

    We are aware of a problem where some customers hosted on pod 'use1-saas-p7' are currently experiencing degraded backup performance for Exchange services. The Kaseya Engineering Team is actively investigating. 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. investigating Aug 27, 2026, 05:38 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 28, 2026, 12:40 PM UTC

    Our R&D team has identified an issue causing the degraded backup performance for Exchange services on pod 'use1-saas-p7'. Configuration changes have been implemented to help mitigate the issue and additional changes are being prepared for deployment to further address Exchange backup performance.

  4. identified Aug 28, 2026, 01:49 PM UTC

    Our R&D team has deployed additional changes to further address the issue and Exchange backup performance on pod 'use1-saas-p7' is improving.

  5. monitoring Aug 28, 2026, 05:18 PM UTC

    Backup success rates for Exchange services on pod 'use1-saas-p7' continue to improve. Additional changes have been applied to further address the Exchange backup performance issue and our R&D team is closely monitoring the results.

  6. monitoring Aug 28, 2026, 08:30 PM UTC

    Backup success rates for Exchange services on pod 'use1-saas-p7' continue to improve following the changes that have been implemented. Our R&D team continues to closely monitor system performance and backup outcomes to ensure the positive trend is maintained.

  7. monitoring Aug 31, 2026, 01:27 PM UTC

    Backup success rate metrics for Exchange services on pod 'use1-saas-p7' have returned to normal levels and remain stable. Our R&D team is continuing to monitor for any other issues.

  8. resolved Aug 31, 2026, 08:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2026 Datto EDR — Elevated Alert Volume — "Possible Shim Database Persistence via sdbinst.exe" 7d 2h

Started Aug 27, 2026, 12:39 PM UTC· resolved Sep 03, 2026, 03:28 PM UTC

  1. investigating Aug 27, 2026, 12:39 PM UTC

    We're seeing a spike in alerts for this rule caused by a recent change in Microsoft's default behavior. This is not indicative of active threats. A rule update is expected today. In the meantime, you can temporarily disable the rule under Policies → Detections → "Possible Shim Database Persistence via sdbinst.exe" to reduce noise until the fix is deployed. 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 Aug 27, 2026, 01:31 PM UTC

    Microsoft's Program Compatibility Assistant (PCA) uses sdbinst.exe to manage application compatibility databases as part of routine Windows maintenance. The August Windows update introduced known gaming compatibility issues, and Microsoft's remediation of those issues triggered sdbinst.exe activity across affected endpoints simultaneously — matching the spike pattern we observed. The affected rule has been updated as of 9:15 AM EST and pushed to all tenants. Alert volumes should return to expected levels. If you disabled the rule as a temporary measure, it is safe to re-enable it under Policies → Detections → "Possible Shim Database Persistence via sdbinst.exe".

  3. resolved Sep 03, 2026, 03:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 26, 2026 Datto Endpoint Backup for PC - Germany - Degraded Service Performance Affecting Select Infrastructure Nodes 2d 3h

Started Aug 26, 2026, 02:40 PM UTC· resolved Aug 28, 2026, 06:18 PM UTC

  1. investigating Aug 26, 2026, 02:40 PM UTC

    We are aware of a problem where Datto Endpoint Backup for PC users in the Germany region, paired to 'des1-dtc-server-30', 'des1-dtc-server-32' and 'des1-dtc-server-33' will experience degraded offsite performance, which may affect backup and recovery operations. The Kaseya Engineering Team is currently investigating the issue and working towards a resolution. 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 Aug 26, 2026, 03:58 PM UTC

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

  3. resolved Aug 28, 2026, 06:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2026 Datto SaaS Protection - M365 Backup and Restore issues affecting customers in multiple regions 5d 17h

Started Aug 25, 2026, 08:39 PM UTC· resolved Aug 31, 2026, 01:43 PM UTC

  1. identified Aug 25, 2026, 08:39 PM UTC

    We are aware of a problem where some Datto SaaS Protection customers hosted in multiple regions are experiencing backup and restore issues. Export services are not affected. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. 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 Aug 25, 2026, 09:48 PM UTC

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

  3. monitoring Aug 25, 2026, 11:57 PM UTC

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

  4. monitoring Aug 26, 2026, 12:03 PM UTC

    We are continuing to monitor for any further issues.

  5. identified Aug 26, 2026, 05:06 PM UTC

    Our R&D team is continuing to address this issue and restore full functionality to the affected customers.

  6. monitoring Aug 26, 2026, 07:44 PM UTC

    Our R&D team has implemented additional changes to restore full functionality to affected customers and they are closely monitoring for any other issues.

  7. resolved Aug 31, 2026, 01:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 25, 2026 Datto BCDR - Server3824 (Germany Region) - Degraded Node Functionality 9d

Started Aug 25, 2026, 04:09 PM UTC· resolved Sep 03, 2026, 04:44 PM UTC

  1. identified Aug 25, 2026, 04:09 PM UTC

    We are aware of a problem where Datto BCDR users paired to Server3824 will experience a service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is working towards a resolution. 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. resolved Sep 03, 2026, 04:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 24, 2026 Germany Data Center Infrastructure - Service Performance Degradation Impacting Offsite Capabilities. 1d

Started Aug 24, 2026, 03:46 PM UTC· resolved Aug 25, 2026, 04:34 PM UTC

  1. identified Aug 24, 2026, 03:46 PM UTC

    We are aware of a problem where customers in the Germany region using Datto BCDR, Datto SaaS Protection, and Datto Endpoint Backup are currently experiencing service degradation affecting offsite performance and related operations. The Kaseya Engineering Team has identified the issue and is working towards a resolution. 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 Aug 24, 2026, 05:15 PM UTC

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

  3. monitoring Aug 25, 2026, 04:05 PM UTC

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

  4. resolved Aug 25, 2026, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2026 Datto SaaS Protection - Backup and Restore issues affecting customers in multiple regions 20h 27m

Started Aug 21, 2026, 06:22 PM UTC· resolved Aug 22, 2026, 02:50 PM UTC

  1. identified Aug 21, 2026, 06:22 PM UTC

    We are aware of a problem where some Datto SaaS Protection customers hosted in multiple regions are experiencing backup and restore failures. Export services are not affected. The Kaseya Engineering Team has identified the issue and are actively working to resolve it. 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 Aug 21, 2026, 07:54 PM UTC

    Our R&D team is actively preparing to deploy changes to address the issue.

  3. identified Aug 21, 2026, 08:46 PM UTC

    Our R&D team has begun deploying changes to the affected regions to address the issue.

  4. monitoring Aug 22, 2026, 12:53 AM UTC

    Backup success rates have returned to normal levels and restoration functions have resumed. Our R&D team is continuing to monitor.

  5. resolved Aug 22, 2026, 02:50 PM UTC

    Changes made by the Kaseya R&D team have proven successful and full functionality has been restored. The issue is now considered resolved.

Read the full incident report →

Minor August 21, 2026 DattoRMM - Vidal - Activity Log pages are slow to load 7d 1h

Started Aug 21, 2026, 05:17 PM UTC· resolved Aug 28, 2026, 06:43 PM UTC

  1. monitoring Aug 21, 2026, 05:17 PM UTC

    We are aware of a problem where the Activity Logs on our Vidal Platform are slow to load after our 15.1 release. The Kaseya Engineering Team has applied a fix and is currently monitoring this closely. 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. resolved Aug 28, 2026, 06:43 PM UTC

    The issue affecting Activity Log performance on the Vidal Platform following the 15.1 release has been resolved. The Kaseya Engineering Team implemented a fix and has confirmed that Activity Logs are loading as expected after monitoring the platform to ensure ongoing stability and performance. 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/

Read the full incident report →

Major August 19, 2026 SaaS Protection - isw1-bfyii-1131 - Backup Performance Degradation 8h 42m

Started Aug 19, 2026, 11:25 AM UTC· resolved Aug 19, 2026, 08:08 PM UTC

  1. identified Aug 19, 2026, 11:25 AM UTC

    We are aware of a problem where backups are not successful for customers hosted on isw1-bfyii-1131 The Kaseya Engineering Team is currently responding to the issue, and we will provide updates on this thread as information becomes available. 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 Aug 19, 2026, 12:29 PM UTC

    The Engineering team has performed the necessary steps to resolve the issue, and are observing that related errors have stopped and backup metrics are improving as the service is recovering.

  3. monitoring Aug 19, 2026, 01:00 PM UTC

    Backups continue to process normally for customers hosted on node 'isw1-bfyii-1131' and our R&D team is monitoring for any other issues.

  4. resolved Aug 19, 2026, 08:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 18, 2026 Datto RMM - Vidal - Post 15.1.0 Release - Activity Log Issues 1d 22h

Started Aug 18, 2026, 02:15 PM UTC· resolved Aug 20, 2026, 12:38 PM UTC

  1. investigating Aug 18, 2026, 02:15 PM UTC

    We are aware of a problem on Datto RMM's Vidal Platform where Jobs are not running and the Activity log can be slow to load. The Kaseya Engineering Team are 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. investigating Aug 18, 2026, 02:52 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 18, 2026, 02:58 PM UTC

    A fix has been implemented for Activity Logs and they should be loading as expected. A fix has also been implemented for Jobs not running, but delays are still expected as the platform works through all queued jobs. We will continue to monitor this queue and resolve this status page once it has cleared.

  4. monitoring Aug 18, 2026, 03:48 PM UTC

    The Job queue has been cleared and Activity Logs continue to load as expected. We are continuing to monitor for any further issues.

  5. identified Aug 18, 2026, 05:13 PM UTC

    We have identified an issue with the Activity Log failing to load. The Kaseya R&D team are working on a fix for the issue.

  6. identified Aug 18, 2026, 07:48 PM UTC

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

  7. monitoring Aug 19, 2026, 07:49 AM UTC

    A fix has been implemented for the Activity Log on the Vidal platform. The service has recovered and we are monitoring the results.

  8. identified Aug 19, 2026, 12:46 PM UTC

    The Engineering team is currently investigating and resolving issues flagged by internal alerting that led to the Activity Log loading and Job execution issues resurfacing. Thank you for your patience!

  9. identified Aug 19, 2026, 01:01 PM UTC

    Scheduled and Quick Job functionality is restored, and the Engineering team is continuing to work on resolving the problem causing issues with the Activity Log loading in accounts.

  10. monitoring Aug 19, 2026, 01:53 PM UTC

    A fix has been implemented for the Jobs and Activity Log on the Vidal platform and we are monitoring the results.

  11. monitoring Aug 19, 2026, 09:01 PM UTC

    At this time, jobs and activity logs remain stable, and no further issues have been observed however we will continue to monitor the environment overnight.

  12. resolved Aug 20, 2026, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 18, 2026 [INKY] - Email processing by INKY is being delayed 10h 27m

Started Aug 18, 2026, 03:46 AM UTC· resolved Aug 18, 2026, 02:13 PM UTC

  1. investigating Aug 18, 2026, 03:46 AM UTC

    We have observed that the email processing by INKY is being delayed. We are aware of the issue and is being investigated

  2. investigating Aug 18, 2026, 07:30 AM UTC

    We are continuing to investigate the issue.

  3. monitoring Aug 18, 2026, 09:42 AM UTC

    Email delays are no longer being recorded and reported and we are monitoring the health of the service.

  4. resolved Aug 18, 2026, 02:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 18, 2026 [Kaseya Store] - [Kaseya Store] - [Kaseya Store inaccessible] 2h 32m Kaseya Store

Started Aug 18, 2026, 01:53 AM UTC· resolved Aug 18, 2026, 04:26 AM UTC

  1. investigating Aug 18, 2026, 01:53 AM UTC

    We are aware of a problem where the Kaseya Store is not accessible. The Kaseya Engineering Team is currently 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. investigating Aug 18, 2026, 01:54 AM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 18, 2026, 04:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 13, 2026 Datto RMM - Merlot (EMEA) - Job Service Failures 1d 10h

Started Aug 13, 2026, 09:24 AM UTC· resolved Aug 14, 2026, 07:32 PM UTC

  1. investigating Aug 13, 2026, 09:24 AM UTC

    We are aware of an issue affecting the Merlot platform where Quick Jobs and Scheduled Jobs are failing to run. The Kaseya Engineering Team is actively 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 Aug 13, 2026, 09:52 AM UTC

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

  3. resolved Aug 14, 2026, 07:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2026 Datto Workplace - Degraded Performance in US Regions 1d 14h

Started Aug 12, 2026, 09:56 PM UTC· resolved Aug 14, 2026, 12:14 PM UTC

  1. identified Aug 12, 2026, 09:56 PM UTC

    We are investigating reports of slow loading times affecting Workplace, the web portal, and agent connectivity for partners hosted in our US regions. A small number of users may also see intermittent connection errors when opening a project or folder. Our engineering 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/

  2. monitoring Aug 13, 2026, 08:27 AM UTC

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

  3. resolved Aug 14, 2026, 12:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 12, 2026 Inky Dashboard partial outage 10h 6m

Started Aug 12, 2026, 01:48 AM UTC· resolved Aug 12, 2026, 11:55 AM UTC

  1. identified Aug 12, 2026, 01:48 AM UTC

    A database issue is causing a partial outage on the US Inky dashboard. Email processing is unaffected but settings will not be able to be changed while we correct the issue. The issue has been identified and a fix is being implemented.

  2. monitoring Aug 12, 2026, 02:24 AM UTC

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

  3. resolved Aug 12, 2026, 11:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 11, 2026 DattoRMM - Vidal - ConnectWise Integration is inaccessible 1d 1h

Started Aug 11, 2026, 05:35 PM UTC· resolved Aug 12, 2026, 07:33 PM UTC

  1. investigating Aug 11, 2026, 05:35 PM UTC

    We are aware of a problem where the ConnectWise integration is returning an error on our Vidal platform. Users may see errors while viewing the integration page and ticketing can be affected. The Kaseya Engineering Team is currently Investigating this 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 Aug 11, 2026, 06:30 PM UTC

    We are no longer seeing errors related to the ConnectWise Integration. We are continuing to monitor the services at this time.

  3. resolved Aug 12, 2026, 07:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 8, 2026 Datto SaaS protection - Backups currently paused des1-bfyii-1127 1d 20h

Started Aug 08, 2026, 05:15 PM UTC· resolved Aug 10, 2026, 01:23 PM UTC

  1. identified Aug 08, 2026, 05:15 PM UTC

    We are aware of a problem where SaaS Protection customers hosted on node ‘des1-bfyii-1127' are experiencing degraded backup performance for some services. The Kaseya R&D Team has identified the issue and are working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Aug 08, 2026, 08:55 PM UTC

    The Kaseya R&D Team has implemented a fix to alleviate backups for customers hosted on the node des1-bfyii-1127. Backups success rates will be monitored for improvement

  3. monitoring Aug 08, 2026, 09:04 PM UTC

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

  4. monitoring Aug 09, 2026, 01:38 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Aug 10, 2026, 01:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 7, 2026 Autotask PSA - Sydney Data Center Web Center and API - Inaccessible 49m

Started Aug 07, 2026, 10:59 PM UTC· resolved Aug 07, 2026, 11:48 PM UTC

  1. investigating Aug 07, 2026, 10:59 PM UTC

    We are aware of a problem where some customers are unable to access Autotask within our Sydney Data Center 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. resolved Aug 07, 2026, 11:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 6, 2026 Datto BCDR - Archived Agents May Generate Sync Completion Alerts for Points Marked for Offsite. 18d

Started Aug 06, 2026, 05:51 PM UTC· resolved Aug 24, 2026, 06:02 PM UTC

  1. investigating Aug 06, 2026, 05:51 PM UTC

    A known issue exists where archived agents may continue to generate sync completion alerts when associated local points are marked as offsite, despite the agents being in an archived state. While a long-term solution is scheduled for implementation in a future release, assets affected before the fix is deployed will need to be corrected through manual intervention. Customers seeking to implement this mitigation should submit a request through the Kaseya Help Desk Portal at https://helpdesk.kaseya.com/hc/en-gb. Our Support team will assist with the required remediation activities. Thank you for your understanding and continued support.

  2. resolved Aug 24, 2026, 06:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 6, 2026 ConnectBooster - Unable to log in via Kaseya One 7h 13m

Started Aug 06, 2026, 02:15 PM UTC· resolved Aug 06, 2026, 09:28 PM UTC

  1. investigating Aug 06, 2026, 02:15 PM UTC

    We are aware of a problem where Partners have reported the inability to log into the portal via Kaseya One The Kaseya R&D Team is investigating the issue. 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 Aug 06, 2026, 04:01 PM UTC

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

  3. monitoring Aug 06, 2026, 05:19 PM UTC

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

  4. monitoring Aug 06, 2026, 05:19 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Aug 06, 2026, 09:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 6, 2026 KaseyaOne & Kaseya Store - Issues with payment provider 3h 14m KaseyaOne, Kaseya Store

Started Aug 06, 2026, 01:41 PM UTC· resolved Aug 06, 2026, 04:56 PM UTC

  1. identified Aug 06, 2026, 01:41 PM UTC

    Our payment provider for KaseyaOne and Kaseya Store has identified intermittent connectivity issues with our fraud prevention provider that might cause increased authentication declines. During this time, users may experience intermittent issues related to payment processing in KaseyaOne and Kaseya Store. Core platform functionality outside of payment services will remain unaffected. We recommend avoiding payment-related actions during this maintenance window where possible. We will monitor the situation and provide updates if necessary.

  2. resolved Aug 06, 2026, 04:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2026 Datto SaaS Protection - Backup performance degradation for M365 services affecting multiple pods/regions 18h 8m

Started Aug 05, 2026, 07:40 PM UTC· resolved Aug 06, 2026, 01:49 PM UTC

  1. identified Aug 05, 2026, 07:40 PM UTC

    Datto SaaS Protection is currently experiencing degraded backup performance and missed backups for some Microsoft 365 services across multiple regions. The issue has been linked to increased API activity and application-level throttling associated with the ongoing transition from Exchange Web Services (EWS) to Microsoft Graph APIs. Affected regions: US (USE/USW) Australia (AUE) Canada (CAE) Germany (DES) UK (GBE) Singapore (SG) Our R&D teams have identified the primary contributing factors and are actively working to restore full service functionality. Multiple mitigation measures have been implemented, including application performance optimizations, infrastructure and capacity improvements, deployment of configuration changes across affected SaaS Protection pods, and a temporary reduction in backup cadence from 3x daily backups to 2x daily backups to help reduce API demand and improve backup success rates during the transition. These actions have resulted in measurable improvement, with backup success rates increasing across all affected regions over the past 24 hours. While performance continues to stabilize, some customers may still experience backup delays or missed backups as remediation efforts continue. Additional software enhancements are scheduled for deployment this week to further reduce API throttling, improve backup performance, and accelerate recovery. Customer data protection remains the highest priority, and our R&D teams continue to closely monitor the environment while implementing further improvements. Updates will continue to be provided through the Kaseya Status Page as progress is made toward full service restoration.

Read the full incident report →

Major August 3, 2026 Datto SaaS Protection - Backup performance degradation for some M365 services on Multiple Pods 2d 2h

Started Aug 03, 2026, 09:12 AM UTC· resolved Aug 05, 2026, 12:06 PM UTC

  1. identified Aug 03, 2026, 09:12 AM UTC

    We are aware of an issue where some Datto SaaS Protection customers may experience degraded backup performance for Exchange and Teams services. The Kaseya R&D team has identified the issue and is actively working to restore normal backup performance as quickly as possible. For the latest updates, please subscribe to the Kaseya Status Page at https://status.kaseya.com/.

  2. identified Aug 03, 2026, 12:31 PM UTC

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

  3. monitoring Aug 03, 2026, 01:30 PM UTC

    Our R&D team has released a fix to address the backup performance degradation for some M365 services affecting customers hosted in multiple regions and they are closely monitoring.

  4. identified Aug 03, 2026, 02:46 PM UTC

    Our R&D team is continuing to address the backup performance issues affecting some M365 services on multiple SaaS Protection pods. In the meantime, they are preparing to temporarily reduce backup cadence on affected pods from 3x backups per day to 2x backups per day to help stabilize backup success rates in all affected regions.

  5. identified Aug 03, 2026, 03:33 PM UTC

    Our R&D team continues to address backup performance issues affecting some Microsoft 365 services across multiple SaaS Protection pods following the transition from EWS to Microsoft Graph APIs. To help stabilize backup success rates and reduce API throttling during this migration, backup cadence on affected pods will be temporarily reduced from 3x backups per day to 2x backups per day.

  6. identified Aug 03, 2026, 05:34 PM UTC

    Our R&D team has begun deployment of the changes to reduce backup cadence on affected SaaS Protection pods across all regions to 2x backups per day to help stabilize backup success rates further. This change is expected to complete deployment by 20:00 ET (00:00 UTC). Our R&D team is continuing to closely monitor backup performance as these additional changes are implemented.

  7. identified Aug 03, 2026, 08:05 PM UTC

    Our R&D team is continuing to deploy the configuration changes to adjust backup frequency from 3x backups per day to 2x backups per day on SaaS Protection pods in all regions and we are continuing to closely monitor backup success rate metrics.

  8. identified Aug 03, 2026, 09:52 PM UTC

    Our R&D team has completed deployment of the configuration changes to SaaS Protection pods in all regions. Daily backup cadence is now temporarily set to 2x backups per day across the fleet to reduce API throttling and help stabilize backup success rate metrics during the transition from EWS to Microsoft Graph APIs. Our R&D team is closely monitoring the effects of the changes and expect backup success rates to begin stabilizing over the next several hours.

  9. identified Aug 04, 2026, 02:29 PM UTC

    After the changes made yesterday, we have observed some improvement to backup success rates however backups are currently still degraded for some M365 services across multiple regions due to API throttling related to the transition from EWS to Microsoft Graph APIs. Our R&D team is continuing to develop additional improvements to address the backup performance issues.

  10. identified Aug 04, 2026, 05:26 PM UTC

    Our R&D team is currently implementing configuration changes in multiple regions to further mitigate the degraded backup performance still affecting some customers. We will be closely monitoring the results of these changes as we continue to develop additional improvements to accelerate recovery for affected customers.

  11. identified Aug 04, 2026, 08:09 PM UTC

    The latest changes have been deployed to SaaS Protection pods in multiple regions still experiencing backup performance issues. Our R&D team is continuing to monitor as backup success rate metrics improve across the fleet.

Read the full incident report →

Major July 31, 2026 Datto Endpoint Backup for PC - Service Disruption for Customers Hosted on Cloud Siris 215069 5d

Started Jul 31, 2026, 05:44 PM UTC· resolved Aug 05, 2026, 06:06 PM UTC

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

  2. monitoring Aug 05, 2026, 05:43 PM UTC

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

  3. resolved Aug 05, 2026, 06:06 PM UTC

    This incident has been resolved.

Read the full incident report →