Contributing - TrackersList

Overview

TrackersList is maintained through community contributions. Whether you’ve discovered a new public tracker or noticed one that’s no longer working, your feedback helps keep the lists accurate and up-to-date.

The project is maintained by ngosang and updated daily by an automated bot that validates all trackers.

How to Contribute

Report New Trackers

Know a public tracker not on the list? Let us know!

Report Dead Trackers

Found a tracker that’s down? Help us remove it

Submit Issues

Learn the proper way to submit reports

Contact Maintainer

Need to reach out directly?

Reporting New Trackers

What Qualifies as a Public Tracker?

Before submitting a new tracker, ensure it meets these criteria:

Publicly Accessible

The tracker must be open to the public without requiring:

Registration or accounts
Invitations or access codes
Payment or subscriptions
VPN or special network access (except I2P/Yggdrasil categories)

Currently Active

The tracker should be:

Responding to announce requests
Returning peer information
Stable and not experiencing extended downtime

BitTorrent Protocol Compliant

Must follow standard BitTorrent tracker protocols:

HTTP/HTTPS trackers: BEP 3 (BitTorrent Protocol)
UDP trackers: BEP 15 (UDP Tracker Protocol)
WebSocket trackers: WebTorrent protocol

Not a Duplicate

The tracker should not:

Use the same domain as an existing tracker
Point to the same IP address as a listed tracker
Be a simple port variation of an existing entry

Submission Process

Verify the Tracker Works

Test the tracker yourself before submitting:

Test with curl (HTTP/HTTPS)

curl "http://tracker.example.com:8080/announce?info_hash=%00%01%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%0f%10%11%12%13&peer_id=-TR3000-abcdefghijkl&port=51413&uploaded=0&downloaded=0&left=0&event=started"

Test with aria2 (UDP)

aria2c --bt-tracker="udp://tracker.example.com:6969/announce" --seed-time=0 test.torrent

The tracker should return a valid response (200 OK for HTTP/HTTPS, peer list for UDP)

Open a GitHub Issue

Go to the TrackersList repository and click “New Issue”

Create Issue

Open a new issue on GitHub

Provide Complete Information

Use this template for your issue:

Issue Template

## New Public Tracker

**Tracker URL:**
udp://tracker.example.com:6969/announce

**Protocol:**
UDP / HTTP / HTTPS / WebSocket / I2P / Yggdrasil

**Status:**
Currently active and responding

**Test Results:**
- Tested with: qBittorrent 4.5.0
- Successfully returned peer list
- Response time: ~50ms

**Additional Notes:**
(Any other relevant information)

Wait for Validation

The automated bot will:

Validate the tracker is working
Check for duplicates
Measure latency and performance
Add it to the appropriate lists if it passes

The bot runs daily, so your submission will be processed within 24 hours

What Happens Next?

After you submit a new tracker:

Automated Testing - The bot validates the tracker during its next run
Duplicate Check - Ensures it’s not already listed under a different URL
Performance Measurement - Tests latency and reliability
List Addition - If valid, added to:
- trackers_all.txt (always)
- Protocol-specific list (e.g., trackers_all_udp.txt)
- trackers_best.txt (if performance is high enough)

High-quality trackers with low latency and high uptime may be promoted to the trackers_best.txt list!

Reporting Non-Working Trackers

When to Report a Tracker

Report a tracker if it exhibits any of these issues:

Timeout

No response after multiple attempts

Connection Refused

Actively rejecting connections

Invalid Responses

Returning malformed or error responses

DNS Failure

Domain no longer resolves

Permanent Redirect

Redirecting to a different tracker

Maintenance Mode

Extended downtime (7+ days)

Before Reporting

Don’t report temporary issues! Trackers may have brief downtime. The automated bot already monitors for extended outages.

Verify It's Actually Down

Test from multiple locations/networks if possible:

Try from a different network
Check if DNS resolves: nslookup tracker.example.com
Test with multiple clients
Wait a few hours and try again

Check if It's Already Known

Search existing GitHub Issues to see if someone already reported it

Document the Problem

Gather information about the failure:

Diagnostic Commands

# DNS resolution
nslookup tracker.example.com

# Connection test
nc -zv tracker.example.com 6969

# HTTP/HTTPS test
curl -v "http://tracker.example.com:8080/announce"

# Traceroute
traceroute tracker.example.com

Submission Process

Open a GitHub Issue

Report Issue

Open a new issue on GitHub

Provide Detailed Information

Use this template:

Issue Template

## Non-Working Tracker Report

**Tracker URL:**
udp://tracker.example.com:6969/announce

**Current List:**
trackers_all.txt, trackers_all_udp.txt

**Problem:**
Connection timeout - no response after 30 seconds

**Testing Details:**
- Tested from: US-East, Europe (multiple locations)
- DNS resolution: Failed (NXDOMAIN)
- Last working: Unknown (first noticed today)
- Error message: "Connection timed out"

**Diagnostic Output:**

$ nslookup tracker.example.com Server: 8.8.8.8 Address: 8.8.8.8#53** server can’t find tracker.example.com: NXDOMAIN

**Additional Context:**
Domain appears to have expired

Await Confirmation

The maintainer or bot will:

Verify the issue
Monitor for extended downtime
Remove if down for 7+ consecutive days

Issue Submission Process

GitHub Issue Guidelines

Best Practices
Title Formats
Required Information
Example Issues

DO:

Use clear, descriptive titles
Provide complete tracker URLs
Include test results and error messages
Be specific about protocols and versions
Add relevant logs or diagnostic output
Update the issue if the situation changes

DON’T:

Submit duplicate issues
Report temporary downtime (< 24 hours)
Use vague descriptions
Submit private/semi-private trackers
Include malicious or spam trackers

Use clear, standardized titles:New Tracker:

[New] UDP tracker: tracker.example.com:6969
[New] HTTP tracker: tracker.example.com:8080

Dead Tracker:

[Dead] tracker.example.com:6969 - Connection timeout
[Dead] tracker.example.com:8080 - Domain expired

General Question:

[Question] About I2P tracker requirements
[Suggestion] Add blacklist entry for X

Good Issue Example:

Title: [New] UDP tracker: tracker.awesome.net:6969

## New Public Tracker Submission

**Tracker URL:** udp://tracker.awesome.net:6969/announce
**Protocol:** UDP
**Status:** Active and responding

**Test Results:**
- Client: qBittorrent 4.5.2
- Successfully connected and received peers
- Average response time: 35ms
- Tested from: US-East and Europe

**Additional Information:**
This is a well-established tracker that's been running for 2+ years.
Currently not listed in any major tracker lists.

Bad Issue Example:

Title: tracker not working

tracker.something.com doesn't work for me.
can you fix it?

Response Times

Typical Response Times:

Automated bot validation: Within 24 hours
Maintainer review: 1-7 days
List updates: Next daily update cycle (3 AM UTC)

Contact Information

Primary Contact

Email

Maintainer: ngosang
Email: ngosang [@] hotmail [.es]

Replace [@] with @ and [.es] with .es when composing the email

When to Contact Directly

Use email for:

Security concerns
Urgent issues affecting many users
Private discussions
General questions not suitable for GitHub

For tracker submissions and reports, always use GitHub Issues to maintain public records and allow community input.

GitHub

Repository

Main TrackersList repository

Issues

Submit tracker reports

Pull Requests

View pending changes

Discussions

Community discussions

Support the Project

TrackersList is maintained by volunteers. If you find it useful, consider supporting:

Support on Ko-fi

Buy ngosang a coffee to support continued development

Other Ways to Help:

Star the Repo

Show your appreciation on GitHub

Spread the Word

Share with others who might benefit

Report Issues

Help improve list accuracy

Community Guidelines

Code of Conduct

When contributing, please:

Be Respectful

Treat maintainers and other contributors with respect

Be Patient

Remember this is a volunteer project

Be Constructive

Provide helpful feedback and context

Be Honest

Don’t submit fake or malicious trackers

What Happens to Submissions

Accepted Submissions

If your tracker submission is accepted:

Added to appropriate lists within 24 hours
Monitored daily for uptime and performance
May be promoted to trackers_best.txt if performance is excellent
Your GitHub username may be credited in commit messages

Rejected Submissions

Submissions may be rejected if:

Tracker is not public
Already exists (duplicate domain/IP)
Not responding during validation
Violates BitTorrent protocol standards
Requires special access or authentication

You’ll receive feedback explaining why it was rejected

Frequently Asked Questions

How long before my tracker appears in the lists?

If validated successfully, your tracker will appear in the next daily update cycle (3 AM UTC). GitHub Raw updates immediately, but mirror CDNs may take up to 60 minutes to propagate.

Can I submit multiple trackers at once?

Yes! Create a single issue with all tracker URLs if they’re related, or separate issues if they’re from different sources.

My tracker was removed. Why?

Trackers are automatically removed after being unresponsive for 7+ consecutive days. If it’s back online, submit it again as a new tracker.

Can I submit a private tracker?

No. TrackersList only includes public trackers that don’t require registration, invitations, or payment.

How can I check if a tracker is already listed?

Search the trackers_all.txt file or use grep:

curl -s https://raw.githubusercontent.com/ngosang/trackerslist/master/trackers_all.txt | grep "tracker.example.com"

What if I found a tracker on the blacklist?

The blacklist contains trackers that are duplicates or have been intentionally excluded. If you believe a blacklisted tracker should be reconsidered, open an issue with justification.

Additional Resources

API Documentation

Learn how to use the tracker lists

Integration Guide

Add trackers to your BitTorrent client

Third-Party Tools

Tools built by the community

FAQ

Common questions and answers

List Endpoints

Community

​Overview

​How to Contribute

Report New Trackers

Report Dead Trackers

Submit Issues

Contact Maintainer

​Reporting New Trackers

​What Qualifies as a Public Tracker?

​Submission Process

Create Issue

​What Happens Next?

​Reporting Non-Working Trackers

​When to Report a Tracker

Timeout

Connection Refused

Invalid Responses

DNS Failure

Permanent Redirect

Maintenance Mode

​Before Reporting

​Submission Process

Report Issue

​Issue Submission Process

​GitHub Issue Guidelines

​Response Times

​Contact Information

​Primary Contact

Email

​When to Contact Directly

​GitHub

Repository

Issues

Pull Requests

Discussions

​Support the Project

Support on Ko-fi

Star the Repo

Spread the Word

Report Issues

​Community Guidelines

​Code of Conduct

​What Happens to Submissions

​Frequently Asked Questions

​Additional Resources

API Documentation

Integration Guide

Third-Party Tools

FAQ

Build docs developers (and LLMs) love

Overview

How to Contribute

Reporting New Trackers

What Qualifies as a Public Tracker?

Submission Process

What Happens Next?

Reporting Non-Working Trackers

When to Report a Tracker

Before Reporting

Submission Process

Issue Submission Process

GitHub Issue Guidelines

Response Times

Contact Information

Primary Contact

When to Contact Directly

GitHub

Support the Project

Community Guidelines

Code of Conduct

What Happens to Submissions

Frequently Asked Questions

Additional Resources