DummyJSON vs IPGeolocation

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms91200
P95 · ms1929994
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — 1000 requests/day
Rate limit100 req/window · 99 remaining · resets 17835102431000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs IPGeolocation: common questions

Which is more reliable, DummyJSON or IPGeolocation?

Both are neck-and-neck — DummyJSON and IPGeolocation each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, DummyJSON or IPGeolocation?

DummyJSON has the lower median latency in our checks — DummyJSON responds in 91 ms versus IPGeolocation at 200 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do DummyJSON and IPGeolocation need an API key?

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

Can I call DummyJSON and IPGeolocation from the browser?

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

DummyJSON 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.