Block Lottos vs Mempool

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

Uptime · 30d
Uptime · 90d98.0%86.3%
Uptime · 30d96.7%90.0%
P50 · ms1025100
P95 · ms36582258
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree, no key (API docs state no key required)Free public API; no key for basic usage
Rate limitUnpublishedEnforced — HTTP 429 on excess, repeated abuse may be banned; numeric limits unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Block Lottos vs Mempool: common questions

Which is more reliable, Block Lottos or Mempool?

On our scheduled checks, Block Lottos leads on measured uptime — Block Lottos at 98.0% versus Mempool at 86.3% 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, Block Lottos or Mempool?

Mempool has the lower median latency in our checks — Block Lottos responds in 1025 ms versus Mempool at 100 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 Block Lottos and Mempool need an API key?

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

Can I call Block Lottos and Mempool from the browser?

Yes — both Block Lottos and Mempool 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 Block Lottos and Mempool free for commercial use?

Block Lottos has unclear commercial terms, and Mempool 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.