IPLocate.io vs ipify

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

IPLocate.io vs ipify: common questions

Which is more reliable, IPLocate.io or ipify?

Only ipify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do IPLocate.io and ipify need an API key?

Neither needs a paid key — IPLocate.io is callable with no signup, and ipify is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IPLocate.io and ipify from the browser?

Yes — both IPLocate.io 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 IPLocate.io and ipify free for commercial use?

IPLocate.io 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.