All services / Barracuda / Nov 4, 2026 / 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.
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
| Check time (UTC) | Probe ran (UTC) | Result | HTTP | Latency | Error code | Trigger |
|---|---|---|---|---|---|---|
| Pass | 200 | 168 ms | — | scheduled | ||
| Pass | 200 | 217 ms | — | scheduled | ||
| Pass | 200 | 133 ms | — | scheduled | ||
| Pass | 200 | 88 ms | — | scheduled | ||
| Pass | 200 | 48 ms | — | scheduled | ||
| Pass | 200 | 63 ms | — | scheduled | ||
| Pass | 200 | 138 ms | — | scheduled | ||
| Pass | 200 | 98 ms | — | scheduled | ||
| Pass | 200 | 167 ms | — | scheduled | ||
| Pass | 200 | 301 ms | — | scheduled | ||
| Pass | 404 | 297 ms | — | scheduled | ||
| Pass | 200 | 58 ms | — | scheduled | ||
| Pass | 200 | 327 ms | — | scheduled | ||
| Pass | 200 | 156 ms | — | scheduled | ||
| Pass | 200 | 120 ms | — | scheduled | ||
| Pass | 200 | 128 ms | — | scheduled | ||
| Pass | 404 | 100 ms | — | scheduled | ||
| Pass | 404 | 327 ms | — | scheduled | ||
| Pass | 404 | 125 ms | — | scheduled | ||
| Pass | 200 | 72 ms | — | scheduled | ||
| Pass | 200 | 352 ms | — | scheduled | ||
| Pass | 200 | 419 ms | — | scheduled | ||
| Pass | 200 | 106 ms | — | scheduled | ||
| Pass | 200 | 148 ms | — | scheduled | ||
| Pass | 200 | 58 ms | — | scheduled | ||
| Pass | 200 | 54 ms | — | scheduled | ||
| Pass | 200 | 56 ms | — | scheduled | ||
| Pass | 200 | 57 ms | — | scheduled | ||
| Pass | 200 | 228 ms | — | scheduled | ||
| Pass | 200 | 65 ms | — | scheduled | ||
| Pass | 200 | 100 ms | — | scheduled | ||
| Pass | 200 | 165 ms | — | scheduled | ||
| Pass | 200 | 86 ms | — | scheduled | ||
| Pass | 404 | 110 ms | — | scheduled | ||
| Pass | 200 | 319 ms | — | scheduled | ||
| Pass | 200 | 76 ms | — | scheduled | ||
| Pass | 200 | 88 ms | — | scheduled | ||
| Pass | 200 | 122 ms | — | scheduled | ||
| Pass | 404 | 591 ms | — | scheduled | ||
| Pass | 200 | 526 ms | — | scheduled | ||
| Pass | 200 | 367 ms | — | scheduled | ||
| Pass | 200 | 163 ms | — | scheduled | ||
| Pass | 200 | 222 ms | — | scheduled | ||
| Pass | 200 | 428 ms | — | scheduled | ||
| Pass | 200 | 75 ms | — | scheduled | ||
| Pass | 200 | 84 ms | — | scheduled | ||
| Pass | 200 | 248 ms | — | scheduled | ||
| Pass | 200 | 42 ms | — | scheduled | ||
| Pass | 200 | 398 ms | — | scheduled | ||
| Pass | 404 | 244 ms | — | scheduled | ||
| Pass | 200 | 179 ms | — | scheduled | ||
| Pass | 200 | 310 ms | — | scheduled | ||
| Pass | 200 | 57 ms | — | scheduled | ||
| Pass | 200 | 230 ms | — | scheduled | ||
| Pass | 200 | 71 ms | — | scheduled | ||
| Pass | 200 | 60 ms | — | scheduled | ||
| Pass | 200 | 73 ms | — | scheduled | ||
| Pass | 404 | 252 ms | — | scheduled | ||
| Pass | 404 | 117 ms | — | scheduled | ||
| Pass | 200 | 138 ms | — | scheduled | ||
| Pass | 404 | 202 ms | — | scheduled | ||
| Pass | 404 | 107 ms | — | scheduled | ||
| Pass | 404 | 111 ms | — | scheduled | ||
| Pass | 200 | 57 ms | — | scheduled | ||
| Pass | 200 | 49 ms | — | scheduled | ||
| Pass | 200 | 53 ms | — | scheduled | ||
| Pass | 404 | 220 ms | — | scheduled | ||
| Pass | 200 | 129 ms | — | scheduled | ||
| Pass | 404 | 96 ms | — | scheduled | ||
| Pass | 200 | 111 ms | — | scheduled | ||
| Pass | 200 | 88 ms | — | scheduled | ||
| Pass | 200 | 150 ms | — | scheduled | ||
| Pass | 200 | 351 ms | — | scheduled | ||
| Pass | 200 | 149 ms | — | scheduled | ||
| Pass | 200 | 99 ms | — | scheduled | ||
| Pass | 200 | 1676 ms | — | scheduled | ||
| Pass | 200 | 1706 ms | — | scheduled | ||
| Pass | 200 | 109 ms | — | scheduled | ||
| Pass | 200 | 1447 ms | — | scheduled | ||
| Pass | 200 | 60 ms | — | scheduled | ||
| Pass | 200 | 90 ms | — | scheduled | ||
| Pass | 404 | 223 ms | — | scheduled | ||
| Pass | 200 | 78 ms | — | scheduled | ||
| Pass | 200 | 87 ms | — | scheduled | ||
| Pass | 404 | 117 ms | — | scheduled | ||
| Pass | 200 | 66 ms | — | scheduled | ||
| Pass | 404 | 374 ms | — | scheduled | ||
| Pass | 200 | 74 ms | — | scheduled | ||
| Pass | 200 | 144 ms | — | scheduled | ||
| Pass | 200 | 80 ms | — | scheduled | ||
| Pass | 200 | 449 ms | — | scheduled | ||
| Pass | 200 | 90 ms | — | scheduled | ||
| Pass | 200 | 172 ms | — | scheduled | ||
| Pass | 200 | 155 ms | — | scheduled | ||
| Pass | 200 | 376 ms | — | scheduled | ||
| Pass | 200 | 156 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.