City, Toronto Open Data vs Data USA

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms872433
P95 · ms2170788
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key required (CKAN)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Toronto Open Data vs Data USA: common questions

Which is more reliable, City, Toronto Open Data or Data USA?

On our scheduled checks, Data USA leads on measured uptime — City, Toronto Open Data at 99.02% versus Data USA at 100% 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, City, Toronto Open Data or Data USA?

Data USA has the lower median latency in our checks — City, Toronto Open Data responds in 872 ms versus Data USA at 433 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 City, Toronto Open Data and Data USA need an API key?

Neither needs a paid key — City, Toronto Open Data is callable with no signup, and Data USA is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City, Toronto Open Data and Data USA from the browser?

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

Are City, Toronto Open Data and Data USA free for commercial use?

City, Toronto Open Data has unclear commercial terms, and Data USA 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.