City Bikes vs Open Disease

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms665451
P95 · ms15801226
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree — no key requiredFree — no key required
Rate limit300 req/window · 296 remaining · resets 837Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City Bikes vs Open Disease: common questions

Which is more reliable, City Bikes or Open Disease?

On our scheduled checks, City Bikes leads on measured uptime — City Bikes at 100% versus Open Disease 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 Open Disease?

Open Disease has the lower median latency in our checks — City Bikes responds in 665 ms versus Open Disease at 451 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 Open Disease need an API key?

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

Can I call City Bikes and Open Disease from the browser?

Yes — both City Bikes and Open Disease 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 Open Disease free for commercial use?

City Bikes has unclear commercial terms, and Open Disease 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.