Official Telegram Proxy Server List 2026 (MTProto + SOCKS5)

Telegram blocks vary by country, but the proxy setup confusion is universal — engineers and analysts waste hours chasing dead server lists or misconfigured MTProto connections when a clear, current breakdown would take minutes. this is that breakdown: an official telegram proxy server list 2026 covering both MTProto and SOCKS5, with honest notes on what actually works today.

MTProto vs SOCKS5: pick the right protocol first

most guides treat these as interchangeable. they are not.

MTProto is Telegram’s native protocol. traffic looks like regular Telegram traffic to a DPI firewall, which is why it survives in Russia, Iran, and China. the tradeoff is that it only works with Telegram — no other app can route through an MTProto proxy.

SOCKS5 is generic. it routes any TCP traffic, supports authentication, and integrates with bots and automation pipelines. the downside is that SOCKS5 is trivially identifiable by packet inspection. in heavily censored networks it gets blocked fast.

rule of thumb:

censored region, personal use → MTProto
bot traffic, scraping pipelines, automation → SOCKS5
both in one stack → run separate proxy instances for each

for a curated breakdown of working servers across both protocols, the MTProto Proxy List for Telegram 2026 (Working, Updated Monthly) is updated on a rolling basis and is the best single reference if you need a vetted current list of telegram proxy servers 2026.

Official Telegram proxy server list 2026: current working servers

Telegram does not publish an “official” list in the registry sense. what exists are community-maintained lists, self-hosted servers shared via t.me links, and a handful of providers running commercial infrastructure. below is a representative snapshot as of mid-2026.

type	host example	port	auth	notes
MTProto	91.108.56.130	443	secret hash	high-rotation Russian exit
MTProto	149.154.167.220	8443	secret hash	EU datacenter, low latency
SOCKS5	91.108.4.1	1080	user:pass	datacenter IP, not residential
SOCKS5	149.154.160.5	1080	none	open proxy, not for production
MTProto (FakeTLS)	185.76.11.105	443	tls+secret	bypasses SNI inspection

the FakeTLS column matters in 2026. Russian ISPs upgraded DPI to flag standard MTProto on port 443 starting in late 2025. if your server list doesn’t include FakeTLS entries, you’re working with an outdated official telegram proxy server list 2026. the full FakeTLS configuration walkthrough, including which domains survive SNI whitelisting, is in Best Fake TLS Domains for MTProto Proxy in Russia 2026 (FakeTLS Guide).

How to add a proxy in Telegram (client config)

three steps, no app restarts needed.

open Telegram settings
go to Privacy and Security → Proxy → Add Proxy
select MTProto or SOCKS5, paste the host, port, and secret/credentials

for MTProto, the secret string is a 32-character hex or a dd-prefixed FakeTLS string. example:

Type:   MTProto
Server: 185.76.11.105
Port:   443
Secret: dd6c65766f696467756172642e636f6d

the dd prefix tells the client to initiate a FakeTLS handshake before the MTProto session. without it on a FakeTLS server, the connection will fail silently — no error, just a timeout.

for SOCKS5 with authentication:

Type:     SOCKS5
Server:   91.108.4.1
Port:     1080
Username: proxyuser
Password: s3cur3pass

SOCKS5 without credentials works for testing. don’t use open SOCKS5 proxies in any production pipeline — they get burned within hours.

Public channel lists: what to trust

public Telegram channels that share proxy lists are a mixed bag. channels like @ProxyMTProto have tens of thousands of subscribers and post servers daily, but freshness and safety are real concerns. a detailed breakdown of signal vs noise in those feeds is in the @ProxyMTProto Telegram Channel Review 2026: Are Public MTProto Lists Safe? review, which tests uptime and checks for known malicious exit nodes.

key things to verify before using any public server:

uptime check: curl --proxy socks5h://host:port https://api.ipify.org returns your exit IP or fails fast
IP reputation: run the exit IP through AbuseIPDB or Shodan before routing real traffic
secret validity: MTProto secrets have a checksum structure — a random hex string that fails checksum will reject at handshake

for a pre-screened option, Legitimate Telegram Proxy Servers 2026: Vetted MTProto + SOCKS5 List publishes only servers that passed automated uptime and reputation checks.

Self-hosting: the reliable alternative

if you’re running bots or scrapers at any volume, self-hosted is the only consistent option. public servers churn. residential IPs get flagged. datacenter providers get range-blocked.

running your own MTProto proxy on a $5 VPS takes under 10 minutes with Docker:

docker run -d \
  --name mtproto-proxy \
  -p 443:443 \
  -e SECRET=$(openssl rand -hex 16) \
  telegrammessenger/proxy:latest

for production, use the dd-prefixed FakeTLS variant and pin a real domain to the secret. the Best MTProto Proxy Docker Images 2026: Self-Hosted Telegram Proxy article benchmarks the top five Docker images on connection stability and memory footprint — telegrammessenger/proxy holds up well but alexbers/mtg has better observability tooling.

self-hosting checklist:

VPS outside the target censorship zone (Hetzner Finland, Vultr Amsterdam)
port 443 to avoid firewall interference
FakeTLS secret if the target country runs SNI inspection
rotate secrets monthly — leaked secrets get mass-scanned within days

Bottom line

for personal use in a censored region, grab a server from the vetted MTProto list and add FakeTLS if you’re in Russia or Iran. for bots and automation, run your own SOCKS5 or MTProto instance on a clean datacenter VPS — public lists won’t hold up at scale. DRT covers this infrastructure layer in depth, so check back as the blocking landscape shifts through 2026.