IPGeolocation vs ipify

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms259149
P95 · ms994354
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — 1000 requests/dayUnlimited
Rate limit1000 requests/day on free planNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

IPGeolocation vs ipify: common questions

Which is more reliable, IPGeolocation or ipify?

On our scheduled checks, IPGeolocation leads on measured uptime — IPGeolocation at 100% versus ipify at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, IPGeolocation or ipify?

ipify has the lower median latency in our checks — IPGeolocation responds in 259 ms versus ipify at 149 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do IPGeolocation and ipify need an API key?

ipify needs no key, while IPGeolocation requires a free API key. If you want to start calling without signup, reach for ipify first.

Can I call IPGeolocation and ipify from the browser?

Yes — both IPGeolocation and ipify send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are IPGeolocation and ipify free for commercial use?

IPGeolocation has unclear commercial terms, and ipify allows commercial use on its free tier. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.