All services / Illinois ABE / Nov 15, 2026 / Evidence

Evidence

Evidence: Illinois ABE, Nov 15, 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/1309/evidence. Free to reuse with attribution.

9 of 18Checks failed in the window
4 of 4Regions failing
http_530Most 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_5309

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

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.
  • : Now failing from US West.
Regional probe results in the window
RegionData centerTime (UTC)ResultHTTPLatencyError code
Asia-PacificKIXFail5306029 mshttp_530
US EastORDFail5306008 mshttp_530
EuropeAMSFail5306009 mshttp_530
US WestSJCFail5306009 mshttp_530

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 Illinois ABE 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

18 checks, 9 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail5306066 mshttp_530scheduled
Fail5306048 mshttp_530scheduled
Fail5306103 mshttp_530scheduled
Fail5306091 mshttp_530scheduled
Fail5306089 mshttp_530scheduled
Fail5306094 mshttp_530scheduled
Fail5306211 mshttp_530scheduled
Fail5306141 mshttp_530scheduled
Fail5306083 mshttp_530scheduled
All 18 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass403459 msbot_challengescheduled
Fail5306066 mshttp_530scheduled
Fail5306048 mshttp_530scheduled
Pass403437 msbot_challengescheduled
Pass403535 msbot_challengescheduled
Pass403490 msbot_challengescheduled
Fail5306103 mshttp_530scheduled
Fail5306091 mshttp_530scheduled
Fail5306089 mshttp_530scheduled
Fail5306094 mshttp_530scheduled
Fail5306211 mshttp_530scheduled
Fail5306141 mshttp_530scheduled
Fail5306083 mshttp_530scheduled
Pass403154 msbot_challengescheduled
Pass403138 msbot_challengescheduled
Pass403163 msbot_challengescheduled
Pass403296 msbot_challengescheduled
Pass403139 msbot_challengescheduled

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

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