Metro Lisboa vs ProblemsByVin

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree — limits not publishedFree (weekly-refreshed static JSON datasets)
Rate limitUnpublishedUnpublished (static JSON files)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metro Lisboa vs ProblemsByVin: common questions

Which is more reliable, Metro Lisboa or ProblemsByVin?

On our scheduled checks, ProblemsByVin leads on measured uptime — Metro Lisboa at —% versus ProblemsByVin at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Metro Lisboa and ProblemsByVin need an API key?

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

Can I call Metro Lisboa and ProblemsByVin from the browser?

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

Metro Lisboa has unclear commercial terms, and ProblemsByVin allows commercial use on its free tier. 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.