Free MTProto proxies for Telegram
Every server below answered a real MTProto handshake, not a ping. The list is re-checked continuously and rebuilt every 20 minutes, so what you see is what is alive. Press Connect and Telegram will ask you to confirm the proxy.
- Live servers
- 200
- FakeTLS
- 36
- dd / padded
- 86
- Median latency
- 1236 ms
Snapshot taken 26 minutes ago
| # | Server | Port | Type | Latency | Uptime | Action |
|---|---|---|---|---|---|---|
| 1 | 194.60.228.78 | 2096 | plain | 1214 ms | 100% | Connect |
| 2 | 194.60.228.185 | 2096 | plain | 1214 ms | 100% | Connect |
| 3 | 194.60.228.190 | 2083 | dd | 1214 ms | 100% | Connect |
| 4 | 66.206.25.194 | 443 | dd | 1214 ms | 100% | Connect |
| 5 | 194.60.228.190 | 2083 | plain | 1215 ms | 100% | Connect |
| 6 | 194.60.228.78 | 2096 | dd | 1215 ms | 100% | Connect |
| 7 | 207.89.20.5 | 443 | plain | 1215 ms | 100% | Connect |
| 8 | 51.158.202.129 | 443 | plain | 1216 ms | 100% | Connect |
| 9 | 89.117.222.125 | 8443 | dd | 1216 ms | 100% | Connect |
| 10 | 194.60.228.99 | 2053 | plain | 1216 ms | 100% | Connect |
| 11 | 89.117.222.130 | 8443 | dd | 1216 ms | 100% | Connect |
| 12 | 185.84.156.45 | 444 | dd | 1217 ms | 100% | Connect |
| 13 | 185.84.156.44 | 444 | dd | 1217 ms | 100% | Connect |
| 14 | 176.100.36.117 | 443 | faketls | 1217 ms | 100% | Connect |
| 15 | 194.60.228.55 | 2096 | dd | 1217 ms | 100% | Connect |
| 16 | 89.117.222.130 | 8443 | plain | 1217 ms | 100% | Connect |
| 17 | 45.11.187.41 | 8443 | plain | 1218 ms | 100% | Connect |
| 18 | 159.69.26.26 | 443 | dd | 1218 ms | 100% | Connect |
| 19 | 168.222.43.128 | 443 | faketls | 1218 ms | 100% | Connect |
| 20 | 89.117.222.149 | 8443 | dd | 1218 ms | 100% | Connect |
| 21 | 45.11.187.110 | 8443 | dd | 1218 ms | 100% | Connect |
| 22 | 51.158.201.123 | 443 | plain | 1218 ms | 100% | Connect |
| 23 | 89.19.217.206 | 443 | plain | 1219 ms | 100% | Connect |
| 24 | 188.245.218.105 | 7799 | dd | 1219 ms | 100% | Connect |
| 25 | 194.60.228.185 | 2096 | dd | 1219 ms | 100% | Connect |
| 26 | 45.11.187.130 | 8443 | plain | 1219 ms | 100% | Connect |
| 27 | 194.60.228.63 | 8880 | plain | 1219 ms | 100% | Connect |
| 28 | 212.118.53.195 | 443 | dd | 1221 ms | 100% | Connect |
| 29 | 194.60.228.22 | 2096 | plain | 1221 ms | 100% | Connect |
| 30 | 51.158.202.129 | 443 | dd | 1221 ms | 100% | Connect |
| 31 | 194.120.230.37 | 443 | dd | 1221 ms | 100% | Connect |
| 32 | 176.65.135.69 | 443 | dd | 1221 ms | 100% | Connect |
| 33 | 172.65.97.217 | 22 | plain | 1222 ms | 100% | Connect |
| 34 | 89.117.222.131 | 8443 | plain | 1222 ms | 100% | Connect |
| 35 | 45.11.187.21 | 8443 | plain | 1222 ms | 100% | Connect |
| 36 | 103.161.35.56 | 443 | dd | 1222 ms | 100% | Connect |
| 37 | 194.60.228.250 | 2053 | dd | 1222 ms | 100% | Connect |
| 38 | 194.60.228.70 | 2053 | plain | 1214 ms | 100% | Connect |
| 39 | 167.233.199.65 | 443 | plain | 1223 ms | 100% | Connect |
| 40 | 116.202.35.160 | 25565 | plain | 1223 ms | 100% | Connect |
| 41 | 168.119.142.46 | 443 | dd | 1223 ms | 100% | Connect |
| 42 | 94.156.112.219 | 443 | faketls | 1223 ms | 100% | Connect |
| 43 | 91.107.160.196 | 443 | dd | 1223 ms | 100% | Connect |
| 44 | 46.225.177.120 | 8443 | plain | 1223 ms | 100% | Connect |
| 45 | 194.60.228.22 | 2096 | dd | 1215 ms | 100% | Connect |
| 46 | 194.60.228.90 | 2096 | dd | 1215 ms | 100% | Connect |
| 47 | see.khelijfars.co.uk | 8443 | plain | 1224 ms | 100% | Connect |
| 48 | 194.60.228.11 | 2053 | plain | 1215 ms | 100% | Connect |
| 49 | 89.125.129.198 | 33799 | faketls | 1205 ms | 99% | Connect |
| 50 | 172.65.97.217 | 22 | dd | 1225 ms | 100% | Connect |
How to connect in three steps
- 1
Pick a server
Lower latency means a faster feed. FakeTLS entries survive aggressive filtering better than plain ones.
- 2
Press Connect
The
t.me/proxylink hands the server, port and secret to the Telegram app. Telegram shows its own confirmation sheet — nothing is applied behind your back. - 3
Confirm inside Telegram
Tap Connect Proxy. If the server dies later, come back and take the next row — the ranking already moved it up.
Questions people actually ask
What is an MTProto proxy for Telegram?
MTProto is the protocol Telegram itself speaks. An MTProto proxy relays your Telegram traffic through another server, so the app keeps working when a network blocks Telegram directly. It only affects Telegram, not the rest of your device.
How do I connect a proxy from this page?
Press Connect on any row. The link opens the Telegram app and Telegram itself shows a confirmation dialog with the server details. Confirm it and the proxy is applied immediately.
Why do some proxies stop working?
Public proxies are run by volunteers and go offline without warning. Our checker re-tests every server roughly every 20 minutes and drops the dead ones from this list, so the top rows are the ones alive right now.
What is the difference between FakeTLS, dd and plain?
Plain is the original MTProto proxy mode. dd adds padding that hides packet sizes. FakeTLS wraps the traffic so it looks like an ordinary HTTPS connection, which survives the strictest filtering. Prefer FakeTLS where it is available.
Is it safe to use a public proxy?
The proxy operator sees that you connect and how much traffic you move, but not the content: Telegram keeps its own end-to-end layer on top. Do not use public proxies for accounts you cannot afford to expose, and never enter credentials on a page a proxy asks you to open.