Fastest free BOB RPC, live no-key EVM endpoint latency
RPCsBOB
Leads175 ms
- p99
- 975 ms
- rank
- #1
- samples
- 525
Thirdweb
No data in window
Per region
| Region | BOB | Thirdweb |
|---|---|---|
| US-East | 175 ms | 566 ms |
| EU-West | 176 ms | 567 ms |
| Singapore | 174 ms | 591 ms |
BOB leads on 1 of 1 shared benchmarks, Thirdweb on 0. BOB wins on Fastest free BOB RPC, live no-key EVM endpoint latency (175 ms vs 575 ms).
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.
ThirdWeb operates a keyless public RPC gateway at `<chainid>.rpc.thirdweb.com` covering 2000+ EVM chains via chain-id routing. Free tier is rate-limited per IP with no signup; paid tiers unlock higher throughput and dedicated endpoints. Used keyless across 13 chains on the RPC latency cluster (arbitrum, ethereum, polygon, optimism, base, bnb, avalanche, linea, worldchain, kaia, ink, opbnb + more).
BOB
Leads175 ms
Thirdweb
No data in window
Per region
| Region | BOB | Thirdweb |
|---|---|---|
| US-East | 175 ms | 566 ms |
| EU-West | 176 ms | 567 ms |
| Singapore | 174 ms | 591 ms |
BOB and Thirdweb 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.
On the Fastest free BOB RPC, live no-key EVM endpoint latency benchmark, BOB leads at 175 ms versus Thirdweb at 575 ms. Live measurement is updated continuously by the OpenChainBench harness.
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.
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.