CIRCL CVE Search vs Currents

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

Uptime · 30d
Uptime · 90d98.0%100%
Uptime · 30d96.7%100%
P50 · ms698586
P95 · ms27651165
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CIRCL CVE Search vs Currents: common questions

Which is more reliable, CIRCL CVE Search or Currents?

On our scheduled checks, Currents leads on measured uptime — CIRCL CVE Search at 98.0% versus Currents at 100% 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 Currents?

Currents has the lower median latency in our checks — CIRCL CVE Search responds in 698 ms versus Currents at 586 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 Currents need an API key?

Both ask you to authenticate — CIRCL CVE Search uses an API key and Currents uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call CIRCL CVE Search and Currents from the browser?

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

Are CIRCL CVE Search and Currents free for commercial use?

CIRCL CVE Search has unclear commercial terms, and Currents 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.