Damn, is it down?

All services / CarMax / Nov 5, 2026 / Evidence

Evidence

Evidence: CarMax, Nov 5, 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/885/evidence. Free to reuse with attribution.

14 of 37Checks failed in the window
2 of 4Regions failing
origin_resetMost 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
origin_reset14

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

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

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

37 checks, 14 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail52012095 msorigin_resetscheduled
Fail52012359 msorigin_resetscheduled
Fail52012415 msorigin_resetscheduled
Fail52012137 msorigin_resetscheduled
Fail52012146 msorigin_resetscheduled
Fail52012235 msorigin_resetscheduled
Fail52012265 msorigin_resetscheduled
Fail52012395 msorigin_resetscheduled
Fail52012430 msorigin_resetscheduled
Fail52012141 msorigin_resetscheduled
Fail52012180 msorigin_resetscheduled
Fail52012159 msorigin_resetscheduled
Fail52012230 msorigin_resetscheduled
Fail52012084 msorigin_resetscheduled
All 37 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail52012095 msorigin_resetscheduled
Pass20084 ms—scheduled
Pass20064 ms—scheduled
Fail52012359 msorigin_resetscheduled
Pass200277 ms—scheduled
Pass20056 ms—scheduled
Pass200152 ms—scheduled
Fail52012415 msorigin_resetscheduled
Fail52012137 msorigin_resetscheduled
Pass200112 ms—scheduled
Fail52012146 msorigin_resetscheduled
Pass200105 ms—scheduled
Pass301—bot_blocked_http_520scheduled
Pass200102 ms—scheduled
Fail52012235 msorigin_resetscheduled
Pass20068 ms—scheduled
Fail52012265 msorigin_resetscheduled
Fail52012395 msorigin_resetscheduled
Pass20081 ms—scheduled
Fail52012430 msorigin_resetscheduled
Fail52012141 msorigin_resetscheduled
Pass200349 ms—scheduled
Fail52012180 msorigin_resetscheduled
Fail52012159 msorigin_resetscheduled
Pass20043 ms—scheduled
Fail52012230 msorigin_resetscheduled
Pass301—bot_blocked_http_520scheduled
Fail52012084 msorigin_resetscheduled
Pass200247 ms—scheduled
Pass20091 ms—scheduled
Pass20056 ms—scheduled
Pass20051 ms—scheduled
Pass200228 ms—scheduled
Pass20078 ms—scheduled
Pass20072 ms—scheduled
Pass200185 ms—scheduled
Pass20054 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=885

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