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 4 min ago · 288 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
505 ms
median 35 ms · slowest 10% 505 ms · best 9 ms · 47.8% answered · at the chain head
Robinhood official
108 ms
median 79 ms · slowest 10% 108 ms · best 64 ms · 0.3% answered · 4 blocks behind
PublicNode
106 ms
median 92 ms · slowest 10% 106 ms · best 74 ms · 26.4% answered · at the chain head
BlockMachine
182 ms
median 174 ms · slowest 10% 182 ms · best 157 ms · 0.5% 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 no 47.8% current
Robinhood official no no 0.3% −4
PublicNode no no 26.4% current
BlockMachine no no 0.5% current
ArrowRPC no 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