Tracker Rules & Announce
Learn about the official AniBT Tracker announce address, 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:
https://tracker.anibt.net/announce- Protocol: Connect using HTTPS on port 443.
- Currently unavailable: UDP is not enabled. Public
/scrapeand legacy/announce/v1/*paths remain closed.
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.
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.
{
"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.
{
"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": [...] } is deprecated. During the transition it is still answered in the old format, with a Deprecation: @1790985600 header (2026-10-03 00:00 UTC). A later release will remove it; switch to releases.