COVID-19 Tracker Sri Lanka vs LAPIS

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

Uptime · 30d
Uptime · 90d98.0%100%
Uptime · 30d96.7%100%
P50 · ms1439524
P95 · ms4548846
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — limits not publishedFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

COVID-19 Tracker Sri Lanka vs LAPIS: common questions

Which is more reliable, COVID-19 Tracker Sri Lanka or LAPIS?

On our scheduled checks, LAPIS leads on measured uptime — COVID-19 Tracker Sri Lanka at 98.0% versus LAPIS 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, COVID-19 Tracker Sri Lanka or LAPIS?

LAPIS has the lower median latency in our checks — COVID-19 Tracker Sri Lanka responds in 1439 ms versus LAPIS at 524 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 COVID-19 Tracker Sri Lanka and LAPIS need an API key?

Neither needs a paid key — COVID-19 Tracker Sri Lanka is callable with no signup, and LAPIS is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call COVID-19 Tracker Sri Lanka and LAPIS from the browser?

Only LAPIS is browser-friendly — it returns CORS headers over HTTPS. COVID-19 Tracker Sri Lanka needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are COVID-19 Tracker Sri Lanka and LAPIS free for commercial use?

COVID-19 Tracker Sri Lanka has unclear commercial terms, and LAPIS 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.