RandomDuck vs HTTP Dog

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RandomDuck vs HTTP Dog: common questions

Which is more reliable, RandomDuck or HTTP Dog?

On our scheduled checks, HTTP Dog leads on measured uptime — RandomDuck at —% versus HTTP Dog at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do RandomDuck and HTTP Dog need an API key?

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

Can I call RandomDuck and HTTP Dog from the browser?

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

Are RandomDuck and HTTP Dog free for commercial use?

RandomDuck has unclear commercial terms, and HTTP Dog 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.