LAPIS vs NHL Records and Stats

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms524366
P95 · ms8461518
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs NHL Records and Stats: common questions

Which is more reliable, LAPIS or NHL Records and Stats?

Both are neck-and-neck — LAPIS and NHL Records and Stats each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, LAPIS or NHL Records and Stats?

NHL Records and Stats has the lower median latency in our checks — LAPIS responds in 524 ms versus NHL Records and Stats at 366 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 LAPIS and NHL Records and Stats need an API key?

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

Can I call LAPIS and NHL Records and Stats from the browser?

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

Are LAPIS and NHL Records and Stats free for commercial use?

LAPIS has unclear commercial terms, and NHL Records and Stats 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.