The website says you are in the wrong country — even though you have landed

A website learns your location from your IP, not your GPS

Every time you load a page, your browser sends along the public IP address of that connection, because the server needs to know where to send its reply. Most websites have no access at all to your phone's GPS unless you separately grant it. What a site can do quickly and cheaply is look that IP address up in an IP geolocation database it has bought or downloaded, and show whatever country or city that lookup returns.

IP geolocation databases are stitched together from several sources: some from regional registries' records of which block belongs to whom, some from geofeeds that network operators publish themselves under RFC 8805 — a standard that lets an operator state where its own IP blocks sit — and some from inference when nothing else is available. Accuracy varies block by block as a result. A block whose operator keeps its geofeed current is often accurate down to the city; a block nobody has updated can still point at wherever it was registered years ago, even if that block has since moved to serving somewhere else entirely.

Why a travel eSIM's traffic often exits somewhere else

There is an extra layer for a travel eSIM specifically: your internet traffic does not necessarily leave the network at the point closest to you. Many providers route data through a gateway sitting in the issuing network's home country, or through a regional hub that pools traffic from several countries before releasing it onto the public internet. When that happens, the public IP address a website sees belongs to that gateway — not to the local cell tower your phone is actually attached to in the city you have landed in.

That gap between where you are standing and where the traffic actually exits is what makes some sites show the wrong country even though the roaming connection itself is working exactly as intended. It is a routing detail, not a sign that anything is broken. For a deeper look at how a travel eSIM's data path works, the guide on how travel eSIM data routing works covers it in more detail.

How your data is routed abroad

The map can be right while the website is wrong

A map app does not rely mainly on your IP address. It uses the phone's GPS together with nearby Wi-Fi and cell readings, through what the web standard calls the Geolocation API — something a browser or app needs your permission for before it can use it. Once you grant it, the app gets a fix accurate to street level, entirely independent of which country any database has decided your IP belongs to. That is why the map can walk you to the right door while an email or shopping site in the next tab greets you in a different country's language.

• GPS reads position directly from satellites and nearby signal points, with no IP database in the chain at all
• A site or app can use your location only after you grant permission; the phone or browser asks first, and you can withdraw it in settings
• IP location comes from a database guess, not a real measurement of where your device is
• The two are separate; a site that uses only the IP has no idea your GPS already has the right fix

SIM country, network country, IP country and account country are not the same thing

Most of the confusion comes from treating a phone's "country" as one value, when there are at least four, each decided by a different party. The eSIM's issuing country is decided by the provider you bought from. The roaming network country is decided by whichever cell tower your phone is attached to. The IP country is decided by the IP geolocation database of whatever site you have open. The app-store region is decided by account settings set up long ago — it does not follow your SIM or current location at all. All four often line up at home, and split apart easily while travelling.

Why some sites react visibly to the wrong location

Many sites and apps use IP location to adapt the page automatically: switching the default language, changing the currency prices are shown in, or swapping which content library you can see. When a travel eSIM's IP points at a country you were not expecting, the visible result is usually one of these — the language changes on its own, prices show in a different currency, or the film and music library looks unfamiliar. Some security-conscious sites may also ask for extra verification or a CAPTCHA more often, treating a login from an unfamiliar IP as worth an extra check.

One more thing complicates it: the public address you are using may not be yours alone. Many mobile network operators use a technique called carrier-grade NAT, which lets thousands of users share the same public IP address, drawing on an address range set aside for exactly this purpose under RFC 6598. When many users sit behind one IP, other people's behaviour on that shared address can affect what a site decides about you too — if someone else keeps failing logins from the same IP, a site may temporarily get stricter with everyone on it.

What you can actually do when a site gets your location wrong

The good news is most of this is easy to fix, and none of the fixes require anything that breaks a service's own terms. If a site's language switches on its own, look for a manual language switcher — most pages have one tucked in a corner. If a signed-in site shows the wrong price or content, logging in usually gives your account's saved settings more weight than a guess from your IP. Grant location permission to maps and navigation apps when asked, since that channel is far more accurate. For banking, use whatever travel notice your bank offers inside its own official app, rather than guessing how it treats a foreign IP. If a login is genuinely blocked, contact that service's own support to explain the situation.

• Switch the site's language yourself using its own language option, rather than waiting for it to guess again
• Sign into your account before opening a page with region-specific pricing or content, so the account's own settings carry more weight
• Grant location permission to maps and navigation apps when asked, since it is far more accurate than IP
• Use the official banking app's own travel-notice feature rather than guessing how it treats a foreign IP
• If the lodging has Wi-Fi, try switching to that path temporarily, since a hotel Wi-Fi's IP is often different from the eSIM's and can resolve the immediate issue

The app-store region follows your account, not your SIM

Another common mix-up is assuming the app store switches to match the country that issued the eSIM, or the current IP location. It does not work that way: an app-store region belongs to your account. Apple sets it in the account's own settings, and Google Play ties it to the account's country and payment profile. Google Play may offer to switch country when it notices you are somewhere new, but the switch happens only if you accept it, and Google limits how often it can be done. Travelling on a travel eSIM does not, by itself, change the apps and listings you see.