IPGeolocation vs JSONPlaceholder

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 — limits not published
Rate limit1000 requests/day on free plan1000 req/window · 999 remaining · resets 1783509378
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs JSONPlaceholder: common questions

Which is more reliable, IPGeolocation or JSONPlaceholder?

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

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

Can I call IPGeolocation and JSONPlaceholder from the browser?

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

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