RSQ API vs Spoo.me

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RSQ API vs Spoo.me: common questions

Which is more reliable, RSQ API or Spoo.me?

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

Neither needs a paid key — RSQ API is callable with no signup, and Spoo.me is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call RSQ API and Spoo.me from the browser?

Neither sends browser-friendly CORS headers reliably, so call RSQ API and Spoo.me from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are RSQ API and Spoo.me free for commercial use?

RSQ API has unclear commercial terms, and Spoo.me 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.