Fastest free BOB RPC, live no-key EVM endpoint latency
RPCsBOB
No data in window
Tenderly Gateway
No data in window
Per region
| Region | BOB | Tenderly Gateway |
|---|---|---|
| US-East | 175 ms | 326 ms |
| EU-West | 176 ms | 328 ms |
| Singapore | 174 ms | 327 ms |
BOB vs Tenderly Gateway
BOB leads on 1 of 1 shared benchmarks, Tenderly Gateway on 0. BOB wins on Fastest free BOB RPC, live no-key EVM endpoint latency (175 ms vs 327 ms).
BOB
BOB's official public RPC (rpc.gobob.xyz) for the Build on Bitcoin OP Stack hybrid L2 bridging BTC and ETH with native BTC collateral support (chain 60808). Standard EVM JSON-RPC, keyless, rate-limited per IP.
Tenderly Gateway
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.
Side by side measurements
Frequently asked questions
BOB vs Tenderly Gateway: which one is better?
BOB and Tenderly Gateway are compared on 1 shared OpenChainBench benchmarks. BOB leads on Fastest free BOB RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
Which is faster on fastest free bob rpc, live no-key evm endpoint latency, BOB or Tenderly Gateway?
On the Fastest free BOB RPC, live no-key EVM endpoint latency benchmark, BOB leads at 175 ms versus Tenderly Gateway at 327 ms. Live measurement is updated continuously by the OpenChainBench harness.
How is the BOB vs Tenderly Gateway 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
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.