Hacker News new | ask | show | jobs
by jonathan-kosgei 2981 days ago
Hi, unfortunately we don't. However performance is very important to us which is why we have 11 endpoints around the world. And average ~65ms response times see status.ipdata.co.
1 comments
jimktrains2 2981 days ago
65ms feels like a lot. I guess you can cache it so you're only calling once per IP.
link
jonathan-kosgei 2980 days ago
I understand what you mean, but every other provider from the tests I've done comes in at double our speeds some even over plain HTTP. We only serve requests over HTTPS

More importantly the performance is consistent and you'd get the same performance wherever you were in the world.

link
jimktrains2 2980 days ago
Why compare to another API endpoint? You should compare it against accessing a local database.
link
jonathan-kosgei 2979 days ago
Comparing a network call vs filesystem i/o wouldn't be a useful comparison for someone deciding between different third part API providers.
link
jimktrains2 2979 days ago
Why not? I can load an IP database locally, so it's an option and a "competitor" to a 3rd party API. That's what I'm comparing it to, not against other APIs.
link
jonathan-kosgei 2979 days ago
It's pretty obvious that hitting your local disk is going to be a lot faster than making a network call. Make the right decision for your use case.
link