A single VPN hop keeps a stranger on the same coworking Wi-Fi from reading your traffic. A second hop keeps the VPN provider itself from ever seeing both ends of that trip in the same glance — and those are two different jobs. Treating NordVPN's Double VPN as a blanket security upgrade for a digital nomad's public Wi-Fi in Bangkok, rather than a narrower tool for a specific kind of risk, is where most of the confusion about it starts.
Quick disclosure before any of this goes further: some of the links below are affiliate links, and if you sign up through one, I earn a small commission at no extra cost to you. I've paid for every one of these subscriptions myself across three years of moving between Bangkok, Lisbon, and Mexico City, mostly so I never lose access to the shows I actually watch back home.
What NordVPN's Double VPN Actually Protects on Bangkok's Public Wi-Fi
Working out of HUBBA-TO most weeks, I'm sharing a connection with dozens of other laptops, and that's what finally pushed me to turn on NordVPN's Double VPN setting instead of leaving it buried under the specialty servers. A standard VPN already does the heavy lifting: it wraps your connection in one layer of encryption before anything reaches the open internet, which is the part that stops someone else on that same coworking router from reading your files. What the second hop adds is different, and it's less like locking your door twice and more like mailing a letter through two separate post offices, so no single person along the way ever sees both your name and your destination at once. That's what makes a traffic correlation attack — where someone tries to match the timing of data leaving your laptop to data arriving at a website — close to impossible. It's also not the same tool as obfuscation, which hides the fact you're using a VPN at all rather than adding a second layer once the VPN is already obvious; Nord keeps those as separate settings for a reason, one built for protecting sensitive work rather than for streaming a show abroad, which barely needs it at all.
The Trade-Off Nobody Mentions
None of that comes free. Running two hops instead of one adds real distance to every request, and the first time I tested it my partner was mid-Teams call in the next room — his screen froze, his voice dropped into a robotic stutter, and I disconnected before he'd even finished asking what was wrong. That's the version of Double VPN nobody advertises: it's not slow in general, it's that it can be too slow for anything live and two-way at the exact moment it's busy protecting a download. Testing backs that up — NordVPN vs Surfshark comparisons I ran in Lisbon showed the same pattern, where an extra layer occasionally introduced a lag spike a single server never would. These days I know it's holding without checking a speed test at all; my partner just stays on his call without glancing up, no frozen frame, nothing worth mentioning, which is honestly the best review a VPN setting can get. Travelling as a couple changes the math again, too — Surfshark is often the best VPN for travel with multiple devices, since juggling device limits between two people becomes its own headache before encryption layers even enter the picture.
Where Double VPN Actively Works Against You
Video editors and anyone syncing large raw files to the cloud should treat this differently. Uploading through two hops instead of one turned a project that should have taken minutes into something the estimate clock refused to even guess at, and no amount of patience fixed it — the fix was switching Double VPN off, not troubleshooting it further. For that kind of work, a fast single-hop connection matters more than a second layer of encryption, and ExpressVPN has been the more reliable pick on the days raw speed mattered more than anything else; I've written more about why ExpressVPN is the best for BBC iPlayer for the days other services start dropping the stream instead. Switching servers, for what it's worth, solves a completely different complaint. If a show simply won't load at all, that's almost always a server problem rather than an encryption one, and adding a second hop won't fix it any faster than picking a better first one would. None of this changes depending on whether you're on a phone, a laptop, or a hotel smart TV, either — Double VPN is a setting inside the app, not something that behaves differently by device.
The Problems Double VPN Was Never Built to Fix
A few things get blamed on encryption strength that have nothing to do with it. Constant captchas are one — I've sat at HUBBA-TO watching an image grid load one tile at a time over patchy mobile data, proving over and over that I wasn't a robot, and that's a server-load problem, not a security gap. A dedicated IP for streaming stops those problems far more reliably than any amount of extra encryption does, because the actual issue is how many other people share your exit node, not how well your traffic is wrapped. Proxy-detection errors on services like Prime Video are the same story — the app is flagging your IP address as suspicious, and no second hop makes an IP look any less suspicious. Geo-blocking is its own separate fight entirely, and I learned that the expensive way: I once bought a UK SIM card thinking a British phone number would be enough to prove residency to iPlayer, and it wasn't — iPlayer never asked what number was on my phone, only where my connection said it was coming from.
When Is It Actually Worth Turning On?
So when does the second hop earn its keep? My rule by now is simple: only on a network I'd genuinely hesitate to trust — an open hotspot with no password, a shared building router with more strangers on it than I can count, anything where the alternative to encryption is nothing at all. On a locked, password-protected coworking connection, a single hop is already doing the real work, and adding a second one purely for the feeling of extra safety isn't worth what it costs your call quality. My friend Yemi, who's been tracking every VPN outage she's hit on a running spreadsheet since 2020, put it to me over a voice note recently — most of what people blame on "not enough encryption" turns out to be a server picking itself badly, not a security failure. Region-spoofing which country a server pretends to sit in is a completely separate skill from encrypting the trip there twice, and a travel router solves yet another problem again, one login for every device instead of five, that has nothing to do with hop count either. None of this touches DNS-level ad and tracker filtering, which lives in a different setting on a different VPN altogether.
Turning the Rule Into an Actual Wi-Fi Setup
A reader named Zoya messaged me from Doha not long ago, asking flatly whether she needed Double VPN turned on every single time she opened Netflix. I wrote her back in steps rather than recording anything, since that's how she said she prefers it — no video, just a clear list of when to bother and when not to. The short version: keep NordVPN's Double VPN for networks that actually worry you, leave it off for everyday streaming and video calls, and don't mistake the extra layer for a fix to problems it was never built to solve. If latency during regular work is what you're actually optimising around, my Private Internet Access review for digital nomads covers that trade-off in more depth than this one does. Public Wi-Fi in a city as dense as Bangkok will always feel a little exposed — the fix for that feeling isn't stacking every security setting at once, it's knowing which one actually answers the risk sitting in front of you.