← List

TRACKER DETAIL

tr.nyacat.pw

Tracker URL
IPV4 · FailedHTTP 200 · Invalid protocol responseChecked: 2026-11-11 17:46 UTC
IPV6 · FailedHTTP 200 · Invalid protocol responseChecked: 2026-11-11 17:46 UTC

EVIDENCE

Observed evidence

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

24h announce success0.0%0 / 80
24h protocol reply0.0%0 / 80
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:07 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 17:46 UTCIPV6Health announceHTTP 200Invalid protocol responseNo246 msinvalid_protocol
2026-11-11 17:46 UTCIPV4Health announceHTTP 200Invalid protocol responseNo201 msinvalid_protocol
2026-11-11 17:15 UTCIPV6Health announceHTTP 200Invalid protocol responseNo199 msinvalid_protocol
2026-11-11 17:15 UTCIPV4Health announceHTTP 200Invalid protocol responseNo201 msinvalid_protocol
2026-11-11 16:44 UTCIPV6Health announceHTTP 200Invalid protocol responseNo197 msinvalid_protocol
2026-11-11 16:44 UTCIPV4Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 16:13 UTCIPV6Health announceHTTP 200Invalid protocol responseNo192 msinvalid_protocol
2026-11-11 16:13 UTCIPV4Health announceHTTP 200Invalid protocol responseNo202 msinvalid_protocol
2026-11-11 15:41 UTCIPV6Health announceHTTP 200Invalid protocol responseNo188 msinvalid_protocol
2026-11-11 15:41 UTCIPV4Health announceHTTP 200Invalid protocol responseNo182 msinvalid_protocol
2026-11-11 15:10 UTCIPV6Health announceHTTP 200Invalid protocol responseNo187 msinvalid_protocol
2026-11-11 15:10 UTCIPV4Health announceHTTP 200Invalid protocol responseNo190 msinvalid_protocol
2026-11-11 14:39 UTCIPV6Health announceHTTP 200Invalid protocol responseNo182 msinvalid_protocol
2026-11-11 14:38 UTCIPV4Health announceHTTP 200Invalid protocol responseNo190 msinvalid_protocol
2026-11-11 14:07 UTCIPV6Health announceHTTP 200Invalid protocol responseNo182 msinvalid_protocol
2026-11-11 14:07 UTCIPV4Health announceHTTP 200Invalid protocol responseNo185 msinvalid_protocol
2026-11-11 13:37 UTCIPV6Health announceHTTP 200Invalid protocol responseNo186 msinvalid_protocol
2026-11-11 13:37 UTCIPV4Health announceHTTP 200Invalid protocol responseNo188 msinvalid_protocol
2026-11-11 13:06 UTCIPV6Health announceHTTP 200Invalid protocol responseNo190 msinvalid_protocol
2026-11-11 13:06 UTCIPV4Health announceHTTP 200Invalid protocol responseNo181 msinvalid_protocol
2026-11-11 12:34 UTCIPV6Health announceHTTP 200Invalid protocol responseNo184 msinvalid_protocol
2026-11-11 12:34 UTCIPV4Health announceHTTP 200Invalid protocol responseNo186 msinvalid_protocol
2026-11-11 12:04 UTCIPV6Health announceHTTP 200Invalid protocol responseNo183 msinvalid_protocol
2026-11-11 12:04 UTCIPV4Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-11 11:32 UTCIPV6Health announceHTTP 200Invalid protocol responseNo187 msinvalid_protocol
2026-11-11 11:32 UTCIPV4Health announceHTTP 200Invalid protocol responseNo185 msinvalid_protocol
2026-11-11 11:02 UTCIPV6Health announceHTTP 200Invalid protocol responseNo184 msinvalid_protocol
2026-11-11 11:02 UTCIPV4Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-11 10:31 UTCIPV6Health announceHTTP 200Invalid protocol responseNo185 msinvalid_protocol
2026-11-11 10:31 UTCIPV4Health announceHTTP 200Invalid protocol responseNo189 msinvalid_protocol
2026-11-11 10:01 UTCIPV6Health announceHTTP 200Invalid protocol responseNo180 msinvalid_protocol
2026-11-11 10:01 UTCIPV4Health announceHTTP 200Invalid protocol responseNo188 msinvalid_protocol
2026-11-11 09:30 UTCIPV6Health announceHTTP 200Invalid protocol responseNo185 msinvalid_protocol
2026-11-11 09:30 UTCIPV4Health announceHTTP 200Invalid protocol responseNo184 msinvalid_protocol
2026-11-11 09:00 UTCIPV6Health announceHTTP 200Invalid protocol responseNo190 msinvalid_protocol
2026-11-11 09:00 UTCIPV4Health announceHTTP 200Invalid protocol responseNo192 msinvalid_protocol
2026-11-11 08:29 UTCIPV6Health announceHTTP 200Invalid protocol responseNo181 msinvalid_protocol
2026-11-11 08:29 UTCIPV4Health announce—Local network unavailableUnknownUnknownlocal_or_network_unknown
2026-11-11 07:59 UTCIPV6Health announceHTTP 200Invalid protocol responseNo183 msinvalid_protocol
2026-11-11 07:59 UTCIPV4Health announceHTTP 200Invalid protocol responseNo180 msinvalid_protocol
2026-11-11 07:28 UTCIPV6Health announceHTTP 200Invalid protocol responseNo186 msinvalid_protocol
2026-11-11 07:28 UTCIPV4Health announceHTTP 200Invalid protocol responseNo180 msinvalid_protocol
2026-11-11 06:57 UTCIPV6Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 06:57 UTCIPV4Health announceHTTP 200Invalid protocol responseNo189 msinvalid_protocol
2026-11-11 06:26 UTCIPV6Health announceHTTP 200Invalid protocol responseNo182 msinvalid_protocol
2026-11-11 06:26 UTCIPV4Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-11 05:54 UTCIPV6Health announceHTTP 200Invalid protocol responseNo197 msinvalid_protocol
2026-11-11 05:54 UTCIPV4Health announceHTTP 200Invalid protocol responseNo198 msinvalid_protocol
2026-11-11 05:24 UTCIPV6Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 05:24 UTCIPV4Health announceHTTP 200Invalid protocol responseNo211 msinvalid_protocol
2026-11-11 04:54 UTCIPV6Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 04:54 UTCIPV4Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 04:24 UTCIPV6Health announceHTTP 200Invalid protocol responseNo202 msinvalid_protocol
2026-11-11 04:24 UTCIPV4Health announceHTTP 200Invalid protocol responseNo224 msinvalid_protocol
2026-11-11 03:53 UTCIPV6Health announce—Local network unavailableUnknownUnknownlocal_or_network_unknown
2026-11-11 03:53 UTCIPV4Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 03:23 UTCIPV6Health announceHTTP 200Invalid protocol responseNo195 msinvalid_protocol
2026-11-11 03:23 UTCIPV4Health announceHTTP 200Invalid protocol responseNo196 msinvalid_protocol
2026-11-11 02:52 UTCIPV6Health announceHTTP 200Invalid protocol responseNo192 msinvalid_protocol
2026-11-11 02:52 UTCIPV4Health announceHTTP 200Invalid protocol responseNo225 msinvalid_protocol
2026-11-11 02:22 UTCIPV6Health announceHTTP 200Invalid protocol responseNo238 msinvalid_protocol
2026-11-11 02:22 UTCIPV4Health announceHTTP 200Invalid protocol responseNo223 msinvalid_protocol
2026-11-11 01:51 UTCIPV6Health announceHTTP 200Invalid protocol responseNo194 msinvalid_protocol
2026-11-11 01:51 UTCIPV4Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 01:20 UTCIPV6Health announceHTTP 200Invalid protocol responseNo188 msinvalid_protocol
2026-11-11 01:20 UTCIPV4Health announceHTTP 200Invalid protocol responseNo200 msinvalid_protocol
2026-11-11 00:49 UTCIPV6Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-11 00:49 UTCIPV4Health announceHTTP 200Invalid protocol responseNo194 msinvalid_protocol
2026-11-11 00:19 UTCIPV6Health announceHTTP 200Invalid protocol responseNo198 msinvalid_protocol
2026-11-11 00:19 UTCIPV4Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-10 23:48 UTCIPV6Health announceHTTP 200Invalid protocol responseNo266 msinvalid_protocol
2026-11-10 23:48 UTCIPV4Health announceHTTP 200Invalid protocol responseNo189 msinvalid_protocol
2026-11-10 23:17 UTCIPV6Health announceHTTP 200Invalid protocol responseNo187 msinvalid_protocol
2026-11-10 23:17 UTCIPV4Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-10 22:46 UTCIPV6Health announceHTTP 200Invalid protocol responseNo191 msinvalid_protocol
2026-11-10 22:46 UTCIPV4Health announceHTTP 200Invalid protocol responseNo187 msinvalid_protocol
2026-11-10 22:15 UTCIPV6Health announceHTTP 200Invalid protocol responseNo186 msinvalid_protocol
2026-11-10 22:15 UTCIPV4Health announceHTTP 200Invalid protocol responseNo196 msinvalid_protocol
2026-11-10 21:44 UTCIPV6Health announceHTTP 200Invalid protocol responseNo185 msinvalid_protocol
2026-11-10 21:44 UTCIPV4Health announceHTTP 200Invalid protocol responseNo200 msinvalid_protocol
2026-11-10 21:13 UTCIPV6Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-10 21:13 UTCIPV4Health announceHTTP 200Invalid protocol responseNo208 msinvalid_protocol

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