Damn, is it down?

All services / Mediacom / Nov 5, 2026 / Evidence

Evidence

Evidence: Mediacom, 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/875/evidence. Free to reuse with attribution.

49 of 77Checks failed in the window
2 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_50349

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

77 checks, 49 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail503648 mshttp_503scheduled
Fail503396 mshttp_503scheduled
Fail503531 mshttp_503scheduled
Fail503184 mshttp_503scheduled
Fail503372 mshttp_503scheduled
Fail503542 mshttp_503scheduled
Fail5031075 mshttp_503scheduled
Fail503367 mshttp_503scheduled
Fail5031045 mshttp_503scheduled
Fail503631 mshttp_503scheduled
Fail503404 mshttp_503scheduled
Fail503400 mshttp_503scheduled
Fail503659 mshttp_503scheduled
Fail503679 mshttp_503scheduled
Fail503512 mshttp_503scheduled
Fail503431 mshttp_503scheduled
Fail503141 mshttp_503scheduled
Fail503666 mshttp_503scheduled
Fail503496 mshttp_503scheduled
Fail503230 mshttp_503scheduled
Fail503930 mshttp_503scheduled
Fail503380 mshttp_503scheduled
Fail503283 mshttp_503scheduled
Fail503352 mshttp_503scheduled
Fail503356 mshttp_503scheduled
Fail503460 mshttp_503scheduled
Fail503424 mshttp_503scheduled
Fail503663 mshttp_503scheduled
Fail503373 mshttp_503scheduled
Fail503396 mshttp_503scheduled
Fail503690 mshttp_503scheduled
Fail503610 mshttp_503scheduled
Fail503486 mshttp_503scheduled
Fail503530 mshttp_503scheduled
Fail503659 mshttp_503scheduled
Fail503695 mshttp_503scheduled
Fail503191 mshttp_503scheduled
Fail503363 mshttp_503scheduled
Fail503385 mshttp_503scheduled
Fail503404 mshttp_503scheduled
Fail503480 mshttp_503scheduled
Fail503370 mshttp_503scheduled
Fail503361 mshttp_503scheduled
Fail503621 mshttp_503scheduled
Fail503288 mshttp_503scheduled
Fail503672 mshttp_503scheduled
Fail503295 mshttp_503scheduled
Fail503667 mshttp_503scheduled
Fail503496 mshttp_503scheduled
All 77 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200296 ms—scheduled
Pass200224 ms—scheduled
Fail503648 mshttp_503scheduled
Fail503396 mshttp_503scheduled
Fail503531 mshttp_503scheduled
Pass200202 ms—scheduled
Fail503184 mshttp_503scheduled
Fail503372 mshttp_503scheduled
Pass200193 ms—scheduled
Fail503542 mshttp_503scheduled
Fail5031075 mshttp_503scheduled
Fail503367 mshttp_503scheduled
Pass200178 ms—scheduled
Fail5031045 mshttp_503scheduled
Pass200520 ms—scheduled
Fail503631 mshttp_503scheduled
Fail503404 mshttp_503scheduled
Pass200293 ms—scheduled
Fail503400 mshttp_503scheduled
Fail503659 mshttp_503scheduled
Fail503679 mshttp_503scheduled
Pass200258 ms—scheduled
Pass200134 ms—scheduled
Fail503512 mshttp_503scheduled
Fail503431 mshttp_503scheduled
Fail503141 mshttp_503scheduled
Pass200402 ms—scheduled
Pass200397 ms—scheduled
Fail503666 mshttp_503scheduled
Fail503496 mshttp_503scheduled
Pass200371 ms—scheduled
Fail503230 mshttp_503scheduled
Fail503930 mshttp_503scheduled
Pass200160 ms—scheduled
Fail503380 mshttp_503scheduled
Fail503283 mshttp_503scheduled
Pass200303 ms—scheduled
Pass200204 ms—scheduled
Pass200242 ms—scheduled
Fail503352 mshttp_503scheduled
Pass200413 ms—scheduled
Pass200284 ms—scheduled
Fail503356 mshttp_503scheduled
Fail503460 mshttp_503scheduled
Fail503424 mshttp_503scheduled
Pass200282 ms—scheduled
Fail503663 mshttp_503scheduled
Fail503373 mshttp_503scheduled
Fail503396 mshttp_503scheduled
Fail503690 mshttp_503scheduled
Pass200254 ms—scheduled
Fail503610 mshttp_503scheduled
Fail503486 mshttp_503scheduled
Fail503530 mshttp_503scheduled
Pass200192 ms—scheduled
Fail503659 mshttp_503scheduled
Fail503695 mshttp_503scheduled
Fail503191 mshttp_503scheduled
Fail503363 mshttp_503scheduled
Fail503385 mshttp_503scheduled
Pass200396 ms—scheduled
Fail503404 mshttp_503scheduled
Fail503480 mshttp_503scheduled
Fail503370 mshttp_503scheduled
Fail503361 mshttp_503scheduled
Fail503621 mshttp_503scheduled
Fail503288 mshttp_503scheduled
Pass200217 ms—scheduled
Fail503672 mshttp_503scheduled
Fail503295 mshttp_503scheduled
Pass200288 ms—scheduled
Pass200380 ms—scheduled
Pass200290 ms—scheduled
Pass200356 ms—scheduled
Fail503667 mshttp_503scheduled
Pass200219 ms—scheduled
Fail503496 mshttp_503scheduled

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

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