IPs compared
Last compared on
Providers compared
% Disputed
IP2Location
BigDataCloud
ipapi.is
IP2Location
DB-IPThe 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.
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: 173.239.249.1, measured in the United States
- IP address
173.239.249.1- Round trip from Dallas
- 0.9 ms
- 7 of 9 providers say
- Ecuador
Ecuador ruled out
In 0.9 ms, light in fiber only gets about 90 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
- 9.0% of compared IPs, where at least one provider disagrees
| IP addressNetwork | IPGeolocation.ioMeasured country | Other providersCountries returned | EvidenceClosest vantage point |
|---|---|---|---|
217.170.20.91IPv4 |  GermanyConfirmed |  Netherlands ×81 agrees with IPGeolocation.io | 0.85 ms from Frankfurtwithin 85 km |
Physical latency constraint Netherlands ruled out Light in fiber covers about 200 km per ms, so a 0.85 ms round trip keeps the IP within 85 km. Netherlands is 356 km away.
| |||
31.57.152.29BusinessIPv4 |  RussiaConfirmed |  Curacao ×41 agrees with IPGeolocation.io | 1.51 ms from Moscowwithin 151 km |
Physical latency constraint Curacao ruled out Light in fiber covers about 200 km per ms, so a 1.51 ms round trip keeps the IP within 151 km. Curacao is 9,897 km away.
| |||
172.225.116.63HostingIPv4 |  FranceConfirmed |  United Kingdom ×70 agree with IPGeolocation.io | 0.96 ms from Pariswithin 96 km |
Physical latency constraint United Kingdom ruled out Light in fiber covers about 200 km per ms, so a 0.96 ms round trip keeps the IP within 96 km. United Kingdom is 343 km away.
| |||
209.206.9.127HostingIPv4 |  SpainConfirmed |  Gibraltar ×80 agree with IPGeolocation.io | 1.08 ms from Madridwithin 108 km |
Physical latency constraint Gibraltar ruled out Light in fiber covers about 200 km per ms, so a 1.08 ms round trip keeps the IP within 108 km. Gibraltar is 497 km away.
| |||
91.206.52.235IPv4 |  IrelandConfirmed |  Switzerland ×80 agree with IPGeolocation.io | 0.14 ms from Dublinwithin 14 km |
Physical latency constraint Switzerland ruled out Light in fiber covers about 200 km per ms, so a 0.14 ms round trip keeps the IP within 14 km. Switzerland is 1,231 km away.
| |||
151.244.164.109HostingIPv4 | United KingdomConfirmed |  United Arab Emirates ×35 agree with IPGeolocation.io | 0.89 ms from Londonwithin 89 km |
Physical latency constraint United Arab Emirates ruled out Light in fiber covers about 200 km per ms, so a 0.89 ms round trip keeps the IP within 89 km. United Arab Emirates is 5,485 km away.
| |||
217.78.199.2ISPIPv4 |  SwedenConfirmed |  Finland ×72 agree with IPGeolocation.io | 0.42 ms from Stockholmwithin 42 km |
Physical latency constraint Finland ruled out Light in fiber covers about 200 km per ms, so a 0.42 ms round trip keeps the IP within 42 km. Finland is 396 km away.
| |||
185.160.45.109HostingIPv4 |  GreeceConfirmed |  India ×71 agrees with IPGeolocation.io | 1.65 ms from Athenswithin 165 km |
Physical latency constraint India ruled out Light in fiber covers about 200 km per ms, so a 1.65 ms round trip keeps the IP within 165 km. India is 5,171 km away.
| |||
173.239.199.132HostingIPv4 | NetherlandsConfirmed | United States ×81 agrees with IPGeolocation.io | 0.62 ms from Amsterdamwithin 62 km |
Physical latency constraint United States ruled out Light in fiber covers about 200 km per ms, so a 0.62 ms round trip keeps the IP within 62 km. United States is 6,607 km away.
| |||
78.47.173.185HostingIPv4 | FinlandConfirmed | Germany ×90 agree with IPGeolocation.io | 0.27 ms from Helsinkiwithin 27 km |
Physical latency constraint Germany ruled out Light in fiber covers about 200 km per ms, so a 0.27 ms round trip keeps the IP within 27 km. Germany is 1,480 km away.
| |||
54.37.140.88HostingIPv4 |  PolandConfirmed | France ×24 agree with IPGeolocation.io | 0.58 ms from Warsawwithin 58 km |
Physical latency constraint France ruled out Light in fiber covers about 200 km per ms, so a 0.58 ms round trip keeps the IP within 58 km. France is 1,244 km away.
| |||
188.64.86.14ISPIPv4 |  Czech RepublicConfirmed | Poland ×62 agree with IPGeolocation.io | 0.52 ms from Praguewithin 52 km |
Physical latency constraint Poland ruled out Light in fiber covers about 200 km per ms, so a 0.52 ms round trip keeps the IP within 52 km. Poland is 517 km away.
| |||
92.39.114.90ISPIPv4 | GermanyConfirmed | United Kingdom ×71 agrees with IPGeolocation.io | 0.93 ms from Frankfurtwithin 93 km |
Physical latency constraint United Kingdom ruled out Light in fiber covers about 200 km per ms, so a 0.93 ms round trip keeps the IP within 93 km. United Kingdom is 640 km away.
| |||
172.217.130.134HostingIPv4 | RussiaConfirmed | United States ×44 agree with IPGeolocation.io | 0.78 ms from St. Petersburgwithin 78 km |
Physical latency constraint United States ruled out Light in fiber covers about 200 km per ms, so a 0.78 ms round trip keeps the IP within 78 km. United States is 6,888 km away.
| |||
129.134.41.43BusinessIPv4 | FranceConfirmed | United States ×62 agree with IPGeolocation.io | 0.89 ms from Marseillewithin 89 km |
Physical latency constraint United States ruled out Light in fiber covers about 200 km per ms, so a 0.89 ms round trip keeps the IP within 89 km. United States is 6,305 km away.
| |||
Showing 15 of 280
Why does country accuracy matter so much?
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.
Only Germany
4 countriesIf 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.
Time zone
Currency
Language
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.
No credit card required
New York
America/New_York
VPN Detected
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 kmTraceroutes 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.
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.
Every reply draws a circle
The server sits at its center, and the IP is somewhere inside it.
The overlap is where the IP is
Circles from different directions cut the area down to the part they all share.
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
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.
Routing and location changes
- A hosting company registered in Amsterdam can run its servers in Berlin.
- Registry data ties a range to the head office; active measurements tie it to where the servers are.
Prefixes that moved
- When a prefix is announced from a network in another country, routing tables show the move right away.
- Databases rebuilt from old registry records can keep the original country long after the move.
Stale geofeeds and records
- Network operators publish geofeeds (RFC 8805) to declare where their ranges are, then forget to update them.
- We test every feed against live measurements before we trust it.
Data center IPWhat 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.
- 142.250.218.16
CO - 142.251.76.12
ZA - 159.124.96.5
AU
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
measurement
Provider AUSCOMismatch
USCOMismatchProvider BCOCOMatch
COCOMatchProvider C
BRCOMismatch
BRCOMismatchEach 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.
Query providers
Every day we check what other providers return for the same IPs.
- Provider A
- Provider B
- Provider C
Every answer, by provider
Each row lists what each IP data provider returned for the IP, by name, next to our measurement.
- Provider AUSDiffers from our measurement
- Provider BCOMatches our measurement
- Provider CBRDiffers from our measurement
- Our measurementCO
Each row has its own evidence
Each row stands on its own: our measurement of the IP, next to what each provider returned.
- 193.251.128.203ESKept
- 62.115.204.35USKept
- 62.25.253.33JPKept
Ignore unclear IPs
Exclude IPs that do not answer probes.
- 192.0.2.1No responseExcluded
- 198.51.100.42No responseExcluded
- 203.0.113.7No responseExcluded
Remove edge cases
Leave out anycast addresses and border-straddling results.
- 192.0.2.17AnycastExcluded
- 198.51.100.77Border caseExcluded
- 203.0.113.33Border caseExcluded
What's left are IPs our measurements place inside a single country.
Keep clear results
Only rows with clear measurements make the list.
- 193.251.128.203ESKept
- 62.115.204.35USKept
- 62.25.253.33JPKept
User connects via VPN
The user's traffic goes through a VPN server in another location.
IP shows VPN server location
The IP appears where the VPN server is, and that is the correct answer for the IP.
203.0.113.12DE
DEUser's own locationHidden behind the VPN
We detect the difference
Our VPN, proxy and relay detection identifies anonymized connections and tells them apart from regular users.
- VPNDetected
- ProxyNot detected
- RelayNot detected
203.0.113.5Reported
We verify with live measurements
We measure the IP again from our servers and compare.
We update if needed
If the location is incorrect, we review and update it.
- 203.0.113.5Location updatedConfirmed
- Lookups return the new locationConfirmed
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.
Singapore- 142.251.228.96: 6 providers said the United States; our measurement placed it in Colombia, 4,003 km away.
- 194.124.66.3: 4 providers said France; our measurement placed it in Japan, 9,717 km away.
- 204.3.153.0: 2 providers said Singapore; our measurement placed it in South Africa, 8,660 km away.
- 202.84.140.29: 5 providers said Hong Kong; our measurement placed it in Australia, 7,370 km away.
