Datto Outage History

Datto degraded · 7 active incidents View live status →

Datto had 82 outages in the last 2 years totaling 1166h 1m of downtime — averaging 3.4 incidents per month.

There were 82 Datto outages since January 27, 2026 totaling 1166h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.datto.com

Major June 12, 2026

Endpoint Backup v2 - A Subset of Endpoint Backup v2 Assets May Experience Backup Failures

Detected by Pingoru
Jun 12, 2026, 07:57 PM UTC
Resolved
Jun 15, 2026, 05:06 PM UTC
Duration
2d 21h
Affected: Backup
Timeline · 3 updates
  1. identified Jun 12, 2026, 07:57 PM UTC

    We are aware of a problem where a subset of Endpoint Backup v2 assets can experience a backup failure due to error "system.ntfs_reparse_data: invalid argument". The Kaseya R&D Team has identified the issue and is working towards a resolution. In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Jun 15, 2026, 01:29 PM UTC

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

  3. resolved Jun 15, 2026, 05:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 10, 2026

Endpoint Backup v2 – Assets Reporting Offline; Backups and Restores Unavailable

Detected by Pingoru
Jun 10, 2026, 09:10 PM UTC
Resolved
Jun 11, 2026, 11:16 PM UTC
Duration
1d 2h
Affected: BackupAgent RegistrationRestore
Timeline · 6 updates
  1. investigating Jun 10, 2026, 09:10 PM UTC

    We are investigating an issue causing Endpoint Backup v2 assets to appear offline in UniView. While this issue is ongoing, scheduled backups are not running, recovery points may show as unavailable, and backup, restore, and BMR operations are failing. All regions are affected. There is no workaround available at this time. The Kaseya R&D team is engaged and actively investigating, and we will provide updates as more information becomes available. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jun 11, 2026, 08:32 AM UTC

    The R&D team identified the issue, and developed a fix. The change is currently being tested before proceeding with the rollout to production.

  3. identified Jun 11, 2026, 10:03 AM UTC

    The hotfixed agent version is being rolled out to production following successful testing and validation that the changes implemented by the R&D team resolves the issue. We are deploying the upgrade in batches to mitigate any risks to the health of the infrastructure.

  4. identified Jun 11, 2026, 11:32 AM UTC

    We are continuing the rollout of the fixed agent version to production.

  5. identified Jun 11, 2026, 04:43 PM UTC

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

  6. resolved Jun 11, 2026, 11:16 PM UTC

    This incident has been resolved. The fixed agent version has been rolled out to production, and Endpoint Backup v2 services have been restored. Assets are reporting correctly in UniView, and backup, restore, BMR, and agent registration operations are functioning as expected. Scheduled backups have resumed and will run at their next scheduled time. We will continue to monitor the environment to ensure ongoing stability. If you continue to experience any issues, please contact Kaseya Support. We sincerely apologize for the disruption and thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Minor June 10, 2026

Datto BCDR - Server5673 (Germany Region) - Degraded Node Functionality

Detected by Pingoru
Jun 10, 2026, 03:44 PM UTC
Resolved
Jun 10, 2026, 08:28 PM UTC
Duration
4h 44m
Affected: Off-Site SynchronizationOff-Site Recovery
Timeline · 3 updates
  1. identified Jun 10, 2026, 03:44 PM UTC

    We are aware of a problem where BCDR users paired to Server5673 can experience degraded offsite capabilities. The Kaseya R&D Team has identified the issue and is working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring Jun 10, 2026, 06:59 PM UTC

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

  3. resolved Jun 10, 2026, 08:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2026

VSA9 - Partial Service Disruption - US-VSA146

Detected by Pingoru
Jun 10, 2026, 12:43 AM UTC
Resolved
Jun 10, 2026, 03:45 AM UTC
Duration
3h 2m
Affected: US - VSA146
Timeline · 3 updates
  1. investigating Jun 10, 2026, 12:43 AM UTC

    We are experiencing a issues with outbound email on US-VSA146. Our team is working to restore functionality on the instance at this time. We apologize for any inconvenience. - Kaseya Cloud Operations Team

  2. monitoring Jun 10, 2026, 02:04 AM UTC

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

  3. resolved Jun 10, 2026, 03:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 5, 2026

Datto SaaS Protection - New customer onboarding is unavailable

Detected by Pingoru
Jun 05, 2026, 02:38 PM UTC
Resolved
Jun 05, 2026, 03:58 PM UTC
Duration
1h 19m
Affected: SaaS Protection Client Onboarding
Timeline · 4 updates
  1. identified Jun 05, 2026, 02:38 PM UTC

    We are aware of a problem where Datto SaaS Protection Partners are currently unable to onboard new customers within the Partner Portal and are receiving an error. The Kaseya R&D Team has identified the issue and they are actively working on a fix. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jun 05, 2026, 03:19 PM UTC

    A fix for this issue has been tested and is being prepared for release.

  3. monitoring Jun 05, 2026, 03:47 PM UTC

    A fix for the issue has been deployed and the SaaS Protection onboarding service has been restored.

  4. resolved Jun 05, 2026, 03:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

Autotask PSA - LR, UKLR, UK01, UK02, UK03, EU1, DE1 - Intermittent Error Messages

Detected by Pingoru
Jun 04, 2026, 07:55 AM UTC
Resolved
Jun 04, 2026, 02:00 PM UTC
Duration
6h 5m
Affected: Limited ReleaseUK Limited Release (United Kingdom)UK (United Kingdom)UK 2 (United Kingdom)UK03 (United Kingdom)EU1 (English Europe and Asia)German (Deutsch)
Timeline · 5 updates
  1. investigating Jun 04, 2026, 07:55 AM UTC

    We are aware of a problem where error messages are being experienced when navigating the Autotask PSA UI. The Kaseya R&D Team is actively investigating this behaviour. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jun 04, 2026, 10:04 AM UTC

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

  3. identified Jun 04, 2026, 10:35 AM UTC

    Thank you for your patience while we continue to work on a fix for this issue. A workaround to prevent the error messages has been confirmed. If you navigate within Autotask to the top right-hand corner: My Account > My Settings > Reset Settings Please note that when applying this change, many of your current settings will be reset. This includes certain column choosers, notification template defaults, search grid default criteria, and default checkbox/radio button selections.

  4. monitoring Jun 04, 2026, 01:12 PM UTC

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

  5. resolved Jun 04, 2026, 02:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 3, 2026

Datto SaaS Protection - Onboarding new customers and Status page within the Partner Portal are unavailable

Detected by Pingoru
Jun 03, 2026, 11:25 AM UTC
Resolved
Jun 03, 2026, 02:32 PM UTC
Duration
3h 7m
Affected: SaaS Protection Console LoginSaaS Protection Client Onboarding
Timeline · 4 updates
  1. investigating Jun 03, 2026, 11:25 AM UTC

    We are aware of a problem where customers are unable to onboard new tenants. The status page within the Datto Partner Portal is also unavailable and returning a 500 error. The Kaseya R&D Team is actively working to address the problem. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified Jun 03, 2026, 12:42 PM UTC

    Our R&D team has identified the issue and are actively working to deploy a fix.

  3. monitoring Jun 03, 2026, 01:51 PM UTC

    A fix to restore access to the SaaS Protection Status Page within the Partner Portal and Onboarding functionality has been implemented. Our R&D team is actively monitoring for any other issues.

  4. resolved Jun 03, 2026, 02:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 29, 2026

Datto SaaS Protection - Service disruption for customers hosted on node 'use1-bfyii-126'

Detected by Pingoru
May 29, 2026, 06:14 PM UTC
Resolved
Jun 01, 2026, 12:25 PM UTC
Duration
2d 18h
Affected: SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Restores/Exports
Timeline · 3 updates
  1. investigating May 29, 2026, 06:14 PM UTC

    We are aware of a problem where customers hosted on node 'use1-bfyii-126' are experiencing a disruption to their SaaS Protection services. The Kaseya R&D Team is actively investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 29, 2026, 06:55 PM UTC

    Our R&D team has implemented a fix to restore services on node 'use1-bfyii-126' and they are actively monitoring.

  3. resolved Jun 01, 2026, 12:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 26, 2026

DattoRMM - Vidal - Datto Continuity devices incorrectly reporting offline

Detected by Pingoru
May 26, 2026, 05:36 PM UTC
Resolved
May 27, 2026, 05:33 PM UTC
Duration
23h 57m
Affected: Vidal (US East)
Timeline · 4 updates
  1. identified May 26, 2026, 05:36 PM UTC

    We are aware of a problem where online BCDR devices are reporting as offline through the Datto Continuity integration on our Vidal platform. The Kaseya R&D Team have identified the issue and are working on a fix Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified May 27, 2026, 10:33 AM UTC

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

  3. monitoring May 27, 2026, 03:34 PM UTC

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

  4. resolved May 27, 2026, 05:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 24, 2026

Datto SaaS Protection - Service disruption for customers hosted on pod 'gbe2-saas-p1'

Detected by Pingoru
May 24, 2026, 05:52 PM UTC
Resolved
May 28, 2026, 06:15 PM UTC
Duration
4d
Affected: SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Restores/Exports
Timeline · 6 updates
  1. investigating May 24, 2026, 05:52 PM UTC

    We are aware of a problem causing a disruption to services for Datto SaaS Protection customers hosted on pod 'gbe2-saas-p1'. Our R&D team has identified the issue and is actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. identified May 26, 2026, 01:16 PM UTC

    Our R&D team is continuing to address the current disruption to SaaS Protection services affecting customers hosted on pod 'gbe2-saas-p1'.

  3. monitoring May 26, 2026, 03:43 PM UTC

    Our R&D team has implemented changes to address the issue affecting customers hosted on pod 'gbe2-saas-p1' and they are monitoring the results.

  4. monitoring May 26, 2026, 08:11 PM UTC

    Backup success rate metrics on pod 'gbe2-saas-p1' are returning to normal. Our R&D team is continuing to monitor for any other issues.

  5. monitoring May 27, 2026, 03:32 PM UTC

    Backup success rate metrics on pod 'gbe2-saas-p1' have returned to normal and our R&D team is continuing to monitor for any other issues.

  6. resolved May 28, 2026, 06:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 23, 2026

[Networking] - [DSE] - [DSE Safe Check Preventing users Access]

Detected by Pingoru
May 23, 2026, 06:51 PM UTC
Resolved
May 23, 2026, 08:04 PM UTC
Duration
1h 13m
Affected: Secure Edge
Timeline · 3 updates
  1. investigating May 23, 2026, 06:51 PM UTC

    We are aware of a problem where DSE subscribers are being rejected from SafeCheck on May 23, 2026. This seems to be a trending outage with multiple partners due to an API issue. The Kaseya R&D Team are currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 23, 2026, 07:41 PM UTC

    The Datto Networking R&D team has implemented a fix that is believed to have resolved the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  3. resolved May 23, 2026, 08:04 PM UTC

    Original reporters have confirmed the issue has been resolved after Engineering fix

Read the full incident report →

Major May 22, 2026

Issues with payment provider – KaseyaOne & Kaseya Store

Detected by Pingoru
May 22, 2026, 09:37 AM UTC
Resolved
May 22, 2026, 11:30 AM UTC
Duration
1h 53m
Affected: KaseyaOneKaseya Store
Timeline · 3 updates
  1. investigating May 22, 2026, 09:37 AM UTC

    Our payment provider has flagged an ongoing issue that could potentially affect transaction processing. We are closely monitoring this and will post an update as soon as the situation is resolved or if any impact is detected. Thank you for your patience.

  2. identified May 22, 2026, 10:23 AM UTC

    Vendor updated that they are currently experiencing American Express transaction failures due to maintenance activity within the American Express network, which extended beyond its planned duration. Vendor is actively working with the American Express team to minimize the impact and prevent additional processing failures while the maintenance is underway. Where possible, we recommend using alternative card brands for new transactions. Merchants may also retry failed American Express transactions after maintenance is complete. We will continue to monitor the situation closely and provide another update as soon as the issue is fully resolved.

  3. resolved May 22, 2026, 11:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 21, 2026

[Datto Workplace & Datto File Protection] Users are unable to login

Detected by Pingoru
May 21, 2026, 08:50 AM UTC
Resolved
May 26, 2026, 01:24 PM UTC
Duration
5d 4h
Affected: US8US1US9US6US17US15
Timeline · 3 updates
  1. investigating May 21, 2026, 08:50 AM UTC

    Our R&D team is currently investigating the issue with the Datto Workplace and Datto File Protection portals in the US region being inaccessible at present. The top level URLs being currently inaccessible, customers in other regions can only access the login page through the subdomains. Please subscribe to this post to receive updates as our efforts to resolve this issue progresses. We apologise for the inconvenience caused!

  2. monitoring May 21, 2026, 09:05 AM UTC

    The R&D team has successfully mitigated the issue and the previously affected pages are accessible again. We continue to monitor the health of the service while reviewing avenues to minimize the risk of the issue reoccurring.

  3. resolved May 26, 2026, 01:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Datto Workplace / Datto File Protection - US Cells - U.S. Based Agents Are Experiencing Connectivity failures, and Portal Access is Intermittently Unavailable

Detected by Pingoru
May 20, 2026, 03:53 PM UTC
Resolved
May 20, 2026, 05:57 PM UTC
Duration
2h 4m
Affected: US8US1US9US6US17US15
Timeline · 3 updates
  1. investigating May 20, 2026, 03:53 PM UTC

    We are aware of a problem where U.S. based Datto Workplace and Datto File Protection agents can experience intermittent connectivity failures and degraded access to the Portal. The Kaseya R&D Team is currently investigating the issue and working towards a resolution. Please note: File access and file downloads can be obtained through the File Explorer option. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

  2. monitoring May 20, 2026, 05:43 PM UTC

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

  3. resolved May 20, 2026, 05:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 18, 2026

Datto SaaS Protection - Backup performance degradation for SharePoint/Teams services on pod 'des1-saas-p0'

Detected by Pingoru
May 18, 2026, 08:15 PM UTC
Resolved
May 21, 2026, 01:22 PM UTC
Duration
2d 17h
Affected: SaaS Protection Backups
Timeline · 4 updates
  1. identified May 18, 2026, 08:15 PM UTC

    We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'des1-saas-p0' may experience degraded SharePoint/Teams backup performance. 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. monitoring May 18, 2026, 10:25 PM UTC

    Our R&D team has implemented changes to address the SharePoint/Teams backup performance degradation affecting some customers on pod 'des1-saas-p0' and they are monitoring the results.

  3. monitoring May 19, 2026, 12:32 PM UTC

    Backup success rate metrics for SharePoint/Teams services on pod 'des1-saas-p0' have returned to normal. Our R&D team is continuing to monitor.

  4. resolved May 21, 2026, 01:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 18, 2026

Datto BCDR - Server3921 (US-East) - Degraded Node Functionality

Detected by Pingoru
May 18, 2026, 03:15 PM UTC
Resolved
May 19, 2026, 01:01 PM UTC
Duration
21h 45m
Affected: Off-Site SynchronizationOff-Site Recovery
Timeline · 3 updates
  1. identified May 18, 2026, 03:15 PM UTC

    We are aware of a problem where BCDR users paired to Server3921 in the US-East region are experiencing degraded performance in offsite operations. 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 May 18, 2026, 07:46 PM UTC

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

  3. resolved May 19, 2026, 01:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 15, 2026

Datto Workplace - AU5 - Some files are unable to be accessed through local agents and the Workplace Online

Detected by Pingoru
May 15, 2026, 09:36 AM UTC
Resolved
May 18, 2026, 11:28 AM UTC
Duration
3d 1h
Affected: AU5
Timeline · 3 updates
  1. investigating May 15, 2026, 09:36 AM UTC

    The R&D Team is currently investigating the issue where users receive an error through the local agent or in Workplace Online when attempting to access certain files on the AU5 cell.

  2. monitoring May 15, 2026, 02:08 PM UTC

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

  3. resolved May 18, 2026, 11:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 11, 2026

Datto SaaS Protection - Service disruption for customers hosted on pod 'usw3-saas-p0'

Detected by Pingoru
May 11, 2026, 05:39 PM UTC
Resolved
May 13, 2026, 02:14 PM UTC
Duration
1d 20h
Affected: SaaS Protection BackupsSaaS Protection Restores/Exports
Timeline · 6 updates
  1. investigating May 11, 2026, 05:39 PM UTC

    We are aware of a problem where customers hosted on pod 'usw3-saas-p0' are experiencing a disruption to Backup and Recovery services for Datto SaaS Protection. 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 May 11, 2026, 06:50 PM UTC

    Our R&D team has implemented a fix to resolve the Backup and Recovery affecting customers on pod 'usw3-saas-p0' and are actively monitoring for any other issues.

  3. identified May 11, 2026, 10:11 PM UTC

    Our R&D team has identified another issue affecting Backup and Recovery services for customers hosted on pod 'usw3-saas-p0' and are actively working to address it.

  4. monitoring May 11, 2026, 10:46 PM UTC

    Our R&D team has resolved the issue and Backup and Recovery services are functioning normally again for customers on pod 'usw3-saas-p0'. We are continuing to monitor.

  5. monitoring May 12, 2026, 08:30 PM UTC

    Backup success rates on pod 'usw3-saas-p0' remain stable at normal levels. Our R&D team is continuing to monitor.

  6. resolved May 13, 2026, 02:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 11, 2026

SaaS Alerts Microsoft Manage Service Interruption

Detected by Pingoru
May 11, 2026, 05:42 AM UTC
Resolved
May 13, 2026, 01:51 PM UTC
Duration
2d 8h
Affected: Manage
Timeline · 7 updates
  1. investigating May 11, 2026, 05:42 AM UTC

    We are aware of the ongoing service interruption issue in SaaS Alerts Microsoft Manage Integration. Our team is investigating the issue and working towards a resolution.

  2. investigating May 11, 2026, 07:01 AM UTC

    Kaseya R&D team is continuing to investigate the issue and working towards a resolution.

  3. investigating May 11, 2026, 10:30 AM UTC

    Kaseya R&D team is continuing to investigate the issue and working towards a resolution.

  4. investigating May 11, 2026, 02:39 PM UTC

    We are continuing to investigate this issue.

  5. identified May 11, 2026, 03:12 PM UTC

    The issue has been identified. One of the endpoints from Microsoft is responding properly sometimes and others is throwing an error. We have implemented retry functionality for that endpoint and are clearing all errors. We will continue to work on this until all impacted Microsoft connections are stable.

  6. monitoring May 11, 2026, 06:09 PM UTC

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

  7. resolved May 13, 2026, 01:51 PM UTC

    We have observed that the Microsoft endpoint is performing as expected. This incident is now closed.

Read the full incident report →

Major May 5, 2026

Datto Workplace AU5 - Agents are unable to connect and sync data; files cannot be created and/or saved in Workplace Online

Detected by Pingoru
May 05, 2026, 08:27 AM UTC
Resolved
May 06, 2026, 12:45 PM UTC
Duration
1d 4h
Affected: AU5
Timeline · 4 updates
  1. investigating May 05, 2026, 08:27 AM UTC

    We are currently investigating an issue impacting partners on AU5 cell, where connections and data syncs are failing. Affected partners may see server errors in applications, no files appearing on the VFS agent, or connection failures on the V8 agent. At this time, other regions are not affected. Subscribe to the Kaseya Status Page for up to date information at https://status.kaseya.com/

  2. investigating May 05, 2026, 11:14 AM UTC

    The R&D and Infrastructure teams are continuing to investigate the cause of the issue.

  3. monitoring May 05, 2026, 01:50 PM UTC

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

  4. resolved May 06, 2026, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Datto Networking - Intermittent Check‑In Failures Observed on Datto Networking D200 Devices

Detected by Pingoru
May 04, 2026, 05:24 PM UTC
Resolved
May 05, 2026, 07:34 PM UTC
Duration
1d 2h
Affected: Routers
Timeline · 3 updates
  1. investigating May 04, 2026, 05:24 PM UTC

    We are aware of a problem where Datto Networking D200 devices can fail to successfully check-in. 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/

  2. monitoring May 05, 2026, 01:07 PM UTC

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

  3. resolved May 05, 2026, 07:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 4, 2026

Datto SaaS Protection - Service disruption for customers hosted on node 'Gbe2-saas-p0-app-2'

Detected by Pingoru
May 04, 2026, 11:52 AM UTC
Resolved
May 05, 2026, 12:19 PM UTC
Duration
1d
Affected: SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Client OnboardingSaaS Protection Report DeliverySaaS Protection Restores/Exports
Timeline · 3 updates
  1. investigating May 04, 2026, 11:52 AM UTC

    We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection services. Backups are still operational, but the platform is unable to be accessed. The Kaseya R&D Team is investigating 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. monitoring May 04, 2026, 01:07 PM UTC

    The Kaseya R&D team has implemented changes to help address the issue and are monitoring the results closely.

  3. resolved May 05, 2026, 12:19 PM UTC

    This incident has been resolved.

Read the full incident report →