LCBO vs RacingHub
Same instrument, two spec sheets — measured, not claimed.
LCBO vs RacingHub: common questions
Which is more reliable, LCBO or RacingHub?
On our scheduled checks, LCBO leads on measured uptime — LCBO at 100% versus RacingHub 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, LCBO or RacingHub?
LCBO has the lower median latency in our checks — LCBO responds in 207 ms versus RacingHub at 473 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 RacingHub need an API key?
Neither needs a paid key — LCBO is callable with no signup, and RacingHub is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call LCBO and RacingHub from the browser?
Only RacingHub 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 RacingHub free for commercial use?
LCBO has unclear commercial terms, and RacingHub 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.