DownStatus vs OpenQR

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API key (per docs)Free tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DownStatus vs OpenQR: common questions

Which is more reliable, DownStatus or OpenQR?

On our scheduled checks, OpenQR leads on measured uptime — DownStatus at —% versus OpenQR 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 DownStatus and OpenQR need an API key?

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

Can I call DownStatus and OpenQR from the browser?

Yes — both DownStatus and OpenQR 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 DownStatus and OpenQR free for commercial use?

DownStatus has unclear commercial terms, and OpenQR 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.