Why Maps, Uber, and Delivery Apps Show the Wrong Location Abroad

How phone location actually works, and where it breaks

Modern phones almost never rely on satellite GPS alone — pure satellite fixes can take 30 seconds to several minutes and don't work well indoors or between tall buildings. Instead, phones use Assisted GPS (A-GPS), which combines satellite signal with nearby cell tower triangulation and Wi-Fi network scanning to get a fast, accurate fix. That system depends on your phone having an up-to-date, correctly registered connection to a local cellular network and access to a local database of Wi-Fi access point locations. When you're on a fresh roaming SIM that hasn't fully registered, or your phone is still holding onto network data cached from your home country, the cell-tower and Wi-Fi components of A-GPS are working from stale or absent local data, which produces a location that's technically "close" but off by anywhere from a block to a few miles, and slow to correct itself.

This is different from a hardware GPS failure, which is rare, and it's why turning location off and on again sometimes helps (it forces a fresh A-GPS handshake) while other times it does nothing, because the underlying cell registration issue is still there.

Why a VPN throws off apps that shouldn't even look at your IP

A VPN's job is to route your internet traffic through a remote server, which changes your apparent IP address and, by extension, your IP-based geolocation — but it does not touch your phone's actual GPS hardware. In theory, an app using real GPS shouldn't care what your VPN says. In practice, a meaningful number of apps, especially web-based map interfaces and some delivery apps, use IP geolocation as either a fallback when GPS permission is denied or slow, or as a cross-check to flag GPS readings that seem implausible given the IP location. When your VPN puts your IP in Frankfurt while your GPS correctly says you're in Lisbon, some apps split the difference, show stale cached data, or simply refuse to update your position until the conflict resolves — which from your side just looks like "the map is wrong." The fix for time-sensitive tasks like hailing a ride is almost always to disable the VPN specifically for that app or that session, get the pickup confirmed, then re-enable it afterward.

When apps quietly fall back to IP location instead of GPS

Some apps, particularly ones opened in a mobile browser rather than as a native app, don't request precise GPS permission at all and rely entirely on IP-based geolocation, which resolves to the location of your ISP's or roaming carrier's nearest routing point — sometimes accurate to the neighborhood, sometimes off by an entire city, especially with carrier-grade NAT setups common on roaming SIMs where hundreds of travelers share the same handful of exit IPs. This is a completely different failure mode from GPS lag: no amount of waiting or restarting fixes it, because the app was never trying to use real GPS in the first place. The tell is usually that the location is wrong by a consistent, large offset (the same wrong city every time) rather than jittering around your actual position, which is the signature of a GPS-lag issue instead.

Why this breaks Uber and delivery apps worse than regular map browsing

Casually browsing Google Maps tolerates a location error of a block or two just fine — you can still find your way. Ride-hailing and delivery apps can't, because the pin isn't just informational, it's the literal coordinate a driver or courier's app routes them to, and a several-hundred-meter error means the driver shows up at the wrong building, on the wrong side of a divided road, or can't find a pickup point that technically doesn't exist at those coordinates. This is compounded in cities with dense high-rises or informal street numbering, where even a small GPS offset can put you in the wrong building entirely. The most reliable workaround when the automatic pin is wrong is to manually drag the pickup pin to your exact location before confirming the ride, rather than trusting the app's auto-detected position, and to add a specific landmark note for the driver.

What actually helps before you land, not after

Set your phone to prefer network-based location alongside GPS rather than GPS-only in the location settings, since the network-assisted component is what speeds up the initial fix in a new country. If you use a VPN, choose a server location reasonably close to your actual country rather than a distant one, which reduces how far apart your IP and GPS locations appear and avoids tripping the cross-check logic some apps use. And give a new roaming SIM or eSIM 15 to 30 minutes of normal phone use — a phone call, some browsing — after landing before relying on it for anything location-critical, since full network registration and the local Wi-Fi/cell database sync isn't always instant. None of this is covered in a generic pre-trip checklist, which is why we built a dedicated pre-trip tech checklist that flags this specifically.

Stop guessing which setting is fighting your GPS