Live data from Hacker News

Show HN: A New, Clean Geolocation API

ipdata.co

151–160 of 168 posts

Re: Show HN: A New, Clean Geolocation API

#151
post #66

Are you able to flag an IP address as an IP coming from a VPN?

If you want to know whether an IP is from a VPN, Tor or a compromised server you can do that for free using the Shodan API ( https://developer.shodan.io ). Disclaimer: I'm the founder of Shodan and identifying the type of connection is something we're often used for.

Which api method exposes that information?

Re: Show HN: A New, Clean Geolocation API

#152

Earlier quoted context omitted.

This just is not reality. It’s funny... Google says this same thing publicly on their various webmaster blogs, but you know how Google Analytics determines your location? Your IP.

This can be considered a reasonable way when it's about statistics rather than about an individual user experience.

Agreed. Using IP for things you present to the user is strange and presumptuous. But the geolocation API is kind of “creepy” I image for the user. At least that’s always how it feels to me.

Re: Show HN: A New, Clean Geolocation API

#153
Just a few reasons why to use Ipdata;

1. Currency Data - The user's country's Currency ISO code and symbol are returned in the API output.

2. Phone Code Data - The user's country's Calling code is returned as well.

3. Global Footprint - Endpoints in 10 locations globally. 4 on both US coasts, 1 in Canada, 2 in Europe, 1 each in Mumbai, Seoul and Sydney. This ensures you get pretty low latencies wherever your app is hosted and wherever your end users are located.

4. Solid Infrastructure - The infrastructure backing Ipdata is pretty impressive, and built to scale to a substantial amount of traffic - in the hundreds of millions.

5. A free tier of 1500 requests daily (45 000/month) with no signup or credit card needed.

6. Examples in multiple languages on the Docs page at https://ipdata.co/docs.html, to make integrating with your site absolutely painless.

7. Regularly updated data - we check for changes daily and regularly update our data.

Coming soon; VPN/Proxy and Tor exit node data.

Re: Show HN: A New, Clean Geolocation API

#154
post #128

Earlier quoted context omitted.

Believe it or not, you make up about 0.000001%[1] of the internet users. There is no saying in what this can be applied, it doesn't have to be for language or anything like that. It doesn't even have to be anything customer facing, and if it's just some stats you will probably probably just be a bit of noise. Don't get me wrong. I totally agree that this thing is definitely not accurate(it thinks i'm 1300mi away) but…

Yes, and you've made up a number that reinforces your point. A number that, if wrong, could negate your point. Many more people are using VPNs these days. It's still not a large percentage, to be sure, but people are indeed doing it. Hell, I'm on my company VPN right now, and this site mis-identified my location because our VPN is set up to route most addresses in AWS's address space through the VPN (and ipdata.co ap…

I agree that IP geolocation is a good approximation. It is never accurate up to street level.

Meanwhile, there is API to detect VPN, so that we can aware that the geolocation is good up to the server physical location.

https://www.ip2location.com/ip2proxy-web-service

Re: Show HN: A New, Clean Geolocation API

#155
post #135

Earlier quoted context omitted.

Unkown, but very probably within a certain range whose boundaries are known.

In my case it gets country and city but misses completely the ZIP and area, as did all similar services tried so far. If someone threw a non nuclear missile to those coordinates I would probably just hear a distant bang. I'm curious to know if other people noticed the same level of accuracy.

We did.

Re: Show HN: A New, Clean Geolocation API

#156

Earlier quoted context omitted.

Assuming mmap 100mb will happen only once in each web-server.

What exactly do you mean by web server? Generally you will have at least one server process wherever you do the maxmind lookup, which could be at the LB/proxy (Nginx) or app server (node, python, go, etc). Nowadays these services are often heavily decoupled and therefore built to be as lightweight as possible. Think about small single purpose containers. Adding 100mb of memory requirements per instance could be quite…

Say you have python/ruby/js processes. You usually build 1 box/container with multiple processes inside. If you have 100 services and you distribute 1 process of each in each box then THAT is your problem.

"Nowadays" people are wrong.

Re: Show HN: A New, Clean Geolocation API

#157

Earlier quoted context omitted.

What exactly do you mean by web server? Generally you will have at least one server process wherever you do the maxmind lookup, which could be at the LB/proxy (Nginx) or app server (node, python, go, etc). Nowadays these services are often heavily decoupled and therefore built to be as lightweight as possible. Think about small single purpose containers. Adding 100mb of memory requirements per instance could be quite…

are you passing the original ip addresses to all these containers? Why don't you just decode the ip to location at the edge of your network (typically load balancer) and add a header with location?

That’s the best way to do it of course. But then you’re adding 100mb to each instance in your load balancing layer.

Re: Show HN: A New, Clean Geolocation API

#158
post #135

Earlier quoted context omitted.

Unkown, but very probably within a certain range whose boundaries are known.

In my case it gets country and city but misses completely the ZIP and area, as did all similar services tried so far. If someone threw a non nuclear missile to those coordinates I would probably just hear a distant bang. I'm curious to know if other people noticed the same level of accuracy.

Got mine pretty close.

Re: Show HN: A New, Clean Geolocation API

#159
post #97

> Get the following datapoints from any IP address; Again :-( I just wonder if people will ever stop making assumptions about others given their IP address or hair colours and divide the Internet on these slippery grounds. The only legitimate and valid way to determine the client's location automatically is the browser or the OS geolocation API, and for the language it is the HTTP_ACCEPT_LANGUAGE header. The fact I h…

This comment reminds me of the couple of people on HN that complain everytime someone shows off a new product and it doesn't work well in their text only lynx browser. It's such an extreme edge case that it doesn't really matter. (unless you are of course targeting that type of market). In other words, IP address gives a general location in a huge number of cases.

[deleted]

Re: Show HN: A New, Clean Geolocation API

#160

Earlier quoted context omitted.

Indonesia -- 47% Thailand -- 39% Brazil -- 36% Turkey -- 36% UAE -- 36% Viet Nam -- 35% Saudi Arabia -- 34% India -- 32% Malaysia -- 32% ... UK -- 14% US -- 14% https://wi-images.condecdn.net/image/3K6WrWwGrKN/crop/810

Those are clearly wildly incorrect numbers. I doubt if even 4.7% (a tenth of your figure) of internet users in Indonesia know what a VPN is .

Not knowing what a VPN doesn't exclude you from using one. Many workplaces use VPNs and it's likely that public internet access points (such as libraries, lounges, restaurants and cafes) could be using VPNs too.

Wikipedia says that Indonesia has an internet penetration rate of 50%. It might be reasonable to assume that a low penetration rate means that a significant amount of the internet access is happening in a work place rather than in a residential place. If a significant amount of access is happening at a work place it might also be reasonable to assume that a lot of that access is happening over a VPN.

https://en.wikipedia.org/wiki/List_of_countries_by_number_of...

Post reply on HN