Metro Lisboa vs OpenVan

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1308864
P95 · ms24592707
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no auth
Rate limitUnpublished120 req/window · 119 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metro Lisboa vs OpenVan: common questions

Which is more reliable, Metro Lisboa or OpenVan?

Both are neck-and-neck — Metro Lisboa and OpenVan each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Metro Lisboa or OpenVan?

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

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

Can I call Metro Lisboa and OpenVan from the browser?

Only OpenVan 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 Metro Lisboa and OpenVan free for commercial use?

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