PublicNode vs UnitedBloc

PublicNode leads on 0 of 1 shared benchmarks, UnitedBloc on 1. UnitedBloc wins on Fastest free Moonriver RPC, live no-key EVM endpoint latency (5 ms vs 141 ms).

Read methodology Last measured Window: rolling 24h1 shared benchmark
PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

UnitedBloc logo
UnitedBloc

UnitedBloc is a community validator and RPC node operator running public infrastructure for Moonbeam and Moonriver. Their keyless endpoint (moonriver.unitedbloc.com) supports Moonriver (chain 1285) without an API key.

Side by side measurements

Frequently asked questions

PublicNode vs UnitedBloc: which one is better?

PublicNode and UnitedBloc are compared on 1 shared OpenChainBench benchmarks. UnitedBloc leads on Fastest free Moonriver RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.

Which is faster on fastest free moonriver rpc, live no-key evm endpoint latency, PublicNode or UnitedBloc?

On the Fastest free Moonriver RPC, live no-key EVM endpoint latency benchmark, UnitedBloc leads at 5 ms versus PublicNode at 141 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the PublicNode vs UnitedBloc comparison measured?

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.

How this pair was selected

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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.