OnFinality leads on all 3 live benchmarks. OnFinality wins on Stellar Soroban RPC endpoints (112 ms vs 612 ms), Cheapest RPC provider, priced per workload across 19 providers ($49 vs $200), Most requests a free RPC plan buys, across 13 providers (6.86M vs 1.00M). Data as of 2026-11-18 UTC.
Read methodology Last measured Window: rolling 24h3 shared benchmarks
Published prices, not invoices. Each figure is human-verified against the provider's own pricing page or API and carries the date it was read; the harness re-hashes 20 of those pages on a loop to catch an upstream edit. A 30-day month and flat traffic are assumed, the most generous reading. NOWNodes prices in EUR. A provider absent from a cell is not missing data: it has no plan that can serve that workload, usually a cap or a throughput ceiling rather than the price.
Allowance, not latency and not reliability. A plan that buys the most requests is not thereby the fastest or the most correct; those are measured on the per-chain RPC pages. Published allowances, human-verified against each provider's own pricing page with the date it was read. A free plan is one that costs nothing and renews, so Quicknode's one-month trial is not here. Where a provider publishes a daily cap it is multiplied by 30.
Frequently asked questions
Ankr vs OnFinality: which one is better?
Ankr and OnFinality are compared on 3 shared OpenChainBench benchmarks. OnFinality leads on Stellar Soroban RPC endpoints. See the live table on this page for every metric.
Which is faster, Ankr or OnFinality?
On the Stellar Soroban RPC endpoints benchmark, OnFinality leads at 112 ms versus Ankr at 612 ms. Live measurement is updated continuously by the OpenChainBench harness.
How is the Ankr vs OnFinality comparison measured?
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
How this pair was selected
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.