AZ511 vs BC Ferries

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

Uptime · 30d
Uptime · 90d95.1%99.02%
Uptime · 30d95.0%98.3%
P50 · ms2272795
P95 · ms46103522
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AZ511 vs BC Ferries: common questions

Which is more reliable, AZ511 or BC Ferries?

On our scheduled checks, BC Ferries leads on measured uptime — AZ511 at 95.1% versus BC Ferries 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 BC Ferries?

BC Ferries has the lower median latency in our checks — AZ511 responds in 2272 ms versus BC Ferries at 795 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 BC Ferries need an API key?

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

Can I call AZ511 and BC Ferries from the browser?

Only BC Ferries 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 BC Ferries free for commercial use?

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