IPGeolocation vs npm Registry

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayFree (public registry)
Rate limit1000 requests/day on free planUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs npm Registry: common questions

Which is more reliable, IPGeolocation or npm Registry?

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

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

Can I call IPGeolocation and npm Registry from the browser?

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

IPGeolocation has unclear commercial terms, and npm Registry 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.