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.
Tenderly's public gateway exposes a no-key JSON-RPC endpoint per chain at `gateway.tenderly.co/public/<slug>`. Covers Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, Linea, Scroll and Mantle. The same Tenderly platform behind the keyed Web3 dev suite.
Merkle
Leads117 ms
Tenderly
Trails121 ms
Per chain · per region
| Chain | Provider | US-East | EU-West | Singapore | Aggregate |
|---|---|---|---|---|---|
| Base | Merkle | 10 ms | 93 ms | 248 ms | 117 ms |
| Tenderly | 9 ms | 18 ms | 238 ms | 88 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.