AZ511 vs Transport for Los Angeles, US

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

Uptime · 30d
Uptime · 90d95.1%99.02%
Uptime · 30d95.0%98.3%
P50 · ms22721478
P95 · ms46104808
AuthapiKeynone
CORSnoyes
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 Los Angeles, US: common questions

Which is more reliable, AZ511 or Transport for Los Angeles, US?

On our scheduled checks, Transport for Los Angeles, US leads on measured uptime — AZ511 at 95.1% versus Transport for Los Angeles, US at 99.02% 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 Los Angeles, US?

Transport for Los Angeles, US has the lower median latency in our checks — AZ511 responds in 2272 ms versus Transport for Los Angeles, US at 1478 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 Los Angeles, US need an API key?

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

Can I call AZ511 and Transport for Los Angeles, US from the browser?

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

Are AZ511 and Transport for Los Angeles, US free for commercial use?

AZ511 has unclear commercial terms, and Transport for Los Angeles, US 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.