Kaseya incident

Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-327'

Major Resolved View vendor source →

Kaseya experienced a major incident on April 24, 2026, lasting 26d 17h. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2026, 07:30 PM UTC
Resolved
May 21, 2026, 01:23 PM UTC
Duration
26d 17h
Detected by Pingoru
Apr 24, 2026, 07:30 PM UTC

Update timeline

  1. investigating Apr 24, 2026, 01:20 PM UTC

    We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection 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 Apr 24, 2026, 02:15 PM UTC

    Our R&D team is continuing to address this issue.

  3. identified Apr 24, 2026, 07:30 PM UTC

    Our R&D team is performing maintenance on node 'gbe2-bfyii-327' over the weekend to repair a hardware issue that was identified. There is still currently no ETA on when services will be fully restored. We will provide more updates from the team as they become available.

  4. identified Apr 27, 2026, 12:45 PM UTC

    Maintenance on node 'gbe2-bfyii-327' is still in progress. We will continue to provide updates as they become available.

  5. identified Apr 29, 2026, 02:00 PM UTC

    Maintenance is still in progress to address a hardware issue found on node 'gbe2-bfyii-327'. We will continue to provide updates from the team as the maintenance progresses.

  6. monitoring May 01, 2026, 12:29 PM UTC

    Maintenance on node 'gbe2-bfyii-327' has been completed and the node is back online. All customer accounts are accessible and backups are running. Our R&D team is continuing to monitor.

  7. identified May 08, 2026, 04:22 PM UTC

    Our R&D team is aware of some customers hosted on node 'gbe2-bfyii-327' experiencing backup performance issues after the maintenance was completed and the team is working to address it.

  8. identified May 13, 2026, 05:50 PM UTC

    Customer accounts hosted on node 'gbe2-bfyii-327' remain functional and our R&D team is continuing to address the backup performance issues affecting some services.

  9. identified May 14, 2026, 07:30 PM UTC

    Our R&D team is continuing to address the backup performance issues affecting a small subset of customer's services on the node and backup success rates are improving.

  10. monitoring May 19, 2026, 04:13 PM UTC

    Our R&D team has implemented changes to address the backup issues affecting a small subset of customer's services on node 'gbe2-bfyii-327' and will be monitoring for any other issues.

  11. monitoring May 19, 2026, 08:25 PM UTC

    Backup success rate metrics for node 'gbe2-bfyii-327' have returned to normal levels. Our R&D team is continuing to monitor.

  12. resolved May 21, 2026, 01:23 PM UTC

    This incident has been resolved.