Longevity World Cup vs Open Disease

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

Uptime · 30d
Uptime · 90d98.9%99.44%
Uptime · 30d100%100%
P50 · ms590217
P95 · ms36771159
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree — no key requiredFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Longevity World Cup vs Open Disease: common questions

Which is more reliable, Longevity World Cup or Open Disease?

On our scheduled checks, Open Disease leads on measured uptime — Longevity World Cup at 98.9% versus Open Disease at 99.44% 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, Longevity World Cup or Open Disease?

Open Disease has the lower median latency in our checks — Longevity World Cup responds in 590 ms versus Open Disease at 217 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 Longevity World Cup and Open Disease need an API key?

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

Can I call Longevity World Cup and Open Disease from the browser?

Yes — both Longevity World Cup and Open Disease 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 Longevity World Cup and Open Disease free for commercial use?

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