shipapis
StarSubmit an APISubmit API

AZ511 vs BVG transport.rest

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

APIAZ511HEALTHY77BVG transport.restDYING67
Uptime · 30d
Uptime · 90d95.1%71.6%
Uptime · 30d95.0%66.7%
P50 · ms22721106
P95 · ms46104431
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 BVG transport.rest: common questions

Which is more reliable, AZ511 or BVG transport.rest?

On our scheduled checks, AZ511 leads on measured uptime — AZ511 at 95.1% versus BVG transport.rest at 71.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 BVG transport.rest?

BVG transport.rest has the lower median latency in our checks — AZ511 responds in 2272 ms versus BVG transport.rest at 1106 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 BVG transport.rest need an API key?

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

Can I call AZ511 and BVG transport.rest from the browser?

Only BVG transport.rest 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 BVG transport.rest free for commercial use?

AZ511 has unclear commercial terms, and BVG transport.rest 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.