AZ511 vs REFUGE Restrooms

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

Uptime · 30d
Uptime · 90d95.1%96.1%
Uptime · 30d95.0%93.3%
P50 · ms22721787
P95 · ms46104202
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (project is open source on GitHub)
Free tierFree tier — API key requiredFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AZ511 vs REFUGE Restrooms: common questions

Which is more reliable, AZ511 or REFUGE Restrooms?

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

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

REFUGE Restrooms needs no key, while AZ511 requires a free API key. If you want to start calling without signup, reach for REFUGE Restrooms first.

Can I call AZ511 and REFUGE Restrooms from the browser?

Only REFUGE Restrooms is browser-friendly — it returns CORS headers over HTTPS. AZ511 needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are AZ511 and REFUGE Restrooms free for commercial use?

AZ511 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.