DiscGolf vs TheCocktailDB

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms762300
P95 · ms2153562
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseFree to use with attribution (per response metadata)Unverified
Free tierFree — public endpoints, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DiscGolf vs TheCocktailDB: common questions

Which is more reliable, DiscGolf or TheCocktailDB?

Both are neck-and-neck — DiscGolf and TheCocktailDB each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, DiscGolf or TheCocktailDB?

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

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

Can I call DiscGolf and TheCocktailDB from the browser?

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

DiscGolf has unclear commercial terms, and TheCocktailDB 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.