ELI vs ipify

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%100%
P50 · ms591149
P95 · ms1817354
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree tier — API key may be required for productionUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

ELI vs ipify: common questions

Which is more reliable, ELI or ipify?

Both are neck-and-neck — ELI and ipify each measure 99.02% 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, ELI or ipify?

ipify has the lower median latency in our checks — ELI responds in 591 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 ELI and ipify need an API key?

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

Can I call ELI and ipify from the browser?

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

ELI 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.