Overview
TrackersList is available through three different mirror sources to ensure maximum availability and global performance. Each mirror serves identical content updated daily.GitHub Raw
Primary source, direct from repository
GitHub Pages
Static hosting with global CDN
jsDelivr CDN
Public CDN with aggressive caching
Mirror Comparison
- GitHub Raw
- GitHub Pages
- jsDelivr CDN
Available Mirrors by Endpoint
Curated Lists
trackers_best.txt
trackers_best.txt
trackers_all.txt
trackers_all.txt
Protocol-Specific Lists
trackers_all_udp.txt
trackers_all_udp.txt
trackers_all_http.txt
trackers_all_http.txt
trackers_all_https.txt
trackers_all_https.txt
trackers_all_ws.txt
trackers_all_ws.txt
Network-Specific Lists
trackers_all_i2p.txt
trackers_all_i2p.txt
trackers_all_yggdrasil.txt
trackers_all_yggdrasil.txt
IP-Based Lists
trackers_best_ip.txt
trackers_best_ip.txt
trackers_all_ip.txt
trackers_all_ip.txt
trackers_all_yggdrasil_ip.txt
trackers_all_yggdrasil_ip.txt
When to Use Each Mirror
Development
Use: GitHub RawGood for:
- Testing and development
- Low-volume requests
- Latest changes verification
Production
Use: GitHub Pages or jsDelivrGood for:
- Production applications
- High-availability requirements
- Public-facing services
High Traffic
Use: jsDelivr CDNGood for:
- Very high request volumes
- Global user base
- Maximum performance needs
Fallback Strategy
Use: All three with failoverGood for:
- Mission-critical applications
- Maximum reliability
- Handling mirror downtime
Caching Behavior
- Cache Headers
- Update Propagation
- Client Caching
Failover Implementation
Mirror Status Monitoring
All mirrors are typically highly available (99.9%+ uptime), but implementing failover ensures your application remains resilient during rare outages.
- Application-Level
- External Monitoring
Track mirror performance within your application:
- Response times for each mirror
- Failure rates
- Which mirror is being used most often
- Alert if all mirrors fail
Performance Comparison
Actual performance varies by geographic location and network conditions. Test from your deployment regions.
| Mirror | North America | Europe | Asia | Australia |
|---|---|---|---|---|
| jsDelivr CDN | 20-50ms | 15-40ms | 30-60ms | 40-80ms |
| GitHub Pages | 40-80ms | 30-70ms | 60-120ms | 80-150ms |
| GitHub Raw | 50-100ms | 40-90ms | 80-150ms | 100-200ms |
- All mirrors handle 100+ concurrent requests easily
- jsDelivr scales to thousands of requests/second
- GitHub Pages handles hundreds of requests/second
Additional Resources
jsDelivr Documentation
Learn more about jsDelivr features and limits
GitHub Pages Docs
Understanding GitHub Pages infrastructure
Rate Limits
GitHub API and raw content rate limits
Best Practices
Integration patterns and optimization tips