shipapis
StarSubmit an APISubmit API

IP Geolocation API vs WHO Global Health Observatory API

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

APIIP Geolocation APINEW—WHO Global Health Observatory APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IP Geolocation API vs WHO Global Health Observatory API: common questions

Which is more reliable, IP Geolocation API or WHO Global Health Observatory API?

On our scheduled checks, WHO Global Health Observatory API leads on measured uptime — IP Geolocation API at —% versus WHO Global Health Observatory API 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 IP Geolocation API and WHO Global Health Observatory API need an API key?

Neither needs a paid key — IP Geolocation API is callable with no signup, and WHO Global Health Observatory API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IP Geolocation API and WHO Global Health Observatory API from the browser?

Neither sends browser-friendly CORS headers reliably, so call IP Geolocation API and WHO Global Health Observatory API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are IP Geolocation API and WHO Global Health Observatory API free for commercial use?

IP Geolocation API has unclear commercial terms, and WHO Global Health Observatory API 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.