Due to the global shortage of IPv4 addresses, Internet Service Providers (ISPs) are working hard trying to utilise the address space available to them, in the most effective way possible. Hence, they usually dedicate a pool of IP addresses, to a section of their network, which sometimes covers a substantial geographical area.
This method of dynamic address allocation significantly minimises the number of IP addresses required to serve the area because it effectively covers the active users rather than the entire clients' base.
Also, when the number of active users is higher than the IP address pool available, ISPs often employ techniques such as network address translation (NAT) to share a single IP address amongst multiple users. Mobile internet users, for instance, almost always share a pool of IP addresses that is much fewer than the number of devices connected.
Therefore, any point-based IP Geolocation can only estimate where an IP address is likely to be accessed from, as it is servicing anywhere within the service area determined by its operator. As a result, it is important to have an estimation of the service area for better decision making.
The IP Address Geolocation with Confidence Area API is designed to provide such crucial insights, and it is unlike any other API that can be found. You can view a demonstration of this on our “What is my IP?” page.
|ip||string||Requested IPv4 IP address in a string format|
|localityLanguageRequested||string||localityLanguage input parameter received|
|country||<Country> object||Geolocated Country|
|lastUpdated||string||Indicates the time of when that particular IP address’s geolocation was assessed the last|
|network||<Network> object||Network it belongs|
|confidence||string||Geolocation confidence, possible values:
|confidenceArea||Array of <point> objects||Closed polygon representing estimated geolocation confidence area|