ITRocket vs Polkachu

Split decision: ITRocket leads on XRPL EVM RPC endpoints (157 ms vs 165 ms); Polkachu leads on MANTRA RPC endpoints (117 ms vs 135 ms). Data as of 2026-10-22 UTC.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
ITRocket logo
ITRocket

ITRocket community validator and public RPC operator. Provides keyless Tendermint RPC endpoints for multiple Cosmos SDK chains.

Polkachu logo
Polkachu

Community-run Cosmos validator and public RPC network. Operates no-key Tendermint RPC endpoints across 40+ Cosmos SDK chains (osmosis-rpc.polkachu.com, cosmos-rpc.polkachu.com, etc.) with archive support on a paid tier.

Side by side measurements

MANTRA RPC endpoints: free public URLs by latency

RPCs

ITRocket

Trails

135 ms

p99
528 ms
rank
#2
samples
4,326

Polkachu

Leads

117 ms

p99
537 ms
rank
#1
samples
4,322

Per region

RegionITRocketPolkachu
US-East144 ms126 ms
EU-West48 ms31 ms
Singapore213 ms194 ms
RPC latency
ITRocketn/aPolkachun/a

XRPL EVM RPC endpoints: free public URLs by latency

RPCs

ITRocket

Leads

157 ms

p99
699 ms
rank
#3
samples
4,326

Polkachu

Trails

165 ms

p99
544 ms
rank
#4
samples
4,329

Per region

RegionITRocketPolkachu
US-East192 ms259 ms
EU-West57 ms34 ms
Singapore223 ms201 ms
RPC latency
ITRocketn/aPolkachun/a

Frequently asked questions

ITRocket vs Polkachu: which one is better?

ITRocket and Polkachu are compared on 2 shared OpenChainBench benchmarks. ITRocket leads on XRPL EVM RPC endpoints. Polkachu leads on MANTRA RPC endpoints. See the live table on this page for every metric.

Which is faster on rpc latency, ITRocket or Polkachu?

On the XRPL EVM RPC endpoints benchmark, ITRocket leads at 157 ms versus Polkachu at 165 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the ITRocket vs Polkachu 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.