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.
Cloudflare's public Ethereum gateway. Recently switched to a permissioned mode for many JSON-RPC methods, returning `-32046 Cannot fulfill request` for most endpoints.
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.
Cloudflare
Leads31 ms
Tenderly
Trails121 ms
Per chain · per region
| Chain | Provider | US-East | EU-West | Singapore | Aggregate |
|---|---|---|---|---|---|
| Ethereum | Cloudflare | 36 ms | 49 ms | 8 ms | 31 ms |
| Tenderly | 8 ms | 15 ms | 235 ms | 86 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.