shipapis
StarSubmit an APISubmit API

IPWhois vs LatLng

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

APIIPWhoisHEALTHY100LatLngHEALTHY89
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms23855
P95 · ms5982171
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs LatLng: common questions

Which is more reliable, IPWhois or LatLng?

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

IPWhois has the lower median latency in our checks — IPWhois responds in 23 ms versus LatLng at 855 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 IPWhois and LatLng need an API key?

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

Can I call IPWhois and LatLng from the browser?

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

Are IPWhois and LatLng free for commercial use?

IPWhois has unclear commercial terms, and LatLng 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.