Proxy for Telegram
Telegram accepts a SOCKS5 proxy in the app itself, no extra software. The question worth answering is which address you point it at, because accounts, bots and bulk collection each want a different one.
What Telegram actually checks
- Your phone number first. Telegram identities are numbers, not addresses, and most limits people run into follow the number rather than the connection.
- The address the session connects from, and whether many accounts share it. A dozen accounts arriving from one address is the pattern that gets them tied together.
- How the account behaves early on. New accounts that immediately message strangers get restricted no matter how clean the address is.
- Whether the address is reachable at all. Some networks block Telegram outright, which is a connectivity problem rather than a reputation one.
Which of our products fits which Telegram job
Four different jobs, four different answers. Buying one product for all of them is the usual mistake.
| What you are doing | What we would use | Why that one |
|---|---|---|
| Holding a few personal accounts | Mobile, one modem per account | A carrier address is what an ordinary Telegram user connects from. At $5.76 a day it only makes sense for accounts worth that. |
| Holding many accounts at once | ISP, one address per account | Fixed for the term, no traffic metering, cheap enough per month to give every account its own. Stability matters more than being residential here. |
| Running a bot on the Bot API | IPv4 datacenter | Your server talks to api.telegram.org over plain HTTPS. Nobody is judging the address, so pay the least for a stable one. |
| Reading public channels in volume | Residential, rotating | Many connections over time from one address is the thing that draws attention. Rotation spreads it, and you pay per gigabyte rather than per address. |
If an account matters to you, give it one address and keep it. Moving an established session to a new country overnight is a stronger signal than anything the address itself carries.
Setting it up
Telegram has SOCKS5 support built in, on desktop and on both mobile apps. For bots and userbots the proxy goes in your code instead.
# In the app: Settings > Data and Storage > Proxy > Add proxy > SOCKS5
Server proxy.sotaproxy.com
Port 10000
Username login_c_US_s_42_ttl_1h
Password your password
# On a static product, point it at the address you own instead:
Server 198.51.100.20
Port 50100
# Bot API from your own code:
proxies = {"https": "socks5://login:password@proxy.sotaproxy.com:10000"}
# Telethon and Pyrogram take the same SOCKS5 details
# pip install python-socks[asyncio]- Telegram also speaks MTProto proxy, which is a Telegram-specific protocol. We sell SOCKS5 and HTTP, which the app supports natively, so use the SOCKS5 option.
- On the residential gateway, the session suffix is what keeps one account on one address. Without it the exit changes and your session moves country mid-conversation.
- One session identifier per account. Two accounts sharing a number share an address, which defeats the point of buying two.
- A residential session ends when the household device goes offline, at an hour at the latest. For an account you intend to keep, that is an argument for ISP or mobile.
What to buy for Telegram
Telegram is the one platform here where the cheapest product is genuinely the right answer for a large share of the work. Prices are entry prices and fall with volume.
Datacenter IPv4
from $1.50 per IP per month, 41 countries
For bots. A bot talking to api.telegram.org is a server talking to a server, and nobody is grading the address.
- The cheapest stable address we sell, and stability is all a bot needs
- Traffic is not metered, so a busy bot costs the same as an idle one
- 41 countries, more than ISP
- The range is recognisable as a datacenter, which matters for accounts and not for bots
- Wrong choice for anything logged in as a person
ISP proxies
from $2.30 per IP per month, 24 countries
For accounts you keep. One address per account, fixed for the whole term.
- Registered to a consumer provider, so it reads as a home connection
- Never moves, which is what a long-lived session wants
- Traffic is not metered
- Dearer per address than IPv4, which is the point rather than a flaw
- 24 countries
Residential proxies
from $2.00 per GB, 220+ countries
For reading public channels in volume, and for reaching Telegram from networks that block it.
- A new exit per connection, which spreads collection across many addresses
- More countries than anything else we sell
- A session suffix holds one exit when you need continuity
- A session ends when the household device drops, one hour at most
- Billed by traffic, so media-heavy channels add up
Mobile proxies exist and work here, but Telegram is not the platform that justifies them. Unlike Instagram, it weighs the phone number far more heavily than the connection, so the extra money is better spent on numbers than on addresses.
Where people go wrong
Buying residential for a bot
A bot calling api.telegram.org is a server talking to a server. Paying per gigabyte for household addresses buys nothing here.
One address, many accounts
The cheapest setup is also the one that ties every account to every other. If the accounts are meant to be unrelated, they cannot share an exit.
Rotating under a logged-in session
Leaving the session suffix off means a new exit per connection. Telegram tolerates more of this than most platforms, but it is still the wrong shape for an account you care about.
Expecting the address to unban a number
Restrictions on Telegram usually attach to the phone number and to what the account did. A new address does not lift them.
What a proxy will not do here
It will not restore a number that has been limited, it will not stop reports from other users, and it will not make a new account safe to message strangers from. Telegram polices behaviour and numbers far more than it polices addresses. Buy a proxy to keep accounts apart and to reach the service from networks that block it, not as protection against what the accounts actually do.
Questions people actually type
Does Telegram support proxies natively?
Yes. Settings, then Data and Storage, then Proxy. It takes SOCKS5 with a username and password, on desktop, iOS and Android alike. No extra software is involved.
SOCKS5 or MTProto?
MTProto is Telegram’s own proxy protocol and needs a server running it. We sell SOCKS5 and HTTP, which the app supports out of the box and which also work for everything else you run.
Which proxy type is best for Telegram accounts?
Mobile if the account is worth $5.76 a day, ISP otherwise. Both give you one address that stays put, which is what an account wants. Residential works with a session suffix but the exit can drop when the household device does.
How many Telegram accounts per IP?
One, if the accounts are meant to look unrelated. Sharing an address is precisely the link you are paying to avoid. If they are openly yours, sharing costs you nothing.
Will a proxy stop my account being banned?
No. Telegram limits follow the phone number and the behaviour behind it. An address keeps separate accounts separate and gets you connected from networks that block Telegram. It does not make an account immune.
Can I use a proxy for a Telegram bot?
Yes, and a plain IPv4 datacenter address is the sensible choice. Point your HTTP client at the proxy and call api.telegram.org as usual. Telethon and Pyrogram take the same SOCKS5 details through python-socks.
Where the claims above come from
Telegram documents more of this than most platforms, which makes it easy to check rather than take on trust. Primary sources only.
- Telegram Bot API documentationConfirms bots are plain HTTPS calls to api.telegram.org. This is the whole reason a cheap datacenter address is the correct choice for a bot: there is no reputation check to pass.
- Telegram, obtaining an api_idStates that one phone number carries one api_id, that accounts on unofficial clients are placed under observation, and that flooding earns permanent bans. It also warns that the sample api_id triggers flood errors, which is the single most common reason a userbot stops working and one no proxy will fix.
- RFC 6269, Issues with IP Address Sharing (IETF)Background for the residential and mobile options: a shared address stops identifying one subscriber, and blocking it penalises everyone behind it.