https://tracker.pmman.tech:443/announce

Is it down? No: up for 8h · last checked 35m ago

Up/Broken   Score 50 · 416 ms · Canada · Show in the table · Map · Follow

2 of its 4 published addresses don't answer

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.

How to fix it
What's wrong: IPv4 or IPv6 broken
How to fix it
Fixed something? Ask for a check now instead of waiting for the next one (once an hour per tracker).
Uptime, last 30 days
30 days agonow
Long-term uptime

Up 99.1% of the time over 59 days, since 2026-09-23.

2026-09-23: 100.0% up2026-09-24: 100.0% up2026-09-25: 100.0% up2026-09-26: 100.0% up2026-09-27: 100.0% up2026-09-28: 100.0% up2026-09-29: 100.0% up2026-09-30: 100.0% up2026-10-01: 100.0% up2026-10-02: 100.0% up2026-10-03: 100.0% up2026-10-04: 100.0% up2026-10-05: 100.0% up2026-10-06: 100.0% up2026-10-07: 100.0% up2026-10-08: 100.0% up2026-10-09: 100.0% up2026-10-10: 100.0% up2026-10-11: 100.0% up2026-10-12: 100.0% up2026-10-13: 100.0% up2026-10-14: 100.0% up2026-10-15: 100.0% up2026-10-16: 100.0% up2026-10-17: 100.0% up2026-10-18: 100.0% up2026-10-19: 75.0% up2026-10-20: 97.9% up2026-10-21: 100.0% up2026-10-22: 100.0% up2026-10-23: 100.0% up2026-10-24: 100.0% up2026-10-25: 100.0% up2026-10-26: 100.0% up2026-10-27: 100.0% up2026-10-28: 100.0% up2026-10-29: 100.0% up2026-10-30: 100.0% up2026-10-31: 100.0% up2026-11-01: 100.0% up2026-11-02: 100.0% up2026-11-03: 100.0% up2026-11-04: 100.0% up2026-11-05: 100.0% up2026-11-06: 100.0% up2026-11-07: 100.0% up2026-11-08: 100.0% up2026-11-09: 100.0% up2026-11-10: 100.0% up2026-11-11: 100.0% up2026-11-12: 100.0% up2026-11-13: 100.0% up2026-11-14: 95.8% up2026-11-15: 93.8% up2026-11-16: 100.0% up2026-11-17: 93.8% up2026-11-18: 100.0% up2026-11-19: 93.8% up2026-11-20: 95.8% up
2026-09-232026-11-20
MonthUptimeTypical 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 202699.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
035070010501400 now4d ago8d ago12d ago16d ago20d ago24d ago28d ago
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

Details
IP addresses
2606:4700:3032::6815:4772, 2606:4700:3036::ac43:9080, 172.67.144.128, 104.21.71.114
Network
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 agoIPv4 address confirmed dead
1h agois Up/Broken: its published IPv4 address is dead
4h agois Up/Slow: averages 435 ms across regions
7h agois 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 agowent Down (HTTP connection failed)
12h agoIPv4 address answering again
12h agois now Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
15h agoIPv4 address confirmed dead
15h agois now Up/Broken: its published IPv4 address is dead
17h agois 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 agowent Down (HTTP connection failed)
20h agoIPv4 address answering again
20h agois now Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
1d 3h agoIPv4 address confirmed dead
1d 3h agois now Up/Broken: its published IPv4 address is dead
1d 6h agois Up/Broken: its published addresses 104.21.71.114, 172.67.144.128 don't answer (it answers on its others)
1d 6h agois back Up after 16m down, but Up/Slow: averages 447 ms across regions
1d 6h agowent Down (HTTP connection failed)
2d 6h agois back Up after 16m down, but Up/Slow: averages 440 ms across regions
2d 6h agowent Down (HTTP connection failed)
2d 12h agois back Up after 16m down, but Up/Slow: averages 456 ms across regions
2d 12h agowent Down (HTTP connection failed)