Metro Lisboa vs REFUGE Restrooms

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

Uptime · 30d
Uptime · 90d100%96.1%
Uptime · 30d100%93.3%
P50 · ms13081787
P95 · ms24594202
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (project is open source on GitHub)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Metro Lisboa vs REFUGE Restrooms: common questions

Which is more reliable, Metro Lisboa or REFUGE Restrooms?

On our scheduled checks, Metro Lisboa leads on measured uptime — Metro Lisboa at 100% versus REFUGE Restrooms at 96.1% 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, Metro Lisboa or REFUGE Restrooms?

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

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

Can I call Metro Lisboa and REFUGE Restrooms from the browser?

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

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