Fastest free Fuse Network RPC, live no-key EVM endpoint latency
HTTP round-trip latency for the `eth_getBlockByNumber("latest", false)` method against every free, no-key public Fuse Network EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , dRPC leads rpc latency at 194 ms (p50, 24h) on Fastest free Fuse Network RPC, live no-key EVM endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/fuse-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Fuse Network is a community-owned EVM-compatible blockchain (chain 122) built around business payments and consumer DeFi, FUSE as gas token, ~5 s block cadence with AuRa-based consensus (parity-style PoA), real-world payment integrations with the Fuse Cash and Fuse Studio ecosystem. The 2026-08-04 audit confirms 3 clean keyless providers: the Fuse Foundation official endpoint (rpc.fuse.io), dRPC (fuse.drpc.org), and Thirdweb (122.rpc.thirdweb.com). Excluded: Ankr (no Fuse route), Alchemy (no Fuse support), QuickNode (key required).
Methodology
Per-chain member of the RPC latency cluster, extended to Fuse Network. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber("latest", false)`) against every no-key public Fuse Network endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Fuse Network-scaled staleness gap (20 blocks at Fuse Network's ~5 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Fuse Network-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Fuse Network RPC right now?
dRPC currently leads at 194 ms (`eth_getBlockByNumber("latest", false)` p50 over the last 24h), measured against 3 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples. Use the region tabs to see the leader from the origin closest to your deployment.
Which Fuse Network RPCs work without an API key?
3 endpoints sustain continuous keyless probing: Fuse Foundation (https://rpc.fuse.io), dRPC (https://fuse.drpc.org), and Thirdweb (https://122.rpc.thirdweb.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion.
Does the fastest Fuse Network RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate.
How is Fuse Network RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities