BC Ferries vs BVG transport.rest
Same instrument, two spec sheets — measured, not claimed.
BC Ferries vs BVG transport.rest: common questions
Which is more reliable, BC Ferries or BVG transport.rest?
On our scheduled checks, BC Ferries leads on measured uptime — BC Ferries at 99.02% versus BVG transport.rest at 71.6% 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, BC Ferries or BVG transport.rest?
BC Ferries has the lower median latency in our checks — BC Ferries responds in 795 ms versus BVG transport.rest at 1106 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 BC Ferries and BVG transport.rest need an API key?
Neither needs a paid key — BC Ferries is callable with no signup, and BVG transport.rest is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call BC Ferries and BVG transport.rest from the browser?
Yes — both BC Ferries and BVG transport.rest 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 BC Ferries and BVG transport.rest free for commercial use?
BC Ferries has unclear commercial terms, and BVG transport.rest 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.