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
104 ms
median 2 ms · slowest 10% 104 ms · best 0 ms · 71.9% answered · at the chain head
Robinhood official
106 ms
median 91 ms · slowest 10% 106 ms · best 71 ms · 0.7% answered · 7 blocks behind
PublicNode
108 ms
median 94 ms · slowest 10% 108 ms · best 82 ms · 38.3% answered · at the chain head
BlockMachine
509 ms
median 179 ms · slowest 10% 509 ms · best 165 ms · 0.6% 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 71.9% current
Robinhood official no no 0.7% −7
PublicNode no no 38.3% current
BlockMachine no no 0.6% 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