udp://opentracker2.lain.moscow:6969/announce

Is it down? No: up for 9h · last checked 58m ago

Up/Unreliable   Score 68 · 205 ms · Russia · Show in the table · Map · Follow

What's wrong: Drops out (Up/Unreliable, Up/Junk)
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 24 days
24 days agonow
Last 48 hours
48 h agonow
Latency by region
0100200300400 now4d ago8d ago12d ago16d ago20d ago24d ago
From Oceania: 352 ms nowFrom Asia: 278 ms nowFrom Europe: 49 ms nowFrom North America: 141 ms now

Announce round trip, in ms, from each place latency is measured. Recorded every 2 hours, kept 30 days.

Score
Recent availability83.7%Stability× 84.5%Reliability score= 71Latency penalty−2Score69Last 7 daysanswered 77.1% of checks · 14 outagesSince addedanswered 89.9% over 24.4 days · longest outage 21.0 h
The tracker's own stats
opentracker2.lain.moscow  read 6h ago · opentracker
uptime        26.2 h
--------------------------------
torrents      782.7k  ▲349.3k
peers           1.7M  ▲735.2k
seeds         169.1k  ▲57.9k
leechers        1.5M  ▲677.3k
completed      67.7k  ▲65.0k
--------------------------------
requests      147.5M  ▲143.7M
announces      81.6M  ▲79.2M
scrapes         1.0M  ▲982.6k
refused        30.8M  ▲30.5M
refused %      20.9%  last 24 h 21.2%
requests/s      1662

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.

Details
IP addresses
46.188.15.49
Network
2COM
Located in
Russia
IPv4 / IPv6
ok / not published
Peer test
pass (passed 6 of the last 6)
Last peer test saw
IPv4 (58m 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 9h ago, asking 10 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 58m ago
Announce interval
27 min
Added
28-10-2026 (24d 11h ago)
Same operator as
udp://opentracker.lain.moscow:6969/announce
Recent events
9h agois back Up after 17m down, but Up/Unreliable: score 68, under 90
9h agowent Down (UDP error: [Errno -3] Try again)
17h agois back Up after 16m down, but Up/Unreliable: score 68, under 90
17h agowent Down (UDP error: [Errno -3] Try again)
19h agois back Up after 17m down, but Up/Unreliable: score 69, under 90
19h agowent Down (UDP error: [Errno -3] Try again)
1d 5h agois back Up after 14m down, but Up/Unreliable: score 68, under 90
1d 5h agowent Down (UDP error: [Errno -3] Try again)
1d 6h agois back Up after 19h down, but Up/Unreliable: score 69, under 90
2d 2h agowent Down (UDP timeout)
2d 2h agois back Up after 16m down, but Up/Unreliable: score 74, under 90
2d 3h agowent Down (UDP timeout)
2d 3h agois back Up after 13m down, but Up/Unreliable: score 75, under 90
2d 3h agowent Down (UDP timeout)
2d 3h agois back Up after 32m down, but Up/Unreliable: score 75, under 90
2d 4h agowent Down (UDP timeout)
2d 4h agois back Up after 15m down, but Up/Unreliable: score 75, under 90
2d 4h agowent Down (UDP timeout)
2d 5h agois back Up after 44m down, but Up/Unreliable: score 75, under 90
2d 5h agowent Down (UDP timeout - answers from other regions)
2d 6h agois back Up after 30m down, but Up/Unreliable: score 76, under 90
2d 6h agowent Down (UDP timeout)
2d 7h agois back Up after 1h down, but Up/Unreliable: score 77, under 90
2d 8h agowent Down (UDP timeout)
2d 8h agois back Up after 49m down, but Up/Unreliable: score 77, under 90
2d 9h agowent Down (UDP timeout)
2d 9h agois back Up after 1h down, but Up/Unreliable: score 78, under 90
2d 11h agowent Down (UDP error: [Errno -3] Try again)
2d 11h agois back Up after 14m down, but Up/Unreliable: score 79, under 90
2d 11h agowent Down (UDP timeout)