CIRCL CVE Search vs WHO Global Health Observatory API

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

Uptime · 30d
Uptime · 90d98.0%88.2%
Uptime · 30d96.7%81.7%
P50 · ms698872
P95 · ms27652320
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CIRCL CVE Search vs WHO Global Health Observatory API: common questions

Which is more reliable, CIRCL CVE Search or WHO Global Health Observatory API?

On our scheduled checks, CIRCL CVE Search leads on measured uptime — CIRCL CVE Search at 98.0% 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, CIRCL CVE Search or WHO Global Health Observatory API?

CIRCL CVE Search has the lower median latency in our checks — CIRCL CVE Search responds in 698 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 CIRCL CVE Search and WHO Global Health Observatory API need an API key?

WHO Global Health Observatory API needs no key, while CIRCL CVE Search requires a free API key. If you want to start calling without signup, reach for WHO Global Health Observatory API first.

Can I call CIRCL CVE Search and WHO Global Health Observatory API from the browser?

Only CIRCL CVE Search 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 CIRCL CVE Search and WHO Global Health Observatory API free for commercial use?

CIRCL CVE Search 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.