Fetch.ai vs PublicNode

PublicNode leads on the only live benchmark. PublicNode wins on Fastest free Fetch.ai RPC, live no-key endpoint latency (144 ms vs 338 ms).

Read methodology Last measured Window: rolling 24h1 shared benchmark
Fetch.ai logo
Fetch.ai

Fetch.ai official public Tendermint RPC node for the FetchHub-4 mainnet. Keyless endpoint maintained by the Fetch.ai / ASI Alliance team.

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.

Side by side measurements

Frequently asked questions

Fetch.ai vs PublicNode: which one is better?

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

Which is faster, Fetch.ai or PublicNode?

On the Fastest free Fetch.ai RPC, live no-key endpoint latency benchmark, PublicNode leads at 144 ms versus Fetch.ai at 338 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the Fetch.ai vs PublicNode 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

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

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