Robinhood Chain public RPC endpoints, tested

Every keyless Robinhood Chain (chain ID 4663) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 9 of 11 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://rpc.nodeflare.app/robinhood/public	107 ms	0 blocks	under 1,000	recent only
https://robinhood-rpc.publicnode.com	20 ms	244 blocks	under 1,000	none
https://rpc.ordofi.network	23 ms	231 blocks	1,000	archive (1M+)
https://robinhood.drpc.org	33 ms	222 blocks	under 1,000	archive (1M+)
https://rpc-robinhood.blockmachine.io	57 ms	182 blocks	1,000	archive (1M+)
https://robinhood.api.pocket.network	63 ms	212 blocks	1,000	recent only
https://robinhood.rpc.blxrbdn.com	101 ms	214 blocks	under 1,000	none
https://rpc.mainnet.chain.robinhood.com	121 ms	259 blocks	10,000+	recent only
https://rpc.swiftnodes.io/rpc/robinhood (SwiftNodes, keyless: 2 req/s)	333 ms	27 blocks	10,000+	archive (1M+)

Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.

WebSocket endpoints

streams robinhood.api.pocket.network: first head after 8 ms
streams robinhood-rpc.publicnode.com: first head after 14 ms
streams robinhood.drpc.org: first head after 127 ms
streams rpc.swiftnodes.io/ws/robinhood (SwiftNodes): first head after 133 ms
streams rpc.ordofi.network: first head after 157 ms

Listed but not working

rpc.arrowrpc.com: no answer (HTTP 530)
lb.routeme.sh/rpc/evm/4663: eth_blockNumber failed

Test any endpoint yourself with the RPC tester. Our Robinhood Chain endpoint, limits and status: Robinhood Chain RPC, uptime history.