shipapis
StarSubmit an APISubmit API

ip.app vs LatLng

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

APIip.appNEW—LatLngNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

ip.app vs LatLng: common questions

Which is more reliable, ip.app or LatLng?

On our scheduled checks, LatLng leads on measured uptime — ip.app at —% versus LatLng 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 ip.app and LatLng need an API key?

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

Can I call ip.app and LatLng from the browser?

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

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