DownStatus vs ELI

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

Uptime · 30d
Uptime · 90d60.8%99.02%
Uptime · 30d33.3%98.3%
P50 · ms589591
P95 · ms12951817
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API key (per docs)Free tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DownStatus vs ELI: common questions

Which is more reliable, DownStatus or ELI?

On our scheduled checks, ELI leads on measured uptime — DownStatus at 60.8% versus ELI 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, DownStatus or ELI?

DownStatus has the lower median latency in our checks — DownStatus responds in 589 ms versus ELI at 591 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 DownStatus and ELI need an API key?

DownStatus needs no key, while ELI requires a free API key. If you want to start calling without signup, reach for DownStatus first.

Can I call DownStatus and ELI from the browser?

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

Are DownStatus and ELI free for commercial use?

DownStatus has unclear commercial terms, and ELI 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.