NHTSA vs Transport for London, England

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licensePublic domain (U.S. Government work)Unverified
Free tierFree, no keyFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NHTSA vs Transport for London, England: common questions

Which is more reliable, NHTSA or Transport for London, England?

On our scheduled checks, Transport for London, England leads on measured uptime — NHTSA at —% versus Transport for London, England 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 NHTSA and Transport for London, England need an API key?

NHTSA needs no key, while Transport for London, England requires a free API key. If you want to start calling without signup, reach for NHTSA first.

Can I call NHTSA and Transport for London, England from the browser?

Yes — both NHTSA and Transport for London, England 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 NHTSA and Transport for London, England free for commercial use?

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