← List

TRACKER DETAIL

t.213891.xyz

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

EVIDENCE

Observed evidence

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

24h announce success0.0%0 / 84
24h protocol reply0.0%0 / 84
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
AS13335
Organization
CLOUDFLARENET - Cloudflare, Inc., US
Country / region
US
Cache updated
2026-11-11 14:31 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:06 UTCIPV6Health announceHTTP 200Invalid protocol responseNo54 msinvalid_protocol
2026-11-11 18:06 UTCIPV4Health announceHTTP 200Invalid protocol responseNo66 msinvalid_protocol
2026-11-11 17:35 UTCIPV6Health announceHTTP 200Invalid protocol responseNo41 msinvalid_protocol
2026-11-11 17:35 UTCIPV4Health announceHTTP 200Invalid protocol responseNo33 msinvalid_protocol
2026-11-11 17:03 UTCIPV6Health announceHTTP 200Invalid protocol responseNo52 msinvalid_protocol
2026-11-11 17:03 UTCIPV4Health announceHTTP 200Invalid protocol responseNo50 msinvalid_protocol
2026-11-11 16:32 UTCIPV6Health announceHTTP 200Invalid protocol responseNo237 msinvalid_protocol
2026-11-11 16:32 UTCIPV4Health announceHTTP 200Invalid protocol responseNo36 msinvalid_protocol
2026-11-11 16:02 UTCIPV6Health announceHTTP 200Invalid protocol responseNo38 msinvalid_protocol
2026-11-11 16:02 UTCIPV4Health announceHTTP 200Invalid protocol responseNo48 msinvalid_protocol
2026-11-11 15:31 UTCIPV6Health announceHTTP 200Invalid protocol responseNo24 msinvalid_protocol
2026-11-11 15:31 UTCIPV4Health announceHTTP 200Invalid protocol responseNo124 msinvalid_protocol
2026-11-11 15:01 UTCIPV6Health announceHTTP 200Invalid protocol responseNo31 msinvalid_protocol
2026-11-11 15:01 UTCIPV4Health announceHTTP 200Invalid protocol responseNo33 msinvalid_protocol
2026-11-11 14:31 UTCIPV6Health announceHTTP 200Invalid protocol responseNo37 msinvalid_protocol
2026-11-11 14:31 UTCIPV4Health announceHTTP 200Invalid protocol responseNo42 msinvalid_protocol
2026-11-11 13:58 UTCIPV6Health announceHTTP 200Invalid protocol responseNo29 msinvalid_protocol
2026-11-11 13:58 UTCIPV4Health announceHTTP 200Invalid protocol responseNo29 msinvalid_protocol
2026-11-11 13:27 UTCIPV6Health announceHTTP 200Invalid protocol responseNo30 msinvalid_protocol
2026-11-11 13:27 UTCIPV4Health announceHTTP 200Invalid protocol responseNo23 msinvalid_protocol
2026-11-11 12:56 UTCIPV6Health announceHTTP 200Invalid protocol responseNo32 msinvalid_protocol
2026-11-11 12:56 UTCIPV4Health announceHTTP 200Invalid protocol responseNo31 msinvalid_protocol
2026-11-11 12:25 UTCIPV6Health announceHTTP 200Invalid protocol responseNo23 msinvalid_protocol
2026-11-11 12:25 UTCIPV4Health announceHTTP 200Invalid protocol responseNo35 msinvalid_protocol
2026-11-11 11:54 UTCIPV6Health announceHTTP 200Invalid protocol responseNo29 msinvalid_protocol
2026-11-11 11:54 UTCIPV4Health announceHTTP 200Invalid protocol responseNo25 msinvalid_protocol
2026-11-11 11:23 UTCIPV6Health announceHTTP 200Invalid protocol responseNo22 msinvalid_protocol
2026-11-11 11:23 UTCIPV4Health announceHTTP 200Invalid protocol responseNo25 msinvalid_protocol
2026-11-11 10:52 UTCIPV6Health announceHTTP 200Invalid protocol responseNo28 msinvalid_protocol
2026-11-11 10:52 UTCIPV4Health announceHTTP 200Invalid protocol responseNo32 msinvalid_protocol
2026-11-11 10:21 UTCIPV6Health announceHTTP 200Invalid protocol responseNo32 msinvalid_protocol
2026-11-11 10:21 UTCIPV4Health announceHTTP 200Invalid protocol responseNo31 msinvalid_protocol
2026-11-11 09:50 UTCIPV6Health announceHTTP 200Invalid protocol responseNo27 msinvalid_protocol
2026-11-11 09:50 UTCIPV4Health announceHTTP 200Invalid protocol responseNo21 msinvalid_protocol
2026-11-11 09:20 UTCIPV6Health announceHTTP 200Invalid protocol responseNo38 msinvalid_protocol
2026-11-11 09:20 UTCIPV4Health announceHTTP 200Invalid protocol responseNo39 msinvalid_protocol
2026-11-11 08:49 UTCIPV6Health announceHTTP 200Invalid protocol responseNo39 msinvalid_protocol
2026-11-11 08:49 UTCIPV4Health announceHTTP 200Invalid protocol responseNo31 msinvalid_protocol
2026-11-11 08:18 UTCIPV6Health announceHTTP 200Invalid protocol responseNo34 msinvalid_protocol
2026-11-11 08:18 UTCIPV4Health announceHTTP 200Invalid protocol responseNo26 msinvalid_protocol
2026-11-11 07:48 UTCIPV6Health announceHTTP 200Invalid protocol responseNo27 msinvalid_protocol
2026-11-11 07:48 UTCIPV4Health announceHTTP 200Invalid protocol responseNo38 msinvalid_protocol
2026-11-11 07:17 UTCIPV6Health announceHTTP 200Invalid protocol responseNo32 msinvalid_protocol
2026-11-11 07:17 UTCIPV4Health announceHTTP 200Invalid protocol responseNo39 msinvalid_protocol
2026-11-11 06:47 UTCIPV6Health announceHTTP 200Invalid protocol responseNo37 msinvalid_protocol
2026-11-11 06:47 UTCIPV4Health announceHTTP 200Invalid protocol responseNo32 msinvalid_protocol
2026-11-11 06:15 UTCIPV6Health announceHTTP 200Invalid protocol responseNo40 msinvalid_protocol
2026-11-11 06:15 UTCIPV4Health announceHTTP 200Invalid protocol responseNo38 msinvalid_protocol
2026-11-11 05:45 UTCIPV6Health announceHTTP 200Invalid protocol responseNo69 msinvalid_protocol
2026-11-11 05:45 UTCIPV4Health announceHTTP 200Invalid protocol responseNo59 msinvalid_protocol
2026-11-11 05:14 UTCIPV6Health announceHTTP 200Invalid protocol responseNo48 msinvalid_protocol
2026-11-11 05:14 UTCIPV4Health announceHTTP 200Invalid protocol responseNo32 msinvalid_protocol
2026-11-11 04:43 UTCIPV6Health announceHTTP 200Invalid protocol responseNo38 msinvalid_protocol
2026-11-11 04:43 UTCIPV4Health announceHTTP 200Invalid protocol responseNo43 msinvalid_protocol
2026-11-11 04:12 UTCIPV6Health announceHTTP 200Invalid protocol responseNo37 msinvalid_protocol
2026-11-11 04:12 UTCIPV4Health announceHTTP 200Invalid protocol responseNo38 msinvalid_protocol
2026-11-11 03:41 UTCIPV6Health announceHTTP 200Invalid protocol responseNo43 msinvalid_protocol
2026-11-11 03:41 UTCIPV4Health announceHTTP 200Invalid protocol responseNo51 msinvalid_protocol
2026-11-11 03:11 UTCIPV6Health announceHTTP 200Invalid protocol responseNo142 msinvalid_protocol
2026-11-11 03:11 UTCIPV4Health announceHTTP 200Invalid protocol responseNo53 msinvalid_protocol
2026-11-11 02:40 UTCIPV6Health announceHTTP 200Invalid protocol responseNo42 msinvalid_protocol
2026-11-11 02:40 UTCIPV4Health announceHTTP 200Invalid protocol responseNo48 msinvalid_protocol
2026-11-11 02:10 UTCIPV6Health announceHTTP 200Invalid protocol responseNo35 msinvalid_protocol
2026-11-11 02:10 UTCIPV4Health announceHTTP 200Invalid protocol responseNo40 msinvalid_protocol
2026-11-11 01:39 UTCIPV6Health announceHTTP 200Invalid protocol responseNo42 msinvalid_protocol
2026-11-11 01:39 UTCIPV4Health announceHTTP 200Invalid protocol responseNo52 msinvalid_protocol
2026-11-11 01:09 UTCIPV6Health announceHTTP 200Invalid protocol responseNo52 msinvalid_protocol
2026-11-11 01:09 UTCIPV4Health announceHTTP 200Invalid protocol responseNo40 msinvalid_protocol
2026-11-11 00:39 UTCIPV6Health announceHTTP 200Invalid protocol responseNo42 msinvalid_protocol
2026-11-11 00:39 UTCIPV4Health announceHTTP 200Invalid protocol responseNo46 msinvalid_protocol
2026-11-11 00:08 UTCIPV6Health announceHTTP 200Invalid protocol responseNo30 msinvalid_protocol
2026-11-11 00:08 UTCIPV4Health announceHTTP 200Invalid protocol responseNo43 msinvalid_protocol
2026-11-10 23:38 UTCIPV6Health announceHTTP 200Invalid protocol responseNo44 msinvalid_protocol
2026-11-10 23:38 UTCIPV4Health announceHTTP 200Invalid protocol responseNo42 msinvalid_protocol
2026-11-10 23:07 UTCIPV6Health announceHTTP 200Invalid protocol responseNo33 msinvalid_protocol
2026-11-10 23:07 UTCIPV4Health announceHTTP 200Invalid protocol responseNo44 msinvalid_protocol
2026-11-10 22:37 UTCIPV6Health announceHTTP 200Invalid protocol responseNo39 msinvalid_protocol
2026-11-10 22:37 UTCIPV4Health announceHTTP 200Invalid protocol responseNo49 msinvalid_protocol
2026-11-10 22:07 UTCIPV6Health announceHTTP 200Invalid protocol responseNo65 msinvalid_protocol
2026-11-10 22:07 UTCIPV4Health announceHTTP 200Invalid protocol responseNo42 msinvalid_protocol
2026-11-10 21:37 UTCIPV6Health announceHTTP 200Invalid protocol responseNo31 msinvalid_protocol
2026-11-10 21:37 UTCIPV4Health announceHTTP 200Invalid protocol responseNo40 msinvalid_protocol
2026-11-10 21:06 UTCIPV6Health announceHTTP 200Invalid protocol responseNo33 msinvalid_protocol
2026-11-10 21:06 UTCIPV4Health announceHTTP 200Invalid protocol responseNo45 msinvalid_protocol

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