shipapis
StarSubmit an APISubmit API

IPGeolocation vs NetBox API

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

APIIPGeolocationREACHABLE—NetBox APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayFree tier — API key required
Rate limit1000 requests/day on free planUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs NetBox API: common questions

Which is more reliable, IPGeolocation or NetBox API?

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

Both ask you to authenticate — IPGeolocation uses an API key and NetBox API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call IPGeolocation and NetBox API from the browser?

Only IPGeolocation is browser-friendly — it returns CORS headers over HTTPS. NetBox API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are IPGeolocation and NetBox API free for commercial use?

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