Hipsum vs Spoo.me

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms723362
P95 · ms17321478
Authnonenone
CORSyesno
HTTPSyesyes
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

Hipsum vs Spoo.me: common questions

Which is more reliable, Hipsum or Spoo.me?

Both are neck-and-neck — Hipsum and Spoo.me each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Hipsum or Spoo.me?

Spoo.me has the lower median latency in our checks — Hipsum responds in 723 ms versus Spoo.me at 362 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 Hipsum and Spoo.me need an API key?

Neither needs a paid key — Hipsum 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 Hipsum and Spoo.me from the browser?

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

Are Hipsum and Spoo.me free for commercial use?

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