BVG transport.rest vs Metro Lisboa

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

Uptime · 30d
Uptime · 90d71.6%100%
Uptime · 30d66.7%100%
P50 · ms11061308
P95 · ms44312459
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BVG transport.rest vs Metro Lisboa: common questions

Which is more reliable, BVG transport.rest or Metro Lisboa?

On our scheduled checks, Metro Lisboa leads on measured uptime — BVG transport.rest at 71.6% versus Metro Lisboa at 100% 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, BVG transport.rest or Metro Lisboa?

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

Neither needs a paid key — BVG transport.rest is callable with no signup, and Metro Lisboa is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

Only BVG transport.rest is browser-friendly — it returns CORS headers over HTTPS. Metro Lisboa needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BVG transport.rest and Metro Lisboa free for commercial use?

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