MegaETH public RPC endpoints, tested
Every keyless MegaETH (chain ID 4326) 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. 5 of 6 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://megaeth.drpc.org | 21 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://megaeth.rpc.sentio.xyz | 167 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc-megaeth-mainnet.globalstake.io | 254 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://mainnet.megaeth.com/rpc | 18 ms | 6 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/megaeth (SwiftNodes, keyless: 2 req/s) | 56 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
- streams
mainnet.megaeth.com/ws: first head after 280 ms - streams
megaeth.drpc.org: first head after 584 ms - does not stream
rpc.swiftnodes.io/ws/megaeth(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
lb.routeme.sh/rpc/evm/4326: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our MegaETH endpoint, limits and status: MegaETH RPC, uptime history.