Callook.info vs WHO Global Health Observatory API

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

Uptime · 30d
Uptime · 90d100%88.2%
Uptime · 30d100%81.7%
P50 · ms437872
P95 · ms11562320
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (data from public FCC ULS records)Unverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Callook.info vs WHO Global Health Observatory API: common questions

Which is more reliable, Callook.info or WHO Global Health Observatory API?

On our scheduled checks, Callook.info leads on measured uptime — Callook.info at 100% versus WHO Global Health Observatory API at 88.2% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Callook.info or WHO Global Health Observatory API?

Callook.info has the lower median latency in our checks — Callook.info responds in 437 ms versus WHO Global Health Observatory API at 872 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 Callook.info and WHO Global Health Observatory API need an API key?

Neither needs a paid key — Callook.info 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 Callook.info and WHO Global Health Observatory API from the browser?

Only Callook.info is browser-friendly — it returns CORS headers over HTTPS. WHO Global Health Observatory API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Callook.info and WHO Global Health Observatory API free for commercial use?

Callook.info 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.