← All posts

Reference

How Accurate Is IP Geolocation? Country, Region and City Compared

June 11, 2026 · 5 min read

TL;DR

IP geolocation is excellent at the country level — typically 95–99% accurate — decent at region level (70–90%), and unreliable at city level (50–80%, often resolving to the ISP's hub city). For business routing decisions like language and pricing, country-level is the right granularity.

Every geo-targeting decision inherits the accuracy of IP geolocation, so it's worth knowing what that actually is — and where the errors come from. The numbers below reflect the ranges commercial geolocation providers themselves report.

Country95–99%Region / state70–90%City50–80%
Typical reported accuracy of commercial IP geolocation databases by granularity.

Why country-level is so reliable

IP address blocks are allocated through regional registries to ISPs that operate within national borders. A Norwegian broadband IP belongs to a Norwegian ISP and says so. The error sources at country level are mostly edge cases: corporate networks that route traffic through another country's gateway, satellite connections, and border-region mobile roaming.

Where it degrades

  • Mobile carriers often route through centralized gateways — a visitor in Bergen may resolve to Oslo. Country: still right. City: wrong.
  • VPNs and proxies replace the visitor's IP entirely. Geolocation reports the exit node, faithfully and uselessly.
  • CGNAT (carrier-grade NAT) pools many users behind shared IPs, blurring sub-national precision.
  • Stale databases — IP blocks get reallocated; providers that update daily stay accurate, free databases drift.

What this means for geo-routing

Match the decision to the granularity. Language, currency, legal entity, and sales region are country-level questions — the 95–99% zone. "Show the nearest store" is a city-level question and should use browser geolocation with user permission, not IP. And because even 98% accuracy means 1-in-50 visitors lands wrong, robust implementations always pair detection with an escape hatch: redirect once per session, and keep a visible country/language switcher.

Rule of thumb

IP geolocation answers "which market is this visitor in?" with high confidence. It cannot reliably answer "which neighborhood?" — and for website routing, it never needs to.

Geo-redirects on your HubSpot site in 5 minutes

One script tag, no code, no DNS changes. Free plan included.

Start free

Frequently asked questions

Why is country-level so much more accurate than city-level?

IP blocks are allocated to national ISPs, which rarely cross borders — so the country is almost always right. Within a country, ISPs route traffic through regional hubs, so the IP often resolves to the hub city rather than the visitor's actual town.

How do VPN users show up?

As the country of their VPN exit node. Estimates put regular VPN usage at a few percent of general web traffic (higher in privacy-conscious and technical audiences). For routing, the fix is behavioral: redirect once per session and keep a manual switcher available.

Is GPS-based location an alternative for websites?

Browsers expose precise location only behind an explicit permission prompt, which most visitors decline — and asking just to route them to a language version is terrible UX. IP-based country detection needs no prompt, which is why all geo-routing uses it.