IPLocate vs OpenQR

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms211125
P95 · ms822851
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPLocate vs OpenQR: common questions

Which is more reliable, IPLocate or OpenQR?

Both are neck-and-neck — IPLocate and OpenQR 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, IPLocate or OpenQR?

IPLocate has the lower median latency in our checks — IPLocate responds in 21 ms versus OpenQR at 1125 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 IPLocate and OpenQR need an API key?

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

Can I call IPLocate and OpenQR from the browser?

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

IPLocate has unclear commercial terms, and OpenQR 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.