PurgoMalum vs RSQ API

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

Uptime · 30d
Uptime · 90d86.3%100%
Uptime · 30d85.0%100%
P50 · ms423783
P95 · ms48331387
Authnonenone
CORSyesyes
HTTPSyesno
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

PurgoMalum vs RSQ API: common questions

Which is more reliable, PurgoMalum or RSQ API?

On our scheduled checks, RSQ API leads on measured uptime — PurgoMalum at 86.3% versus RSQ API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, PurgoMalum or RSQ API?

PurgoMalum has the lower median latency in our checks — PurgoMalum responds in 423 ms versus RSQ API at 783 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 PurgoMalum and RSQ API need an API key?

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

Can I call PurgoMalum and RSQ API from the browser?

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

Are PurgoMalum and RSQ API free for commercial use?

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