Sirv vs Wallhaven

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — key may be required
Rate limitUnpublished45 req/window · 44 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Sirv vs Wallhaven: common questions

Which is more reliable, Sirv or Wallhaven?

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

Both ask you to authenticate — Sirv uses an API key and Wallhaven uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Sirv and Wallhaven from the browser?

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

Are Sirv and Wallhaven free for commercial use?

Sirv has unclear commercial terms, and Wallhaven 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.