Fuse Network RPC endpoints: free public URLs by latency

Fuse Network: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. dRPC leads at 353 ms; the chain-official endpoint measures 460 ms. 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, 2 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.

• ·Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
• ·Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest", false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
• ·Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Fuse Network-scoped view of the same harness, with the same exclusion rules.
• ·Chain scope: every query on this page is pinned to `chain="fuse"`. Provider coverage: 2 no-key endpoints.