Skip to content

June 8, 2026 · 8 min read

How Accurate Is IP-Based Location?

How close IP geolocation really gets — measured against GPS, Wi-Fi, and cell positioning — and the practical reasons your result shows the wrong city.

IP-based location gets the country right 98.4% of the time, lands within 50 km in about three cases out of four, and never reaches your street address. The coordinates a site shows are the centre of a region or your ISP's hub — not a measured point — so the pin is an estimate that is usually close and occasionally hundreds of kilometres out. Here's how that compares to the other ways apps find you, and why your own result might look wrong.

Those figures come from our own measurements, not from estimates: we checked IP geolocation against 2,000 locations whose true coordinates were known, and published the script and raw data. That post has the full distribution, the per-country breakdown, and the method. This one is the practical "how close does it get and why is mine off" companion.

The short answer, by granularity

LevelMeasured accuracyTrust it for…
Country98.4% correctContent licensing, fraud checks, language defaults
Within 50 km75.3% of lookupsCoarse analytics, regional pricing
Within 10 km58.3% of lookups"Near me" hints — with a margin
Postal codeLow / unreliableAlmost nothing — treat as a marketing radius
Street addressNever from IP aloneNothing

Figures from our 2,000-location measurement. The median miss was 6.4 km — but 10.8% of lookups were off by more than 250 km, which is why none of these are safe as a single source of truth.

See your own result on the What Is My Location tool — it now shows an OpenStreetMap pin so you can judge the gap between the estimate and where you actually are.

IP location vs the other ways apps find you

This is the key thing most people miss: IP geolocation is the least precise location method by a wide margin. The browser and OS have far better options — they just require permission.

MethodHow it worksTypical precisionNeeds permission?
GPSSatellite ranging on the device~5 mYes
Wi-Fi positioningNearby Wi-Fi networks matched to a database~20–50 mYes (Geolocation API)
Cell towerTriangulation between masts~150 m – 1 kmYes
IP geolocationIP range matched to a registration databaseCity / region (often tens of km)No

The practical takeaway: when a site asks "Allow location access?", that's the precise path (GPS/Wi-Fi via the browser's Geolocation API). What it knows without asking — from your IP — is the coarse estimate this tool shows. If a site seems to know your exact spot, you granted the permission; your IP didn't reveal it.

Why your result looks wrong

If the city is off, it's almost always one of these — and none of them mean the lookup is broken:

  • You're on a VPN or proxy. You inherit the exit server's location. Connect to a London server and you "are" in London. Confirm your real exit point with the VPN Leak Test, and see how a VPN changes your IP.
  • You're on mobile data. Carrier-grade NAT funnels many users through a regional gateway, so you can show up a city — or a whole region — away.
  • Your ISP registers a wide area to one city. Smaller or rural ISPs often map an entire region to their billing or POP city.
  • Your IP was recently reassigned. Databases lag reality by days or weeks; a freshly allocated block may still point to the previous holder's location.
  • You're behind a corporate or campus network. Traffic may egress through a headquarters in another city or country entirely.

How to check your own accuracy

  1. Open the What Is My Location tool and note the city and the map pin.
  2. Compare it to where you actually are. Off by a few kilometres? That's normal and expected.
  3. Off by a city or country? Run the VPN Leak Test — a VPN, proxy, or mobile gateway is the usual explanation.
  4. Want the precise version for comparison? Any maps app using GPS will show the real difference between measured and inferred location.

When IP location is accurate enough — and when it isn't

Good enough for: fraud and bot screening, content licensing and geo-blocking, choosing a default language or currency, and coarse analytics. These only need country or region, which IP nails reliably.

Not good enough for: navigation, emergency dispatch, delivery, or anything needing your actual address. Those rely on GPS or an address you provide — never on IP alone. That gap is a feature, not a flaw: it's a large part of why browsing doesn't broadcast your doorstep to every site you visit. For the flip side — what can be inferred from your IP — read what someone can do with your IP address.


Check what your IP reveals about your location right now — including a live OpenStreetMap pin — with the What Is My Location tool. For the numbers behind every figure on this page, see our measurement of 2,000 known locations — script and raw data included — and if you rely on a VPN to control your apparent location, make sure it isn't leaking with the VPN Leak Test.

Related Reading

📄IP Geolocation Accuracy: We Measured 2,000 Known LocationsWe compared IP geolocation against 2,000 RIPE Atlas probes with known coordinates. Median error 6.4 km, mean 152.9 km — accuracy is bimodal, not merely imprecise. Full data and method included.12 min read📄How to Check If Your Password Was Leaked (Without Sending It Anywhere)Typing a password into a website to check it sounds reckless. Here is the method that makes it safe, how to verify the claim yourself, and why a clean result proves less than you think.7 min read📄How to Read Email Headers: Delivery Path, Delays and Spam SignalsEmail headers record every server that touched a message, how long each held it, and whether the sender was who they claimed. Here is how to read them without guessing.8 min read📄What to Send Your ISP or IT Support When Your Internet BreaksThe details support asks for every time — browser, OS, IP, ISP, latency, device — what each one is actually for, and how to collect all of them in one pass instead of ten.8 min read