LCBO vs TheSportsDB

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

Uptime · 30d
Uptime · 90d100%56.9%
Uptime · 30d100%58.3%
P50 · ms207238
P95 · ms4293182
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 59 remaining · resets 60Retry-After: 92s
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs TheSportsDB: common questions

Which is more reliable, LCBO or TheSportsDB?

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

LCBO has the lower median latency in our checks — LCBO responds in 207 ms versus TheSportsDB at 238 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 TheSportsDB need an API key?

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

Can I call LCBO and TheSportsDB from the browser?

Only TheSportsDB 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 TheSportsDB free for commercial use?

LCBO has unclear commercial terms, and TheSportsDB 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.