Some IPs return incomplete geolocation data. Is this expected?

Yes–in some cases, we intentionally won’t locate an IP to a more granular geolocation value (postal, city, subdivision, or even country) if our data indicate that the end-users are spread over wider geographic areas. The less granular geolocation data is considered to more accurately reflect the end-users’ actual location, to avoid false-positives. For example, mobile carriers tend to assign their IP addresses over widespread areas and reassign them frequently, so it is fairly common that we may only be able to return country-level location data for some IPs with cellular connections (e.g. 3g, 4g).

In other cases, we may simply not have data that reliably locates an IP to a more granular level. We’ll only return a geolocation value if we’re reasonably confident in it.

Our database should cover nearly all public IPs in use, so if we aren’t returning a country for an IP, the end-user is likely using some sort of proxy; is otherwise not identifiable on a country level (e.g. end-users are spread across multiple countries in Europe or Asia); or has submitted a valid Do Not Sell My Personal Information request.

You can double check the GeoIP2 geolocation data we return for up to 25 IPs daily, using our free online demo.