shipapis
StarSubmit an APISubmit API

ELI vs IPGeolocation

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

APIELINEW—IPGeolocationREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — 1000 requests/day
Rate limitUnpublished1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

ELI vs IPGeolocation: common questions

Which is more reliable, ELI or IPGeolocation?

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

Do ELI and IPGeolocation need an API key?

Both ask you to authenticate — ELI uses an API key and IPGeolocation uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call ELI and IPGeolocation from the browser?

Yes — both ELI and IPGeolocation 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 ELI and IPGeolocation free for commercial use?

ELI has unclear commercial terms, and IPGeolocation 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.