We just published this detailed comparison of the most popular commercial IP Geolocation APIs.
We looked at factors such as;
- Data qualityβββthe accuracy of their geolocation data
- Data varietyβββthreat intelligence data, proxy detection, carrier detection, tor detection
- API latencyβββwe used a third party monitoring tool to monitor each API for 24 hrs. We sent a request every 30 seconds from 8 locations globally. Los Angeles - US, Miami - US, Montreal - Canada, Gravelines - France, Frankfurt - Germany, Singapore, Tokyo - Japan, Sydney - Australia.
- Global endpointsβββwhether the API has more than one endpoint in different locations for redundancy and high scalability.
- Costβββcost per million calls
- Libraries
- HTTPs support
- Rate limits
- Infrastructure/High Availabilityβββwe use
dig
to show if a provider is terminating on a single server with an A record - Simplicity of Documentation
To measure API latency we setup status pages on updown.io for each API and monitored it for 24hrs. Updown sent a request every 30 seconds from 8 locations globally.
Feel free to reach out with feedback on your experiences using any of these services.
Top comments (2)
Thank You
I am using the IP geolocation API from ipwhois.io
Some comments may only be visible to logged-in visitors. Sign in to view all comments.