shipapis
StarSubmit an APISubmit API

Foodish vs RacingHub

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

APIFoodishDYING53RacingHubHEALTHY92
Uptime · 30d
Uptime · 90d27.5%99.02%
Uptime · 30d11.7%98.3%
P50 · ms250473
P95 · ms7603557
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)CC BY 4.0 (source data from the F1DB project)
Free tierFree — no keyFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs RacingHub: common questions

Which is more reliable, Foodish or RacingHub?

On our scheduled checks, RacingHub leads on measured uptime — Foodish at 27.5% versus RacingHub 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, Foodish or RacingHub?

Foodish has the lower median latency in our checks — Foodish responds in 250 ms versus RacingHub at 473 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 Foodish and RacingHub need an API key?

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

Can I call Foodish and RacingHub from the browser?

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

Are Foodish and RacingHub free for commercial use?

Foodish has unclear commercial terms, and RacingHub 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.