Monad public RPC endpoints, tested
Every keyless Monad (chain ID 143) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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. 9 of 11 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://gm.monad.at.htw.tech | 85 ms | 0 blocks | 1,000 | archive (1M+) |
| https://rpc.monad.xyz | 12 ms | 42 blocks | under 1,000 | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/143 | 19 ms | 21 blocks | under 1,000 | recent only |
| https://monad-mainnet.drpc.org | 72 ms | 35 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/monad (SwiftNodes, keyless: 2 req/s) | 88 ms | 24 blocks | under 1,000 | archive (1M+) |
| https://monad-rpc.huginn.tech | 92 ms | 8 blocks | 1,000 | archive (1M+) |
| https://infra.originstake.com/monad/evm | 138 ms | 24 blocks | 10,000+ | archive (1M+) |
| https://monad-mainnet.rpc.sentio.xyz | 170 ms | 21 blocks | 10,000+ | archive (1M+) |
| https://monad-mainnet.api.onfinality.io/public | 310 ms | 7 blocks | 1,000 | none |
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
wss.monad-rpc.huginn.tech: first head after 126 ms - does not stream
gm.monad.at.htw.tech: chainId: Method not found - does not stream
rpc.swiftnodes.io/ws/monad(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
monad-mainnet-rpc.spidernode.net: no answer (HTTP 503)monad-mainnet.gateway.tatum.io: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Monad endpoint, limits and status: Monad RPC, uptime history.