BC Ferries vs NHTSA

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

Uptime · 30d
Uptime · 90d99.44%98.9%
Uptime · 30d100%98.3%
P50 · ms609514
P95 · ms35224902
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic domain (U.S. Government work)
Free tierFree — no keyFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BC Ferries vs NHTSA: common questions

Which is more reliable, BC Ferries or NHTSA?

On our scheduled checks, BC Ferries leads on measured uptime — BC Ferries at 99.44% versus NHTSA at 98.9% 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 NHTSA?

NHTSA has the lower median latency in our checks — BC Ferries responds in 609 ms versus NHTSA at 514 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 NHTSA need an API key?

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

Can I call BC Ferries and NHTSA from the browser?

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

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