RacingHub vs Squiggle

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseCC BY 4.0 (source data from the F1DB project)Unverified
Free tierFree — no key requiredFree — no key
Rate limit100 req/window · 99 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RacingHub vs Squiggle: common questions

Which is more reliable, RacingHub or Squiggle?

On our scheduled checks, Squiggle leads on measured uptime — RacingHub at —% versus Squiggle 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 RacingHub and Squiggle need an API key?

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

Can I call RacingHub and Squiggle from the browser?

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

Are RacingHub and Squiggle free for commercial use?

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