Vendor Status Watch

← all vendors

Barracuda MSP status history

Current state: operational — “All Systems Operational” per https://mwrmm.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
1incidents, last 90 days
4incidents on record
Incidents per week, last 12 weeks:
Get Barracuda MSP alerts in your Slack — free templateRSS for Barracuda MSP

How long do Barracuda MSP incidents last?

24.3 hmedian incident duration3 measured
7.2 days90th percentile1 in 10 ran longer
—median, major/critical onlynone posted

From 3 incidents with a vendor-posted start and resolve time. Longest on record: US07 - Degraded Performance — 7.2 days (2026-03-02 14:25 UTC). Excluded, never estimated: 1 still open / no resolve time. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (4)

StartedIncidentStatusImpactDuration
2026-09-09 16:24 UTCUS07 Degraded Performanceinvestigatingminoropen
2026-05-08 12:26 UTCUS03 - Unplanned Outage - Investigationresolvednone24 h 19 min
2026-03-02 14:25 UTCUS07 - Degraded Performanceresolvedminor7 d 3 h
2026-01-05 14:18 UTCPartners are not receiving emails from Barracuda RMMresolvedminor23 h 29 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Barracuda MSP with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "barracuda-msp"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}