Plasma public RPC endpoints, tested
Every keyless Plasma (chain ID 9745) 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. 3 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/9745 | 22 ms | 0 blocks | under 1,000 | none |
| https://rpc.plasma.to | 7 ms | 22 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/plasma (SwiftNodes, keyless: 2 req/s) | 146 ms | 8 blocks | 10,000+ | archive (1M+) |
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/plasma(SwiftNodes): first head after 149 ms - does not stream
plasma.drpc.org: chainId: chain is not available on free plan, please upgrade to paid plan
Listed but not working
plasma.drpc.org: chainId: chain is not available on free plan, please upgrade to paid planrpc.nodeflare.app/plasma/public: chainId: rate limitedplasma-mainnet.gateway.tatum.io: chainId: rate limitedplasma.api.onfinality.io/public: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Plasma endpoint, limits and status: Plasma RPC, uptime history.