Mirror Infrastructure - TrackersList

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

Primary Source

Base URL:

https://raw.githubusercontent.com/ngosang/trackerslist/master/

Availability

High

Direct access to repository files with GitHub’s infrastructure

Rate Limits

Authenticated: 5,000 requests/hour
Unauthenticated: 60 requests/hour per IP

Caching

Moderate

GitHub CDN caching with standard TTL

Latency

Good

Served from GitHub’s global CDN

Example:

curl https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best.txt

Best for: Development, testing, and applications with authentication

Static Hosting Mirror

Base URL:

https://ngosang.github.io/trackerslist/

Availability

Very High

Served from GitHub Pages with dedicated infrastructure

Rate Limits

More generous than raw.githubusercontent.com

Designed for public web traffic
No documented hard limits

Caching

Aggressive

Optimized for static content delivery with longer TTL

Latency

Excellent

Global CDN with edge caching

Example:

curl https://ngosang.github.io/trackerslist/trackers_best.txt

Best for: Production applications, public-facing services, high-volume requests

Public CDN Mirror

Base URL:

https://cdn.jsdelivr.net/gh/ngosang/trackerslist@master/

Availability

Very High

Multi-CDN infrastructure with automatic failover

Rate Limits

Very high limits for open source projects:

No request limits for most use cases
Designed for high-traffic scenarios

Caching

Very Aggressive

Optimized for static assets with long-term caching

Latency

Best

Multi-CDN with 200+ global edge locations

Example:

curl https://cdn.jsdelivr.net/gh/ngosang/trackerslist@master/trackers_best.txt

Best for: High-availability production services, global distribution, maximum performance

Available Mirrors by Endpoint

Curated Lists

trackers_best.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best.txt

trackers_all.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all.txt

Protocol-Specific Lists

trackers_all_udp.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_udp.txt

trackers_all_http.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_http.txt

trackers_all_https.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_https.txt

trackers_all_ws.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_ws.txt

Network-Specific Lists

trackers_all_i2p.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_i2p.txt

trackers_all_yggdrasil.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all_yggdrasil.txt

IP-Based Lists

trackers_best_ip.txt

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

trackers_all_ip.txt

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

trackers_all_yggdrasil_ip.txt

https://raw.githubusercontent.com/ngosang/trackerslist/master/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

Response Headers

Each mirror returns different caching headers:GitHub Raw:

Cache-Control: max-age=300
ETag: "..."
X-Content-Type-Options: nosniff

GitHub Pages:

Cache-Control: max-age=600
ETag: "..."
X-GitHub-Request-Id: ...

jsDelivr:

Cache-Control: public, max-age=86400
CDN-Cache-Control: public, max-age=31536000
ETag: "..."

Recommended Client Strategy

import requests
from datetime import datetime, timedelta
import pickle

CACHE_FILE = 'trackers_cache.pkl'
CACHE_DURATION = timedelta(hours=24)

def get_trackers_cached():
    try:
        with open(CACHE_FILE, 'rb') as f:
            cache = pickle.load(f)
            if datetime.now() - cache['timestamp'] < CACHE_DURATION:
                return cache['trackers']
    except FileNotFoundError:
        pass
    
    # Try mirrors in order of preference
    mirrors = [
        'https://cdn.jsdelivr.net/gh/ngosang/trackerslist@master/trackers_best.txt',
        'https://ngosang.github.io/trackerslist/trackers_best.txt',
        'https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best.txt'
    ]
    
    for mirror in mirrors:
        try:
            response = requests.get(mirror, timeout=10)
            response.raise_for_status()
            trackers = [line.strip() for line in response.text.split('\n') if line.strip()]
            
            # Cache the result
            with open(CACHE_FILE, 'wb') as f:
                pickle.dump({'timestamp': datetime.now(), 'trackers': trackers}, f)
            
            return trackers
        except requests.RequestException:
            continue
    
    raise Exception('All mirrors failed')

Failover Implementation

Define Mirror Priority

List mirrors in order of preference based on your use case:

const mirrors = [
  'https://cdn.jsdelivr.net/gh/ngosang/trackerslist@master/trackers_best.txt',  // Fastest
  'https://ngosang.github.io/trackerslist/trackers_best.txt',                    // Reliable
  'https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_best.txt' // Authoritative
];

Implement Timeout

Set reasonable timeouts (5-10 seconds) for each request

Try Next Mirror on Failure

On timeout or error, immediately try the next mirror

Log and Monitor

Track which mirrors are failing to detect infrastructure issues

package main

import (
    "context"
    "fmt"
    "io"
    "net/http"
    "time"
)

func fetchWithFailover(endpoint string) (string, error) {
    mirrors := []string{
        "https://cdn.jsdelivr.net/gh/ngosang/trackerslist@master/",
        "https://ngosang.github.io/trackerslist/",
        "https://raw.githubusercontent.com/ngosang/trackerslist/master/",
    }
    
    client := &http.Client{
        Timeout: 10 * time.Second,
    }
    
    for _, mirror := range mirrors {
        url := mirror + endpoint
        ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
        defer cancel()
        
        req, err := http.NewRequestWithContext(ctx, "GET", url, nil)
        if err != nil {
            continue
        }
        
        resp, err := client.Do(req)
        if err != nil {
            continue
        }
        defer resp.Body.Close()
        
        if resp.StatusCode == 200 {
            body, err := io.ReadAll(resp.Body)
            if err == nil {
                return string(body), nil
            }
        }
    }
    
    return "", fmt.Errorf("all mirrors failed for %s", endpoint)
}

Mirror Status Monitoring

All mirrors are typically highly available (99.9%+ uptime), but implementing failover ensures your application remains resilient during rare outages.

Recommended Monitoring:

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.

Typical Global Response Times:

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

Throughput:

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

Documentation Index

​Overview

GitHub Raw

GitHub Pages

jsDelivr CDN

​Mirror Comparison

​Primary Source

​Static Hosting Mirror

​Public CDN Mirror

​Available Mirrors by Endpoint

​Curated Lists

​Protocol-Specific Lists

​Network-Specific Lists

​IP-Based Lists

​When to Use Each Mirror

Development

Production

High Traffic

Fallback Strategy

​Caching Behavior

​Response Headers

​Time to Propagate

​Recommended Client Strategy

​Failover Implementation

​Mirror Status Monitoring

​Performance Comparison

​Additional Resources

jsDelivr Documentation

GitHub Pages Docs

Rate Limits

Best Practices

Overview

Mirror Comparison

Primary Source

Static Hosting Mirror

Public CDN Mirror

Available Mirrors by Endpoint

Curated Lists

Protocol-Specific Lists

Network-Specific Lists

IP-Based Lists

When to Use Each Mirror

Caching Behavior

Response Headers

Time to Propagate

Recommended Client Strategy

Failover Implementation

Mirror Status Monitoring

Performance Comparison

Additional Resources