DiscGolf vs Open Disease

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms762451
P95 · ms21531226
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseFree to use with attribution (per response metadata)Unverified (sources vary; see project repo)
Free tierFree — public endpoints, no keyFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DiscGolf vs Open Disease: common questions

Which is more reliable, DiscGolf or Open Disease?

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

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

Neither needs a paid key — DiscGolf 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 DiscGolf and Open Disease from the browser?

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

DiscGolf 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.