Barracuda incident

Barracuda Backup Service (Japan)

Notice Resolved View vendor source →
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

Looking to track Barracuda downtime and outages?

Pingoru polls Barracuda's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Barracuda reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Barracuda alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Barracuda for free

5 free monitors · No credit card required