Last updated: August 2026 · 9 min read

What IP geolocation is — and what it isn't

IP geolocation is the process of estimating a physical location from an IP address. When you connect to the internet, your provider hands your connection a public IP, and every site you visit sees it. Databases run by companies like MaxMind, IP2Location and others map ranges of those addresses to a country, region, city and rough set of coordinates. When a website — or our own IP lookup — shows your location, it's reading one of these databases, not tracking a signal from your device.

That distinction matters, because IP geolocation is often confused with GPS. GPS uses satellites to fix your device to within a few metres. IP geolocation does nothing of the kind. It's an educated guess based on how a block of addresses has been registered and observed, and the location it returns is really the location of a piece of network infrastructure — often the point where your provider routes your traffic — rather than the spot where you're sitting. Most of the time that's close enough to be useful. Sometimes it isn't close at all.

How accurate is it, level by level?

The honest answer is that accuracy depends heavily on how precise a location you're asking for. IP geolocation is excellent at answering "which country?" and progressively shakier as you zoom in. It helps to look at each level separately.

Country level: very reliable

At the country level, IP geolocation is genuinely dependable. MaxMind, one of the most widely used providers, reports country-level accuracy above 99% — and independent write-ups commonly cite figures around 99.8% for its GeoIP2 data on IPv4 addresses. This is why region-locked streaming, "you appear to be visiting from…" banners and basic fraud checks lean on IP location so heavily: getting the country right is something the databases do well the overwhelming majority of the time. The main thing that breaks country-level accuracy is deliberate masking, which we'll come to.

Region and state level: usually right, not always

Zoom in to the state, province or region and accuracy starts to slip. Published estimates for U.S. IP addresses tend to sit around 80% at the state level, according to comparisons of MaxMind's data. That's still useful for things like rough tax or content decisions, but it means roughly one in five lookups can land you in the wrong state — often a neighbouring one, or the state where your provider happens to route a whole region's traffic.

City level: a coin toss in many places

This is where expectations and reality part ways. City-level accuracy is far lower than most people assume. Providers themselves put typical city-level accuracy anywhere from about 20% to 75%, depending on the country and how it's measured. For U.S. IP addresses, analyses of MaxMind's database have found it correct only around two-thirds of the time when "correct" is defined generously — as landing within a 50-kilometre (about 30-mile) radius of the real location. Read that carefully: even the two-thirds that "succeed" are allowed to be up to 50 km off. Precise, street-level accuracy from an IP address alone essentially doesn't exist for ordinary consumer connections.

Those numbers vary by provider and by region, so treat any single figure with caution rather than as gospel. But the shape is consistent everywhere: country is easy, region is decent, city is a rough estimate, and anything more precise than a city — a postal code, a neighbourhood, a house — is not something a public IP can honestly deliver.

Why IP geolocation gets it wrong

None of this is because the databases are badly made. It's because an IP address was never designed to encode a location in the first place — the geography is inferred after the fact, and several everyday realities of how the internet is built get in the way.

Addresses are registered, not surveyed

Providers get blocks of IP addresses from regional internet registries and can assign them across a wide service area. The "location" of an address often comes from registration records and provider data, not from any physical measurement. A single block might be documented against a company's head office, a regional hub or a nearby major city, so everyone on that block appears to share that spot even if they're spread across a whole county. When a lookup puts you in a large city an hour away, this is usually why: you've been mapped to the centre of gravity of your provider's network, not to your address.

Carrier-grade NAT stacks many users behind one address

Because the world ran short of IPv4 addresses, many providers now use carrier-grade NAT (CGNAT), which lets hundreds or even thousands of customers share a single public IP. That shared address maps to a regional routing point rather than to any one household, so city-level precision for those users is blurred by design. The move from old-style IPv4 to IPv6 may eventually change this picture, but IPv6 geolocation databases are still less mature, and location data for IPv6 ranges is often noticeably weaker than for long-established IPv4 blocks.

Mobile data is especially fuzzy

If you're on a phone using cellular data, your IP typically traces back to a regional gateway for the mobile carrier — sometimes in a different city, occasionally in a different state. That's why the same phone can show one location on Wi‑Fi and a very different one on mobile data a minute later: the Wi‑Fi connection uses your home provider's address, while the cellular connection uses the carrier's gateway. Neither is "wrong" exactly; they're just describing different pieces of network plumbing.

VPNs and proxies relocate you on purpose

A VPN or proxy routes your traffic through a server somewhere else, so the address the world sees belongs to that server rather than to you. Any IP lookup then reports the server's location — which is the entire point of using one. This is common enough to matter at scale: surveys have estimated that roughly a fifth to a quarter of internet users worldwide used a VPN in recent years. If a large share of traffic is deliberately relocated, geolocation of those connections reflects the exit server, not the person. You can see this for yourself: check your location with the VPN off, connect to a server in another country, and watch the reported city and flag jump to match the server.

Data-centre and business addresses

Traffic from cloud services, hosting providers and some corporate networks comes from centralised addresses that don't correspond to any end user's home. If your employer backhauls everyone's internet through a single data centre, your work connection may geolocate to that facility's city no matter where you actually are.

So what can your IP address actually reveal?

Given all that, it's worth being precise about what someone learns from your IP. Realistically, a public IP reliably reveals your country, usually your region, an approximate city or metro area, and your internet provider. That's genuinely useful information — enough to serve region-appropriate content, flag an unusual login from another country, or block traffic from somewhere a service doesn't operate. It is not your home address. An IP address on its own doesn't reveal your name, your street, or a pinpoint location, and no reputable geolocation database claims otherwise. If you want to see the full profile a single visit exposes — IP, approximate location, provider, browser and device hints — our what websites see about you page lays it out.

It's also worth remembering that IP is only one signal among many. A site you're logged into already knows who you are regardless of your IP, and precise location usually comes from things you grant directly, like a browser or app location permission, not from the IP itself. Getting worked up about IP-level location while handing out GPS permission to every app is aiming at the wrong target.

How to check — and improve — your own result

The quickest way to understand IP geolocation is to test it on yourself. Open our IP lookup and see what it reports: note the country, region, city and provider. Compare the city to where you actually are. For a lot of people it'll be the right metro area but not the exact town, or a nearby city where their provider is centred — a perfect illustration of everything above.

If the location shown is more revealing than you'd like, the fix isn't to fight the database — it's to change the address the world sees. Routing your traffic through a VPN replaces your real IP and its location with the server's, so lookups report the server's city instead of your metro area. That improves your location privacy, though it's a trade-off: you're trusting the VPN provider with the traffic you're hiding from everyone else, and it does nothing about accounts you're logged into or permissions you've already granted. For the wider picture of what a connection gives away and how to tighten it, our guide to what websites see about you is the place to start.

And if you're on the other side of this — wondering why a service thinks you're in the wrong place — the answer is almost always one of the causes above: CGNAT, a mobile gateway, a provider that routes your region through a distant city, or a VPN you forgot was on. It's rarely a mistake you can "correct," because the database isn't tracking you; it's describing your provider's network.

Frequently Asked Questions

How accurate is IP geolocation?

It depends on the level of detail. Country-level accuracy is very high — often cited above 99% for major providers. State or region accuracy is roughly 80% for U.S. addresses. City-level accuracy is much lower, commonly in the 20–75% range depending on the provider and region, and even "correct" city results are typically only guaranteed to within tens of kilometres. IP geolocation is an estimate, not a pinpoint.

Can an IP address reveal my exact home address?

No. A public IP reliably indicates your country, usually your region, an approximate city or metro area, and your internet provider — but not your name or street address. The location returned reflects your provider's network infrastructure, not your front door. Precise, street-level location from an IP alone isn't something reputable databases claim to offer.

Why does an IP lookup show the wrong city?

Usually because your address is mapped to your provider's regional hub rather than your neighbourhood, or because you're behind carrier-grade NAT that shares one address among many users. Mobile connections route through carrier gateways that can be in another city entirely, and a VPN will show the server's city instead of yours. None of these are errors you can fix — they're how the underlying network is built.

Why is my location different on Wi-Fi and mobile data?

Because they use different IP addresses. On Wi‑Fi you're using your home internet provider's address; on mobile data you're using your cellular carrier's gateway, which often sits in a regional hub far from you. Each connection geolocates to its own piece of infrastructure, so the same phone can show two very different locations minutes apart.

Does a VPN change what IP geolocation shows?

Yes. A VPN routes your traffic through a server elsewhere, so any lookup reports that server's IP and location rather than your real one. This is the main way people deliberately change their apparent location. It improves location privacy but means trusting the VPN provider, and it doesn't hide accounts you're logged into or location permissions you've granted apps.

Is IP geolocation the same as GPS tracking?

No. GPS fixes a device to within a few metres using satellites and needs your permission. IP geolocation just estimates a location from a database of how address ranges are registered and observed, with no signal from your device — which is exactly why it's accurate at the country level and only approximate at the city level.