104.21.71.114 (IPv4, last answer 3h ago), 172.67.144.128 (IPv4, last answer 3h ago).
The tracker works on its other addresses, but every client that picks these
can't reach it. If it's an old address, remove it from the tracker's DNS records.
Its IPv4 addresses 172.67.144.128, 104.21.71.114 didn't answer in 4 checks in a row, while IPv6 did.
IPv4 answered in 16 of its last 20 checks.
Up/Junk or Up/Broken for 1 day. 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 28 days left to fix it.
Up 99.1% of the time over 59 days, since 2026-09-23.
2026-09-232026-11-20
Month
Uptime
Typical latency
Nov 2026 (20 d)
98.7%
Oceania 364 ms · Asia 523 ms · Europe 375 ms · North America 413 ms · South America 452 ms
Oct 2026
99.1%
Oceania 362 ms · Asia 556 ms · Europe 374 ms · North America 403 ms
Sep 2026 (8 d)
100.0%
–
Last 48 hours
48 h agonow
Latency by region
From Oceania: 359 ms nowFrom Asia: 477 ms nowFrom Europe: 375 ms nowFrom North America: 419 ms nowFrom South America: 452 ms now
Announce round trip, in ms, from each place latency is measured. Recorded every 2 hours, kept 30 days.
Score
Recent availability97.3%Stability× 93.8%Reliability score= 91Latency penalty−13Quality capheld to 50 for failing a quality test (see Status)Score50Last 7 daysanswered 95.5% of checks · 9 outagesSince addedanswered 98.7% over 30.0 days · longest outage 1.0 h
The tracker's own stats
It doesn't publish a stats page this site can read (asked https://tracker.pmman.tech:443 for /stats, /stats.json, /metrics 8d 3h ago; asked again in 22 days). About this
Cloudflare, Inc., Cloudflare, Inc., Cloudflare, Inc., Cloudflare, Inc.
Located in
Canada, Canada, Canada, Canada
Addresses
104.21.71.114 (IPv4: not answering, last answer 3h ago) 172.67.144.128 (IPv4: not answering, last answer 3h ago) 2606:4700:3032::6815:4772 (IPv6) 2606:4700:3036::ac43:9080 (IPv6)
IPv4 / IPv6
dead / ok IPv4 answered 16 of the last 20 checks
Peer test
IPv4: pass (passed 6 of 6) · IPv6: pass (passed 6 of 6)
Last peer test saw
IPv4 (3h ago): our second test client was handed our first one, with its real address: clients find each other.
IPv6 (3h ago): our second test client was handed our first one, with its real address: clients find each other.
Delayed peer test
IPv4: passed 6 of 6; last 4h ago, asking 12 min after our first client announced: it was still handed out.
IPv6: passed 6 of 6; last 11h ago, asking 12 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
60 min, last 35m ago
Announce interval
31 min
Added
23-9-2026 (58d 21h ago)
Recent events
1h ago
IPv4 address confirmed dead
1h ago
is Up/Broken: its published IPv4 address is dead
4h ago
is Up/Slow: averages 435 ms across regions
7h ago
is back Up after 18m down, but Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
8h ago
went Down (HTTP connection failed)
12h ago
IPv4 address answering again
12h ago
is now Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
15h ago
IPv4 address confirmed dead
15h ago
is now Up/Broken: its published IPv4 address is dead
17h ago
is back Up after 17m down, but Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
17h ago
went Down (HTTP connection failed)
20h ago
IPv4 address answering again
20h ago
is now Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
1d 3h ago
IPv4 address confirmed dead
1d 3h ago
is now Up/Broken: its published IPv4 address is dead
1d 6h ago
is Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
1d 6h ago
is back Up after 16m down, but Up/Slow: averages 447 ms across regions
1d 6h ago
went Down (HTTP connection failed)
2d 6h ago
is back Up after 16m down, but Up/Slow: averages 440 ms across regions
2d 6h ago
went Down (HTTP connection failed)
2d 12h ago
is back Up after 16m down, but Up/Slow: averages 456 ms across regions