Base public RPC endpoints, tested

Every keyless Base (chain ID 8453) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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. 16 of 37 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://base.rpc.blxrbdn.com99 ms1 blocks10,000+archive (1M+)
https://base.rpc.sentio.xyz168 ms0 blocks10,000+archive (1M+)
https://base.api.pocket.network297 ms1 blocks10,000+archive (1M+)
https://rpc.swiftnodes.io/rpc/base (SwiftNodes, keyless: 2 req/s)311 ms2 blocks10,000+none
https://api.zan.top/base-mainnet14 ms5 blocksunder 1,000archive (1M+)
https://base-rpc.publicnode.com19 ms13 blocks10,000+none
https://base.drpc.org24 ms6 blocksunder 1,000archive (1M+)
https://base.public.blockpi.network/v1/rpc/public61 ms8 blocks1,000archive (1M+)
https://base-public.nodies.app88 ms7 blocksunder 1,000archive (1M+)
https://rpc.baseazul.dev99 ms12 blocks1,000archive (1M+)
https://base.meowrpc.com100 ms5 blocksunder 1,000archive (1M+)
https://base-mainnet.public.blastapi.io110 ms7 blocksunder 1,000archive (1M+)
https://developer-access-mainnet.base.org114 ms14 blocks1,000archive (1M+)
https://mainnet.base.org120 ms15 blocks1,000archive (1M+)
https://xrpc.cl/base1302 ms10 blocks1,000archive (1M+)
https://public.1rpc.io/base2066 ms4 blocksunder 1,000recent only

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 base-rpc.publicnode.com: first head after 443 ms
  • streams base.drpc.org: first head after 727 ms
  • streams rpc.swiftnodes.io/ws/base (SwiftNodes): first head after 844 ms
  • streams base.api.pocket.network: first head after 915 ms
  • does not stream base.gateway.tenderly.co: connection failed (connect)
  • does not stream base.callstaticrpc.com: connection failed (connect)

Listed but not working

  • rpcfree.com/base-rpc: no answer (HTTP 200)
  • rpc.satelink.network/rpc/base: chainId: Payment required
  • base.gateway.tenderly.co: chainId: rate limited
  • base-mainnet.diamondswap.org/rpc: chainId: fetch failed
  • lb.routeme.sh/rpc/evm/8453: chainId: rate limited
  • rpc.nodeflare.app/base/public: chainId: rate limited
  • li-fi-base.intustechno.workers.dev/rpc: chainId: rate limited
  • rpc.notadegen.com/base: chainId: fetch failed
  • public.stackup.sh/api/v1/node/base-mainnet: chainId: fetch failed
  • endpoints.omniatech.io/v1/base/mainnet/public: no answer (HTTP 521)
  • base.lava.build: chainId: This endpoint has been discontinued.
  • rpc.owlracle.info/base/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
  • base.therpc.io: chainId: fetch failed
  • rpc.poolz.finance/base: chainId: fetch failed
  • gateway.tenderly.co/public/base: chainId: rate limited
  • base.api.onfinality.io/public: chainId: rate limited
  • rpcbase.hairylabs.io/rpc: chainId: fetch failed
  • base-mainnet.gateway.tatum.io: chainId: rate limited
  • base-rpc.keccak.io: chainId: auth error - api key required. This method needs an account — register free and get an API
  • rpc.numa.network/base: chainId: timeout
  • api-base-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited

Test any endpoint yourself with the RPC tester. Our Base endpoint, limits and status: Base RPC, uptime history.