IP Geolocation Accuracy, Proven by Active Measurement

Registry records say one country; the network sometimes says another. We verify IP geolocation with ping, traceroute and BGP data, and show where other providers get it wrong.

Speed of light check

1 of 4: 170.81.135.1, measured in the United States

1,000 km10,000 km
IP address
170.81.135.1
Round trip from Dallas
1.23 ms
7 of 9 providers say
Brazil

Brazil ruled out

In 1.23 ms, light in fiber only gets about 123 km from Dallas and back.

IPGeolocation.io

United States

IP geolocation accuracy, checked IP by IP

IPs from today's measurements where at least four IP data providers named a different country and our active measurement proved ours right. Each row shows what we measured, what they returned and the network evidence behind the call.

IPs compared
3,702,258,432 IPv4 addresses
Last compared on
2026
Providers compared
9 other IP geolocation providers
% Disputed
8.6% of compared IPs, where at least one provider disagrees
IPs measured in Europe where at least four IP data providers returned a different country
IP addressNetworkIPGeolocation.ioMeasured countryOther providersCountries returnedEvidenceClosest vantage point
209.127.158.20BusinessIPv4
GermanyConfirmed
United States ×42 agree with IPGeolocation.io
0.8 ms from Frankfurtwithin 80 km
82.47.0.127HostingIPv4
FranceConfirmed
United Kingdom ×34 agree with IPGeolocation.io
1.09 ms from Pariswithin 109 km
80.84.173.0BusinessIPv4
SwedenConfirmed
United Kingdom ×53 agree with IPGeolocation.io
0.5 ms from Stockholmwithin 50 km
45.199.248.123HostingIPv4
RussiaConfirmed
Belarus ×71 agrees with IPGeolocation.io
1.52 ms from Moscowwithin 152 km
Hong Kong ×24 agree with IPGeolocation.io
1.05 ms from Londonwithin 105 km
91.90.124.140HostingIPv4
IrelandConfirmed
Isle of Man ×62 agree with IPGeolocation.io
0.34 ms from Dublinwithin 34 km
SpainConfirmed
Netherlands ×35 agree with IPGeolocation.io
1.46 ms from Madridwithin 146 km
78.47.153.231HostingIPv4
FinlandConfirmed
Germany ×90 agree with IPGeolocation.io
0.3 ms from Helsinkiwithin 30 km
108.156.64.127HostingIPv4
NetherlandsConfirmed
United States ×33 agree with IPGeolocation.io
0.63 ms from Amsterdamwithin 63 km
54.37.140.88HostingIPv4
PolandConfirmed
France ×24 agree with IPGeolocation.io
0.71 ms from Warsawwithin 71 km
185.160.45.109HostingIPv4
GreeceConfirmed
India ×71 agrees with IPGeolocation.io
1.69 ms from Athenswithin 169 km
185.237.106.86BusinessIPv4
UkraineConfirmed
United States ×23 agree with IPGeolocation.io
0.46 ms from Kyivwithin 46 km
185.186.52.11BusinessIPv4
GermanyConfirmed
United Arab Emirates ×62 agree with IPGeolocation.io
0.4 ms from Nurembergwithin 40 km
FranceConfirmed
United States ×34 agree with IPGeolocation.io
1.21 ms from Marseillewithin 121 km
136.23.55.153HostingIPv4
SwedenConfirmed
Norway ×60 agree with IPGeolocation.io
0.66 ms from Stockholmwithin 66 km

Showing 15 of 277

Why does country accuracy matter so much?

The field everything depends on

Accurate pricing, local forms, and tax checkouts all rely on getting the country right.

When the country is wrong, region, city and time zone can go wrong with it, and so can localization and analytics.

What a round trip proves

A ping crosses fiber at about 200 km per millisecond and has to come back, so each millisecond of round trip allows at most 100 km.

If the circle stays inside one country, physics settles the country. If it crosses a border, one ping isn't enough: traceroute paths, BGP routing data and pings from other servers fill the gap.

The first test for any provider

When evaluating raw IP data, you must always start by checking the country field.

If an IP is in the wrong country, the fields that depend on it can be wrong too, which makes country errors the quickest way to spot weak data.

Where IP geolocation accuracy starts

IP geolocation accuracy starts with the country. City-level location, region, time zone, currency, calling code and language all build on it, and so do tax, compliance and content-licensing rules. A wrong country can make every one of them wrong too.

It's also the quickest field to check from the outside, which makes it the clearest one to show here.

Everything lines up

Try IP Geolocation for yourself

See accurate location data in real time with our APIs.

Get a free API key

No credit card required

How does active measurement prove an IP's location?

Every IP in today's list was measured by our Vantage Network rather than taken from registry records. Each measurement leaves evidence you can read: how fast the IP answered, which path the packets took and which network announces the address.

Measurement points around the world send probes and time every reply. Light in fiber covers about 200 km per millisecond, so each round trip draws a circle the IP cannot sit outside.

Ping the IP from Frankfurt:0.6 ms → within 60 km

Traceroutes reveal the network path and last known hop leading to the IP.

BGP routing data shows which network currently announces the IP's prefix.

A location is confirmed when the measurements agree on it, for the country and for the city.

Multilateration: pinning an IP to a city

Multilateration times one IP from many of our servers and finds the one place every answer agrees on. It's one of the layers in how our IP geolocation data is built.

  1. Time becomes distance

    A ping's round trip caps how far away the IP can be. Light in fiber covers about 200 km per millisecond, so a 1 ms round trip puts the IP within 100 km of the server.

  2. Every reply draws a circle

    The server sits at its center, and the IP is somewhere inside it.

  3. The overlap is where the IP is

    Circles from different directions cut the area down to the part they all share.

  4. Closer servers draw tighter circles

    Servers hundreds of kilometers away can only narrow the IP to a region. Servers tens of kilometers away narrow it to a city.

Narrowed to 11 km

7 far servers narrow one IP to a region within about 130 km. 5 servers inside that region narrow it to within 24 km, and 3 servers about 10 km away narrow it to Philadelphia, within 11 km.

Why do IP databases get the country wrong?

Country errors come from trusting paperwork over the network. These are the four patterns behind them.

Leased and transferred IPv4 blocks

  • With almost no new IPv4 space left to allocate, organizations buy, sell and lease address blocks across borders.
  • A lease often leaves the registry record as it was, and a sale can take a while to show up, so a database can keep the old country long after the block moved.
Example for Leased and transferred IPv4 blocks: 203.0.113.0/24 IPv4 block. Registered to: Netherlands. Leased to: Germany. Registry record: Netherlands (still listed).

What this page shows, and what it doesn't

The examples here are country level because that's where an error is plainest to see. All of our location data, city level included, runs through the same measurement pipeline.

Example IPs

A few IPs where providers report different countries than our measurement.

  • 74.125.147.88ZA
  • 203.76.232.2US
  • 138.99.146.2CO

Real IPs from today's list above.

Compare locations

We check where each IP data provider says the IP is located, and compare it to our measurement.

ProviderReported countryOur
measurement
Provider AUSZAMismatch
Provider BZAZAMatch
Provider CJPZAMismatch

Each row stands on its own. We're looking for differences, not counting how often providers make them.

Examples highlight where errors happen

These IPs show where at least four IP data providers reported a different country than our measurement.

Use measured location data in your stack

Every location on this page comes from the data your app gets back. Put it behind fraud checks, localization and analytics, and start free with 1,000 credits a day.

No credit card required.

  • 45.223.158.19: 7 providers said the United States; our measurement placed it in Germany, 6,203 km away.
  • 63.223.48.9: 2 providers said Hong Kong; our measurement placed it in South Africa, 10,717 km away.
  • 43.239.102.165: 4 providers said Singapore; our measurement placed it in Australia, 6,298 km away.
  • 190.98.179.214: 6 providers said Brazil; our measurement placed it in Colombia, 4,058 km away.

Subscribe to Our Newsletter

Get the latest in geolocation tech, straight to your inbox.