shipapis
StarSubmit an APISubmit API

LCBO vs TourneyRadar

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

APILCBOHEALTHY98TourneyRadarHEALTHY77
Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms2072911
P95 · ms4294191
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limit60 req/window · 59 remaining · resets 60100 req/window · 99 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs TourneyRadar: common questions

Which is more reliable, LCBO or TourneyRadar?

On our scheduled checks, LCBO leads on measured uptime — LCBO at 100% 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, LCBO or TourneyRadar?

LCBO has the lower median latency in our checks — LCBO responds in 207 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 LCBO and TourneyRadar need an API key?

Neither needs a paid key — LCBO 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 LCBO and TourneyRadar from the browser?

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

Are LCBO and TourneyRadar free for commercial use?

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