dRPC vs Thyme Gate

dRPC leads on all 3 live benchmarks. dRPC wins on Ethereum RPC endpoints (29 ms vs 83 ms), Optimism RPC endpoints (108 ms vs 111 ms), Polygon RPC endpoints (33 ms vs 93 ms). Data as of 2026-11-11 UTC.

Read methodology Last measured Window: rolling 24h3 shared benchmarks
dRPC logo
dRPC

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

Thyme Gate logo
Thyme Gate

Thyme Labs operates keyless public RPC on its own nodes with a 22-unit/s per-IP limit (one unit per call; eth_getLogs and eth_getBlockReceipts cost four), batches of up to 10 calls and no paid-provider fallback.

Side by side measurements

Optimism RPC endpoints: free public URLs by latency

RPCs

dRPC

Leads

108 ms

p99
251 ms
rank
#3
samples
4,318

Thyme Gate

Trails

111 ms

p99
168 ms
rank
#4
samples
877

Per region

RegiondRPCThyme Gate
US-East67 ms112 ms
EU-West37 ms37 ms
Singapore221 ms184 ms
RPC latency
dRPCn/aThyme Gaten/a

Frequently asked questions

dRPC vs Thyme Gate: which one is better?

dRPC and Thyme Gate are compared on 3 shared OpenChainBench benchmarks. dRPC leads on Ethereum RPC endpoints. See the live table on this page for every metric.

Which is faster, dRPC or Thyme Gate?

On the Ethereum RPC endpoints benchmark, dRPC leads at 29 ms versus Thyme Gate at 83 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the dRPC vs Thyme Gate 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.