shipapis
StarSubmit an APISubmit API

ip.app vs ipapi.co

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

APIip.appHEALTHY100ipapi.coDYING35
Uptime · 30d
Uptime · 90d100%1.0%
Uptime · 30d100%1.7%
P50 · ms76440
P95 · ms276440
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — quota not published; returns 429 when exceeded
Rate limitUnpublishedUnpublished (429 Quota exceeded)
In directory since2026-07-052026-07-05
operationalpartialdownno data

ip.app vs ipapi.co: common questions

Which is more reliable, ip.app or ipapi.co?

On our scheduled checks, ip.app leads on measured uptime — ip.app at 100% versus ipapi.co at 1.0% 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, ip.app or ipapi.co?

ip.app has the lower median latency in our checks — ip.app responds in 76 ms versus ipapi.co at 440 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 ip.app and ipapi.co need an API key?

Neither needs a paid key — ip.app is callable with no signup, and ipapi.co is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ip.app and ipapi.co from the browser?

Yes — both ip.app and ipapi.co 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 ip.app and ipapi.co free for commercial use?

ip.app has unclear commercial terms, and ipapi.co 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.