DownStatus vs Yes No

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

Uptime · 30d
Uptime · 90d60.8%100%
Uptime · 30d33.3%100%
P50 · ms589692
P95 · ms12951165
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API key (per docs)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DownStatus vs Yes No: common questions

Which is more reliable, DownStatus or Yes No?

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

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

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

Can I call DownStatus and Yes No from the browser?

Only Yes No 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 Yes No free for commercial use?

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