Aurora public RPC endpoints, tested
Every keyless Aurora (chain ID 1313161554) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: 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 8 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/1313161554 | 56 ms | 0 blocks | under 1,000 | none |
| https://mainnet.aurora.dev | 43 ms | 44 blocks | 10,000+ | archive (1M+) |
| https://aurora.drpc.org | 43 ms | 65 blocks | under 1,000 | archive (1M+) |
| https://aurora-mainnet.gateway.tatum.io | 100 ms | 39 blocks | under 1,000 | none |
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
aurora.drpc.org: subscribe rejected: method is not available - does not stream
rpc.swiftnodes.io/ws/aurora(SwiftNodes): connection failed (connect)
Listed but not working
public.1rpc.io/aurora: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unendpoints.omniatech.io/v1/aurora/mainnet/public: no answer (HTTP 521)rpc.owlracle.info/aurora/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)rpc.swiftnodes.io/rpc/aurora: no answer (HTTP 502)
Test any endpoint yourself with the RPC tester. Our Aurora endpoint, limits and status: Aurora RPC, uptime history.