rpc.ordofi.network/compare · chain 4663

Every Robinhood Chain RPC, measured.

Latency, chain-head freshness, availability and capabilities for every public endpoint on this chain, ours included, on the same axes, from the same place, with the method published below. Re-run it yourself and you should get this.

updated 2 min ago · 287 cycles over the last 24h · measured from the Ordo RPC host in the United States

Response time

One eth_blockNumber call. The solid bar is the median; the pale extension is the slowest 10%, which is the part you actually notice. Shorter is better.

Ordo
169 ms
median 18 ms · slowest 10% 169 ms · best 8 ms · 100.0% answered · 1 block behind
Robinhood official
1936 ms
median 88 ms · slowest 10% 1936 ms · best 68 ms · 1.0% answered · 6 blocks behind
PublicNode
183 ms
median 93 ms · slowest 10% 183 ms · best 81 ms · 95.4% answered · at the chain head
BlockMachine
195 ms
median 168 ms · slowest 10% 195 ms · best 155 ms · 7.4% answered · at the chain head
ArrowRPC
no response
no successful call in 24h

What each one can do

Speed is not the only thing that matters, and we are not best at all of it.

EndpointCall tracingArchive stateAnsweredHead
Ordo ? no 100.0% −1
Robinhood official ? no 1.0% −6
PublicNode ? no 95.4% current
BlockMachine ? no 7.4% current
ArrowRPC ? no
Not on this chart: Private Send, pre-send simulation and the approval-drain guard are Ordo product features. They are not latency, they are not independently measured on the other endpoints, and they are not a reason this table would put us first.

Method

So that this is checkable rather than claimed.

curl -s https://rpc.ordofi.network \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

Machine-readable: /compare.json · /llms.txt · attested volume: dune.com/jemordo/ordofi-rpc