shipapis
StarSubmit an APISubmit API

Fruityvice vs RacingHub

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

APIFruityviceHEALTHY88RacingHubHEALTHY92
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms951473
P95 · ms39963557
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedCC BY 4.0 (source data from the F1DB project)
Free tierFree — no API keyFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fruityvice vs RacingHub: common questions

Which is more reliable, Fruityvice or RacingHub?

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

RacingHub has the lower median latency in our checks — Fruityvice responds in 951 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 Fruityvice and RacingHub need an API key?

Neither needs a paid key — Fruityvice 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 Fruityvice and RacingHub from the browser?

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

Are Fruityvice and RacingHub free for commercial use?

Fruityvice 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.