Telegram in Russia 2026: why it's throttled, not blocked, and what still works

Telegram is not blocked in Russia. That’s the first thing to get straight, because almost everyone gets it wrong. The app opens, text loads, so people assume it’s working fine. Then they try to send a photo and it stalls. They try a voice call and the audio drops within seconds. What’s actually happening is throttling, deliberate and tuned, and if you don’t understand the mechanism you’ll waste months cycling through VPNs that die one after another.

I run managed Telegram hosting on dedicated hardware in Singapore, so I watch this problem from the infrastructure side every day. Russia’s filtering runs through TSPU, the “sovereign internet” hardware mandated under the 2019 law. Roskomnadzor never made peace with Telegram after the failed blocking attempt from 2018 to 2020. They learned from that loss. Instead of hard blocks that generate headlines and push everyone straight to VPNs, they shifted to a quieter strategy: throttle, degrade, and make the experience miserable enough that casual users quit on their own.

What TSPU actually does to your traffic

The numbers tell the story. By early 2025, Rostelecom, the largest ISP in Russia and controller of roughly 40% of fixed line connections, had rolled out updated TSPU hardware across most of its major transit points. MTS and MegaFon followed with their own rollouts through 2025. The practical result is that Telegram download speeds in Moscow and Saint Petersburg regularly drop to 20 to 40 kilobits per second on mobile during peak hours. That’s enough to load text. It is not enough for voice, video, or Stories. Group calls become unusable. The app works, technically, but not in a way that sustains a business or a community.

There’s a second layer of friction in 2026 that doesn’t get talked about, and it’s doing more damage than the throttling itself: payment infrastructure. Mir cards and sanctioned bank card equivalents can’t pay most offshore VPN subscriptions. Crypto payments work, but the average Russian user trying to keep Telegram alive isn’t going to self-custody a wallet just to buy a monthly VPN plan. So the population that can actually route around the censorship is shrinking, not growing. That payment gap is quietly doing more harm to circumvention tools than the deep packet inspection ever did.

Why your VPN keeps dying

There are four mechanisms working against you here, and you need to understand all of them.

The first is DPI fingerprinting. The same TSPU units Rostelecom runs can identify VPN protocol signatures even when the traffic itself is encrypted. WireGuard handshakes have a recognizable pattern. OpenVPN over TCP on port 443 used to fool these systems, but the updated rulesets from late 2024 onward have caught up. Handshake timing, packet sizes, and TLS fingerprints are all features in the detection model now. The system doesn’t need to read your traffic to classify it as VPN-like and worth throttling.

The second is IP list enumeration. Every major consumer VPN publishes its server IPs, directly or indirectly through Autonomous System lookups, and RKN maintains these lists actively. If your VPN runs servers in the same address block as ten other already-blocked endpoints, your IP is likely in the database before you even connect. Datacenter ranges from the big cloud providers are almost completely burned for this use case in Russia. You can verify it yourself: connect, check your exit IP on any geolocation service, and if it comes back as a German datacenter, you’re already visible.

The third is SNI inspection. TLS connections advertise a hostname in the SNI field during the handshake, unless encrypted client hello is active, and most consumer VPN providers don’t enable that by default. RKN can see the hostname you’re connecting to without breaking the encryption at all. If that hostname resolves to a known VPN gateway, the connection gets throttled or dropped. You did nothing wrong; the protocol told on you.

The fourth is collateral damage by design. When a VPN or proxy IP gets blocked, the addresses next to it frequently go with it. Shared residential proxy pools that rotate you through thousands of addresses burn through their Russia-accessible inventory constantly. What worked yesterday is gone by Tuesday. You end up spending more time debugging your connection than using Telegram.

What still works, ranked honestly

MTProto proxies, Telegram’s own native proxy protocol, are still usable in Russia as of early 2026. The catch is they need a fresh address every week or two as individual endpoints get listed. Public lists go stale fast. Russian channels rotate working addresses, but you’re on a treadmill: new address, works for a few days, throttled, repeat. For a journalist checking Telegram a few times a day, this is workable. For anyone running a channel, a business, or a bot that needs consistent uptime, it isn’t.

Next up is mobile SOCKS5 routing through a neutral jurisdiction. A SOCKS5 proxy on a real mobile IP in a country without internet sovereignty disputes gives you traffic that looks, to the DPI system, like ordinary mobile data from a foreign roaming user, a completely different signature from a datacenter VPN. It can work well, but you still have to source a reliable endpoint and pay for it, and the same payment friction that hits VPNs hits proxy services too. If you go this route, verify the endpoint before you trust it: the org field should show SingTel, M1, StarHub, or Vivifi, and the country should show SG. If you see a datacenter ASN or any country other than Singapore, it isn’t what it was advertised as, and you shouldn’t route Telegram through it. The socks5h scheme matters here too, since it forces DNS resolution through the proxy rather than on your own machine, which prevents the DNS leaks that would otherwise reveal your real location.

The option with the highest survival rate, for anyone running a serious Telegram operation, is a fully managed cloud phone. Your Telegram session lives on hardware in Singapore, running around the clock, pinned to one carrier IP, and you access it remotely through a browser. From inside Russia, all you’re sending is remote session traffic, not Telegram protocol at all. There’s nothing on your local network for TSPU to fingerprint as VPN-like, because structurally it’s just a streaming session that looks like remote work software.

Why Singapore specifically

The censorship calculus for any regulator is simple: what does blocking this thing cost, relative to what’s gained. Singapore is Russia’s third largest trading partner in Southeast Asia, and Russian companies move significant commodity, financial, and logistics traffic through it. The diplomatic cost of appearing to block Singaporean carrier ranges, particularly while Russia is actively courting ASEAN neutrality, isn’t trivial. RKN blocks Cloudflare IPs without hesitation. It does not block SingTel or M1. That asymmetry is the whole point. It’s not about being clever, it’s about choosing a jurisdiction where the political cost of blocking is too high relative to the benefit.

The honest tradeoff is latency. Singapore to Moscow runs roughly 85 to 110 milliseconds round trip, depending on your ISP and routing that day. If you use Telegram for voice calls, you’ll notice it, since a 90 millisecond one-way delay on top of Telegram’s own jitter budget makes calls feel slightly sluggish. But text messages, media delivery, bots, and channel management aren’t latency sensitive in practice. A message sent arrives in under a second regardless of where the session lives. The latency issue only applies to real time audio and video, which is a small slice of how most Telegram operations actually use the app.

The setup differs from a proxy because there’s nothing to configure on your own machine. You log in once through a browser-based session, and the Telegram session on the Singapore hardware is already live. You authenticate with your own phone number and your own OTP, which only you see at the moment of login. After that, the session runs on real hardware in Singapore, pinned to one carrier IP, managed through the browser.

Account safety from inside Russia

The country code you registered with matters more than most people realize. A +7 number draws more platform attention when an account starts behaving unusually, because the volume of spam operations historically run through Russian virtual numbers has trained Telegram’s risk systems accordingly. If your +7 account suddenly connects from Singapore IPs and starts driving heavy activity, that pattern can trigger a review. So the first thing to do, before anything else, is enable two-step verification under Privacy and Security. That’s a password layered on top of your SMS code, so if someone intercepts your OTP through a SIM swap, they still can’t get in. SIM swap fraud targeting Russian numbers is well documented, so this isn’t theoretical.

A couple more calls worth making. Turn off contact sync unless you specifically need it, since Telegram uploads your phone address book to find contacts, and that’s a list of real people permanently associated with your account and its metadata. And on the number question: if you’re starting a new channel operation and have the option, a +65, +44, or +1 number will statistically face less friction than a +7. But if you’re an individual with an established +7 account, years of history, contacts, and group memberships, keep it. Swapping the number on an aged account carries its own risk, and some users report their account behaving as if partially new afterward, losing discoverability. Don’t throw away your history to chase a marginal gain.

The operational benefit

Russian internet gets throttled aggressively during politically sensitive windows, evenings around election cycles, weekends during sanctions news. A cloud phone session in Singapore doesn’t see any of that. If your local connection in Russia goes down completely, the Telegram session in Singapore stays live. Messages keep arriving, bots keep executing, channels keep receiving posts. You’re back in sync the moment your local connection returns, with no session loss and no need to re-authenticate. For anyone whose work genuinely depends on Telegram availability, that continuity is the core value.

If you’ve burned through a few VPNs this year and you’re tired of weekend troubleshooting, this is the problem telegramvault.org is built to solve: managed Telegram hosting on dedicated Singapore hardware, with real carrier IPs and your own number staying yours. Find out more at telegramvault.org.

Get new guides and videos first — join the Telegram channel.