Since June 5, 2026, Telegram is almost unusable in Russia. Official MTProto proxies (including built‑in Fake TLS) are fully blocked by DPI. Direct connections also fail. Issue affects all clients (Desktop, Android, iOS) on all major ISPs (Rostelecom, MTS, Beeline).
Symptoms: permanent "Connecting...", no media, no messages, calls drop. Changing IP/port/proxy provider does nothing.
Root cause: Russian DPI now analyzes TLS handshake fingerprints. Official client uses a static JA4 fingerprint in ClientHello. DPI recognises it and injects RST packets. Even Fake TLS is detected because client's TLS stack differs from real browsers.
Proof it's client‑side: community forks with dynamic JA4 rotation (e.g., telemt/tdlib-obf) work immediately with the same proxy and network. Local DPI tools (GoodbyeDPI, zapret) also help.
What doesn't work: any MTProto proxy, Telegram Premium proxy, SOCKS5, many VPNs.
Working workarounds: forked client with JA4 randomization, or local fragmentation tools (GoodbyeDPI/zapret/ByeDPI).
Why Telegram must fix: same network+proxy work with patched client. Official static fingerprint is a design weakness.
Request to developers:
Implement dynamic JA4 fingerprint randomization (random browser‑like ClientHello per connection). Community already did it.
Add packet fragmentation for initial handshake packets (inspired by GoodbyeDPI/zapret).
Full detailed description, including steps to reproduce, logs, and GitHub issue #30733, is attached as a screenshots.
Please prioritise this fix. Millions of Russian users are affected since June 5, 2026.
Thank you.
Steps to reproduce
Steps to reproduce (for developers)
Be in Russia with an ISP that implements TSPU DPI filtering.
Install the latest official Telegram Desktop client.
Obtain any working MTProto proxy (with or without Fake TLS).
Configure the proxy in Settings → Advanced → Connection Type.
Observe that the client remains in “Connecting…” indefinitely.
Capture traffic with Wireshark – you will see a TLS ClientHello with a static fingerprint, followed by a forged RST packet from the ISP.
Switch to a community forked client (e.g., the one linked in issue #30733) without changing the proxy or network – the connection works immediately.
Device info
Telegram Desktop 6.8.2 x64, Veriton Z4630G, Windows 10 x64