Foodish vs OpenF1

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

Uptime · 30d
Uptime · 90d27.5%47.1%
Uptime · 30d11.7%41.7%
P50 · ms250747
P95 · ms7603525
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Unverified
Free tierFree — no keyFree & open (historical); real-time may require a free account
Rate limitUnpublishedRetry-After: 60s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs OpenF1: common questions

Which is more reliable, Foodish or OpenF1?

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

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

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

Can I call Foodish and OpenF1 from the browser?

Only OpenF1 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 OpenF1 free for commercial use?

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