Is Telegram blocked in Russia, or is it my phone?

Mainly not your phone. From 10 February 2026 Russia's regulator RKN began throttling Telegram at the network layer (images, videos and voice messages were the first to stop loading), then escalated to actual blocking, to push users onto the state-backed Max messenger (confirmed by CPJ, The Moscow Times, Meduza and others). This is the same RKN network-layer mechanism used to block Signal/WhatsApp/Discord, not Telegram withdrawing from Russia. The test: on the same phone, switch to a clean, well-camouflaged foreign line (a system-level VLESS+Reality client) — if images/videos/calls come back instantly, the problem is the throttling in between, not your device.

Why do text messages arrive but images and videos won't open?

Because RKN is 'throttling', not cleanly cutting off, and prioritises choking media and CDN connections. So the app looks alive — text trickles in, but images, videos, voice messages and files hang forever. This 'half-working' state is the most confusing and makes people blame their own connection and keep restarting the phone. To restore media loading and calls you need a stable foreign tunnel that routes the whole Telegram app out.

Can Telegram's built-in MTProto proxy or a free proxy solve it?

In 2026 it's often not reliable. RKN is actively throttling and mass-blocking public MTProto proxies and bare protocols (bare SOCKS5, bare VLESS, WireGuard are increasingly fingerprinted by DPI and blocked), and many public proxies are run by strangers who inject ads or log metadata. What survives the current environment is a protocol that camouflages traffic as ordinary HTTPS to a real website (VLESS+Reality), harder for DPI to fingerprint; pair it with a stable dedicated node and turn on system-level TUN covering the whole Telegram app and calls.

Will switching to a foreign line make me re-register my Telegram account?

No. Your account is tied to your phone number, and your account, channels, contacts, message history and end-to-end-encrypted secret chats are all intact; switching lines only restores your device's connectivity to Telegram's servers, no re-registration needed. The whole point of restoring Telegram is precisely so you're not forced onto the state-backed Max, which has no end-to-end encryption and is reported to share data with the FSB.

Telegram Not Loading Images / Not Working in Russia — Honest Explanation (in 2026 RKN Escalated from Throttling to Blocking to Push Users onto the State Max App, It's Not Your Phone) + a More Reliable Way to Access It (VLESS+Reality Client)

Updated 2026-07-08

Diagram: the main reason Telegram won't load images / won't work in Russia in 2026 is that RKN escalated from throttling to blocking Telegram at the network layer (from 10 February 2026 media was hit first — images/videos/voice messages hang and won't load), to push users onto the state-backed Max messenger which has no end-to-end encryption and shares data with the FSB — this is state censorship, not your phone's problem and not Telegram withdrawing; because it's interference on the path between your device and Telegram's servers, a foreign tunnel camouflaged as ordinary HTTPS usually restores connectivity; Telegram's built-in MTProto proxy/SOCKS5 is itself being targeted in 2026, and only VLESS+Reality, camouflaged as real-website traffic, is harder for DPI to fingerprint; a system-level (TUN) client routes the whole device — including the Telegram app and voice/video calls — out through one clean, stable foreign line

First, what actually happens to Telegram in Russia in 2026 (RKN escalating from throttling to blocking, not your phone's problem)

Many people's situation: Telegram text messages barely send and receive, but images, videos and voice messages hang forever and won't open, and voice/video calls won't connect — so you suspect your phone, WiFi or carrier. The honest direction: this is mainly not your device but Russia's regulator RKN interfering with Telegram at the network layer. From 10 February 2026 users reported mass Telegram disruptions, RKN began throttling Telegram and images, videos and voice messages were the first to stop loading; the throttling then escalated to actual blocking. Independent outlets (CPJ, The Moscow Times, Meduza) confirm this is a campaign to push users onto the state-backed Max messenger, and Telegram founder Durov publicly said the authorities are restricting the app to force people onto Max. So what blocks you is state network-layer censorship (the same mechanism Russia uses to block Signal, WhatsApp and Discord), not Telegram withdrawing from Russia (that's the 'company left' case like Spotify — the opposite direction).

Why 'half-working' is the most confusing: throttling kills media first, text still trickles in

Telegram's specific trap is that it's 'throttled', not cleanly cut off: RKN prioritises choking the media and CDN connections, so you see an app that looks alive — text messages trickle in, but images, videos, voice messages and files hang forever, and avatars and previews won't load. Precisely because 'text still trickles in', many people blame their own connection and keep restarting phone and router, when in fact the path is being deliberately throttled. The test is simple: if the same phone loads images/videos instantly after switching to a clean foreign line, then the problem isn't your device — it's the throttling in between.

Telegram's hardest-hit area: voice/video calls

Hit earlier and harder than media messages are Telegram's voice/video calls. Since 2025, authorities began restricting voice and video calls on Telegram, WhatsApp, FaceTime and Snapchat (again to push users onto Max). Calls run over real-time VoIP, extremely sensitive to latency, jitter and packet loss, so you'll often find chat text arrives but a call won't connect or drops within seconds. To make calls stable you need a low-latency, stable foreign line, not a random public proxy.

The key point (and where this differs most from 'just find a free Telegram proxy'): built-in MTProto proxy/SOCKS5 is itself being targeted in 2026

Many people's first instinct is Telegram's built-in MTProto proxy or SOCKS5 — that used to work, but in 2026 it's no longer reliable: RKN is actively throttling and mass-blocking public MTProto proxies and bare protocols (bare SOCKS5, bare VLESS, WireGuard etc. are increasingly fingerprinted by DPI and blocked), and many public proxies are run by strangers who inject ads or log metadata (details in why free Telegram proxies in Russia are unreliable/risky). The key difference: what survives RKN in 2026 is a protocol that camouflages traffic as 'ordinary HTTPS to a real, existing public website' — that is VLESS+Reality below, which is harder for DPI to fingerprint and target.

Honest reminder: don't let yourself be pushed onto Max

The purpose of this throttling/blocking is to force you onto the state-backed Max messenger. Honestly, Max has no end-to-end encryption, is reported to share data with the FSB, and has been mandatory pre-installed on phones sold in Russia since September 2025; multiple human-rights and press-freedom groups describe it as a surveillance-friendly app. Restoring Telegram is precisely so you're not forced onto Max — keeping your existing account, channels, contacts and end-to-end-encrypted secret chats.

The key point: Telegram is a standalone app + calls, a browser extension can't cover the whole device

Many people install a free browser VPN extension, but that's often not enough for Telegram: a browser extension only proxies browser tabs, whereas what you use daily is the standalone Telegram app on phone/desktop, plus voice/video calls, which use their own network connections and don't go through the browser — the extension can't touch them. To make Telegram stable you need a system-level (whole-device) channel that routes the entire Telegram app and calls out through the same clean foreign line — the TUN mode below (see what is VLESS Reality).

The more reliable alternative: a system-level VLESS + Reality client

VLESS is a lightweight transport protocol and Reality is its TLS-camouflage layer, making your traffic look like ordinary HTTPS to a real, existing public website, so it's harder for RKN's DPI to fingerprint and target — which is exactly why bare protocols keep getting blocked in 2026 while camouflaged ones survive. Running a real client (sing-box / v2rayN / Nekoray) in system-level TUN mode means the whole Telegram app, desktop client, and voice/video calls all exit through the same clean foreign line, images/videos/voice messages load again and calls are steadier; a stable dedicated node is harder to flag as suspicious and drops less than a free proxy with a public, heavily-abused entry point. The cost is a subscription and a client. Several honest boundaries remain: during a near-total shutdown or a 'whitelist'-style sovereign-internet drill (including a Max whitelist), any foreign channel (including VLESS) may fail to connect; RKN has banned 439+ VPN services and actively hunts VPN protocols, so a self-hosted, well-camouflaged node usually outlasts a public free VPN app; and an individually-blocked channel/account may not open even after switching lines — no method can guarantee it always works.

How to use Telegram reliably in Russia: concrete steps

In your user panel, copy your subscription link (for Russian conditions, prioritise DPI-resistant VLESS+Reality nodes, not bare protocols).
Install a mature client: Streisand / Shadowrocket on iOS, sing-box or v2rayN / Nekoray on Android / desktop, and import the subscription URL (don't add nodes one by one by hand).
Pick a stable, low-latency foreign node and run a speed test (calls are latency-sensitive, so prefer a nearby, stable dedicated node).
Turn on system-level TUN / 'virtual network card' mode so the whole Telegram app and voice/video calls go through the tunnel (don't rely on a browser extension or the built-in MTProto proxy alone).
Verify: reopen Telegram, confirm images, videos and voice messages load normally, and place a voice/video call to confirm it connects and doesn't drop frequently.
Honest expectation: your account, channels, contacts and end-to-end-encrypted secret chats are all intact, no re-registration needed; all you're doing is restoring your device's connectivity to Telegram's servers.

Honest expectations

Telegram won't load images / won't work in Russia in 2026 mainly because RKN escalated from throttling to blocking at the network layer (from 2026-02-10 media was hit first, then blocking), to push users onto the state-backed, no-E2E, FSB-data-sharing Max — this is state censorship, not your phone's problem and not Telegram withdrawing; because it's interference on the path, a foreign tunnel camouflaged as ordinary HTTPS usually restores connectivity.
'Half-working' is the most confusing: throttling kills images/videos/voice messages and calls first while text still trickles in, making people blame their own connection; the test is that the same phone loads media instantly after switching to a clean foreign line — so the problem is the throttling in between.
Built-in MTProto proxy/SOCKS5 is itself targeted in 2026: RKN throttles/mass-blocks public proxies and bare protocols (bare SOCKS5/VLESS/WireGuard are easily fingerprinted), and only VLESS+Reality camouflaged as real-website traffic is harder for DPI to fingerprint (public-proxy risks in why free Telegram proxies are unreliable).
Telegram is a standalone app + voice/video calls; a browser extension only proxies tabs and can't touch it — you need system-level TUN covering the whole device; a stable dedicated node outlasts a public free proxy and drops less.
During a near-total shutdown or a 'whitelist'-style sovereign-internet drill, any foreign channel (including VLESS) may fail, regardless of protocol; for the overall choice see which VPN works in Russia 2026, and for client setup see sing-box setup in Russian.

Please comply with local laws and third-party terms of service; this article is a technical explainer only, security and compliance are the user's responsibility, and no guarantee can be made about the long-term availability of third-party services or changes in regulatory policy.

FAQ

Is Telegram blocked in Russia, or is it my phone?: Mainly not your phone. From 10 February 2026 Russia's regulator RKN began throttling Telegram at the network layer (images, videos and voice messages were the first to stop loading), then escalated to actual blocking, to push users onto the state-backed Max messenger (confirmed by CPJ, The Moscow Times, Meduza and others). This is the same RKN network-layer mechanism used to block Signal/WhatsApp/Discord, not Telegram withdrawing from Russia. The test: on the same phone, switch to a clean, well-camouflaged foreign line (a system-level VLESS+Reality client) — if images/videos/calls come back instantly, the problem is the throttling in between, not your device.
Why do text messages arrive but images and videos won't open?: Because RKN is 'throttling', not cleanly cutting off, and prioritises choking media and CDN connections. So the app looks alive — text trickles in, but images, videos, voice messages and files hang forever. This 'half-working' state is the most confusing and makes people blame their own connection and keep restarting the phone. To restore media loading and calls you need a stable foreign tunnel that routes the whole Telegram app out.
Can Telegram's built-in MTProto proxy or a free proxy solve it?: In 2026 it's often not reliable. RKN is actively throttling and mass-blocking public MTProto proxies and bare protocols (bare SOCKS5, bare VLESS, WireGuard are increasingly fingerprinted by DPI and blocked), and many public proxies are run by strangers who inject ads or log metadata. What survives the current environment is a protocol that camouflages traffic as ordinary HTTPS to a real website (VLESS+Reality), harder for DPI to fingerprint; pair it with a stable dedicated node and turn on system-level TUN covering the whole Telegram app and calls.
Will switching to a foreign line make me re-register my Telegram account?: No. Your account is tied to your phone number, and your account, channels, contacts, message history and end-to-end-encrypted secret chats are all intact; switching lines only restores your device's connectivity to Telegram's servers, no re-registration needed. The whole point of restoring Telegram is precisely so you're not forced onto the state-backed Max, which has no end-to-end encryption and is reported to share data with the FSB.

The service you're trying to reach is blocked. Restore access — free.

Back online in about 2 minutes — no credit card. A working VLESS + Reality route on iOS, Android, Windows and macOS.

Free 1 GB/day
·
No credit card
·
VLESS + Reality in 60 seconds

You and your friend each get +30 bonus days plus bonus traffic once they start using Univista.

Restore access — free

Telegram WhatsApp

Already subscribed? Help for import & troubleshooting.

Ready for reliable international access?

View plans

This article is for technical education only. Comply with local laws when using network tools. Univista is not liable for how you use the service.