ngosang/trackerslist

Updated list of public BitTorrent trackers

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 20 minutes ago
Added to GitGenius on August 31st, 2026
Created on April 24th, 2016
Open Issues & Pull Requests: 12 (+0)
Number of forks: 6,590
Total Stargazers: 55,011 (+0)
Total Subscribers: 1,291 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.2 days
Mean response time: 13.5 days
90th percentile: 34.1 days
Tracked items: 116

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 14% of issues opened in the past year have been closed. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 631 days
Stale 30+ days: 7
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (7)
  • waiting (6)
  • question (4)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Trackerslist is a maintained collection of public BitTorrent trackers organized by protocol and availability.

The project solves the problem of finding working BitTorrent trackers by maintaining curated lists that are automatically updated daily. Trackers are segmented by protocol type—UDP, HTTP, HTTPS, WebSocket, I2P, and Yggdrasil—allowing users to select the appropriate list for their needs. The tool also provides IP-address variants of these lists for situations where DNS resolution is problematic. Multiple mirror endpoints ensure availability and redundancy.

Developers building BitTorrent clients, torrent applications, or peer-discovery systems should consider this resource when they need a reliable, regularly maintained tracker list. The project suits any application that requires current tracker endpoints without the overhead of implementing tracker discovery or validation logic. The curated best-trackers list offers a minimal starting point, while the comprehensive all-trackers list provides broader coverage for applications that benefit from more options.

The project typically responds to issues and pull requests within one to two weeks. Work in the issue tracker centers on enhancement requests, items awaiting feedback or action, and user questions, indicating an active but measured approach to maintenance and community engagement.