Open Disease vs TourneyRadar

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

Uptime · 30d
Uptime · 90d99.02%98.0%
Uptime · 30d98.3%96.7%
P50 · ms4512911
P95 · ms12264191
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (sources vary; see project repo)Unverified
Free tierFree — no key requiredFree — no key required
Rate limitUnpublished100 req/window · 99 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Disease vs TourneyRadar: common questions

Which is more reliable, Open Disease or TourneyRadar?

On our scheduled checks, Open Disease leads on measured uptime — Open Disease at 99.02% versus TourneyRadar at 98.0% 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, Open Disease or TourneyRadar?

Open Disease has the lower median latency in our checks — Open Disease responds in 451 ms versus TourneyRadar at 2911 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 Open Disease and TourneyRadar need an API key?

Neither needs a paid key — Open Disease is callable with no signup, and TourneyRadar is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Open Disease and TourneyRadar from the browser?

Yes — both Open Disease and TourneyRadar send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Open Disease and TourneyRadar free for commercial use?

Open Disease has unclear commercial terms, and TourneyRadar 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.