Barracuda incident

Barracuda Backup Service (Japan)

Resolved after 9 days 2 hours, affecting Offsite Transfers, on February 9, 2026.

monitoring Feb 09, 2026, 03:50 PM UTC

There was a previous incident on 06 Feb 2026 which is resolved. However to fully validate the resolution, all file share data for the affected customers was re-queued to replicate to the Barracuda Cloud. This did not re-queue all data only the the data that was not replicated as a result of the incident. Customer will see a discrepancy in the replication queue size until the validation check completes.

Started
Feb 09, 2026, 03:50 PM UTC
Resolved
Feb 18, 2026, 06:24 PM UTC
Duration
9d 2h
Detected by Pingoru
Feb 09, 2026, 03:50 PM UTC

Affected components

Offsite Transfers

Update timeline

  1. monitoring Feb 09, 2026, 03:50 PM UTC

    There was a previous incident on 06 Feb 2026 which is resolved. However to fully validate the resolution, all file share data for the affected customers was re-queued to replicate to the Barracuda Cloud. This did not re-queue all data only the the data that was not replicated as a result of the incident. Customer will see a discrepancy in the replication queue size until the validation check completes.

  2. resolved Feb 18, 2026, 06:24 PM UTC

    This incident has been resolved

Your product runs on more than Barracuda

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →