Is Telegram blocked in Russia?

Strictly, it's currently mostly not "blocked" but systematically "throttled" (zamedlenie). Voice/video calls were limited first from August 2025, and on 10 February 2026 RKN officially confirmed nationwide throttling of Telegram, citing "violations of Russian law." You'll find text still sends, but voice messages, photos, video, large files and calls are noticeably slow — TSPU targets Telegram's media and built-in MTProxy specifically, to push users toward the state-controlled Max. To restore it, use a system-level client running VLESS+Reality that disguises traffic as ordinary HTTPS so TSPU can't tell it's Telegram.

Why are text messages fine but voice, photos, video and files all slow?

Because this round of throttling is selective: TSPU primarily targets Telegram's media traffic (voice messages, photos, video, large files) and its built-in MTProxy, while plain text is low-volume and prioritized differently, so it often still flows. Hence the typical experience: "I can chat, but can't send voice, can't see images, can't make calls." To restore media and calls the channel must stay unrecognizable to TSPU as Telegram — a system-level, well-camouflaged, dedicated VLESS+Reality node is more reliable.

Can I just use Telegram's built-in MTProxy or a free VPN?

Often not. MTProxy is itself a prime target for TSPU identification and slowdown, so using it can make things worse; RKN has also upgraded TSPU to recognize and block most popular VPN protocols (OpenVPN, WireGuard, plain Shadowsocks, etc.), so signature-heavy channels are unreliable; and free VPNs mostly use public shared IPs, while voice/video calls are extremely sensitive to latency and loss, so they keep dropping. The more reliable option is a system-level VLESS+Reality dedicated node whose handshake looks like real HTTPS.

Does using VLESS guarantee permanent full speed?

No. Telegram is relatively tolerant of foreign IPs, and a stable, high-bandwidth dedicated VLESS+Reality node usually restores voice and media noticeably; but TSPU keeps upgrading, individual protocols or lines may be gradually identified and slowed, exit-IP reputation and line bandwidth matter, and during a "sovereign internet" drill or broad clampdown any cross-border channel can be affected — independent of the protocol. Voice calls in particular are sensitive to latency and loss, so try several nodes and don't switch mid-call.

Telegram Slow in Russia — Voice, Video & Files Lagging? An Honest Explanation (Deliberately Throttled — zamedlenie — Since February 2026, Not Blocked) and How to Get Media Working Again (a VLESS+Reality Client)

Updated 2026-07-06

Diagram: since February 2026 Russia has systematically throttled Telegram (zamedlenie, not a block) — TSPU targets Telegram's media (voice messages / photos / video / large files) and its built-in MTProxy specifically, while text mostly still flows; a foreign IP (system-level VLESS+Reality client) disguises the traffic as ordinary HTTPS so TSPU can't tell it's Telegram, restoring voice and media

First, plainly: what happened to Telegram in Russia (it's "throttling," not a "block")

The most important fact first, to avoid misleading you: Telegram in Russia is currently mostly not "blocked" (заблокирован) but systematically "throttled" (замедление). What many people actually experience: text messages still send, but voice messages take forever, photos and video won't load, large files crawl, and voice/video calls keep dropping — and it's usually not your broadband or your phone. The rough timeline: voice/video calls were limited first, from August 2025; then on 10 February 2026 Russia's RKN (the telecom regulator) officially confirmed nationwide throttling of Telegram, citing "violations of Russian law." This is a subtler slow strangulation: no "blocked" page pops up — media and calls are just made slow enough that you give up, pushing users toward the state-controlled Max.

Why it's "throttling" not a "block" — and what exactly TSPU is squeezing

Understanding that "throttling ≠ a block" matters because the fix differs: a block means "won't connect," throttling means "connects but is deliberately slowed" — and TSPU doesn't squeeze everything, it squeezes selectively. Per reporting by Forbes and others, TSPU (the deep-packet-inspection / shaping boxes RKN installed at every operator) primarily targets Telegram's media traffic and its built-in MTProxy: hence text is fine but voice messages, photos, video and large files are noticeably slow. There's a counter-intuitive but real detail: Telegram's own MTProxy generates a lot of "un-Telegram-like" junk traffic that in turn overloads TSPU itself — and by March 2026 RKN's TSPU was overloaded enough that the throttling became inconsistent, better some days than others. For you this means: Telegram's servers are fine — it's the path from you to Telegram that TSPU recognizes and throttles by media type; the key isn't to "unblock" but to make that path unrecognizable as Telegram traffic.

Why free VPNs, or Telegram's own MTProxy, often aren't enough (they get throttled too)

Many people's first instinct is to turn on Telegram's built-in MTProxy / proxy, or install a free VPN. Against this round of throttling that's often not enough: first, MTProxy is itself a prime target for TSPU identification and slowdown, so using it can make things worse; second, RKN has upgraded TSPU to recognize and block the traffic of most popular VPN protocols — OpenVPN, WireGuard, plain Shadowsocks and similar signature-heavy channels are unreliable; third, free VPNs mostly use public shared IPs, and voice/video calls are extremely sensitive to latency and packet loss, so a congested line means constant dropping; fourth, a browser extension only protects the browser, so the Telegram mobile app and desktop client stay slow. In other words, whether voice and media come back depends on whether your channel can stay unrecognizable to TSPU and be fast and stable — exactly the weak spot of free tools and the built-in proxy.

A key point: to restore voice, video and files you need system-level coverage with a handshake TSPU can't identify

You use Telegram both in the mobile app and on the desktop client and tablet, and what the throttling hits hardest is exactly voice messages, voice/video calls, photos and video, and large files — high-bandwidth media that is also sensitive to latency / packet loss. To restore it overall, the channel is best system-level, dedicated, with a handshake TSPU struggles to identify — covering the whole Telegram client (including calls), not just a browser extension, and not Telegram's own heavily-targeted MTProxy. The good news: Telegram's servers are relatively tolerant of foreign IPs, so a stable, well-camouflaged, high-bandwidth tunnel usually makes voice messages send instantly, calls stop dropping, and photos, video and files return to normal speed. Incidentally, this system-level channel also covers your Instagram, YouTube and browser at once.

A more reliable alternative: a VLESS + Reality client

VLESS is a lean transport protocol, and Reality is its TLS-camouflage layer that makes your traffic look like ordinary HTTPS to a real public website — which is exactly the answer to TSPU's "protocol identification + throttle-by-media-type": if TSPU can't tell this is traffic to Telegram, it can't selectively squeeze its media and calls, and speed comes back. Running VLESS+Reality in a real client (sing-box / v2rayN / Shadowrocket) is system-level: Telegram's app and desktop client, including voice/video calls, go through the tunnel; on a dedicated node with enough bandwidth and low latency, voice messages, calls and files recover noticeably; and compared with the built-in MTProxy and free proxies with public entry points, it's harder to identify and throttle automatically. The cost is that you need a subscription and a client. And to be honest: TSPU keeps upgrading, and no method can guarantee permanent smoothness — exit-IP reputation, SNI and line bandwidth all matter, and during a "sovereign internet" drill or broad clampdown any cross-border channel can be affected, independent of the protocol itself.

How to restore smooth Telegram voice and media in Russia: step by step

In your dashboard, copy your subscription link (prefer VLESS+Reality nodes for the Russian environment).
Install a mature client: Shadowrocket on iOS, sing-box or v2rayN on Android / desktop, and import the subscription URL (don't rely on Telegram's built-in MTProxy).
Pick a foreign node with low latency, low packet loss and enough bandwidth and speed-test it — voice/video calls are the most sensitive to latency and loss; if it lags, switch to a more stable node, and don't hop nodes constantly (switching mid-call drops it).
Use Rule mode: send Russian local banking / government (Gosuslugi) direct, and route Telegram (app and desktop) through the tunnel.
In Telegram, send a voice message, make a voice/video call, and download a large file to verify it's smooth again; you can also cover Instagram / YouTube / your browser at the same time.

Honest expectations

Telegram in Russia is currently mostly throttled, not fully blocked; a stable foreign tunnel that TSPU can't identify usually restores voice and media noticeably, but no method can guarantee permanent, always-full speed.
Don't rely on Telegram's built-in MTProxy — it's exactly what TSPU targets and throttles; ordinary VPN protocols (OpenVPN / WireGuard, etc.) are also increasingly identified by TSPU, so a dedicated, well-camouflaged VLESS+Reality node is the most resilient.
Voice/video calls are the most sensitive to latency and packet loss — don't pick a node by latency number alone; try several, and don't switch nodes mid-call.
During a "sovereign internet" drill or broad clampdown, any cross-border channel (including VLESS) can be affected — independent of the protocol.
If what you hit is can't-connect-at-all / replaced by Max rather than slowness, see "Telegram not working in Russia"; for how the protocol works see "what is VLESS Reality"; for overall options see "what works more reliably in Russia".

Please comply with local law and third-party terms of service; this article is a technical tutorial only, security and compliance are the user's own responsibility, and no guarantee can be made about the long-term availability of third-party services (including Telegram).

FAQ

Is Telegram blocked in Russia?: Strictly, it's currently mostly not "blocked" but systematically "throttled" (zamedlenie). Voice/video calls were limited first from August 2025, and on 10 February 2026 RKN officially confirmed nationwide throttling of Telegram, citing "violations of Russian law." You'll find text still sends, but voice messages, photos, video, large files and calls are noticeably slow — TSPU targets Telegram's media and built-in MTProxy specifically, to push users toward the state-controlled Max. To restore it, use a system-level client running VLESS+Reality that disguises traffic as ordinary HTTPS so TSPU can't tell it's Telegram.
Why are text messages fine but voice, photos, video and files all slow?: Because this round of throttling is selective: TSPU primarily targets Telegram's media traffic (voice messages, photos, video, large files) and its built-in MTProxy, while plain text is low-volume and prioritized differently, so it often still flows. Hence the typical experience: "I can chat, but can't send voice, can't see images, can't make calls." To restore media and calls the channel must stay unrecognizable to TSPU as Telegram — a system-level, well-camouflaged, dedicated VLESS+Reality node is more reliable.
Can I just use Telegram's built-in MTProxy or a free VPN?: Often not. MTProxy is itself a prime target for TSPU identification and slowdown, so using it can make things worse; RKN has also upgraded TSPU to recognize and block most popular VPN protocols (OpenVPN, WireGuard, plain Shadowsocks, etc.), so signature-heavy channels are unreliable; and free VPNs mostly use public shared IPs, while voice/video calls are extremely sensitive to latency and loss, so they keep dropping. The more reliable option is a system-level VLESS+Reality dedicated node whose handshake looks like real HTTPS.
Does using VLESS guarantee permanent full speed?: No. Telegram is relatively tolerant of foreign IPs, and a stable, high-bandwidth dedicated VLESS+Reality node usually restores voice and media noticeably; but TSPU keeps upgrading, individual protocols or lines may be gradually identified and slowed, exit-IP reputation and line bandwidth matter, and during a "sovereign internet" drill or broad clampdown any cross-border channel can be affected — independent of the protocol. Voice calls in particular are sensitive to latency and loss, so try several nodes and don't switch mid-call.

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.