dht44 — Live BitTorrent Mainline DHT Dashboard

Live snapshot

peers: 164637 observed (v4 120066 · v6 44571)
queries: 31359235 total · 544/min
infohashes: 2428120
uptime: 50d 7h

Top peer countries

US · 20406
CN · 18285
KR · 13875
NL · 13095
FR · 11183
JP · 10708
RU · 10225
CA · 8459
DE · 8354
GB · 4160
BR · 3750
IN · 3239
TW · 3210
AU · 2216
HK · 1703

Top BitTorrent clients (BEP 20 v-string prefixes)

4c54012f · 26353
4c540100 · 11823
4c540102 · 8094
4c54020b · 7617
5554b896 · 4825
4c54020a · 4067
58444854 · 3463
4c54012e · 3452
4c540207 · 3398
4c540010 · 3331
6c740d60 · 2607
4a432d78 · 2549

Real-time observation of the public BitTorrent Mainline DHT. The dashboard is a single-page React app — the interactive peer / queries / infohashes / bep44 / 3D graph tabs require JavaScript. Below is a static description of what the page presents and links into the parts of the site that don't need JS.

What this page tracks

Peer counts — total unique (ip, port) observed since the observation database opened, split by IPv4 and IPv6, plus liveness windows (alive in last 6 hours, last 24 hours, stale beyond that). IPs are redacted to /24 (IPv4) and /48 (IPv6) before any exposure.
Query rate — DHT KRPC traffic observed in the last 60 seconds: ping, find_node, get_peers, announce_peer, plus BEP 51 sample_infohashes.
Top BitTorrent clients — distribution by BEP 20 v-string prefix. Commonly libtorrent, µTorrent, qBittorrent, Transmission, Deluge, XD, JC, plus a long tail of forks and embedded clients.
Top peer countries — GeoIP attribution via MaxMind GeoLite2. Typically led by China, United States, Japan, Taiwan, France, Russia, Netherlands, Canada, Spain, United Kingdom, India, Germany, South Korea, Brazil, Hong Kong.
Infohash discovery sources — how each infohash was first seen: get_peers query (asked-about), BEP 51 sample_infohashes response, or as a find_node target.
Multi-signal classifier — per-peer label of ok / crawler / monitor / honeypot, derived from reply ratio, BEP 42 secure-id check, BEP 51 support, and v-string anomalies.
Peer graph — 3D force-directed visualization of who returns whom in find_node replies, restricted to the top-N internally-connected nodes by in-result degree.
Uptime — time since the first peer observation in the current observation database. The crawler runs continuously; the database persists across daemon restarts.

JSON APIs (no JavaScript required)

Every panel above is backed by a JSON endpoint. Crawlers and scripts can read the live data directly:

/api/stats — top-line counts and rates
/api/peers — observed peers with geo + classifier
/api/queries — recent KRPC queries
/api/infohashes — observed infohashes with discovery source
/api/country-stats — peer count by ISO 2-letter country
/api/client-stats — peer count by BEP 20 v-string
/api/graph — peer graph nodes + links