BC Ferries vs REFUGE Restrooms

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

Uptime · 30d
Uptime · 90d99.02%96.1%
Uptime · 30d98.3%93.3%
P50 · ms7951787
P95 · ms35224202
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (project is open source on GitHub)
Free tierFree — no keyFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BC Ferries vs REFUGE Restrooms: common questions

Which is more reliable, BC Ferries or REFUGE Restrooms?

On our scheduled checks, BC Ferries leads on measured uptime — BC Ferries at 99.02% 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, BC Ferries or REFUGE Restrooms?

BC Ferries has the lower median latency in our checks — BC Ferries responds in 795 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 BC Ferries and REFUGE Restrooms need an API key?

Neither needs a paid key — BC Ferries 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 BC Ferries and REFUGE Restrooms from the browser?

Yes — both BC Ferries and REFUGE Restrooms send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are BC Ferries and REFUGE Restrooms free for commercial use?

BC Ferries 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.