Live data from Hacker News

Show HN: IP Geolocation and Threat Data API

ipdata.co

11–20 of 67 posts

Re: Show HN: IP Geolocation and Threat Data API

#12

Seems nice. Small suggestion : 1500 api request for free and 2500 api requests for 10€. I think it's a huge leap for pricing, either reduce the requests for free user or reduce de price / increase the requests for the first payed plan.

It's not really that huge, 1000 requests is a rounding error for our other plans :)

Re: Show HN: IP Geolocation and Threat Data API

#13
post #9

Earlier quoted context omitted.

Tried in a new private browser window, even. Here's part of the page source on that URL: Oops Page Not Found! Sorry. That page doesn't exist. Edit: The images are loading now. But https://api.ipdata.co returns: {"message": "Internal server error"} and the demo on the right hand side of the frontpage shows: Your IP Address is {}0 items

Could you try visiting https://api.ipdata.co . I'm positive the API is up https://status.ipdata.co

It still errors out:

  % curl --header "Accept: application/json" https://api.ipdata.co
  {"message": "Internal server error"}
Also, this request doesn't seem to return valid JSON:

  % curl --header "Accept: application/json" https://api.ipdata.co/224.0.0.1
  224.0.0.1 is a bogon address.

Re: Show HN: IP Geolocation and Threat Data API

#14
Jonathan's been doing a great job of ipdata.co! I'd like to also shout out to my own service https://ipinfo.io here though, where we've recently launched new plans that include company details, carrier details, and IP type - we have a custom classifier that labels each IP as isp, business, or hosting, which can be really useful for a bunch of use cases. Here's sample output from the pro plan:

    {
      "ip": "66.87.125.72",
      "hostname": "66-87-125-72.pools.spcsdns.net",
      "city": "Southbridge",
      "region": "Massachusetts",
      "country": "US",
      "loc": "42.0707,-72.0440",
      "postal": "01550",
      "asn": {
        "asn": "AS10507",
        "name": "Sprint Personal Communications Systems",
        "domain": "spcsdns.net",
        "route": "66.87.125.0/24",
        "type": "isp"
      },
      "company": {
        "name": "Sprint",
        "domain": "sprint.com",
        "type": "isp"
      },  
      "carrier": {
        "name": "Sprint",
        "mcc": "310",
        "mnc": "120"
      }
    }
See https://ipinfo.io/responses for more of an overview of the differences between our plans.

Re: Show HN: IP Geolocation and Threat Data API

#15
post #13

Earlier quoted context omitted.

Could you try visiting https://api.ipdata.co . I'm positive the API is up https://status.ipdata.co

It still errors out: % curl --header "Accept: application/json" https://api.ipdata.co {"message": "Internal server error"} Also, this request doesn't seem to return valid JSON: % curl --header "Accept: application/json" https://api.ipdata.co/224.0.0.1 224.0.0.1 is a bogon address.

That's an expected response for bogon IP addresses, but you have you make a good point, we should make our error responses JSON.

Please email me your IP address at jonathan at ipdata dot co and I'll help you out.

Re: Show HN: IP Geolocation and Threat Data API

#16

Jonathan's been doing a great job of ipdata.co! I'd like to also shout out to my own service https://ipinfo.io here though, where we've recently launched new plans that include company details, carrier details, and IP type - we have a custom classifier that labels each IP as isp, business, or hosting, which can be really useful for a bunch of use cases. Here's sample output from the pro plan: { "ip": "66.87.125.72",…

Hey Ben! Thank you :)

Re: Show HN: IP Geolocation and Threat Data API

#20

Jonathan's been doing a great job of ipdata.co! I'd like to also shout out to my own service https://ipinfo.io here though, where we've recently launched new plans that include company details, carrier details, and IP type - we have a custom classifier that labels each IP as isp, business, or hosting, which can be really useful for a bunch of use cases. Here's sample output from the pro plan: { "ip": "66.87.125.72",…

Do you think it's appropriate to shill your own service every time a competitor has a Show HN?

You made the same post during OP's last Show HN: https://news.ycombinator.com/item?id=15881463

I also wonder how mature a project has to be before it seems sheepish to "Show HN".

Post reply on HN