REFUGE Restrooms vs SBB Open Data
Same instrument, two spec sheets — measured, not claimed.
REFUGE Restrooms vs SBB Open Data: common questions
Which is more reliable, REFUGE Restrooms or SBB Open Data?
On our scheduled checks, SBB Open Data leads on measured uptime — REFUGE Restrooms at 96.1% versus SBB Open Data at 99.02% 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, REFUGE Restrooms or SBB Open Data?
SBB Open Data has the lower median latency in our checks — REFUGE Restrooms responds in 1787 ms versus SBB Open Data at 1230 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 REFUGE Restrooms and SBB Open Data need an API key?
Neither needs a paid key — REFUGE Restrooms is callable with no signup, and SBB Open Data is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call REFUGE Restrooms and SBB Open Data from the browser?
Only REFUGE Restrooms is browser-friendly — it returns CORS headers over HTTPS. SBB Open Data needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are REFUGE Restrooms and SBB Open Data free for commercial use?
REFUGE Restrooms has unclear commercial terms, and SBB Open Data 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.