World Chain public RPC endpoints, tested
Every keyless World Chain (chain ID 480) 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. 4 of 6 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/480 | 18 ms | 1 blocks | under 1,000 | none |
| https://worldchain.drpc.org | 36 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/worldchain (SwiftNodes, keyless: 2 req/s) | 50 ms | 3 blocks | under 1,000 | archive (1M+) |
| https://sparkling-autumn-dinghy.worldchain-mainnet.quiknode.pro | 98 ms | 1 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
worldchain.drpc.org: first head after 1466 ms - does not stream
worldchain-mainnet.gateway.tenderly.co: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/worldchain(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
worldchain-mainnet.gateway.tenderly.co: chainId: rate limited480.rpc.thirdweb.com: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our World Chain endpoint, limits and status: World Chain RPC, uptime history.