1RPC vs dRPC

1RPC leads on 2 of 3 shared benchmarks, dRPC on 1. 1RPC wins on Mode RPC endpoints (209 ms vs 452 ms), Manta Pacific RPC endpoints (190 ms vs 447 ms). dRPC wins on OKTC RPC endpoints (353 ms vs 385 ms). Data as of 2026-10-05 UTC.

Read methodology Last measured Window: rolling 24h4 shared benchmarks, 3 measured on both sides
1RPC logo
1RPC

Privacy-preserving public RPC by Automata Network. Strips client metadata before forwarding to upstream node operators; load-balanced across providers.

dRPC logo
dRPC

Decentralized RPC mesh routing requests across third-party node providers with consensus checks. Free public tier plus higher-tier authenticated access.

Side by side measurements

Mode RPC endpoints: free public URLs by latency

RPCs

1RPC

Leads

209 ms

p99
7.20 s
rank
—
samples
4,293

dRPC

Trails

452 ms

p99
889 ms
rank
#2
samples
4,313

Per region

Region1RPCdRPC
US-East102 ms414 ms
EU-West174 ms358 ms
Singapore352 ms583 ms
RPC latency
1RPCn/adRPCn/a

OKTC RPC endpoints: free public URLs by latency

RPCs

1RPC

Trails

385 ms

p99
7.22 s
rank
—
samples
4,291

dRPC

Leads

353 ms

p99
659 ms
rank
#2
samples
4,299

Per region

Region1RPCdRPC
US-East285 ms349 ms
EU-West350 ms320 ms
Singapore522 ms394 ms
RPC latency
1RPCn/adRPCn/a

Frequently asked questions

1RPC vs dRPC: which one is better?

1RPC and dRPC are compared on 4 shared OpenChainBench benchmarks. 1RPC leads on Mode RPC endpoints. dRPC leads on OKTC RPC endpoints. See the live table on this page for every metric.

Which is faster on rpc latency, 1RPC or dRPC?

On the Mode RPC endpoints benchmark, 1RPC leads at 209 ms versus dRPC at 452 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the 1RPC vs dRPC 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.