Episodate vs Openwhyd

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

Uptime · 30d
Uptime · 90d99.02%98.0%
Uptime · 30d100%100%
P50 · ms867219
P95 · ms17081055
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Episodate vs Openwhyd: common questions

Which is more reliable, Episodate or Openwhyd?

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

Openwhyd has the lower median latency in our checks — Episodate responds in 867 ms versus Openwhyd at 219 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 Episodate and Openwhyd need an API key?

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

Can I call Episodate and Openwhyd from the browser?

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

Are Episodate and Openwhyd free for commercial use?

Episodate has unclear commercial terms, and Openwhyd 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.