What's wrong: Hands out an address nobody can reach
Over IPv6 it sees every client as 172.17.0.1, a private address, and hands that out instead of their real address, so nobody can connect to those peers. That almost always means Docker: traffic reaches the tracker through Docker's port proxy, which replaces each client's address with the container's gateway.
Over IPv6 it doesn't share peers: passed 0 of its last 6 IPv6 peer tests, while IPv4 passed 6 of 6. Clients on IPv6 get no peers from it.
Up/Junk or Up/Broken for 3 days. Trackers that stay Up/Junk (score under 50) or Up/Broken (an address that doesn't answer, a dead IPv4 or IPv6 family, one family not sharing peers, or separate servers not sharing swarms) for 30 days in a row are removed and banned: about 26 days left to fix it.
Up 81.8% of the time over 59 days, since 2026-09-23.
2026-09-232026-11-20
Month
Uptime
Typical latency
Nov 2026 (20 d)
77.2%
Oceania 314 ms · Asia 254 ms · Europe 31 ms · North America 138 ms · South America 162 ms
Oct 2026
83.3%
Oceania 313 ms · Asia 256 ms · Europe 31 ms · North America 131 ms
Sep 2026 (8 d)
87.8%
–
Last 48 hours
48 h agonow
Latency by region
From Oceania: 313 ms nowFrom Asia: 177 ms nowFrom Europe: 30 ms nowFrom North America: 128 ms nowFrom South America: 162 ms now
Announce round trip, in ms, from each place latency is measured. Recorded every 2 hours, kept 30 days.
Score
Recent availability73.4%Stability× 97.4%Reliability score= 72Latency penaltyunder 1Quality capheld to 50 for failing a quality test (see Status)Score50Last 7 daysanswered 54.2% of checks · 3 outagesSince addedanswered 79.4% over 30.0 days · longest outage 99.0 h
What the tracker's own public stats page says, read once a day: reported by the tracker, not measured by this site. ▲▼ are the change over the last 24 hours. Torrent counts include made-up hashes some clients spray at trackers. –: not reported.
IPv4: pass (passed 6 of 6) · IPv6: fail (passed 0 of 6)
Last peer test saw
IPv4 (11m ago): our second test client was handed our first one, with its real address: clients find each other.
IPv6 (11m ago): our second test client was handed our first one as 172.17.0.1, a private address nobody can connect to. That almost always means Docker: traffic reaches the tracker through Docker's port proxy, which replaces each client's address with the container's gateway.
Delayed peer test
IPv4: passed 6 of 6; last 8h ago, asking 8 min after our first client announced: it was still handed out.
About once a day, the same test with a wait, like real clients that announce minutes apart. For information only for now.
Checked every
15 min, last 11m ago
Announce interval
31 min
Added
23-9-2026 (58d 21h ago)
Recent events
5h ago
is back Up after 16m down, but Up/Broken: its IPv6 side doesn't share peers (3+ of its last 6 IPv6 peer tests failed)
6h ago
went Down (UDP error: [Errno -3] Try again)
2d 7h ago
is back Up after 16m down, but Up/Broken: its IPv6 side doesn't share peers (3+ of its last 6 IPv6 peer tests failed)