NHTSA vs Transport for Toronto, Canada

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

Uptime · 30d
Uptime · 90d99.02%67.6%
Uptime · 30d100%66.7%
P50 · ms760781
P95 · ms49021477
Authnonenone
CORSyesno
HTTPSyesyes
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 Toronto, Canada: common questions

Which is more reliable, NHTSA or Transport for Toronto, Canada?

On our scheduled checks, NHTSA leads on measured uptime — NHTSA at 99.02% versus Transport for Toronto, Canada at 67.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, NHTSA or Transport for Toronto, Canada?

NHTSA has the lower median latency in our checks — NHTSA responds in 760 ms versus Transport for Toronto, Canada at 781 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 Toronto, Canada need an API key?

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

Can I call NHTSA and Transport for Toronto, Canada from the browser?

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

Are NHTSA and Transport for Toronto, Canada free for commercial use?

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