Geocode.xyz vs ipapi.com

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms386301
P95 · ms6041575
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocode.xyz vs ipapi.com: common questions

Which is more reliable, Geocode.xyz or ipapi.com?

Both are neck-and-neck — Geocode.xyz and ipapi.com each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Geocode.xyz or ipapi.com?

ipapi.com has the lower median latency in our checks — Geocode.xyz responds in 386 ms versus ipapi.com at 301 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 Geocode.xyz and ipapi.com need an API key?

Geocode.xyz needs no key, while ipapi.com requires a free API key. If you want to start calling without signup, reach for Geocode.xyz first.

Can I call Geocode.xyz and ipapi.com from the browser?

Only Geocode.xyz is browser-friendly — it returns CORS headers over HTTPS. ipapi.com needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Geocode.xyz and ipapi.com free for commercial use?

Geocode.xyz has unclear commercial terms, and ipapi.com has unclear commercial terms. 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.