+ A BitTorrent tracker is a crucial piece of infrastructure that coordinates peers in the + swarm. Without one, clients cannot discover each other and the torrent effectively becomes + unreachable. While modern BitTorrent clients support peer discovery through DHT, PEX, and + magnet links, having a healthy set of working trackers in your torrent file or client + configuration significantly improves download speeds and reliability. +
++ The challenge is that public trackers come and go — some disappear, others change + addresses, and new ones emerge. Keeping your tracker list up to date is an ongoing task. + Fortunately, several community-maintained resources do this work for you. This article + surveys the most reliable sources for finding active public BitTorrent tracker lists. +
+ ++ The most popular public tracker list on the internet. Maintained by Diego Heras (ngosang), + this GitHub repository is updated daily by an automated bot that tests each tracker and + sorts them by popularity and latency. It is the go-to source for anyone who needs a + curated list of working public trackers. +
+The repository provides several distinct lists:
+ +| List | +Trackers | +Description | +
|---|---|---|
trackers_best.txt |
+ 20 | +Top-performing trackers with the best uptime and latency | +
trackers_all.txt |
+ 76 | +All active trackers, any protocol, sorted by performance | +
trackers_all_udp.txt |
+ 43 | +UDP-only trackers | +
trackers_all_http.txt |
+ 19 | +HTTP-only trackers | +
trackers_all_https.txt |
+ 14 | +HTTPS-only trackers | +
trackers_all_ws.txt |
+ 1 | +WebSocket (WebTorrent) trackers | +
trackers_all_i2p.txt |
+ 13 | +I2P trackers (requires I2P router) | +
trackers_all_yggdrasil.txt |
+ 1 | +Yggdrasil network trackers | +
trackers_all_ip.txt |
+ 47 | +All trackers with IP addresses instead of domains (avoids DNS issues) | +
+ The bot automatically removes trackers that point to the same domain or IP address, and it + maintains a blacklist of known unreliable entries. Each list is also available through CDN mirrors (jsDelivr and + GitHub Pages), making them easy to consume programmatically. +
+ ++ You can add the trackers to your torrent client manually, or use one of the many community + scripts that automate the process. Popular options include: +
+.torrent files
+ + You can also fetch the lists directly from the raw GitHub URLs or the CDN mirrors and + incorporate them into your own tooling. +
+ ++ newTrackon is a meta-tracker service that continuously monitors the uptime of public + BitTorrent trackers. It probes each tracker every few minutes and publishes the results, + including an uptime percentage based on the last 1000 checks. Unlike ngosang's list, which + is a static snapshot, newTrackon provides a live view of tracker health. +
+Key features that make newTrackon particularly useful for tracker list curation:
++ For a practical walkthrough on submitting your own tracker to newTrackon, including how to + handle the one-tracker-per-IP constraint and configure BEP34 DNS records, see our + dedicated guide: + Submitting Trackers to newTrackon. +
+ ++ Another well-maintained and frequently updated tracker list. The project aggregates + trackers from multiple upstream sources — including ngosang/trackerslist, newTrackon, and + several others — into a single curated collection. It is a good alternative if you want a + broader set of trackers without having to combine lists yourself. +
+The available lists include:
+| List | +Trackers | +Description | +
|---|---|---|
best.txt |
+ 80 | +Top-performing trackers across all protocols | +
all.txt |
+ 129 | +Complete collection from all upstream sources | +
http.txt |
+ 58 | +HTTP and HTTPS trackers only | +
nohttp.txt |
+ 70 | +Non-HTTP trackers (UDP and WebSocket) | +
+ The Torrust project maintains a + community discussion on GitHub where tracker operators and users share working public trackers. This is a good + place to find new trackers that may not yet appear in the larger automated lists, as well as + to discuss tracker reliability and configuration with other community members. +
+ ++ Most modern BitTorrent clients include a default list of public trackers that they add to + torrents automatically. These lists are maintained by the client developers and are often + a good starting point: +
++ With multiple sources available, here are some factors to consider when deciding which + tracker list to use: +
+ +| Factor | +ngosang/trackerslist | +newTrackon | +XIU2/TrackersListCollection | +
|---|---|---|---|
| Update frequency | +Daily (automated bot) | +Continuous (live probes) | +Daily (aggregates multiple sources) | +
| Protocol filters | +Separate lists per protocol | +Single list, protocol varies | +HTTP-only, non-HTTP, and combined | +
| Uptime tracking | +No (presence only) | +Yes (percentage + history) | +No (aggregation only) | +
| Client-ready | +Raw text files | +95%+ uptime filter at /list | +Raw text files | +
| Submit new trackers | +Via GitHub issues | +Web form with live validation | +Closed (no longer accepts submissions) | +
| IP-based lists | +Yes (avoids DNS issues) | +No | +No | +
| Alternative networks | +I2P, Yggdrasil, WebSocket | +Mainstream only | +Mainstream only | +
+ For most users, ngosang/trackerslist is the best choice: it is well + maintained, offers per-protocol lists, and provides IP-based alternatives for environments + with DNS problems. Use newTrackon when you care about long-term uptime + data or want to verify the reliability of a specific tracker before adding it to your + configuration. + XIU2/TrackersListCollection is a convenient option if you want a broader set + of trackers aggregated from multiple sources with minimal effort. +
+ ++ If you run a torrent client on a server (for example, a seedbox or a home NAS), you can + automate the process of keeping your tracker list fresh. A typical approach: +
++ If you run a Torrust Tracker, you can enable both UDP and HTTP/S protocols simultaneously by adding multiple server + blocks in the configuration file: +
+ +[[udp_trackers]]
+bind_address = "0.0.0.0:6969"
+
+[[http_trackers]]
+bind_address = "0.0.0.0:7070"
+
+
+ Each protocol gets its own announce URL (for example udp://your-server:6969/announce
+ and https://your-server:7070/announce). You can add both to your torrent
+ files or client configuration. The tracker also supports an
+ external_ip
+ config option: when a peer announces from the same machine (127.0.0.1), the
+ tracker replaces their loopback address with this public IP so other peers in the swarm
+ can reach them.
+
+ Keeping your tracker list up to date is essential for a healthy BitTorrent experience. + Whether you use ngosang's comprehensive daily-updated lists, newTrackon's live uptime + monitoring, or a combination of both, these community resources save you from the tedious + task of manually testing and updating trackers. +
++ The ecosystem around public tracker lists is active and well maintained. Bookmark these + sources, set up automation if you run a server, and check back periodically — the list of + working trackers changes every day. +
+