ProblemsByVin vs BC Ferries

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC BY 4.0Unverified
Free tierFree (weekly-refreshed static JSON datasets)Free — no key
Rate limitUnpublished (static JSON files)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ProblemsByVin vs BC Ferries: common questions

Which is more reliable, ProblemsByVin or BC Ferries?

On our scheduled checks, BC Ferries leads on measured uptime — ProblemsByVin at —% versus BC Ferries at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ProblemsByVin and BC Ferries need an API key?

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

Can I call ProblemsByVin and BC Ferries from the browser?

Yes — both ProblemsByVin and BC Ferries 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 ProblemsByVin and BC Ferries free for commercial use?

ProblemsByVin allows commercial use on its free tier, and BC Ferries 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.