All services / Barracuda / Nov 4, 2026 / Evidence

Evidence

Evidence: Barracuda, Nov 4, 2026

The raw data behind this incident page: every check we ran, the regions that failed, the error codes and the user report curve. Check our work.

Our verdict: Vendor-reported issue: only the company's status page flagged it; our checks and user reports did not confirm an outage. How we verify outages

Download JSON Download CSV Also at /api/v1/outages/614/evidence. Free to reuse with attribution.

0 of 96Checks failed in the window
0 of 4Regions failing
—Most common error code
0Peak user reports in 15 min

Window: to . Checks from 15 minutes before the start to 15 minutes after recovery (or now). Report curve: one hour either side. Tables are in UTC.

Error codes

No failed checks with an error code in this window.

http_5xx = the site answered with that server error; timeout = no answer in time; network = the connection failed; origin_reset = the connection to the site's server was reset (HTTP 520–527) and a second fetch path got no answer either; no_status = no usable answer. Bot walls (bot_*), certificate problems on a server that answers (cert_*) and maintenance pages count as up.

Regions

  • We check from: US East, US West, Europe, Asia-Pacific.
  • Failing during this incident: none recorded.

Regional probes run from Cloudflare data centers in each region. We keep the latest regional result per region, plus a timestamped timeline entry when a region starts failing during an incident, so older incidents show the failing regions and when each was first seen, not every regional probe.

Report curve

No user reports for Barracuda in this window.

User reports per 15-minute bucket. Counts only: no reporter identity, IP address, location or text is published. We call reports a spike at 5 or more in 15 minutes.

Raw checks

96 checks, 0 failed.

All 96 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200168 ms—scheduled
Pass200217 ms—scheduled
Pass200133 ms—scheduled
Pass20088 ms—scheduled
Pass20048 ms—scheduled
Pass20063 ms—scheduled
Pass200138 ms—scheduled
Pass20098 ms—scheduled
Pass200167 ms—scheduled
Pass200301 ms—scheduled
Pass404297 ms—scheduled
Pass20058 ms—scheduled
Pass200327 ms—scheduled
Pass200156 ms—scheduled
Pass200120 ms—scheduled
Pass200128 ms—scheduled
Pass404100 ms—scheduled
Pass404327 ms—scheduled
Pass404125 ms—scheduled
Pass20072 ms—scheduled
Pass200352 ms—scheduled
Pass200419 ms—scheduled
Pass200106 ms—scheduled
Pass200148 ms—scheduled
Pass20058 ms—scheduled
Pass20054 ms—scheduled
Pass20056 ms—scheduled
Pass20057 ms—scheduled
Pass200228 ms—scheduled
Pass20065 ms—scheduled
Pass200100 ms—scheduled
Pass200165 ms—scheduled
Pass20086 ms—scheduled
Pass404110 ms—scheduled
Pass200319 ms—scheduled
Pass20076 ms—scheduled
Pass20088 ms—scheduled
Pass200122 ms—scheduled
Pass404591 ms—scheduled
Pass200526 ms—scheduled
Pass200367 ms—scheduled
Pass200163 ms—scheduled
Pass200222 ms—scheduled
Pass200428 ms—scheduled
Pass20075 ms—scheduled
Pass20084 ms—scheduled
Pass200248 ms—scheduled
Pass20042 ms—scheduled
Pass200398 ms—scheduled
Pass404244 ms—scheduled
Pass200179 ms—scheduled
Pass200310 ms—scheduled
Pass20057 ms—scheduled
Pass200230 ms—scheduled
Pass20071 ms—scheduled
Pass20060 ms—scheduled
Pass20073 ms—scheduled
Pass404252 ms—scheduled
Pass404117 ms—scheduled
Pass200138 ms—scheduled
Pass404202 ms—scheduled
Pass404107 ms—scheduled
Pass404111 ms—scheduled
Pass20057 ms—scheduled
Pass20049 ms—scheduled
Pass20053 ms—scheduled
Pass404220 ms—scheduled
Pass200129 ms—scheduled
Pass40496 ms—scheduled
Pass200111 ms—scheduled
Pass20088 ms—scheduled
Pass200150 ms—scheduled
Pass200351 ms—scheduled
Pass200149 ms—scheduled
Pass20099 ms—scheduled
Pass2001676 ms—scheduled
Pass2001706 ms—scheduled
Pass200109 ms—scheduled
Pass2001447 ms—scheduled
Pass20060 ms—scheduled
Pass20090 ms—scheduled
Pass404223 ms—scheduled
Pass20078 ms—scheduled
Pass20087 ms—scheduled
Pass404117 ms—scheduled
Pass20066 ms—scheduled
Pass404374 ms—scheduled
Pass20074 ms—scheduled
Pass200144 ms—scheduled
Pass20080 ms—scheduled
Pass200449 ms—scheduled
Pass20090 ms—scheduled
Pass200172 ms—scheduled
Pass200155 ms—scheduled
Pass200376 ms—scheduled
Pass200156 ms—scheduled

Every main HTTP check of this service in the window, oldest first: the scheduled check time, when the probe actually ran, the result, HTTP status, latency and the stored error code. A failed check is a 5xx or 408 answer, a timeout or a failed connection; bot walls and maintenance pages count as passing and are noted in passing_notes.

How to check this

  • Compare checks.rows with the outage page: the first and last failed checks bound the incident times we published.
  • error_codes counts every failed check by its stored code; recount it from checks.rows.
  • report_curve.points sum to summary.reports_in_curve; the peak is summary.peak_reports_15m.
  • Disagree? Dispute it at https://damnisitdown.com/support?dispute=614

No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.

← Back to the incident · Methodology · Dispute this report