Hacker News Reader

AWS (http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.h...), GCE (https://cloud.google.com/compute/docs/faq#where_can_i_find_s...), and other clouds maintain an up-to-date list of the ip blocks within their data-centers -- providing for more accurate data than a whois lookup.

however! I just added whois as a fallback, this seems like a really good idea:

https://github.com/bcoe/which-cloud/pull/10

View on HN

What are you doing to prevent others using you as a whois proxy?

Alternately, how are you planning to evade the (rather restrictive) rate limits which whois servers impose?

it's a goal to use the advertised IP blocks of cloud providers where possible, with whois simply as a fallback.

Will happily accept patches for other providers.

You realize that the majority of IPs submitted may not be from a known cloud provider/test suite, and so you're still dealing with the rate limiting from falling back for most requests?

I built this library to track signups for an application that has a fairly low request rate.

if you need a higher request rate 🤷 ¯\_(ツ)_/¯ pitch in and help add support for a wider variety of cloud providers.

Reply on news.ycombinator.com