IP Address Tracker Lists

IP address tracker lists provide direct IP access to trackers, bypassing DNS resolution. These are essential for environments where DNS is blocked, censored, or unreliable.

Why IP Address Lists?

DNS Issues? If your DNS is blocked, poisoned, or unavailable, domain-based tracker URLs won’t work. IP address lists solve this problem.

Common DNS Problems

ISP-level DNS blocking of torrent trackers
Government-mandated DNS censorship
DNS poisoning attacks
Restricted network environments (corporate, school)
VPN or proxy DNS leaks
Slow or unreliable DNS resolvers

Available IP Lists

Best Trackers (IP)

20 trackers with IP addressestrackers_best_ip.txt

All Trackers (IP)

61 trackers with IP addressestrackers_all_ip.txt

IP lists contain fewer trackers than domain-based lists because Cloudflare-protected trackers cannot be reliably converted to static IP addresses.

Best Trackers (IP)

20 trackers - trackers_best_ip.txt

The same top 20 trackers from trackers_best.txt, but with IP addresses instead of domain names.

Download URLs

curl -O https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best_ip.txt

Direct Links

GitHub Raw

Primary source

Mirror

GitHub Pages

CDN

jsDelivr (fastest)

Example Trackers

udp://93.158.213.92:1337/announce
udp://185.121.168.96:1337/announce
udp://185.243.218.213:80/announce
udp://89.234.156.205:451/announce
udp://209.141.59.16:6969/announce
udp://91.186.213.204:6969/announce
udp://52.58.128.163:6969/announce
udp://211.75.210.221:6969/announce
udp://34.66.57.33:80/announce
udp://109.201.134.183:80/announce
... and 10 more

IP addresses can change. Download the latest list regularly to ensure you have current IP addresses.

When to Use

Ideal for:

DNS-blocked networks
Countries with DNS censorship
VPN configurations with DNS leaks
Networks without DNS servers
Testing if DNS is causing tracker issues
Maximum reliability (no DNS lookup delays)

All Trackers (IP)

61 trackers - trackers_all_ip.txt

Comprehensive list of public trackers using IP addresses. Contains 61 out of the 112 trackers from trackers_all.txt.

Download URLs

curl -O https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_ip.txt

Direct Links

GitHub Raw

Primary source

Mirror

GitHub Pages

CDN

jsDelivr (fastest)

Example Trackers

udp://93.158.213.92:1337/announce
http://93.158.213.92:1337/announce
udp://185.121.168.96:1337/announce
udp://185.243.218.213:80/announce
udp://89.234.156.205:451/announce
udp://209.141.59.16:6969/announce
udp://91.186.213.204:6969/announce
udp://52.58.128.163:6969/announce
udp://211.75.210.221:6969/announce
udp://34.66.57.33:80/announce
http://34.66.57.33:2710/announce
http://34.66.57.33:11450/announce
http://211.75.205.188:80/announce
... and 48 more

Why Only 61 Trackers?

The IP list is shorter because:

Cloudflare Protection

Cloudflare-protected trackers hide their real IP addresses behind Cloudflare’s network. These cannot be included in IP lists because:

Cloudflare IPs change frequently
Multiple sites share same Cloudflare IPs
Direct IP access is blocked by Cloudflare

Dynamic IP Addresses

Some trackers use dynamic IP addresses that change too frequently to maintain in a daily-updated list.

Load Balancers

Trackers behind load balancers with multiple IPs or DNS-based load balancing cannot be reduced to a single IP address.

HTTP/3 and QUIC

Some modern trackers require domain names for protocol features and certificate validation.

Comparison: Domain vs IP Lists

Feature Comparison

Feature	Domain Lists	IP Lists
Tracker Count	112 (all) / 20 (best)	61 (all) / 20 (best)
DNS Required	Yes	No
Bypass DNS Blocking	No	Yes
Works with Censorship	Sometimes	Usually
Certificate Validation	Works	May fail on HTTPS
IP Changes	No impact	Requires updates
Cloudflare Trackers	Included	Excluded

Performance Impact

Domain-Based
IP-Based

trackers_all.txt (112 trackers)

DNS lookup (5-50ms per tracker)
Connect to resolved IP
Announce to tracker

Total overhead: ~560-5600ms for initial DNS lookups

trackers_all_ip.txt (61 trackers)

1. Connect directly to IP
2. Announce to tracker

Total overhead: 0ms (no DNS lookups)

IP lists can be 5-50ms faster per tracker by eliminating DNS lookups.

Integration Examples

qBittorrent
Transmission
Deluge
Command Line

# Download IP-based tracker list
curl -s https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best_ip.txt \
  -o ~/trackers_ip.txt

# Open qBittorrent
# Go to Tools → Options → BitTorrent
# Check "Automatically add these trackers to new downloads"
# Paste the contents of trackers_ip.txt

You can combine domain and IP lists for maximum reliability.

#!/bin/bash
# Add IP-based trackers to all torrents

# Download and format trackers
trackers=$(curl -s https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best_ip.txt | \
  grep -v '^$' | tr '\n' ',')

# Add to each torrent
for torrent in $(transmission-remote -l | grep -v Sum | awk '{print $1}'); do
  transmission-remote -t $torrent -td "$trackers"
done

echo "Added $(echo $trackers | tr ',' '\n' | wc -l) IP-based trackers"

# deluge_add_ip_trackers.py
from deluge_client import DelugeRPCClient
import requests

# Connect to Deluge
client = DelugeRPCClient('127.0.0.1', 58846, 'admin', 'password')
client.connect()

# Download IP-based trackers
url = 'https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best_ip.txt'
response = requests.get(url)
trackers = [t.strip() for t in response.text.split('\n') if t.strip()]

# Add to all torrents
for torrent_id in client.core.get_torrents_status({}, []):
    for tracker in trackers:
        client.core.add_tracker_to_torrent(torrent_id, tracker)

print(f"Added {len(trackers)} IP-based trackers")

# Test if DNS is the problem

# Try domain-based tracker
curl -I "http://tracker.opentrackr.org:1337/announce"

# Try IP-based tracker (same tracker)
curl -I "http://93.158.213.92:1337/announce"

# If IP works but domain doesn't = DNS issue

DNS Testing

Determine if you need IP-based lists:

Test DNS Resolution

# Test if tracker domains resolve
nslookup tracker.opentrackr.org
dig tracker.opentrackr.org

If this fails or returns wrong IPs, you have DNS problems.

Test Direct IP Connection

# Connect using IP address
curl -I "http://93.158.213.92:1337/announce" --max-time 5

If this works, IP lists will solve your problem.

Compare Response Times

# Domain-based (includes DNS lookup)
time curl -I "http://tracker.opentrackr.org:1337/announce"

# IP-based (no DNS lookup)
time curl -I "http://93.158.213.92:1337/announce"

If IP is significantly faster, use IP lists.

Limitations and Considerations

Important Limitations:

IP Address Changes

IP addresses can change without notice:

Server migrations
Network changes
ISP modifications
DDoS mitigation

Update IP lists weekly to maintain current addresses. The list is updated daily to track IP changes.

HTTPS Certificate Issues

HTTPS trackers with IP addresses may fail certificate validation:

Certificate Error: tracker.example.com
Connecting to: https://93.158.213.92:443/announce
Error: Certificate domain mismatch

Solution: Use HTTP or UDP protocols with IP lists:

# Filter for non-HTTPS trackers
grep -v "https://" trackers_all_ip.txt > trackers_ip_no_https.txt

Geographic Routing

Some trackers use GeoDNS to route users to nearest servers. IP lists bypass this optimization.

Missing Trackers

51 trackers from trackers_all.txt are not available in trackers_all_ip.txt due to Cloudflare and dynamic IPs.

Update Frequency

IP lists are updated daily to track IP address changes. Update your local copy regularly.

Automation

#!/bin/bash
# update-ip-trackers.sh

# Download latest IP-based trackers
curl -s https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best_ip.txt \
  -o /tmp/trackers_best_ip.txt

# Check if file changed
if ! cmp -s /tmp/trackers_best_ip.txt ~/.config/trackers_best_ip.txt; then
  cp /tmp/trackers_best_ip.txt ~/.config/trackers_best_ip.txt
  echo "Tracker IPs updated: $(date)"
  
  # Reload torrent client configuration
  # (client-specific commands)
else
  echo "No changes in tracker IPs"
fi

Add to crontab:

# Update IP trackers twice daily
0 3,15 * * * /path/to/update-ip-trackers.sh

Troubleshooting

IP trackers not working

Possible causes:

IP addresses have changed (download latest list)
Firewall blocking direct IP connections
ISP blocking tracker IPs specifically
Tracker server moved/offline

Solutions:

Download latest IP list
Test with single tracker: curl http://IP:PORT/announce
Check firewall rules
Try VPN to bypass IP-based blocking

Certificate errors with HTTPS

HTTPS trackers require domain names for certificate validation.Solutions:

Use only UDP and HTTP from IP lists
Use domain-based lists for HTTPS trackers
Disable certificate verification (not recommended)

# Extract only UDP and HTTP trackers
grep -E "^(udp|http)://" trackers_all_ip.txt > trackers_ip_safe.txt

How often do tracker IPs change?

Frequency varies:

Stable trackers: Monthly or never
Dynamic infrastructure: Weekly
Under attack: Daily

Recommendation:

Update IP lists weekly minimum
Daily updates for critical applications
Monitor tracker success rates in your client

The list is regenerated daily to catch IP changes immediately.

Combining domain and IP lists

Yes, you can use both:

# Combine best trackers (domain and IP)
cat trackers_best.txt trackers_best_ip.txt > trackers_combined.txt

Benefits:

Redundancy (if DNS fails, IP works)
Performance (faster without DNS on some trackers)
Maximum reliability

Drawbacks:

Duplicate trackers (same tracker via domain and IP)
More tracker overhead
Client may show duplicate warnings

Best Practices

Recommendations for IP Lists:

Update regularly - Weekly minimum, daily for best results
Monitor logs - Check which trackers are actually working
Combine protocols - Use UDP and HTTP, avoid HTTPS with IPs
Test connectivity - Verify IP trackers work before relying on them
Keep backups - Save domain-based lists as fallback
Check client compatibility - Some clients handle IP trackers differently

Next Steps

Best Trackers

Domain-based version of top 20 trackers

All Trackers

Complete list with domain names (112 trackers)

Protocol-Specific

Filter by UDP, HTTP, HTTPS, WebSocket

Integration Guide

Add trackers to your torrent client

Getting Started

Tracker Lists

Integration Guides

Advanced

​Why IP Address Lists?

​Common DNS Problems

​Available IP Lists

Best Trackers (IP)

All Trackers (IP)

​Best Trackers (IP)

​Download URLs

​Direct Links

GitHub Raw

Mirror

CDN

​Example Trackers

​When to Use

​All Trackers (IP)

​Download URLs

​Direct Links

GitHub Raw

Mirror

CDN

​Example Trackers

​Why Only 61 Trackers?

​Comparison: Domain vs IP Lists

​Feature Comparison

​Performance Impact

​Integration Examples

​DNS Testing

​Limitations and Considerations

​IP Address Changes

​HTTPS Certificate Issues

​Geographic Routing

​Missing Trackers

​Update Frequency

​Automation

​Troubleshooting

​Best Practices

​Next Steps

Best Trackers

All Trackers

Protocol-Specific

Integration Guide

Build docs developers (and LLMs) love

Why IP Address Lists?

Common DNS Problems

Available IP Lists

Best Trackers (IP)

Download URLs

Direct Links

Example Trackers

When to Use

All Trackers (IP)

Download URLs

Direct Links

Example Trackers

Why Only 61 Trackers?

Comparison: Domain vs IP Lists

Feature Comparison

Performance Impact

Integration Examples

DNS Testing

Limitations and Considerations

IP Address Changes

HTTPS Certificate Issues

Geographic Routing

Missing Trackers

Update Frequency

Automation

Troubleshooting

Best Practices

Next Steps