Collect & identify
Aggregate public lists, resolve DNS, and distinguish server endpoints from duplicate aliases.
A public, open-source MTProto proxy directory with three-round end-to-end checks, distinct server counts, clear selection criteria and disclosed testing limits.
Tested at the runner location — not a guarantee for every ISP.
Meet @configexBot, the Telegram bot from Raydikalx. A free-proxy section connected to this repository is planned, so you can discover proxy links and open them inside Telegram instead of navigating back through a browser.
The bot link works now. Free proxy delivery inside the bot has not launched yet.
Or browse proxies on this pageA clear view of the network, not just a long list of links.
| SERVER / OPERATOR | LOCATION | PROTOCOL | RTT | HISTORY | Action |
|---|
Try a different search or filter.
Measured by real network responses, with clear selection rules and inspectable output.
Aggregate public lists, resolve DNS, and distinguish server endpoints from duplicate aliases.
Confirm actual MTProto replies from Telegram datacenters in all required test rounds.
Prioritize independent server IPs, historical uptime, and measured runner-side latency.
Many working links may resolve to the same IP. The repository reports links and real server counts separately.
Latency and uptime are historical measurements from the designated test runner, not the visitor’s browser or ISP.
The public README documents the test method, the data format and important limitations. There is no promise that each proxy works everywhere.
The current repository recommends top100.txt: independent resilient servers, proven uptime before speed, and normally at most five selected links per network. The published network cap may rise if needed. top50.txt remains a compatibility subset, not the primary recommendation.
Open recommended Top 100 on GitHub →Tap any Connect link in the explorer, or any line of top100.txt, and Telegram asks to connect. To add one by hand: Settings → Data and Storage → Proxy → Add Proxy → MTProto, then enter the server, port and secret.
Click a Connect link, or open Settings → Advanced → Connection type → Use custom proxy → Add proxy → MTProto and enter the same three values.
Try another one. Tests run from the runner location, so a proxy that passed there can still be blocked on your network. Telegram keeps message content encrypted, but the proxy operator can see your IP address.
Answers grounded in the public repository, its verification methodology and its documented limitations.
It is an open-source collection of Telegram MTProto proxy links maintained by 0xRadikal under the Raydikalx brand. It groups results by verification and selection criteria rather than promising universal access.
The project tests whether a proxy relays an MTProto request to a real Telegram datacenter and returns the expected response containing the test nonce. Verified proxies must pass all three rounds. A successful TCP connection alone is not enough.
Verified includes links that pass every end-to-end round, which may contain multiple aliases for the same server. Resilient keeps at most one link per server IP so repeated domains do not inflate apparent server diversity.
Fast is the fastest quarter of the resilient list by median round-trip time measured from the test runner. Stable requires at least 90% success over the recent history, with a minimum of 12 checks.
No. Tests are carried out from the indicated runner location. Firewalls and censorship differ by network, and runner-side measurements cannot guarantee reachability from your own provider.
The proxy operator can see your IP address and connection metadata. Telegram protects message content using its own MTProto encryption; this project does not certify operators or post-login sponsored channels.
The GitHub repository publishes machine-readable index.json, tier-specific proxies.json files, direct Telegram links and selection criteria. You can inspect the source, issue history and methodology independently.