Base public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://api-base-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c243 ms0 blocksunder 1,000none
https://api.zan.top/base-mainnet13 ms106 blocksunder 1,000archive (1M+)
https://api.blockvectra.com/v1/base_mainnet/public20 ms145 blocksunder 1,000recent only
https://rpc.swiftnodes.io/rpc/base (SwiftNodes, keyless: 2 req/s)23 ms53 blocksunder 1,000recent only
https://base-rpc.blockreq.com/v1/rpc/public27 ms170 blocks1,000recent only
https://base-rpc.publicnode.com28 ms186 blocks10,000+archive (1M+)
https://base-mainnet.gateway.tatum.io29 ms108 blocksunder 1,000none
https://rpc-base.blockmachine.io31 ms64 blocksunder 1,000none
https://rpc.degenprotocol.io/base35 ms81 blocks1,000archive (1M+)
https://base.daybreak-rpc.network38 ms168 blocks1,000recent only
https://base.api.pocket.network40 ms94 blocks10,000+archive (1M+)
https://base.public.blockpi.network/v1/rpc/public46 ms150 blocks1,000archive (1M+)
https://mainnet.base.org89 ms205 blocksunder 1,000archive (1M+)
https://base.rpc.blxrbdn.com99 ms85 blocks10,000+archive (1M+)
https://rpc.baseazul.dev100 ms169 blocks1,000archive (1M+)
https://base-mainnet.public.blastapi.io105 ms113 blocksunder 1,000archive (1M+)
https://base.api.onfinality.io/public106 ms87 blocksunder 1,000recent only
https://base-public.nodies.app112 ms147 blocksunder 1,000archive (1M+)
https://base.rpc.sentio.xyz164 ms79 blocksunder 1,000archive (1M+)
https://base.meowrpc.com188 ms127 blocksunder 1,000archive (1M+)
https://xrpc.cl/base265 ms167 blocksunder 1,000none

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.api.pocket.network: first head after 18 ms
  • streams base-rpc.publicnode.com: first head after 54 ms
  • does not stream base.gateway.tenderly.co: connection failed (connect)
  • does not stream base.drpc.org: chainId: You reached Public endpoint rate limit, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/base (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • developer-access-mainnet.base.org: chainId: fetch failed
  • rpcfree.com/base-rpc: no answer (HTTP 200)
  • rpc.satelink.network/rpc/base: no answer (HTTP 404)
  • rpc.hostdefi.com/api/rpc/base: no answer (HTTP 403)
  • li-fi-base.intustechno.workers.dev/rpc: wrong chain (1)
  • base.gateway.tenderly.co: chainId: rate limited
  • public.1rpc.io/base: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
  • lb.routeme.sh/rpc/evm/8453: chainId: rate limited
  • rpc.nodeflare.app/base/public: chainId: rate limited
  • rpc.owlracle.info/base/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
  • gateway.tenderly.co/public/base: chainId: rate limited
  • base.drpc.org: chainId: rate limited
  • rpc.driftguard.live/base: no answer (HTTP 502)
  • rpc.numa.network/base: chainId: timeout

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