shipapis
StarSubmit an APISubmit API

Makeup vs RacingHub

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

APIMakeupHEALTHY89RacingHubHEALTHY94
Uptime · 30d
Uptime · 90d98.9%99.44%
Uptime · 30d96.6%100%
P50 · ms557378
P95 · ms25293557
Authnonenone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedCC BY 4.0 (source data from the F1DB project)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Makeup vs RacingHub: common questions

Which is more reliable, Makeup or RacingHub?

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

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

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

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

Are Makeup and RacingHub free for commercial use?

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