incolumitas
Joined 5 years ago
Joined 5 years ago
In this study I wanted to find out how good various different geolocation providers rank when being compared with real GPS location data obtained via the JS Location API.
Seems like IP Geolocation is 93% correct to the country level and like 70% correct to the city level.
This is way better than a "random guess" and therefore the utility is definitely given.
it's not hard to infer location data from IP addresses, albeit it's not necessarily an exact science
I am the creator of https://ipapi.is/ and already some time in the niche. I also have my own IP Geolocation Database as described here: https://ipapi.is/geolocation.html
Do you have your first customers?
You can derive an enormous amount of geolocation data by looking at WHOIS data: https://ipapi.is/geolocation.html
But I picked just one faulty classification of ipinfo.io, that's not fair, I know. I only wanted to point out that what you are doing is exactly the same as https://ipapi.is/ is doing and that we both make mistakes
----
You are using the 700 measuring servers to interpolate geolocations of IP addresses, right?
That works sometimes, but more than often it does not. It does not scale either.
Active latency triangulation of every IPv4 address (let's not even speak about IPv6) is simply not possible. The reasons are manyfold:
- Most hosts don't reply to ICMP
- Many routers block ICMP traffic, or they throttle / downgrade it, thus skewing measurements
- Traffic from your probing servers is probably not handled in the same way as is normal residential ISP traffic
- You have to constantly measure all IPv4, since IPs are constantly reassigned, which is simply not possible with only 700 servers
Latency triangulation works in theory, but in practice it is just not applicable to the full IP space.
Having said that, active geolocation with probing servers is still better than not doing it :D
Latency triangulation works much better in a passive way, meaning that a client is visiting a server that is under your control and you triangulate the client with JS for example (web sockets).
But I doubt that ipinfo.io has a significant share of the Internet's traffic...
Maybe I am missing something?
Hosting detection is a finite process, meaning that there is a finite amount of hosting providers out there to detect after all. Challenge lies in staying up to date.
So maybe we can make a compromise and state that ipinfo.io is likely a bit better than ipapi.is in hosting detection.
But ipapi.is for sure detects some hosting provider's that you don't. Examples:
https://api.ipapi.is/?q=185.45.13.144
https://api.ipapi.is/?q=185.50.248.0
https://api.ipapi.is/?q=91.102.88.0
Summary: Your product is maybe a bit better in regards to hosting detection than https://ipapi.is/, but it is much much much much more expensive ;)
https://ipapi.is/ is not as good in regards to geolocation, but our hosting detection is more advanced and https://ipapi.is/ is much cheaper...