Poof vs Sirv

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Poof vs Sirv: common questions

Which is more reliable, Poof or Sirv?

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

Both ask you to authenticate — Poof uses an API key and Sirv 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 Poof and Sirv from the browser?

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

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