Damn, is it down?

All services / WiscNet / Nov 6, 2026 / Evidence

Evidence

Evidence: WiscNet, Nov 6, 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/1016/evidence. Free to reuse with attribution.

1 of 40Checks failed in the window
0 of 4Regions failing
http_503Most 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

Error codeFailed checks
http_5031

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 WiscNet 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

40 checks, 1 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail5031296 mshttp_503scheduled
All 40 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass20093 ms—scheduled
Pass200311 ms—scheduled
Pass200342 ms—scheduled
Pass200381 ms—scheduled
Pass200353 ms—scheduled
Pass200339 ms—scheduled
Pass200306 ms—scheduled
Pass200129 ms—scheduled
Pass200321 ms—on demand
Pass200350 ms—on demand
Fail5031296 mshttp_503scheduled
Pass200158 ms—scheduled
Pass200332 ms—scheduled
Pass200428 ms—on demand
Pass200103 ms—scheduled
Pass200370 ms—scheduled
Pass200367 ms—scheduled
Pass200359 ms—scheduled
Pass200351 ms—scheduled
Pass200157 ms—scheduled
Pass20047 ms—scheduled
Pass200152 ms—scheduled
Pass200312 ms—scheduled
Pass200394 ms—scheduled
Pass200381 ms—scheduled
Pass200233 ms—scheduled
Pass200204 ms—scheduled
Pass200362 ms—scheduled
Pass200341 ms—scheduled
Pass200349 ms—scheduled
Pass200132 ms—scheduled
Pass200328 ms—scheduled
Pass200376 ms—scheduled
Pass200360 ms—scheduled
Pass200349 ms—scheduled
Pass200218 ms—scheduled
Pass200344 ms—on demand
Pass200350 ms—scheduled
Pass20083 ms—scheduled
Pass200336 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=1016

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