The Slow Internet Problem: How Lag Can Reveal You Are Overseas

It is 8:47 on a Tuesday morning, and you are sitting in a co-working space in Chiang Mai with a flat white going cold next to your laptop. Standup started two minutes ago. You unmute, say good morning, and watch your manager’s face freeze mid-nod.

“You’re breaking up,” someone says. “Are you in a tunnel?”

You are not in a tunnel. You are 8,600 miles from the office, and your connection is telling on you before you have said a single useful thing. You laugh it off, blame the wifi, and spend the rest of the call talking in short bursts between the freezes. Two days later, an email lands from IT: “We’ve noticed unusual latency on your account. Everything okay with your setup?” Your stomach drops. They did not ask where you are. They did not have to.

Most nomads worry about their IP address giving them away, and they should. But there is a second signal hiding underneath it, one that no VPN app on your laptop can fake: how long your internet takes to answer. This post explains latency in plain English, what normal looks like from home, and why slow internet is quietly one of the most honest location signals you have.

Latency, in plain English

Every time your laptop loads a page, joins a video call, or opens a shared file, it sends a tiny signal to a server and waits for the answer. The round trip time is called latency. Gamers and network engineers call it ping. It is measured in milliseconds, which are thousandths of a second.

Think of it like shouting across a canyon and timing the echo. A short echo means the wall is close. A long echo means it is far away. Your computer shouts, the server shouts back, and the stopwatch never lies about the distance in between.

Here is the part that matters for you: light and electricity move fast, but they are not instant, and they have to travel through real cables under real oceans. A signal from Chicago to a server in Chicago makes a short trip. A signal from Bali to that same server crosses the Pacific, and no software on your laptop can make that trip shorter than physics allows. Your IP address is a label you can change. Your latency is a measurement of the real world.

What normal looks like from your couch

When you work from home, your numbers are boring, and boring is exactly what you want. A typical home connection on cable or fiber shows about 15 to 40 milliseconds to servers in the same country. Run a speed test and you will see the ping number right at the top. That is your baseline, the number your employer’s systems have quietly gotten used to seeing from you.

Video calls are forgiving up to a point. Zoom, Teams, and Meet all work fine under about 150 milliseconds. Below 50, everything feels instant. Between 50 and 100, you might notice the tiniest pause before someone reacts to what you said. Past 150, people start talking over each other, because each person hears the other a beat late. Past 250, you get the full robot voice experience, frozen faces, and the dreaded “can you repeat that.”

Your company’s systems know your normal. VPN dashboards, call quality reports, and security tools record latency on every session automatically. Nobody stares at these numbers for fun, but they form a background pattern: you, 20 to 40 milliseconds, day after day. Patterns are comfortable. Breaks in the pattern get noticed.

What it looks like from the other side of the world

Now picture the same workday from a beach town in Thailand or a apartment in Lisbon. Your laptop is the same. Your accounts are the same. But every signal now has to cross an ocean, and the numbers change dramatically.

From Western Europe to the US East Coast, expect roughly 80 to 120 milliseconds. From Southeast Asia to the US, 180 to 300 is normal. From Australia to Europe, you are looking at 280 milliseconds and up. These are not worst case numbers on bad wifi. These are good days, on decent connections, with nothing else going wrong. The distance sets a floor that no cafe upgrade can get you under.

It gets worse in practice, because latency is rarely steady from abroad. The number jumps around, a problem engineers call jitter. One second you are at 190, the next at 340, then back to 210. That wobble is what turns a video call into a slideshow. Your voice arrives in clumps. Your face freezes mid-expression. Everyone on the call experiences you as “the person with the bad connection,” which is a short step from “the person who is clearly very far away.”

Think about it from your manager’s side. For two years your calls were crisp. Now every call with you has that half-second delay where you both start talking at once, then both stop, then both apologize. You can blame the wifi once. You can blame it twice. By the third week, people start doing quiet math.

Your IT team can see these numbers

Here is the uncomfortable part: latency is not a secret you keep. It is a measurement your employer’s tools take automatically, on every call and every connection, and store in dashboards your IT team already uses.

Microsoft Teams has a call quality dashboard that shows latency, jitter, and packet loss per user, per call. Zoom’s admin dashboard shows similar numbers. Your company’s VPN concentrator, the box your work laptop connects through, logs session statistics including round trip time. None of this requires anyone to suspect you. It is routine operational data, the same way a shop keeps security camera footage whether or not anyone steals anything.

Most of the time, nobody looks. IT teams are busy, and one person with slightly slow calls is not a priority. But latency becomes interesting the moment something else raises a question: a login alert from a new country, a timezone that does not match, a colleague mentioning your beach photos. Then someone pulls up your recent sessions, sees ping times that tripled overnight, and the picture fills itself in. Latency rarely catches anyone on its own. It is the corroborating witness that makes the rest of the evidence stick.

There is also a subtler version of this. Some companies run automated rules on connection data. A common one flags sessions where latency jumps far outside a user’s historical baseline. You do not need a suspicious IT admin for this. You just need a script doing its job, the same script that catches compromised accounts. From the system’s point of view, “employee suddenly connecting from 9,000 miles away” and “account taken over by someone 9,000 miles away” look identical at first.

Why a VPN alone does not fix the lag

This is the misunderstanding that gets the most nomads in trouble. A VPN changes where your traffic appears to come from. It does not change where your traffic physically travels.

Say you are in Bali and you connect to a commercial VPN server in Dallas so your IP address looks American. Your laptop still sits in Bali. Every signal still leaves Bali, crosses the Pacific, reaches Dallas, goes on to your company’s server, and comes all the way back. You have added a stop, not removed the ocean. Your IP address says Dallas. Your latency says “somewhere very far from Dallas,” because a real Dallas user would answer in 20 milliseconds and you are answering in 240.

Worse, the extra hop can make latency higher than it would be without the VPN. Your signal now travels to the VPN server and then to its destination, instead of going direct. So the standard nomad setup, laptop VPN to look like home, often produces the worst of both worlds: an IP address that claims to be home, paired with response times that prove it is not.

Security teams know this pattern well. “Impossible travel” alerts, the kind that fire when an account logs in from two far-apart places in a short time, often use latency as a sanity check. If the IP says New York but the round trip time looks like Southeast Asia, the system trusts the stopwatch, not the label. Labels can be faked. Physics cannot. Note that app-level leaks like Teams need their own fix.

What you can actually do about it

You cannot negotiate with physics, but you can change what the stopwatch is measuring. The trick is to make your connection take its long trip before it ever reaches your employer’s systems, so that everything your company measures looks like it started at home.

That is what a home-routed setup does. Instead of your laptop connecting straight to the company server across the ocean, your traffic goes through a connection that physically sits in your house. From your employer’s point of view, the session begins at your home address, with your home’s normal response times. The long leg of the journey, from wherever you actually are to your house, happens outside what their dashboards measure.

A few practical things still matter. The connection at your home base should be decent, because everything flows through it. A basic cable or fiber line is plenty; you do not need anything exotic. Test the whole arrangement before you travel, not from the airport. Run a video call through it while you are still home, check the numbers, and make sure it feels like a normal workday. If something is off, you want to discover it with your home router in the next room, not with a twelve hour time difference.

This is also where the quality of the setup matters more than the idea. A travel router pointed at a random server farm is still a commercial VPN with the latency problem described above. What you want is your own residential connection, your house, your internet provider, your everyday IP address, because that is the one whose latency pattern your employer already knows and trusts. The team at HomeIPVPN builds exactly this kind of setup for travelers, using your real home internet as the anchor point.

The bottom line on lag

Latency is the most honest signal your connection sends. Your IP address is a claim about where you are. Your latency is a measurement of how far away you really are, taken automatically, stored in dashboards, and very hard to argue with. Most nomads never think about it until IT asks an awkward question.

The good news is that once you understand it, the fix is straightforward: stop trying to fake the measurement from your laptop, and start routing through a connection whose measurements already look right. Get that in place, test it properly, and your video calls go back to being boring. Boring is the goal.

The root cause is simple: a VPN changes your address but not your distance, and latency always tells the truth about distance. That mismatch, an IP that says home paired with a ping that says ocean, is the problem HomeIPVPN was built to solve. If you would rather have someone set it up and verify it works, the Pre-Travel Audit & Advisory session is 1 hour, costs $79, and that fee comes straight off the $279 Secure Home IP VPN System session if you go ahead.

Travel is supposed to be the fun part. Your internet connection should not be narrating your itinerary. Get the routing right, and the only thing your team notices about your calls is what you actually said.