ngosang/trackerslist: a public BitTorrent trackers list
/trackerslist
ngosang/trackerslist is a daily-updated collection of public BitTorrent tracker URLs, split into files by protocol and quality tier. Reach for the trackers_best file when you want a quick set of active trackers to paste into a torrent client or magnet link; skip the whole repo if you're already on a private tracker or don't understand what a tracker even does.
What is ngosang/trackerslist?
ngosang/trackerslist is a plain-text repository of public BitTorrent tracker URLs, arranged into multiple .txt files by protocol (UDP, HTTP, HTTPS, WebSocket) and by curation tier (best vs. all). Each file is one tracker URL per line, meant to be copied into a torrent client's tracker list or appended to a magnet link. There's no code to install or run.
Available tracker lists
- ✓trackers_best: 20 trackers, sorted by popularity and latency, for a short list that just works.
- ✓trackers_all: 114 trackers across every protocol, for broader coverage in a single file.
- ✓Protocol-specific files — trackers_all_udp (50), trackers_all_http (48), trackers_all_https (16), trackers_all_ws (3) — for clients that only speak one protocol.
- ✓trackers_all_i2p (13) and trackers_all_yggdrasil (1) for anonymity-network setups that need an I2P router or a Yggdrasil network router.
- ✓IP-address variants (trackers_best_ip, trackers_all_ip, trackers_all_yggdrasil_ip) for when DNS to the tracker domain is broken but the tracker itself isn't.
- ✓A bot rechecks every tracker and regenerates the lists daily; duplicate domains or IPs get removed automatically.
- ✓blacklist.txt records what got removed, so a missing tracker isn't a mystery.
Adding trackers to your BitTorrent client
- •Paste trackers_best.txt into qBittorrent's per-torrent 'Edit trackers' dialog, or into a magnet link's tracker parameters, to help peer discovery on a torrent with few seeds.
- •Point a client's 'update trackers from URL' setting at the raw.githubusercontent.com or jsdelivr mirror if it supports fetching a list on a schedule.
- •Use the third-party scripts the README links — the Deluge plugin, the Transmission bash/python scripts, the aria2 go script — to bulk-add trackers instead of copy-pasting.
- •Switch to trackers_best_ip or trackers_all_ip when a resolver or VPN blocks the tracker domains but not their IP addresses.
- •Load trackers_all_i2p only if an I2P router and a compatible client like qBittorrent, BiglyBT, or I2PSnark are already running.
Strengths
- ✓Files are split cleanly by protocol and by best/all, so you grab the subset your client or network actually needs.
- ✓Daily automated checks prune dead and duplicate trackers instead of letting them pile up for years.
- ✓IP-address mirrors solve the specific case where DNS to the tracker domain is broken but the tracker isn't.
- ✓Multiple mirrors (GitHub raw, GitHub Pages, jsdelivr) mean no single host has to stay up for the list to work.
Limitations of public trackers
- △Public trackers are shared by everyone, so load is heavier than a private tracker, and some entries in trackers_all are slow or flaky between daily bot runs.
- △No privacy guarantee: a public tracker can see which IPs are announcing which info-hashes, unlike DHT or a private tracker with its own access rules.
- △WebSocket and I2P/Yggdrasil trackers only help if your client and network stack already support those protocols, and most desktop clients don't by default.
- △It's plain text with git history as the only changelog — no versioned release, no way to pin a 'known good' snapshot besides a commit hash.
Alternatives to ngosang/trackerslist
Frequently asked questions
Announcing to a public tracker isn't itself illegal — the tracker only coordinates IP addresses, it doesn't host content. What's legal depends on what you're downloading and your local copyright law, not on which tracker list you used.
The README says a bot automatically checks every tracker and regenerates the lists daily, removing duplicates that share a domain or IP address.
trackers_best (20 trackers, sorted by popularity and latency) is the safer default for most torrents; trackers_all (114 trackers) adds redundancy but also more dead weight when some are down.
The README is upfront that WebSocket trackers (WebTorrent, ws/wss) are supported by only a few clients — check webtorrent.io before assuming yours works with trackers_all_ws.
Copy the URLs from trackers_best.txt or trackers_all.txt into qBittorrent's per-torrent 'Edit trackers' dialog, or use one of the third-party helper scripts the README links for qBittorrent.
trackers_all_udp (50 trackers) uses the lighter UDP protocol; trackers_all_http (48) and trackers_all_https (16) use HTTP(S) announce requests, which cost more overhead per request but are easier to proxy through firewalls that block UDP.
Who should try it — and who should skip
Try this if you run torrents on public trackers and want a ready-made, protocol-sorted list to paste into a client or magnet link. The best/all split and IP mirrors cover the common snags: DNS issues, WebSocket-only clients, I2P setups. Skip it if you're exclusively on private trackers, where adding public tracker URLs breaks the rules, or if DHT already gets you enough peers without extra announce endpoints.
Related repositories
Curious whether trackerslist is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about trackerslist.