All services / Wisconsin DMV / Nov 12, 2026 / Evidence

Evidence

Evidence: Wisconsin DMV, Nov 12, 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: Possible problem, not a confirmed outage: it did not meet our evidence bar. How we verify outages

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

7 of 9Checks failed in the window
4 of 4Regions failing
origin_resetMost common error code
1Peak 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
origin_reset7

Passing checks with a note (counted as up, not as failures): bot_blocked_http_520 ×1, maintenance ×1.

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: Asia-Pacific, US East, Europe, US West.
  • : Failing from Asia-Pacific, US East, Europe, US West.

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

11:45 AM ET: 012:00 PM ET: 012:15 PM ET: 012:30 PM ET: 012:45 PM ET: 11:00 PM ET: 01:15 PM ET: 01:30 PM ET: 01:45 PM ET: 02:00 PM ET: 02:15 PM ET: 02:30 PM ET: 011:45 AM ET2:30 PM ET
User reports per 15 minutes (peak 1). Times are ET.
Report counts per 15 minutes (1 non-zero buckets)
15 minutes from (UTC)Reports
1

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

9 checks, 7 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail5202366 msorigin_resetscheduled
Fail5202481 msorigin_resetscheduled
Fail5202662 msorigin_resetscheduled
Fail5204367 msorigin_resetscheduled
Fail5202032 msorigin_reseton demand
Fail5201564 msorigin_reseton demand
Fail5201404 msorigin_resetscheduled
All 9 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail5202366 msorigin_resetscheduled
Fail5202481 msorigin_resetscheduled
Pass404—bot_blocked_http_520scheduled
Fail5202662 msorigin_resetscheduled
Fail5204367 msorigin_resetscheduled
Fail5202032 msorigin_reseton demand
Fail5201564 msorigin_reseton demand
Pass503261 msmaintenancescheduled
Fail5201404 msorigin_resetscheduled

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=1216

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