Tracker Rules & Announce

Learn about the official AniBT Tracker announce address, scrape, torrent creation setup, whitelist mechanism, torrent file downloads, and the tracker stats endpoint.

AniBT operates a high-speed BitTorrent tracker specifically dedicated to anime releases published on our platform.

Whitelist Communication Policy: To prevent traffic abuse and spam torrents, the AniBT Tracker enforces an infohash whitelist. Only torrents successfully published on AniBT are automatically registered into the whitelist. Unregistered torrents announcing to this tracker will receive a not whitelisted error.

Official Tracker Announce Address

When creating .torrent files or configuring trackers in your BitTorrent client, use the standard announce URL:

AniBT Tracker Announce URL
https://tracker.anibt.net/announce
  • Protocol: Connect using HTTPS on port 443.
  • Currently unavailable: UDP is not enabled. Legacy /announce/v1/* paths remain closed.
  • Partial downloads: libtorrent-based clients such as qBittorrent and Deluge announce event=paused (BEP 21) when only some files are downloaded. The tracker treats it as a regular announce instead of returning an error.

Scrape

BitTorrent clients derive https://tracker.anibt.net/scrape from the announce URL to read seeder, leecher, and completion counts (BEP 48). No extra configuration is needed.

  • GET only. Send 1–64 info_hash values, each 20 bytes; the query string must not exceed 4608 bytes. Requests outside these bounds are rejected.
  • Whitelisted torrents return real complete (seeders), downloaded (completed), and incomplete (leechers) counts. A hash that is not whitelisted does not get not whitelisted; all three counts are 0.
  • Scrape shares the announce rate limits. When the tracker is busy it still answers HTTP 200 with an empty files dictionary and flags.min_request_interval; wait at least that many seconds before scraping again.

To look up stats by release ID, use the tracker stats endpoint below.

Check service status

Visit the Tracker status page to view seeders, leechers, tracked torrents, completed downloads, and connections. Select a 30-, 60-, or 90-minute history window and switch between peer, torrent, completion, and connection views.

Data updates every minute. Outdated or unavailable snapshots are clearly marked. Missing measurements display —, and charts never invent missing history. Peers are counted per torrent swarm, not as unique users. Connections include idle connections and are not counts of seeders or leechers.

The selected time window keeps its full span. Shaded regions mark missing samples, and lines do not bridge those gaps. Each chart shows the valid sample count and recorded time range. The announce mean includes valid samples only.

The vertical axis starts at zero by default. Select Fit data to inspect small changes in cumulative completions or other metrics; the starting value is shown below the chart. Completed downloads remain a cumulative count.

Hover over a chart or tap it on a phone to inspect the exact time and values. Tapping a gap reports that no sample is available. With the chart focused, use the arrow keys to move between samples, Home / End to jump to the first or last sample, and Esc to clear the selection. Expand View sample details to read individual records in the current window.

Torrent Creation and Publishing Workflow

Add Tracker in Torrent Creator

When creating a torrent with qBittorrent, Transmission, or mktorrent, place https://tracker.anibt.net/announce at the top of your tracker list.

Publish Release on AniBT

Upload the generated .torrent file via your fansub group console or through the Release API. Once accepted into the catalog, its infohash is instantly added to the tracker whitelist and included in the resulting magnet URI.

Seed from Your Client

Load the torrent into your seeding client and verify that the tracker status shows working. Downloader clients fetching magnets or torrents from AniBT will immediately establish peer connections with you.

Torrent Download Endpoints

AniBT provides direct binary .torrent download endpoints for third-party downloaders and automation scripts:

Prop

Type

Tracker Stats Endpoint

Look up seeders, leechers, and completed downloads for a batch of releases by release ID. No login is required, and cross-origin requests are allowed. Neither the request nor the response contains an infohash.

POST https://anibt.net/api/tracker-stats/batch

Send a JSON body that lists the releases in releases.

Request example
{
  "releases": [
    { "kind": "release", "releaseId": "rel_dE7jiWrXPwPw" },
    { "kind": "other-release", "releaseId": "orel_wiki_audit_missing" }
  ]
}

Prop

Type

statsByRelease groups the results by kind and release ID. Both the release and other-release groups are always present. now is the server time in Unix milliseconds.

Response example
{
  "statsByRelease": {
    "release": {
      "rel_dE7jiWrXPwPw": {
        "state": "fresh",
        "seeders": 53,
        "leechers": 44,
        "completed": 64,
        "updatedAt": 1791023419906,
        "refreshQueued": false
      }
    },
    "other-release": {
      "orel_wiki_audit_missing": { "state": "unavailable" }
    }
  },
  "now": 1791023794205
}

Prop

Type

Errors are JSON; see Conventions and authentication for the format.

Prop

Type

The old request body { "infoHashHexes": [...] } was removed on 2026-11-13 and now returns 422 VALIDATION_ERROR. Use releases.

On this page