← List

TRACKER DETAIL

open.ftorrent.com

Tracker URL
IPV4 · FailedHTTP 200 · Invalid protocol responseChecked: 2026-11-11 18:00 UTC
IPV6 · FailedHTTP 200 · Invalid protocol responseChecked: 2026-11-11 18:00 UTC

EVIDENCE

Observed evidence

Handshakes verify sampled peers; bitmaps are claims, not proof of downloadable content.

24h announce success0.0%0 / 82
24h protocol reply0.0%0 / 82
Median latencyUnknownObserved responses
Verified peers0Handshakes in 7 days
Sample resources0Public samples
Claimed bitmap coverageUnknown0 observations

NETWORK

Network information

Network ownership comes from public data and does not pinpoint a datacenter.

ASN
AS394838
Organization
PULSE - Pulse, US
Country / region
US
Cache updated
2026-11-11 13:53 UTC

LAST 24 HOURS

24-hour observations

The charts and event table show health announces only. Lines do not prove continuous availability.

Green: success · Red: failure · Amber: rate limit/rejection · Grey: unknown/local unavailable. IPv4 and IPv6 are separate checks and can occur close together.

Observed response latency (ms)
Time (UTC)FamilyStageTransportObservation resultValid tracker replyStage latencyReason
2026-11-11 18:00 UTCIPV6Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 18:00 UTCIPV4Health announceHTTP 200Invalid protocol responseNo142 msinvalid_protocol
2026-11-11 17:29 UTCIPV6Health announceHTTP 200Invalid protocol responseNo146 msinvalid_protocol
2026-11-11 17:29 UTCIPV4Health announceHTTP 200Invalid protocol responseNo144 msinvalid_protocol
2026-11-11 16:58 UTCIPV6Health announceHTTP 200Invalid protocol responseNo150 msinvalid_protocol
2026-11-11 16:58 UTCIPV4Health announceHTTP 200Invalid protocol responseNo142 msinvalid_protocol
2026-11-11 16:27 UTCIPV6Health announceHTTP 200Invalid protocol responseNo171 msinvalid_protocol
2026-11-11 16:27 UTCIPV4Health announceHTTP 200Invalid protocol responseNo151 msinvalid_protocol
2026-11-11 15:56 UTCIPV6Health announceHTTP 200Invalid protocol responseNo139 msinvalid_protocol
2026-11-11 15:56 UTCIPV4Health announceHTTP 200Invalid protocol responseNo146 msinvalid_protocol
2026-11-11 15:25 UTCIPV6Health announceHTTP 200Invalid protocol responseNo148 msinvalid_protocol
2026-11-11 15:25 UTCIPV4Health announceHTTP 200Invalid protocol responseNo177 msinvalid_protocol
2026-11-11 14:54 UTCIPV6Health announceHTTP 200Invalid protocol responseNo135 msinvalid_protocol
2026-11-11 14:54 UTCIPV4Health announceHTTP 200Invalid protocol responseNo143 msinvalid_protocol
2026-11-11 14:23 UTCIPV6Health announceHTTP 200Invalid protocol responseNo172 msinvalid_protocol
2026-11-11 14:23 UTCIPV4Health announceHTTP 200Invalid protocol responseNo173 msinvalid_protocol
2026-11-11 13:53 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 13:53 UTCIPV4Health announceHTTP 200Invalid protocol responseNo172 msinvalid_protocol
2026-11-11 13:22 UTCIPV6Health announceHTTP 200Invalid protocol responseNo153 msinvalid_protocol
2026-11-11 13:22 UTCIPV4Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 12:51 UTCIPV6Health announceHTTP 200Invalid protocol responseNo146 msinvalid_protocol
2026-11-11 12:51 UTCIPV4Health announceHTTP 200Invalid protocol responseNo175 msinvalid_protocol
2026-11-11 12:21 UTCIPV6Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 12:21 UTCIPV4Health announceHTTP 200Invalid protocol responseNo175 msinvalid_protocol
2026-11-11 11:50 UTCIPV6Health announceHTTP 200Invalid protocol responseNo137 msinvalid_protocol
2026-11-11 11:50 UTCIPV4Health announceHTTP 200Invalid protocol responseNo145 msinvalid_protocol
2026-11-11 11:18 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 11:18 UTCIPV4Health announceHTTP 200Invalid protocol responseNo138 msinvalid_protocol
2026-11-11 10:47 UTCIPV6Health announceHTTP 200Invalid protocol responseNo139 msinvalid_protocol
2026-11-11 10:47 UTCIPV4Health announceHTTP 200Invalid protocol responseNo137 msinvalid_protocol
2026-11-11 10:17 UTCIPV6Health announceHTTP 200Invalid protocol responseNo146 msinvalid_protocol
2026-11-11 10:17 UTCIPV4Health announceHTTP 200Invalid protocol responseNo144 msinvalid_protocol
2026-11-11 09:46 UTCIPV6Health announceHTTP 200Invalid protocol responseNo154 msinvalid_protocol
2026-11-11 09:46 UTCIPV4Health announceHTTP 200Invalid protocol responseNo151 msinvalid_protocol
2026-11-11 09:15 UTCIPV6Health announceHTTP 200Invalid protocol responseNo236 msinvalid_protocol
2026-11-11 09:15 UTCIPV4Health announceHTTP 200Invalid protocol responseNo139 msinvalid_protocol
2026-11-11 08:44 UTCIPV6Health announceHTTP 200Invalid protocol responseNo143 msinvalid_protocol
2026-11-11 08:44 UTCIPV4Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 08:13 UTCIPV6Health announceHTTP 200Invalid protocol responseNo177 msinvalid_protocol
2026-11-11 08:13 UTCIPV4Health announceHTTP 200Invalid protocol responseNo142 msinvalid_protocol
2026-11-11 07:42 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 07:42 UTCIPV4Health announceHTTP 200Invalid protocol responseNo146 msinvalid_protocol
2026-11-11 07:12 UTCIPV6Health announceHTTP 200Invalid protocol responseNo179 msinvalid_protocol
2026-11-11 07:12 UTCIPV4Health announceHTTP 200Invalid protocol responseNo147 msinvalid_protocol
2026-11-11 06:41 UTCIPV6Health announceHTTP 200Invalid protocol responseNo154 msinvalid_protocol
2026-11-11 06:41 UTCIPV4Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 06:11 UTCIPV6Health announceHTTP 200Invalid protocol responseNo137 msinvalid_protocol
2026-11-11 06:11 UTCIPV4Health announceHTTP 200Invalid protocol responseNo138 msinvalid_protocol
2026-11-11 05:40 UTCIPV6Health announceHTTP 200Invalid protocol responseNo139 msinvalid_protocol
2026-11-11 05:40 UTCIPV4Health announceHTTP 200Invalid protocol responseNo147 msinvalid_protocol
2026-11-11 05:09 UTCIPV6Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 05:09 UTCIPV4Health announceHTTP 200Invalid protocol responseNo135 msinvalid_protocol
2026-11-11 04:39 UTCIPV6Health announceHTTP 200Invalid protocol responseNo137 msinvalid_protocol
2026-11-11 04:39 UTCIPV4Health announceHTTP 200Invalid protocol responseNo147 msinvalid_protocol
2026-11-11 04:08 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 04:08 UTCIPV4Health announceHTTP 200Invalid protocol responseNo148 msinvalid_protocol
2026-11-11 03:38 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-11 03:38 UTCIPV4Health announceHTTP 200Invalid protocol responseNo161 msinvalid_protocol
2026-11-11 03:07 UTCIPV6Health announceHTTP 200Invalid protocol responseNo139 msinvalid_protocol
2026-11-11 03:07 UTCIPV4Health announceHTTP 200Invalid protocol responseNo142 msinvalid_protocol
2026-11-11 02:37 UTCIPV6Health announceHTTP 200Invalid protocol responseNo136 msinvalid_protocol
2026-11-11 02:37 UTCIPV4Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 02:05 UTCIPV6Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 02:05 UTCIPV4Health announceHTTP 200Invalid protocol responseNo168 msinvalid_protocol
2026-11-11 01:35 UTCIPV6Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 01:35 UTCIPV4Health announceHTTP 200Invalid protocol responseNo145 msinvalid_protocol
2026-11-11 01:05 UTCIPV6Health announceHTTP 200Invalid protocol responseNo142 msinvalid_protocol
2026-11-11 01:05 UTCIPV4Health announceHTTP 200Invalid protocol responseNo151 msinvalid_protocol
2026-11-11 00:34 UTCIPV6Health announceHTTP 200Invalid protocol responseNo137 msinvalid_protocol
2026-11-11 00:33 UTCIPV4Health announceHTTP 200Invalid protocol responseNo177 msinvalid_protocol
2026-11-11 00:03 UTCIPV6Health announceHTTP 200Invalid protocol responseNo141 msinvalid_protocol
2026-11-11 00:03 UTCIPV4Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-10 23:31 UTCIPV6Health announceHTTP 200Invalid protocol responseNo139 msinvalid_protocol
2026-11-10 23:31 UTCIPV4Health announceHTTP 200Invalid protocol responseNo156 msinvalid_protocol
2026-11-10 23:01 UTCIPV6Health announceHTTP 200Invalid protocol responseNo179 msinvalid_protocol
2026-11-10 23:01 UTCIPV4Health announceHTTP 200Invalid protocol responseNo167 msinvalid_protocol
2026-11-10 22:30 UTCIPV6Health announceHTTP 200Invalid protocol responseNo149 msinvalid_protocol
2026-11-10 22:30 UTCIPV4Health announceHTTP 200Invalid protocol responseNo150 msinvalid_protocol
2026-11-10 21:59 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-10 21:59 UTCIPV4Health announceHTTP 200Invalid protocol responseNo146 msinvalid_protocol
2026-11-10 21:29 UTCIPV6Health announceHTTP 200Invalid protocol responseNo140 msinvalid_protocol
2026-11-10 21:29 UTCIPV4Health announceHTTP 200Invalid protocol responseNo138 msinvalid_protocol

Measurements come from one network; missing data and local probe failures are not tracker downtime.