The latest articles on DEV Community by Jonathan Kosgei (@jonathankosgei). https://dev.to/jonathankosgei https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F55364%2Fd4baa5f4-5162-40aa-a041-f71862c5fcc9.jpeg https://dev.to/jonathankosgei en Jonathan Kosgei Wed, 04 Jul 2018 22:04:20 +0000 https://dev.to/jonathankosgei/comparing-8-commercial-ip-geolocation-apis-4nep https://dev.to/jonathankosgei/comparing-8-commercial-ip-geolocation-apis-4nep <p>We just published this detailed <a href="https://medium.com/@ipdata_co/what-is-the-best-commercial-ip-geolocation-api-d8195cda7027">comparison of the most popular commercial IP Geolocation APIs</a>.</p> <p>We looked at factors such as;</p> <ol> <li>Data quality — the accuracy of their geolocation data</li> <li>Data variety — threat intelligence data, proxy detection, carrier detection, tor detection</li> <li>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.</li> <li>Global endpoints — whether the API has more than one endpoint in different locations for redundancy and high scalability.</li> <li>Cost — cost per million calls</li> <li>Libraries</li> <li>HTTPs support</li> <li>Rate limits</li> <li>Infrastructure/High Availability — we use <code>dig</code> to show if a provider is terminating on a single server with an A record</li> <li>Simplicity of Documentation</li> </ol> <p>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.</p> <p>Feel free to reach out with feedback on your experiences using any of these services.</p> api