← List

TRACKER DETAIL

tracker.foreverpirates.co

Tracker URL
IPV4 · FailedHTTP 200 · Invalid protocol responseChecked: 2026-11-11 17:43 UTC
IPV6 · FailedHTTP 200 · Invalid protocol responseChecked: 2026-11-11 17:43 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
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:43 UTCIPV6Health announceHTTP 200Invalid protocol responseNo206 msinvalid_protocol
2026-11-11 17:43 UTCIPV4Health announceHTTP 200Invalid protocol responseNo212 msinvalid_protocol
2026-11-11 17:12 UTCIPV6Health announceHTTP 200Invalid protocol responseNo225 msinvalid_protocol
2026-11-11 17:12 UTCIPV4Health announceHTTP 200Invalid protocol responseNo200 msinvalid_protocol
2026-11-11 16:42 UTCIPV6Health announceHTTP 200Invalid protocol responseNo203 msinvalid_protocol
2026-11-11 16:41 UTCIPV4Health announceHTTP 200Invalid protocol responseNo206 msinvalid_protocol
2026-11-11 16:11 UTCIPV6Health announceHTTP 200Invalid protocol responseNo219 msinvalid_protocol
2026-11-11 16:11 UTCIPV4Health announceHTTP 200Invalid protocol responseNo204 msinvalid_protocol
2026-11-11 15:40 UTCIPV6Health announceHTTP 200Invalid protocol responseNo201 msinvalid_protocol
2026-11-11 15:40 UTCIPV4Health announceHTTP 200Invalid protocol responseNo232 msinvalid_protocol
2026-11-11 15:10 UTCIPV6Health announceHTTP 200Invalid protocol responseNo217 msinvalid_protocol
2026-11-11 15:10 UTCIPV4Health announceHTTP 200Invalid protocol responseNo209 msinvalid_protocol
2026-11-11 14:38 UTCIPV6Health announceHTTP 200Invalid protocol responseNo234 msinvalid_protocol
2026-11-11 14:38 UTCIPV4Health announceHTTP 200Invalid protocol responseNo196 msinvalid_protocol
2026-11-11 14:07 UTCIPV6Health announceHTTP 200Invalid protocol responseNo214 msinvalid_protocol
2026-11-11 14:07 UTCIPV4Health announceHTTP 200Invalid protocol responseNo199 msinvalid_protocol
2026-11-11 13:36 UTCIPV6Health announceHTTP 200Invalid protocol responseNo194 msinvalid_protocol
2026-11-11 13:36 UTCIPV4Health announceHTTP 200Invalid protocol responseNo198 msinvalid_protocol
2026-11-11 13:05 UTCIPV6Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 13:05 UTCIPV4Health announceHTTP 200Invalid protocol responseNo204 msinvalid_protocol
2026-11-11 12:34 UTCIPV6Health announceHTTP 200Invalid protocol responseNo201 msinvalid_protocol
2026-11-11 12:34 UTCIPV4Health announceHTTP 200Invalid protocol responseNo200 msinvalid_protocol
2026-11-11 12:03 UTCIPV6Health announceHTTP 200Invalid protocol responseNo238 msinvalid_protocol
2026-11-11 12:03 UTCIPV4Health announceHTTP 200Invalid protocol responseNo244 msinvalid_protocol
2026-11-11 11:32 UTCIPV6Health announceHTTP 200Invalid protocol responseNo193 msinvalid_protocol
2026-11-11 11:32 UTCIPV4Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 11:01 UTCIPV6Health announceHTTP 200Invalid protocol responseNo205 msinvalid_protocol
2026-11-11 11:01 UTCIPV4Health announceHTTP 200Invalid protocol responseNo212 msinvalid_protocol
2026-11-11 10:31 UTCIPV6Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 10:31 UTCIPV4Health announceHTTP 200Invalid protocol responseNo214 msinvalid_protocol
2026-11-11 10:01 UTCIPV6Health announceHTTP 200Invalid protocol responseNo210 msinvalid_protocol
2026-11-11 10:01 UTCIPV4Health announceHTTP 200Invalid protocol responseNo212 msinvalid_protocol
2026-11-11 09:30 UTCIPV6Health announceHTTP 200Invalid protocol responseNo199 msinvalid_protocol
2026-11-11 09:30 UTCIPV4Health announceHTTP 200Invalid protocol responseNo211 msinvalid_protocol
2026-11-11 08:59 UTCIPV6Health announceHTTP 200Invalid protocol responseNo208 msinvalid_protocol
2026-11-11 08:59 UTCIPV4Health announceHTTP 200Invalid protocol responseNo204 msinvalid_protocol
2026-11-11 08:29 UTCIPV6Health announceHTTP 200Invalid protocol responseNo192 msinvalid_protocol
2026-11-11 08:29 UTCIPV4Health announceHTTP 200Invalid protocol responseNo215 msinvalid_protocol
2026-11-11 07:59 UTCIPV6Health announceHTTP 200Invalid protocol responseNo198 msinvalid_protocol
2026-11-11 07:59 UTCIPV4Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 07:28 UTCIPV6Health announceHTTP 200Invalid protocol responseNo187 msinvalid_protocol
2026-11-11 07:28 UTCIPV4Health announceHTTP 200Invalid protocol responseNo208 msinvalid_protocol
2026-11-11 06:57 UTCIPV6Health announceHTTP 200Invalid protocol responseNo211 msinvalid_protocol
2026-11-11 06:57 UTCIPV4Health announceHTTP 200Invalid protocol responseNo212 msinvalid_protocol
2026-11-11 06:26 UTCIPV6Health announceHTTP 200Invalid protocol responseNo251 msinvalid_protocol
2026-11-11 06:26 UTCIPV4Health announceHTTP 200Invalid protocol responseNo202 msinvalid_protocol
2026-11-11 05:55 UTCIPV6Health announceHTTP 200Invalid protocol responseNo214 msinvalid_protocol
2026-11-11 05:55 UTCIPV4Health announceHTTP 200Invalid protocol responseNo208 msinvalid_protocol
2026-11-11 05:25 UTCIPV6Health announceHTTP 200Invalid protocol responseNo216 msinvalid_protocol
2026-11-11 05:25 UTCIPV4Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 04:54 UTCIPV6Health announceHTTP 200Invalid protocol responseNo216 msinvalid_protocol
2026-11-11 04:54 UTCIPV4Health announceHTTP 200Invalid protocol responseNo197 msinvalid_protocol
2026-11-11 04:24 UTCIPV6Health announceHTTP 200Invalid protocol responseNo242 msinvalid_protocol
2026-11-11 04:24 UTCIPV4Health announceHTTP 200Invalid protocol responseNo199 msinvalid_protocol
2026-11-11 03:54 UTCIPV6Health announceHTTP 200Invalid protocol responseNo220 msinvalid_protocol
2026-11-11 03:54 UTCIPV4Health announceHTTP 200Invalid protocol responseNo207 msinvalid_protocol
2026-11-11 03:23 UTCIPV6Health announceHTTP 200Invalid protocol responseNo264 msinvalid_protocol
2026-11-11 03:23 UTCIPV4Health announceHTTP 200Invalid protocol responseNo218 msinvalid_protocol
2026-11-11 02:53 UTCIPV6Health announceHTTP 200Invalid protocol responseNo203 msinvalid_protocol
2026-11-11 02:53 UTCIPV4Health announceHTTP 200Invalid protocol responseNo198 msinvalid_protocol
2026-11-11 02:22 UTCIPV6Health announceHTTP 200Invalid protocol responseNo251 msinvalid_protocol
2026-11-11 02:22 UTCIPV4Health announceHTTP 200Invalid protocol responseNo232 msinvalid_protocol
2026-11-11 01:51 UTCIPV6Health announceHTTP 200Invalid protocol responseNo277 msinvalid_protocol
2026-11-11 01:51 UTCIPV4Health announceHTTP 200Invalid protocol responseNo202 msinvalid_protocol
2026-11-11 01:21 UTCIPV6Health announceHTTP 200Invalid protocol responseNo220 msinvalid_protocol
2026-11-11 01:21 UTCIPV4Health announceHTTP 200Invalid protocol responseNo225 msinvalid_protocol
2026-11-11 00:50 UTCIPV6Health announceHTTP 200Invalid protocol responseNo214 msinvalid_protocol
2026-11-11 00:50 UTCIPV4Health announceHTTP 200Invalid protocol responseNo209 msinvalid_protocol
2026-11-11 00:19 UTCIPV6Health announceHTTP 200Invalid protocol responseNo213 msinvalid_protocol
2026-11-11 00:19 UTCIPV4Health announceHTTP 200Invalid protocol responseNo214 msinvalid_protocol
2026-11-10 23:48 UTCIPV6Health announceHTTP 200Invalid protocol responseNo311 msinvalid_protocol
2026-11-10 23:48 UTCIPV4Health announceHTTP 200Invalid protocol responseNo215 msinvalid_protocol
2026-11-10 23:17 UTCIPV6Health announceHTTP 200Invalid protocol responseNo210 msinvalid_protocol
2026-11-10 23:17 UTCIPV4Health announceHTTP 200Invalid protocol responseNo226 msinvalid_protocol
2026-11-10 22:46 UTCIPV6Health announceHTTP 200Invalid protocol responseNo196 msinvalid_protocol
2026-11-10 22:46 UTCIPV4Health announceHTTP 200Invalid protocol responseNo204 msinvalid_protocol
2026-11-10 22:16 UTCIPV6Health announceHTTP 200Invalid protocol responseNo224 msinvalid_protocol
2026-11-10 22:16 UTCIPV4Health announceHTTP 200Invalid protocol responseNo214 msinvalid_protocol
2026-11-10 21:44 UTCIPV6Health announceHTTP 200Invalid protocol responseNo199 msinvalid_protocol
2026-11-10 21:44 UTCIPV4Health announceHTTP 200Invalid protocol responseNo212 msinvalid_protocol
2026-11-10 21:13 UTCIPV6Health announceHTTP 200Invalid protocol responseNo226 msinvalid_protocol
2026-11-10 21:13 UTCIPV4Health announceHTTP 200Invalid protocol responseNo277 msinvalid_protocol

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