Readit Newsincolumitas commented on A simple tool to check IP reputation ipscore.info/... · Posted by u/gigalord
If you want another simple tool that is much more advanced, try out https://ipapi.is/
incolumitas commented on Show HN: I Made a Ultra-Low Latency IP Geolocation API in Go ipflare.io/... · Posted by u/Lukem121
Your product looks very good.
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?
incolumitas commented on How accurate can IP Geolocation get? (2021) bigdatacloud.com/blog/how... · Posted by u/Leftium
I recently wrote a large article on IP geolocation and it turns out that the main source for IP geolocation is still WHOIS data: https://ipapi.is/geolocation.html
incolumitas commented on Ask HN: How does my new ISP "leak" my geolocation? · Posted by u/thisislife2
There are tools such as https://ipapi.is/ that can be used to geolocate any IPv4 and IPv6 address in the world. Sometimes those tools are not extremely accurate, but usually they are accurate to the city level.
incolumitas commented on IP Geolocation Is Twenty-Five Years Old sanjayparekh.com/ip-geolo... · Posted by u/sanjayparekh
And IP geolocation is still very relevant as of today.
You can derive an enormous amount of geolocation data by looking at WHOIS data: https://ipapi.is/geolocation.html
incolumitas commented on IPinfo's IP Hunt: 2.2M IPs submitted over 3 weeks ipinfo.io/blog/ipinfos-ip... · Posted by u/reincoder
Thank you. I hope you don't think I am pushing back or being sarcastic in any way because I personally like your work and really appreciate your comment. This is a typical conversation in a very "HN" way. Sometimes, it's hard to determine tone in written communication.
I appreciate that you make a wide variety of data accessible, and that has a positive impact. Our goal is to be the most accurate IP data provider, with geolocation being our foremost priority. It requires a "significant" amount of effort to simply be better than the rest of the industry. If customers want that bump in quality they will pay for our services. The ProbeNet has about 700 servers now, and nobody is investing in that level of infrastructure for IP data accuracy.
The whole game for us is accuracy. Consider our free IP to Country database. It is so accurate that it goes down to individual IP address (`/32`) levels for country-level locations. This high level of accuracy, however, results in a bigger file size. Some developers compromise on accuracy over file size. While rounding up the ranges to `/24` and updating them twice a week would reduce cost, it does not align with our philosophy.
> ipapi.is for sure detects some hosting provider's that you don't
ipinfo 91.102.88.0 -j | jq '.asn' { "asn": "AS47292", "name": "Sentia Denmark A/S", "domain": "sentia.com", "route": "91.102.88.0/21", "type": "hosting" }
ipinfo 185.45.13.144 -j | jq '.asn' { "asn": "AS9009", "name": "M247 Europe SRL", "domain": "m247.com", "route": "185.45.12.0/23", "type": "hosting" }
ipinfo 185.50.248.0 -j | jq .company { "name": "ATOMOHOST LLC", "domain": "atomohost.com", "type": "business" }
For the last one, it is not associated with an ASN, so the company field can be used as a proxy. As that company's IP data is a bit vague labeling it as hosting or business is difficult.
We have four types of "types": business, education, hosting, and ISP. This applies to both ASN and companies/organizations. For us, it is not simply a binary classification of hosting and non-hosting. Instead, we categorize IP ranges based on a statistical model with assigned weights. These ranges are then aggregated to determine AS types. When our customers say why is that this or that, you can show them the underlying reasoning.
But still, I grok and understand you. I really appreciate your feedback.
the last one is not vague, it is clearly a hosting provider: https://www.instagram.com/atomohost/?hl=en
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?
it's not hard to infer location data from IP addresses, albeit it's not necessarily an exact science