City Bikes vs RacingHub

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms665473
P95 · ms15803557
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedCC BY 4.0 (source data from the F1DB project)
Free tierFree — no key requiredFree — no key required
Rate limit300 req/window · 296 remaining · resets 837100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

City Bikes vs RacingHub: common questions

Which is more reliable, City Bikes or RacingHub?

On our scheduled checks, City Bikes leads on measured uptime — City Bikes 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, City Bikes or RacingHub?

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

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

Yes — both City Bikes and RacingHub send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are City Bikes and RacingHub free for commercial use?

City Bikes 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.