HTTP Dog vs RandomFox

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

Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%96.7%
P50 · ms57672
P95 · ms3642224
Authnonenone
CORSnoyes
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

HTTP Dog vs RandomFox: common questions

Which is more reliable, HTTP Dog or RandomFox?

On our scheduled checks, HTTP Dog leads on measured uptime — HTTP Dog at 100% versus RandomFox at 97.1% 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, HTTP Dog or RandomFox?

HTTP Dog has the lower median latency in our checks — HTTP Dog responds in 57 ms versus RandomFox at 672 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 HTTP Dog and RandomFox need an API key?

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

Can I call HTTP Dog and RandomFox from the browser?

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

Are HTTP Dog and RandomFox free for commercial use?

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