On the morning of August 4, 2026, complaints about VPN unavailability began flooding in from across Russia. Users report sessions dropping one to two minutes after connecting, endless loading spinners in clients, and sharp speed collapse — even when the tunnel appears "active." iPhone owners are hit especially hard, but failures show up on Android, Windows, and macOS too, across different ISPs and mobile carriers.
This is not the first wave-like outage in 2026 — similar cycles happened in spring and last autumn. But the current wave coincides with a shift in blocking tactics: where filters used to target specific server addresses, they now increasingly cut the method of data transmission itself — by protocol fingerprints and cloud provider IP ranges.
What users are reporting
Based on social media, forums, and monitoring services, typical symptoms look like this:
- VPN won't connect — the client spins on "Connecting…" and never establishes a working session.
- Session drops after 1–2 minutes — the tunnel looks active, but traffic doesn't pass.
- Critical speed collapse — pages take minutes to load; video and calls fail.
- Constant server switching — a node that worked yesterday stops within hours.
- Different behavior by network — fails on home Wi‑Fi but sometimes works on mobile data (or the reverse).
- iPhone-specific issues — after iOS updates, many VPN profiles no longer bring up a tunnel.
As of publication, Roskomnadzor and the Ministry of Digital Development had not issued official comments on a specific "system outage" on August 4. The context of recent days, however, is a series of reports about tightening VPN controls and a growing number of restricted services.
What changed in blocking tactics
From IP addresses to protocols
The old main method was blocking known VPN server IPs. VPN providers responded by rotating nodes, and the cycle repeated. Now, TSPU equipment (technical means of countering threats) at ISPs increasingly recognizes encrypted protocol fingerprints — OpenVPN, WireGuard, IKEv2, L2TP/IPSec — and cuts traffic regardless of the specific app.
This means switching servers within the same protocol may not help if the filter targets the connection type, not the address.
Blocking entire cloud provider subnets
Filters also target IP ranges belonging to major cloud platforms — AWS, Cloudflare, and similar hosts where VPN infrastructure often lives. Side effect: other services using the same networks may suffer too.
From drops to "viscosity"
Industry sources describe the next stage as not instant disconnects but throttling to unusable levels: pages load, there are no error messages in the UI, but the connection is practically useless. Users see an "active" tunnel that doesn't actually work.
For how network-level blocking is structured, see Internet Blocking Measures and Methods in Russia in 2026.
Numbers and context
- By end of February 2026, 469 VPN services appeared on restriction lists — up from 197 in 2024 and 439 in 2025.
- On August 3, reports surfaced that up to 95% of VPN services were blocked, with another 90% throttled to unusable speeds.
- In June 2026, Amnezia lost over 90% of its servers in Russia within two weeks; new addresses stopped working within hours.
- The Ministry of Digital Development is preparing tighter controls on "whitelist" IP addresses: if banned VPN infrastructure is found on an address, providers get 24 hours to respond.
Quiet periods in this model are not retreats — they are preparation for the next stage. After several months of relatively stable operation, users again face the need to hunt for working configurations.
Why iPhones are especially affected
On August 4, iPhone owners filed the most complaints. Likely reasons:
- iOS 18 and 19 updates tightened requirements for network extensions — older VPN profiles downloaded from unverified sites no longer bring up a tunnel.
- App Store — since early 2026, Apple has restricted Russian users' access to certain apps and payments, making client updates harder.
- Default protocols — many iOS clients use IKEv2 and WireGuard, which TSPU filters now target more aggressively.
If VPN stopped working after an iOS update, first update the client from an official source or try a different protocol. Step-by-step setup is in our Happ installation guide for all platforms.
What to do if your VPN isn't working
1. Confirm the problem is VPN-related
- Turn VPN off — does regular internet work?
- Try another network (mobile data instead of Wi‑Fi, or vice versa).
- Compare behavior with and without VPN on the same site.
Full diagnostics: VPN not working: step-by-step troubleshooting.
2. Change protocol and server
If OpenVPN or WireGuard are filtered, try VLESS with Reality, Hysteria2, or other obfuscated transports. Changing only the country with the same protocol may not help.
Protocol overview: VLESS guide and Happ encryption protocols.
3. Update the client
Outdated apps often fail to bring up a tunnel after TUN-mode and OS network stack changes. Download only from official sources.
4. Don't trust "magic" free VPNs
During mass outages, phishing apps and fake configs multiply. Free public VPNs fail first and carry data risks — see free VPN security risks.
5. Use a service with automatic config updates
When entire subnets get blocked, manual server switching is exhausting. A subscription with auto-update via subscription link offloads the work: the provider rotates nodes, and the client pulls the current list.
Our service was not affected by the blocking — connections remain stable. You can verify this with trial access for just 10 rubles, before buying a full plan.
What to expect next
Restrictions will likely keep tightening — especially amid discussions of "whitelist" IP controls and identity verification requirements for hosting customers. Expect:
- more throttling instead of obvious disconnects;
- stricter filters on popular protocols;
- more friction in app stores and payment systems;
- a need to update configurations and change transports more often.
Fully "turning off VPN forever" is technically hard without massive collateral damage — see can VPN be fully blocked in Russia. But for everyday users, the gap between "theoretically possible" and "doesn't work today" is significant.
Summary
On August 4, 2026, Russia saw a new wave of mass complaints about VPN unavailability. The key difference from previous outages is blocking by protocol and subnet, not just individual IP addresses. Users should update clients, try modern obfuscated protocols, and use services with automatic server rotation.
Practical bypass methods: how to bypass VPN blocking. If Happ won't connect: 10 reasons Happ is not working.