DownStatus vs Hunter

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

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

DownStatus vs Hunter: common questions

Which is more reliable, DownStatus or Hunter?

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

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

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

Can I call DownStatus and Hunter from the browser?

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

Are DownStatus and Hunter free for commercial use?

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