Damn, is it down?

All services / i3Dnet / Nov 6, 2026 / Evidence

Evidence

Evidence: i3Dnet, Nov 6, 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: Vendor-reported issue: only the company's status page flagged it; our checks and user reports did not confirm an outage. How we verify outages

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

0 of 36Checks failed in the window
0 of 4Regions failing
—Most 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

No failed checks with an error code in this window.

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

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: none recorded.

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

36 checks, 0 failed.

All 36 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass40399 msbot_challengescheduled
Pass403147 msbot_challengescheduled
Pass403141 msbot_challengescheduled
Pass403148 msbot_challengescheduled
Pass403179 msbot_challengescheduled
Pass403166 msbot_challengescheduled
Pass40357 msbot_challengescheduled
Pass40396 msbot_challengeon demand
Pass403173 msbot_challengescheduled
Pass403137 msbot_challengescheduled
Pass403145 msbot_challengescheduled
Pass40329 msbot_challengescheduled
Pass40348 msbot_challengescheduled
Pass403144 msbot_challengescheduled
Pass403149 msbot_challengescheduled
Pass403102 msbot_challengescheduled
Pass403135 msbot_challengescheduled
Pass403177 msbot_challengescheduled
Pass403104 msbot_challengescheduled
Pass403149 msbot_challengescheduled
Pass40359 msbot_challengescheduled
Pass40360 msbot_challengescheduled
Pass403115 msbot_challengescheduled
Pass40370 msbot_challengescheduled
Pass403118 msbot_challengescheduled
Pass40364 msbot_challengescheduled
Pass40337 msbot_challengescheduled
Pass403189 msbot_challengescheduled
Pass403183 msbot_challengescheduled
Pass40388 msbot_challengescheduled
Pass40335 msbot_challengescheduled
Pass403150 msbot_challengescheduled
Pass403112 msbot_challengescheduled
Pass403102 msbot_challengescheduled
Pass40315 msbot_challengescheduled
Pass40359 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=1000

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