Public Torrent Trackers

A public torrent tracker is a server that coordinates peer discovery in BitTorrent swarms and accepts connections from anyone. No account, passkey, or invitation required. Any BitTorrent client can announce to a public tracker and receive a list of peers sharing the same content.

Pulsed Media has run seedbox infrastructure in Finland since 2009. Our PMSS platform includes a Tracker Cleaner feature because public trackers are what most users deal with day to day. This article explains how they work.

What makes a tracker public

The distinction between public and private comes down to authentication. A private tracker assigns each user a unique passkey embedded in every .torrent file they download. The tracker uses this passkey to track ratio, enforce upload requirements, and control swarm membership. A public tracker has none of this. Any info_hash, any client, any IP gets a response.

Public trackers also behave differently around peer discovery. Private trackers enforce the "private" flag in torrent metadata, which forces clients to disable DHT (Distributed Hash Table) and PEX (Peer Exchange). Without that flag, public swarms use both tracker announces and DHT at the same time. If the tracker is slow or unreachable, DHT keeps the swarm alive.

Public trackers are open infrastructure. They support the same underlying protocol that private trackers use, just without access control.

The announce protocol

Two protocols carry tracker traffic: HTTP and UDP.

HTTP announces

The original BitTorrent announce protocol runs over HTTP or HTTPS. When your client starts a torrent, it sends a GET request to the tracker URL with these parameters:

info_hash (the 20-byte SHA-1 hash that uniquely identifies the torrent)
peer_id (a random identifier your client generates at startup)
ip and port (where peers can reach you)
uploaded, downloaded, left (transfer accounting)
event (started, stopped, or completed)

The tracker responds with a bencoded list of peer addresses. HTTP trackers are universally supported but carry overhead: TCP handshake, HTTP headers, connection teardown for each announce.

UDP announces

The UDP tracker protocol (BitTorrent Enhancement Proposal 15) cuts that overhead. Instead of a full HTTP exchange, it uses four UDP packets: two to establish a connection token, two for the announce itself. No TCP, no headers. At scale, this is faster and cheaper for both client and tracker.

Most modern public trackers support UDP. rTorrent, qBittorrent, Deluge, and Transmission all handle UDP tracker URLs. A tracker URL beginning with udp:// uses this protocol.

Scrape

Both protocols support a scrape endpoint. A scrape request asks the tracker for seeder and leecher counts across multiple torrents in a single query. Clients use scrape to update the peer count display without sending a full announce for each torrent. Public trackers generally support scrape, though the endpoint is sometimes rate-limited.

Announce intervals

Trackers tell clients how often to re-announce via the interval field in the announce response. Public trackers typically set intervals between 30 minutes and a few hours. Clients re-announce on schedule, plus immediately on status changes (start, stop, complete).

If a peer stops announcing for longer than the interval, the tracker drops it from the active peer list. Stale entries age out; active peers stay visible.

Using multiple trackers

A .torrent file can list multiple tracker URLs. The BitTorrent spec groups them into tiers: the client tries trackers in order within each tier and moves to the next tier only if all trackers in the current one fail. Many clients contact all trackers simultaneously for faster initial peer discovery.

Adding trackers to a torrent does not change the content or info_hash. It adds more peer discovery paths. Volunteers maintain public tracker lists, checking uptime and updating them as trackers come and go. Anyone can append these lists to their torrents.

Individual public trackers go down. A torrent with one tracker URL stops finding new peers when that tracker goes offline. Multiple trackers plus DHT means the swarm survives individual failures.

Public trackers and seedboxes

Public tracker swarms have no ratio enforcement. There is no account to protect, no minimum seeding requirement. A seedbox still makes a real difference.

When your client connects to a public tracker, it announces an IP and port. Other peers connect to that IP to download from you. On a home connection, that means incoming connections through your router, upload bandwidth competing with everything else, and the client going offline when the machine sleeps or the internet drops.

A seedbox at Pulsed Media removes those constraints. The server sits in our datacenters in Helsinki and Kerava with bandwidth up to 20Gbps. It announces a datacenter IP with an always-open port. Peers connect without interruption. Because the server stays online and the connection is fast, the client holds active upload slots in public swarms even for content with low traffic.

PMSS Tracker Cleaner

Pulsed Media's PMSS platform includes a Tracker Cleaner feature. It automatically appends a curated list of working public trackers to existing torrents. Torrents with a single tracker URL, or with a tracker that has since gone offline, get additional announce paths without manual work.

Older torrents that stopped finding peers because their original tracker closed down start finding them again through the additional URLs. Tracker Cleaner runs automatically and updates its list as tracker availability changes.

Tracker reliability

Public trackers run on volunteer infrastructure. Some have operated for years without interruption; others shut down without warning. A tracker that works today may be unreachable next month.

Tracker diversity matters more than any specific URL. A torrent with eight working tracker URLs is more resilient than one with a single URL. DHT provides a further fallback. At Pulsed Media we see this in real swarm behavior: the seedboxes with the best peer connections consistently have multiple active tracker URLs and DHT enabled.

Legality

Public trackers coordinate peer discovery but do not store content. They know which IP addresses are in which swarms, not what those swarms contain. Tracker operators have faced legal challenges in various jurisdictions; the outcome depends on local law.

On Pulsed Media servers, each user is solely responsible for the files they download, distribute, or share.