LCBO vs Padel Snipe

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

Uptime · 30d
Uptime · 90d100%82.4%
Uptime · 30d100%80.0%
P50 · ms2073830
P95 · ms4294941
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC-BY 4.0
Free tierFree — limits not publishedFree — no auth
Rate limit60 req/window · 59 remaining · resets 60Fair use — no hard limit stated
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs Padel Snipe: common questions

Which is more reliable, LCBO or Padel Snipe?

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

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

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

Can I call LCBO and Padel Snipe from the browser?

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

LCBO has unclear commercial terms, and Padel Snipe allows commercial use on its free tier. 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.