Public Mirror Leech
t.me · Debrid · 1 record · JSON
Public Mirror Leech (@publicmirrorbot) Debrid
caveatany-phoneno cardphoneRper-object-cap
| Free tier | Leech: upto 80 GB/link (4gb support); Yt-dlp: upto 80 GB/link; Mega.nz Link: upto 80 GB/link; Daily Limit: Unlimited". unit unlimited; metered on none; Unlimited refers to the daily count of links, not to bytes in flight; each link is capped at 80 GB. |
|---|---|
| Price | USD 0 |
| Per-object cap | 80 GB per link on every mode: mirror, leech, yt-dlp and MEGA. (85899345920 bytes) |
| Retention | Not stated. A mirror lands in operator storage and a leech lands in the user's Telegram; no expiry is published for either. |
| Egress | The bot pulls from a remote URL and re-serves it: a mirror returns a link on the operator's host, a leech returns the file into the chat. No bandwidth figure or price is published. free_allowance: unlimited daily link count |
| Identity | any-phone A Telegram account is the only gate: any phone number that can receive the signup code. No email, payment or identity document is asked for by the bot. |
| Limits |
The 80 GB figure is generous for a free bot and is the only hard number the operator publishes. Nothing is said about how many tasks may run at once, which is where a shared public bot actually queues. |
| Binding | per-object-cap At 1 TiB a month the link ceiling is what stops a single transfer: 80 GB is about 12 links to the monthly target, so a 1 TiB archive has to be split. The daily count is explicitly unlimited, so it cannot bind. |
| Interface | unknown A Telegram bot, not an HTTP service: the control channel is Telegram chat with @publicmirrorbot, and there is no documented REST endpoint. The bot's preview names a fallback bot and a support group rather than an API. |
| Tooling | Telegram client only. Automating it means driving a Telegram user session, which is a real constraint for a client that wants a script rather than a chat window. |
| Composes with | A resolver for links a normal client cannot fetch: a MEGA or yt-dlp URL goes in, a direct file comes out, and it bypasses the per-host limits a downloader would otherwise meet. It is the human-shaped version of what a debrid subscription does, with an 80 GB per-link ceiling instead of a monthly one. |
| Reliability | A shared public bot with no SLA and an operator who publishes limits in a channel post rather than a page: the 80 GB figure can change in one message, and the bot's uptime depends on somebody else's server. |
| Notes | Classified as a service because it resolves and fetches remote URLs rather than mirroring an account: a client hands it a URL and gets bytes back. The account-mirror bots in the same ledger were not recorded, because they only drive somebody's own cloud account. |
| Evidence rung | reported Moving to documented needs the numbers on a stable page; moving to measured needs one 80 GB job run and read. |
| Checked | 2026-10-24 (live); stale on 2026-11-07 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | t.me/s/PublicMirrorLeechUpdates | the limits post verbatim: 80 GB per link on mirror, leech, yt-dlp and MEGA, and 'Daily Limit: Unlimited' |
| 2026-10-23 | t.me/publicmirrorbot | the bot exists as 'Mirror Leech Bot 3' and links @PublicMirrorLeechGroup and @PublicMirrorLeechUpdates as its group and channel |
| 2026-10-23 | t.me/PublicMirrorLeechGroup | 3,088 members and 380 online, which is the scale signal for a public bot's queue |
More fields (1)
{
"modes": "mirror, leech, yt-dlp, MEGA"
}Unknown or withheld values (3)
$.free_tier.statedpartly-held$.interfaceinterface-unknown$.per_object_cap.notespartly-held