Paste any magnet link, info hash, or drop a .torrent file — instantly check live seeder and leecher counts across every tracker. Know if a torrent is healthy, dying, or dead before you download. The fastest way to check torrent health online and verify a torrent is still alive.
Seeders are users who have the complete torrent file and are actively uploading to others. More seeders = faster downloads and longer torrent lifespan. A torrent with 0 seeders cannot be downloaded — it is effectively dead even if leechers are present.
Leechers are users actively downloading the torrent. They may have partial pieces they can share, but they haven't finished yet. High leecher-to-seeder ratios can slow downloads. Many leechers with few seeders is a warning sign.
Each tracker maintains its own peer list based on who announced to it. Not all clients announce to all trackers, so counts vary. Some trackers may also be temporarily offline or slow to respond. The highest count from any single tracker is usually the most reliable indicator of actual swarm size.
Every tracker in this list has logged your real IP address when you announced to it. Trackers know which info hash you queried, your IP, port, and client details. Public trackers are routinely monitored by copyright enforcement firms. A SOCKS5 proxy replaces your IP with a datacenter address before any announce reaches a tracker.
| Seeders | Status | Expectation |
|---|---|---|
| 0 | DEAD | Download impossible. No complete copies available. |
| 1–4 | DYING | Slow and unreliable. Download before it drops to zero. |
| 5–20 | HEALTHY | Good download speeds. Stable swarm. |
| 20+ | THRIVING | Excellent speeds. Long-lived torrent. Safe to seed back. |
Built exclusively for torrenting. No generic VPN compromises — every feature is designed around how BitTorrent actually works. 30-day money-back guarantee.
Configure once in qBittorrent, uTorrent, or Deluge. Every announce to every tracker uses the proxy IP. No more logging your real address.
Get Armor →Most VPNs kill seeding because inbound connections are blocked. Armor's WireGuard includes port forwarding so peers can reach you — speed and privacy together.
Check Armor →VPNs drop. Proxies time out. Armor watches your torrent IP 24/7 and fires an instant email alert the moment your real IP surfaces in any swarm.
Check Monitor →Everything about checking torrent health, understanding tracker data, and staying private while torrenting.
No paid API is used. Our server queries each tracker's HTTP /scrape endpoint directly using the standard BitTorrent tracker protocol. UDP trackers are queried via a server-side proxy since browsers can't speak raw UDP. Trackers return seeder/leecher/completed counts for any info hash in milliseconds. All results are live — nothing is cached.
No. When you upload a .torrent file, it is parsed entirely inside your browser using JavaScript. The file bytes never leave your device. Only the extracted 40-character info hash (and any tracker URLs from the file) are sent to our scraping backend — the same data you would send by pasting a magnet link.
Each tracker only knows about peers who announced to it. If your client announced to tracker A but not tracker B, tracker B has no record of you. Additionally, torrent clients use different default tracker lists, and many use DHT independently of trackers entirely. The highest count across all trackers is typically the best indicator of true swarm size.
Not necessarily. DHT (Distributed Hash Table) operates independently of trackers — some peers may still be available via DHT even when no trackers report any seeders. Try loading the torrent in your client and enabling DHT. However, 0 seeders across all trackers with no DHT activity usually does mean the torrent is dead. For rare or old content, check torrent forums for re-seeds.
The scrape request our server makes exposes our server's IP, not yours. However, if you then download the torrent with your client, your client will announce your real IP to every tracker when it joins the swarm. This is when your IP gets logged. Use a SOCKS5 proxy in your torrent client to prevent this — the tracker sees the proxy IP instead of yours.
The "completed" count (sometimes called "downloaded") is the total number of times any peer successfully finished downloading the torrent and reported it to this tracker. It's cumulative — it doesn't represent how many people are currently seeding, but rather the total all-time download count tracked by that particular tracker. A high completed count with few current seeders means it was once very popular but most people stopped seeding.
The most effective method is a dedicated SOCKS5 proxy configured directly inside your torrent client (qBittorrent, uTorrent, Deluge). This routes all tracker announces and peer connections through the proxy IP — trackers and peers in the swarm see the proxy's IP address, not yours. It works at the application level so only your torrent client is proxied, not your whole system.
A VPN with port forwarding is the second option — it hides your IP system-wide, but most VPNs block inbound connections which kills seeding performance and destroys your ratio on private trackers. Port forwarding solves this but most providers don't offer it.
The ideal setup combines both: SOCKS5 proxy for the torrent client + WireGuard VPN with port forwarding for seeding. This is exactly what TorSentinel Armor provides — a dedicated 10 Gbps SOCKS5 proxy and a WireGuard VPN with port forwarding, built specifically so torrenting works correctly with full privacy. See the Armor plan →
