Playnance public RPC endpoints, tested
Every keyless Playnance (chain ID 1829) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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 3 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.playblock.io | 23 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/playnance (SwiftNodes, keyless: 2 req/s) | 73 ms | 19 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
ws.playblock.io: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/playnance(SwiftNodes): gateway: WebSocket not available for chain: playnance
Listed but not working
lb.routeme.sh/rpc/evm/1829: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Playnance endpoint, limits and status: Playnance RPC, uptime history.