ClinicalTrials.gov vs LCBO

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms243207
P95 · ms574429
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

ClinicalTrials.gov vs LCBO: common questions

Which is more reliable, ClinicalTrials.gov or LCBO?

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

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

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

Can I call ClinicalTrials.gov and LCBO from the browser?

Only ClinicalTrials.gov 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 ClinicalTrials.gov and LCBO free for commercial use?

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