Fuse public RPC endpoints, tested
Every keyless Fuse (chain ID 122) 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. 5 of 10 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://fuse.liquify.com | 9 ms | 0 blocks | 10,000+ | recent only |
| https://rpc.fuse.io | 10 ms | 1 blocks | 10,000+ | recent only |
| https://fuse.drpc.org | 26 ms | 1 blocks | under 1,000 | recent only |
| https://fuse.api.pocket.network | 43 ms | 0 blocks | 10,000+ | recent only |
| https://rpc.swiftnodes.io/rpc/fuse (SwiftNodes, keyless: 2 req/s) | 90 ms | 1 blocks | 10,000+ | recent only |
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
rpc.swiftnodes.io/ws/fuse(SwiftNodes): first head after 168 ms - streams
fuse.api.pocket.network: first head after 3529 ms - does not stream
fuse.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
Listed but not working
fuse-public.nodies.app: no answer (HTTP 403)fuse-mainnet.chainstacklabs.com: chainId: fetch failedfuse.api.onfinality.io/public: chainId: fetch failedrpc.owlracle.info/fuse/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)lb.routeme.sh/rpc/evm/122: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Fuse endpoint, limits and status: Fuse RPC, uptime history.