v2rcIn Russia a tunnel can show as connected while pages never load. This article separates what is documented from what is only claimed, gives a checklist for that symptom, and summarises the legal background. It describes how the technology behaves. It does not recommend servers or providers.
What is documented and what is only reported
| Claim | Basis | How firm |
|---|---|---|
| Blocking runs on inspection equipment (TSPU) at ISPs and mobile operators, controlled centrally by the regulator Roskomnadzor | Journalism and measurement research | Well established |
| From June 2025, connections to many foreign servers freeze after about 16 KB of data | Cloudflare, Zona Media, heise, community analysis | Well documented for 2025; scope varies by operator |
| By mid-January 2026 Roskomnadzor had restricted access to 439 VPN services | News report | Reported |
| Plain VLESS (without REALITY) is increasingly filtered | Russian news and vendor reports | Reported, not independently measured |
| VLESS with REALITY still works on many networks, but not all | Conflicting vendor and community claims | No reliable public success rate |
| Mobile networks have periods when only a list of approved services is reachable | News and community reports | Reported |
You will find many posts that give exact success rates for one protocol or another. Almost all come from companies that sell VPN services, and they contradict each other. We found no independent measurement, so we give no numbers. In October 2026 Meduza reported that the government plans to spend nearly 60 billion rubles over three years on traffic filtering. Expect the picture to keep changing.
The 16 KB freeze
Since June 2025 many users have reported connections to servers outside Russia that start normally and then stall after about 15 to 20 KB of data coming back from the server. Cloudflare reported that its own data suggests users can load only the first 16 KB of a web asset. Community analysis on the net4people forum describes the censor freezing a connection after about 25 packets in either direction, with address space of foreign data centres more likely to be affected and some exemptions by server name and by address range.
The signature is easy to recognise: the tunnel connects, something tiny works (a DNS lookup, a very small page), and anything larger hangs.
No setting in your client fixes this. What changes the outcome is the server: a different host, a different address range or a different network path.
Checklist: it connects, but nothing loads
- Change the network, not the app. Try the same config on mobile data and on home Wi-Fi. Operators differ. If it works on one and not the other, the cause is the operator.
- Try a config from a different host. If every config from one provider fails and one from another works, the first provider's address range is the likely cause.
- Test with something small and something large. A page that starts and then stalls points to the freeze above. Nothing at all points to a blocked address or port, or to a wrong parameter.
- Check the parameters of a REALITY config.
sni,pbk,sid,fpandflowmust match the server exactly, and one wrong character fails silently. Paste the link into the link decoder; it decodes in the page and flags REALITY without a public key or server name, among other mistakes. See also how to read a config link. - Check the clock. VMess fails when the device clock is off by a couple of minutes. Turn on automatic date and time.
- Check DNS. If the tunnel is up and nothing resolves, try a different DNS server in the app's settings.
- Use Smart Connect. It confirms that traffic really passes before it switches, so a config that connects but carries nothing is skipped.
- Keep spares from unrelated hosts and refresh your subscription. Blocked addresses get replaced over time.
If you run your own server
- Use port 443 with a setup that looks like ordinary HTTPS. Unusual ports stand out.
- For REALITY, choose a server name that is a real site supporting TLS 1.3 and HTTP/2; the REALITY documentation requires it.
- Hosting reputation matters. Address ranges of well-known foreign data centres are the most likely to be flagged. A less obvious host may behave differently, with no guarantee.
- Do not publish the config. The more people share one address, the sooner it is blocked.
Legal background
This is not legal advice. Reports say that Russia has restricted the advertising and promotion of VPN services, with fines, and has introduced fines for searching for extremist materials. Amounts and dates differ between reports and we could not confirm them against the official texts. Officials have reportedly said that a complete ban on VPNs is not planned. v2rc is a client for servers you bring yourself; the app ships no servers. If you are unsure what applies to you, ask a lawyer who knows Russian law.
Sources
- Cloudflare: Russian Internet users are unable to access the open Internet
- Zona Media: The 16-kilobyte curtain, confirmed
- heise: The 16-Kbyte trick: Russian providers block foreign content again
- net4people: community discussion of the 16 KB freeze
- Zona Media: Russia's internet censorship in 2026
- Meduza: Russia plans to spend nearly 60 billion rubles on traffic filtering
- www1.ru: Roskomnadzor restricted access to 439 VPN services
- Meduza: Russian lawmakers propose fines for searching for extremist materials and advertising VPNs