a kill switch blocks all traffic if the vpn connection drops. sounds simple. implementation is not.
system-level kill switch vs app-level kill switch : completely different failure modes. app-level fails if the app crashes. system-level doesn't. Most providers advertise kill switch. few specify which type. even fewer explain what happens during a vpn reconnect.
the World Cup starts June 11. depending on where you are, half the matches will be behind a paywall or geo-blocked entirely.
here's the reality by region :
the simplest workaround : a VPN set to a UK server gives you BBC/ITV free for every match. no account needed, no paywall.
what to look for in a VPN for this specific use case :
which providers actually work for iPlayer and hold up under peak traffic is in the sidebar. tested, not guessed.
the World Cup starts June 11. depending on where you are, half the matches will be behind a paywall or geo-blocked entirely.
here's the reality by region :
the simplest workaround : a VPN set to a UK server gives you BBC/ITV free for every match. no account needed, no paywall.
what to look for in a VPN for this specific use case :
which providers actually work for iPlayer and hold up under peak traffic is in the sidebar. tested, not guessed.
wireguard : 4000 lines of code, formally verified, faster handshake, better battery on mobile.
openvpn : 600,000 lines of code, mature, more configurable, wider support.
the real question isn't which protocol — it's whether your provider implements it correctly. most don't bother to tell you how.
vpn hides your ip from your isp and the sites you visit. genuinely useful. vpn does not hide you from google if you're logged in. does not stop browser fingerprinting. does not prevent behavioral tracking by ad networks. most people think vpn = anonymous. it doesn't. it's one layer of a much bigger picture.
what's actually worth the money is broken down in the sidebar. tbh the honest answer is more nuanced than most vpn marketing admits.
router-level vpn : covers every device automatically. but your router cpu handles encryption — which is slower than a modern cpu. no kill switch. no split tunneling.
app-level vpn : faster, flexible, kill switch works, split tunneling available. requires installation on each device. neither is objectively better. depends on your setup and threat model.
not fearmongering. just facts. hola, turbo vpn, thunder vpn — look up who owns them now.
chinese companies operate under laws that require cooperation with state intelligence. no logs policy is legally meaningless under that framework. the free vpn you downloaded because it had good reviews on the app store might be logging everything.
us, uk, australia, canada, new zealand — the five eyes — plus 12 others have data retention laws that allow isp-level logging and resale. This is the actual threat model for 95% of vpn users. not government surveillance. not hackers. your isp selling your browsing history to advertisers. A vpn solves this specific problem completely. whether the vpn itself is trustworthy is the separate question worth asking.
mullvad dropped port forwarding in 2023. the reason : it was being used to correlate user identity via torrent swarms.
technically correct decision. operationally annoying for anyone using it for legitimate self-hosting or torrenting.
it's a good example of a provider making a privacy decision that hurts usability. most providers do the opposite.
tradeoffs between providers on this in the sidebar.
openvpn : blocked. l2tp : blocked. ikev2 : blocked in most regions.
what still works as of may 2026 : wireguard with obfuscation, shadowsocks, v2ray, and stealth/camouflage protocols from specific providers. The key word is obfuscation. a vpn without it is just a vpn-shaped hole in your privacy in russia right now.
Which providers have working obfuscation in russia is covered in the sidebar.
chat control 2.0 proposes client-side scanning. meaning the scan happens before encryption, not after. A vpn does nothing against client-side scanning. zero. the traffic is already compromised before it hits the tunnel. this is not a vpn problem. this is an endpoint problem. understanding the difference matters if you're actually trying to protect something.
in 2022 india's cert-in directive required vpns to store user data for 5 years. most vpns quietly complied. a few actually pulled their servers.
the ones that left : proton, mullvad, pia, expressvpn, nordvpn. the ones that stayed and added logging : most of the smaller providers nobody talks about.
if you have servers in india you're storing data. that's not a threat model, that's a legal requirement.
the amendment passed last week. practically speaking, age verification for vpn services means either id checks or device-level restrictions.
neither works the way legislators think. id checks are trivially bypassed. device restrictions depend on os-level enforcement that doesn't exist yet.
what it does do : push vpn providers to implement data collection they currently don't have. depends on your threat model whether that's a problem.
An in-depth review of 2026's VPN regulatory landscape finds that while no democratic country has moved from 'legal' to 'banned,' the UK's House of Lords passed an amendment restricting VPN use by under-16s, Russia's crackdown continues to drive millions underground, and copyright lobbying groups are pushing to hold VPN providers liable for users' piracy.
An in-depth review of 2026's VPN regulatory landscape finds that while no democratic country has moved from 'legal' to 'banned,' the UK's House of Lords passed an amendment restricting VPN use by under-16s, Russia's crackdown continues to drive millions underground, and copyright lobbying groups are pushing to hold VPN providers liable for users' piracy.