NHTSA vs Transport for The Netherlands

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms760680
P95 · ms49021557
Authnonenone
CORSyesno
HTTPSyesno
Card requirednono
Commercial useyesunclear
Data licensePublic domain (U.S. Government work)Unverified
Free tierFree, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NHTSA vs Transport for The Netherlands: common questions

Which is more reliable, NHTSA or Transport for The Netherlands?

Both are neck-and-neck — NHTSA and Transport for The Netherlands each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, NHTSA or Transport for The Netherlands?

Transport for The Netherlands has the lower median latency in our checks — NHTSA responds in 760 ms versus Transport for The Netherlands at 680 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 NHTSA and Transport for The Netherlands need an API key?

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

Can I call NHTSA and Transport for The Netherlands from the browser?

Only NHTSA is browser-friendly — it returns CORS headers over HTTPS. Transport for The Netherlands needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are NHTSA and Transport for The Netherlands free for commercial use?

NHTSA allows commercial use on its free tier, and Transport for The Netherlands 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.