Ankr vs thirdweb

Ankr leads on 4 of 5 shared benchmarks, thirdweb on 1. Ankr wins on Kava RPC endpoints (39 ms vs 507 ms), Flare RPC endpoints (71 ms vs 515 ms), Core Chain RPC endpoints (83 ms vs 503 ms), TAC RPC endpoints (41 ms vs 581 ms). thirdweb wins on Cheapest RPC provider, priced per workload across 19 providers ($171 vs $200). Data as of 2026-11-02 UTC.

Read methodology Last measured Window: rolling 24h5 shared benchmarks
Ankr logo
Ankr

Multi-chain RPC service covering 65+ chains on the freemium tier. One API key across chains; some networks are premium-gated.

thirdweb logo
thirdweb

ThirdWeb operates a keyless public RPC gateway at `<chainid>.rpc.thirdweb.com` covering 2000+ EVM chains via chain-id routing. Free tier is rate-limited per IP with no signup; paid tiers unlock higher throughput and dedicated endpoints. Used keyless across 13 chains on the RPC latency cluster (arbitrum, ethereum, polygon, optimism, base, bnb, avalanche, linea, worldchain, kaia, ink, opbnb + more).

Side by side measurements

Kava RPC endpoints: free public URLs by latency

RPCs

Ankr

Leads

39 ms

p99
103 ms
rank
#1
samples
4,315

thirdweb

Trails

507 ms

p99
665 ms
rank
—
samples
4,309

Per region

RegionAnkrthirdweb
US-East12 ms333 ms
EU-West96 ms579 ms
Singapore9 ms617 ms
RPC latency
Ankrn/athirdwebn/a

Flare RPC endpoints: free public URLs by latency

RPCs

Ankr

Leads

71 ms

p99
223 ms
rank
#1
samples
4,320

thirdweb

Trails

515 ms

p99
634 ms
rank
—
samples
4,313

Per region

RegionAnkrthirdweb
US-East25 ms343 ms
EU-West27 ms586 ms
Singapore159 ms614 ms
RPC latency
Ankrn/athirdwebn/a

Cheapest RPC provider, priced per workload across 19 providers

RPCs
ProviderMonthly cost, dapp mix at 10M requestsEffective cost per 1M requestsBilling units per request
Ankrprovisional$200$20200
thirdwebprovisional$171$17.101
View
Ankrn/athirdwebn/a

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.

Latest value · Monthly cost, dapp mix at 10M requestsRaw JSON

TAC RPC endpoints: free public URLs by latency

RPCs

Ankr

Leads

41 ms

p99
121 ms
rank
#1
samples
4,321

thirdweb

Trails

581 ms

p99
709 ms
rank
—
samples
4,319

Per region

RegionAnkrthirdweb
US-East79 ms404 ms
EU-West26 ms651 ms
Singapore18 ms686 ms
RPC latency
Ankrn/athirdwebn/a

Frequently asked questions

Ankr vs thirdweb: which one is better?

Ankr and thirdweb are compared on 5 shared OpenChainBench benchmarks. Ankr leads on Kava RPC endpoints. thirdweb leads on Cheapest RPC provider, priced per workload across 19 providers. See the live table on this page for every metric.

Which is faster, Ankr or thirdweb?

On the Kava RPC endpoints benchmark, Ankr leads at 39 ms versus thirdweb at 507 ms. Live measurement is updated continuously by the OpenChainBench harness.

Which is cheaper, Ankr or thirdweb?

On the Cheapest RPC provider, priced per workload across 19 providers benchmark, thirdweb leads at $171 (provisional) versus Ankr at $200 (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the Ankr vs thirdweb 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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.