BVG transport.rest vs Ignav Flight API
Same instrument, two spec sheets — measured, not claimed.
BVG transport.rest vs Ignav Flight API: common questions
Which is more reliable, BVG transport.rest or Ignav Flight API?
On our scheduled checks, Ignav Flight API leads on measured uptime — BVG transport.rest at 71.6% versus Ignav Flight API 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, BVG transport.rest or Ignav Flight API?
Ignav Flight API has the lower median latency in our checks — BVG transport.rest responds in 1106 ms versus Ignav Flight API at 773 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 BVG transport.rest and Ignav Flight API need an API key?
Neither needs a paid key — BVG transport.rest is callable with no signup, and Ignav Flight API is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call BVG transport.rest and Ignav Flight API from the browser?
Only BVG transport.rest is browser-friendly — it returns CORS headers over HTTPS. Ignav Flight API needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are BVG transport.rest and Ignav Flight API free for commercial use?
BVG transport.rest has unclear commercial terms, and Ignav Flight API 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.