shipapis
StarSubmit an APISubmit API

IPGeolocation vs PyPI

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

APIIPGeolocationREACHABLE—PyPINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayFree — limits not published
Rate limit1000 requests/day on free planUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs PyPI: common questions

Which is more reliable, IPGeolocation or PyPI?

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

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

Can I call IPGeolocation and PyPI from the browser?

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

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