Openwhyd vs Shoof Aflam

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

Uptime · 30d
Uptime · 90d98.0%99.02%
Uptime · 30d100%98.3%
P50 · ms219539
P95 · ms10551312
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limit100 req/window · 99 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Openwhyd vs Shoof Aflam: common questions

Which is more reliable, Openwhyd or Shoof Aflam?

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

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

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

Can I call Openwhyd and Shoof Aflam from the browser?

Neither sends browser-friendly CORS headers reliably, so call Openwhyd and Shoof Aflam from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Openwhyd and Shoof Aflam free for commercial use?

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