Proxies for Telegram
Proxies that pass the Telegram service-access check.
Proxies that pass the Telegram service-access check.
Addresses are collected by the telegram=1 service test result rather than a single hardcoded type. In practice SOCKS5 is often the best fit for Telegram, but the service test is more useful than a formal type restriction because it shows proxies that actually reach the Telegram API.
telegram=1Main use cases
- Telegram bots
- API usage (TDLib, Telethon)
- Bypassing Telegram blocks
- Multi-account Telegram
- Channel and group scraping
Proxies for Telegram
The full list keeps this service preset and adds extra filters on top of it.
Buy access Open listWhat you can refine next
- Country and city
- Proxy type and HTTPS support
- Anonymity level
- Ping, uptime and last-check time
Proxy table
Masked demo subset with the same service filter.
| Address and type | C | Anon. & services | Speed, latency | Location | Uptime | Updated |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Showing a masked 12-row preview. The full list and exact addresses stay behind the dashboard and API.
Continue with ready-made presets
After a service wrapper, the next step usually mirrors the full proxy list flow: keep the original verification slice and add one more filter on top of it.
Related use-case pages
If the current service slice is too narrow or you need a neighbouring scenario, keep moving without rebuilding links by hand.