AZ511 vs Transport for Toronto, Canada

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

Uptime · 30d
Uptime · 90d95.1%67.6%
Uptime · 30d95.0%66.7%
P50 · ms2272781
P95 · ms46101477
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AZ511 vs Transport for Toronto, Canada: common questions

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

On our scheduled checks, AZ511 leads on measured uptime — AZ511 at 95.1% 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, AZ511 or Transport for Toronto, Canada?

Transport for Toronto, Canada has the lower median latency in our checks — AZ511 responds in 2272 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 AZ511 and Transport for Toronto, Canada need an API key?

Transport for Toronto, Canada needs no key, while AZ511 requires a free API key. If you want to start calling without signup, reach for Transport for Toronto, Canada first.

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

Neither sends browser-friendly CORS headers reliably, so call AZ511 and Transport for Toronto, Canada from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

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

AZ511 has unclear commercial terms, 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.