ELI vs ItsThisForThat

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms591242
P95 · ms1817555
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished (docs ask you not to hammer it)
In directory since2026-07-052026-07-05
operationalpartialdownno data

ELI vs ItsThisForThat: common questions

Which is more reliable, ELI or ItsThisForThat?

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

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

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

Can I call ELI and ItsThisForThat from the browser?

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

Are ELI and ItsThisForThat free for commercial use?

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