District of Columbia Open Data vs City, Toronto Open Data

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (DC Open Data terms)Unverified
Free tierFree — limits not publishedFree — no key required (CKAN)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

District of Columbia Open Data vs City, Toronto Open Data: common questions

Which is more reliable, District of Columbia Open Data or City, Toronto Open Data?

On our scheduled checks, City, Toronto Open Data leads on measured uptime — District of Columbia Open Data at —% versus City, Toronto Open Data 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 District of Columbia Open Data and City, Toronto Open Data need an API key?

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

Can I call District of Columbia Open Data and City, Toronto Open Data from the browser?

Only District of Columbia Open Data 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 District of Columbia Open Data and City, Toronto Open Data free for commercial use?

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