shipapis
StarSubmit an APISubmit API

BigDataCloud Geocode vs ip.app

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

APIBigDataCloud GeocodeNEW—ip.appNEW—
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 limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BigDataCloud Geocode vs ip.app: common questions

Which is more reliable, BigDataCloud Geocode or ip.app?

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

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

Can I call BigDataCloud Geocode and ip.app from the browser?

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

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