GeoApi vs IPWhois

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useyesunclear
Data licenseLicence Ouverte (Etalab; INSEE/IGN data)Unverified
Free tierFree, no API keyFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoApi vs IPWhois: common questions

Which is more reliable, GeoApi or IPWhois?

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

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

Can I call GeoApi and IPWhois from the browser?

Only GeoApi 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 GeoApi and IPWhois free for commercial use?

GeoApi allows commercial use on its free tier, and IPWhois 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.