All services / iboats / Nov 17, 2026 / Evidence

Evidence

Evidence: iboats, Nov 17, 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/1404/evidence. Free to reuse with attribution.

26 of 29Checks failed in the window
4 of 4Regions failing
http_503_edgeMost 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_503_edge26

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

No user reports for iboats 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

29 checks, 26 failed (first , last ).

Failed checks

Failed checks
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail503296 mshttp_503_edgescheduled
Fail503271 mshttp_503_edgescheduled
Fail503301 mshttp_503_edgescheduled
Fail503205 mshttp_503_edgescheduled
Fail503154 mshttp_503_edgescheduled
Fail503312 mshttp_503_edgescheduled
Fail503285 mshttp_503_edgescheduled
Fail503286 mshttp_503_edgescheduled
Fail503306 mshttp_503_edgescheduled
Fail503181 mshttp_503_edgescheduled
Fail503285 mshttp_503_edgescheduled
Fail503267 mshttp_503_edgescheduled
Fail503274 mshttp_503_edgescheduled
Fail503296 mshttp_503_edgescheduled
Fail503274 mshttp_503_edgescheduled
Fail50396 mshttp_503_edgescheduled
Fail503286 mshttp_503_edgescheduled
Fail503282 mshttp_503_edgescheduled
Fail503249 mshttp_503_edgescheduled
Fail503296 mshttp_503_edgescheduled
Fail503262 mshttp_503_edgescheduled
Fail503259 mshttp_503_edgescheduled
Fail503255 mshttp_503_edgescheduled
Fail503170 mshttp_503_edgescheduled
Fail503322 mshttp_503_edgescheduled
Fail503269 mshttp_503_edgescheduled
All 29 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Fail503296 mshttp_503_edgescheduled
Fail503271 mshttp_503_edgescheduled
Fail503301 mshttp_503_edgescheduled
Fail503205 mshttp_503_edgescheduled
Fail503154 mshttp_503_edgescheduled
Fail503312 mshttp_503_edgescheduled
Fail503285 mshttp_503_edgescheduled
Fail503286 mshttp_503_edgescheduled
Fail503306 mshttp_503_edgescheduled
Fail503181 mshttp_503_edgescheduled
Fail503285 mshttp_503_edgescheduled
Fail503267 mshttp_503_edgescheduled
Fail503274 mshttp_503_edgescheduled
Fail503296 mshttp_503_edgescheduled
Fail503274 mshttp_503_edgescheduled
Fail50396 mshttp_503_edgescheduled
Fail503286 mshttp_503_edgescheduled
Fail503282 mshttp_503_edgescheduled
Fail503249 mshttp_503_edgescheduled
Fail503296 mshttp_503_edgescheduled
Fail503262 mshttp_503_edgescheduled
Fail503259 mshttp_503_edgescheduled
Fail503255 mshttp_503_edgescheduled
Fail503170 mshttp_503_edgescheduled
Fail503322 mshttp_503_edgescheduled
Fail503269 mshttp_503_edgescheduled
Pass200779 ms—scheduled
Pass200883 ms—scheduled
Pass200817 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=1404

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