PublicNode vs Thyme Gate

PublicNode leads on 3 of 4 shared benchmarks, Thyme Gate on 1. PublicNode wins on Optimism RPC endpoints (84 ms vs 111 ms), BNB Chain RPC endpoints (82 ms vs 110 ms), Polygon RPC endpoints (83 ms vs 93 ms). Thyme Gate wins on Ethereum RPC endpoints (83 ms vs 85 ms). Data as of 2026-11-11 UTC.

Read methodology Last measured Window: rolling 24h4 shared benchmarks
PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

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

PublicNode

Leads

84 ms

p99
243 ms
rank
#1
samples
4,318

Thyme Gate

Trails

111 ms

p99
172 ms
rank
#4
samples
712

Per region

RegionPublicNodeThyme Gate
US-East46 ms112 ms
EU-West28 ms37 ms
Singapore177 ms184 ms
RPC latency
PublicNoden/aThyme Gaten/a

Frequently asked questions

PublicNode vs Thyme Gate: which one is better?

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

Which is faster on rpc latency, PublicNode or Thyme Gate?

On the Optimism RPC endpoints benchmark, PublicNode leads at 84 ms versus Thyme Gate at 111 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the PublicNode 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.