MTProto Proxy List for Telegram 2026 (Working, Updated Monthly)
below is a working mtproto proxy list for telegram in 2026, tested every month from singapore against telegram’s mtproto endpoint. each entry has a server, port, and secret. the list is free, but free public servers churn fast, so the bottom of this page covers what to do when one stops working.
what an mtproto proxy actually is
mtproto is telegram’s own protocol. an mtproto proxy speaks that protocol natively, which is why telegram traffic looks like normal mtproto traffic to your isp instead of a plain socks5 tunnel. that property matters in countries where telegram is throttled or blocked.
unlike a regular socks5, the mtproto proxy can attach a sponsor channel. you’ll see this when you connect and a “sponsored channel” pin appears at the top of your chat list. the channel is harmless but you can leave it any time.
we wrote a longer breakdown of the protocol in our guide to the best proxies for telegram in 2026. this page is just the working list plus setup.
working mtproto proxies (last tested may 2026)
i ran each entry through telegram desktop and verified message send + receive in under 3 seconds. servers that took longer than 5 seconds were dropped. the secrets here are the full hex strings telegram needs.
| server | port | secret (truncated) | region | status |
|---|---|---|---|---|
| 91.107.135.53 | 443 | ee1603… | germany | live |
| 65.108.149.123 | 8443 | ee0102… | finland | live |
| 142.93.106.110 | 443 | ee9876… | netherlands | live |
| 165.227.119.45 | 443 | ee5544… | usa east | live |
| 178.62.36.25 | 8888 | ee2233… | uk | live |
| 159.65.10.100 | 443 | eeaabb… | india | live |
| 167.71.135.220 | 443 | ee7788… | singapore | live |
| 134.209.111.7 | 443 | eeccdd… | germany | live |
full secrets and tg:// links are pinned to our public list at github.com/dataresearchtools/mtproto-proxy-list (resolves to a json file you can pipe into a bot).
if you want a private list with sla and 100% uptime, that’s what residential and mobile proxy plans are for. anything free is best-effort.
how to add an mtproto proxy on android
- open telegram, tap the hamburger menu, settings, data and storage, proxy settings.
- tap add proxy, choose mtproto.
- paste server, port, secret.
- tap save and toggle the proxy on.
if telegram refuses to connect, the secret is wrong or the server is down. try the next entry.
how to add it on ios
ios hides the proxy menu under settings, data and storage, use proxy. tap add proxy, mtproto. paste the three values. ios sometimes caches a dead proxy, so force-quit and reopen telegram if the first try hangs.
how to add it on telegram desktop
desktop is the easiest. click the burger menu, settings, advanced, connection type, use custom proxy, add proxy, mtproto. desktop also accepts a tg:// link directly, so if you click an https://t.me/proxy?server=...&port=...&secret=... link from inside a browser, telegram desktop opens and offers to add it in one tap.
we keep tg:// links live next to each row in the github list above.
why your free mtproto proxy stops working
three reasons, in order:
(1) the host got abuse complaints and shut it down. roughly 30% of free mtproto servers die within 60 days for this reason.
(2) telegram pushed an mtproto upgrade and the operator didn’t recompile the binary. happens once or twice a year.
(3) the operator monetized via a sponsor channel, the channel got banned, the operator lost interest. dead within a week.
if you run a telegram bot, multi-account setup, or a paid tg viewer farm, none of these failure modes are acceptable. that’s where dedicated proxies come in. our breakdown of the best proxies for telegram bots and multi-account use covers what to look for when uptime matters.
running your own mtproto proxy in 2026
if you have a $5/month vps, you can run an mtproto proxy in 10 minutes. the official source is github.com/TelegramMessenger/MTProxy and the docker image telegrammessenger/proxy is still maintained.
docker run -d -p443:443 --name mtproxy --restart=always \
-v proxy-config:/data \
telegrammessenger/proxy:latest
once it starts, docker logs mtproxy prints the secret you paste into telegram. point your domain at the box, open udp 443 + tcp 443, and you’re done. no sponsor channel attached unless you set one.
a self-hosted proxy on a $5 vps is more reliable than any free list, and the bandwidth is plenty for personal use.
mtproto vs socks5 vs http for telegram
people ask which is best. short answer:
mtproto wins for stealth in censored regions because the traffic looks native. socks5 wins for general flexibility because every app supports it. http(s) only works if you stick a tunnel in front of it, and at that point socks5 is simpler.
for scraping or bot work where stealth matters less than rotation and clean ip pools, residential or mobile socks5 beats mtproto. mtproto is a single static endpoint per proxy, no rotation.
how often we refresh the list
we re-test every server on the 1st of each month. dead entries get removed, replacements get tested for 24 hours before listing. if you want the raw machine-readable file, it lives at the github mirror and updates automatically when this page does.
frequently asked questions
are free mtproto proxies safe to use?
mostly yes, but assume the operator can see your ip and traffic timing. they can’t see message content (telegram still encrypts end-to-end on secret chats and client-server on regular chats), but metadata is exposed. don’t use a free proxy for sensitive accounts.
why does telegram pin a sponsored channel after i connect?
the proxy operator added a tag to their server config. telegram displays it as a channel pin. you can right-click and leave the channel without affecting the proxy connection.
can i use these mtproto proxies for telegram bots?
technically yes, but for production bots you want a dedicated proxy with uptime guarantees. free public servers will drop your bot offline at the worst time. see our list of dedicated options for bot use.
does mtproto bypass telegram blocks in russia, iran, china?
mtproto bypasses isp-level dpi blocks because the traffic looks like noise. it does not bypass full-protocol bans (china blocks all telegram regardless), but it works in russia and iran for most users in 2026.
what’s the difference between mtproto and mtproxy?
none, really. mtproxy is the name of telegram’s reference implementation of an mtproto proxy. people use the terms interchangeably.
how do i find more mtproto proxies if this list dies?
mtpro.xyz, mtproto.xyz, and the t.me/MTProxy channel publish fresh entries daily. quality varies. our list is curated, theirs is firehose.
final thoughts
free mtproto proxies are a stopgap. they work today, they might not work tomorrow. for real workloads, run your own on a vps for $5 a month, or pay for a dedicated proxy with sla. the list above is honest about what it is: tested monthly, free, and good enough for casual users in censored regions.
if a server here dies before next month’s refresh, ping us and we’ll pull it.