Overview
TrackersList provides multiple endpoint variants to fetch public BitTorrent trackers. All lists are automatically updated daily and return newline-separated tracker URLs in plain text format.Last Update: 2026/03/03
Total Public Trackers: 112
Total Public Trackers: 112
Endpoint Categories
Protocol-Filtered Lists
Get trackers by specific protocol (UDP, HTTP, HTTPS, WebSocket)
Network-Specific Lists
Access trackers for I2P and Yggdrasil networks
IP-Based Lists
Bypass DNS issues with IP address variants
Curated Lists
Get the best performing trackers
Curated Lists
Best Trackers
The top 20 most reliable and fastest public trackers, sorted by popularity and latency.
- Request
- Response
- Metadata
All Trackers
Complete list of all 112 working public trackers across all protocols.
- Request
- Metadata
Protocol-Filtered
UDP Trackers
Only UDP protocol trackers (51 trackers). Most widely supported by BitTorrent clients.
Example Request
Example:
udp://tracker.opentrackr.org:1337/announce
HTTP Trackers
Only HTTP protocol trackers (47 trackers). Compatible with clients that don’t support UDP.
Example Request
Example:
http://tracker.example.com:80/announce
HTTPS Trackers
Only HTTPS protocol trackers (14 trackers). Encrypted tracker connections.
Example Request
Example:
https://torrent.tracker.durukanbal.com:443/announce
WebSocket Trackers
Only WebSocket protocol trackers (2 trackers). For WebTorrent clients.
Example Request
Network-Specific
I2P Trackers
Trackers for the I2P anonymous network (12 trackers).
Example Request
Requirements:
- I2P Router installed and running
- Compatible BitTorrent client: qBittorrent, BiglyBT, Tixati, I2PSnark, or libtorrent
Yggdrasil Trackers
Trackers for the Yggdrasil overlay network (1 tracker).
Example Request
Requirements:
- Yggdrasil Network Router installed and configured
IP-Based
These lists contain the same trackers but with IP addresses instead of domain names. Use these if you’re experiencing DNS resolution issues.
Best Trackers (IP)
Top 20 trackers with IP addresses instead of domains.
Example Request
Note: Cloudflare IPs are excluded
All Trackers (IP)
All trackers with IP addresses (61 trackers).
Example Request
Note: Lists with IPs are shorter because Cloudflare IPs are removed
Yggdrasil Trackers (IP)
Yggdrasil trackers with IP addresses (3 trackers).
Example Request
Response Format
All endpoints return plain text with the following characteristics:- Content-Type:
text/plain - Encoding: UTF-8
- Line endings: LF (
\n) - Separator: Single blank line between tracker URLs
- No header or footer
Rate Limits & Caching
- GitHub Raw
- Best Practices
Base URL:
https://raw.githubusercontent.com/ngosang/trackerslist/master/Rate Limits
GitHub enforces rate limits on raw content:
- Authenticated: 5,000 requests/hour
- Unauthenticated: 60 requests/hour per IP
Caching
- Responses may be cached by GitHub’s CDN
- Use
Cache-Controlheaders for optimization - Lists update once daily (3 AM UTC)
Integration Examples
Tracker Sorting
All lists are automatically sorted using the following criteria:1. Popularity
1. Popularity
Trackers are ranked by the number of successful peer connections and swarm participation across monitored torrents.
2. Latency
2. Latency
Response time for tracker announces is measured. Lower latency trackers rank higher.
3. Uptime
3. Uptime
Trackers with consistent availability over the past 7 days are prioritized.
4. Deduplication
4. Deduplication
Trackers with the same domain or pointing to the same IP address are removed. Check the blacklist for excluded trackers.
Automatic Updates
A bot automatically checks all trackers daily and updates the lists at 3:00 AM UTC.
- Bot tests each known public tracker
- Measures latency and availability
- Removes dead or unresponsive trackers
- Adds newly discovered trackers
- Sorts by performance metrics
- Publishes updated lists
- Each tracker is tested with real announce requests
- Trackers failing for 7+ consecutive days are removed
- Same-domain and same-IP duplicates are filtered