shipapis
StarSubmit an APISubmit API

InternetDB API vs IPGeolocation

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

APIInternetDB APINEW—IPGeolocationREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — 1000 requests/day
Rate limitUnpublished1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

InternetDB API vs IPGeolocation: common questions

Which is more reliable, InternetDB API or IPGeolocation?

On our scheduled checks, IPGeolocation leads on measured uptime — InternetDB API 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 InternetDB API and IPGeolocation need an API key?

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

Can I call InternetDB API and IPGeolocation from the browser?

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

InternetDB API 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.