Plasma public RPC endpoints, tested
Every keyless Plasma (chain ID 9745) 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. 2 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.plasma.to | 5 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/plasma (SwiftNodes, keyless: 2 req/s) | 34 ms | 5 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
- does not stream
plasma.drpc.org: chainId: chain is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/plasma(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.nodeflare.app/plasma/public: chainId: unknown_chainplasma.drpc.org: chainId: chain is not available on free plan, please upgrade to paid planlb.routeme.sh/rpc/evm/9745: 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.