Side by side OpenChainBench measurements. Identical layout, no editorial verdict, the live data leads. Each panel surfaces the aggregate plus the chain and region breakdowns when the underlying bench exposes them, straight from the Prometheus queries that drive the parent benchmark pages.
Merkle exposes per-chain RPC subdomains (`eth.merkle.io`, `base.merkle.io`, `bsc.merkle.io`). Stable on Base + BSC for no-key benchmarking; Ethereum is fronted by an aggressive Cloudflare bot filter (20-minute lockout after a single request) so we exclude it from the leaderboard.
Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.
Merkle
Trails117 ms
PublicNode
Leads39 ms
Per chain · per region
| Chain | Provider | US-East | EU-West | Singapore | Aggregate |
|---|---|---|---|---|---|
| Base | Merkle | 10 ms | 93 ms | 248 ms | 117 ms |
| PublicNode | 12 ms | 19 ms | 80 ms | 37 ms | |
| BNB Chain | Merkle | 9 ms | 95 ms | 246 ms | 117 ms |
| PublicNode | 13 ms | 21 ms | 176 ms | 70 ms |
A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.