Taiko public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc.ankr.com/taiko13 ms2 blocks10,000+archive (1M+)
https://taiko-rpc.publicnode.com19 ms3 blocks10,000+archive (1M+)
https://taiko.drpc.org33 ms1 blocksunder 1,000archive (1M+)
https://taiko.api.pocket.network33 ms0 blocks10,000+archive (1M+)
https://rpc.swiftnodes.io/rpc/taiko (SwiftNodes, keyless: 2 req/s)48 ms3 blocks10,000+archive (1M+)
https://rpc.mainnet.taiko.xyz119 ms3 blocks10,000+archive (1M+)
https://rpc.taiko.xyz120 ms2 blocks10,000+archive (1M+)
https://taiko.rpc.sentio.xyz167 ms0 blocks10,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 taiko.drpc.org: first head after 290 ms
  • streams taiko-rpc.publicnode.com: first head after 929 ms
  • does not stream taiko-mainnet.4everland.org/ws/v1/37fa9972c1b1cd5fab542c7bdd4cde2f: connection failed (connect)
  • does not stream rpc.swiftnodes.io/ws/taiko (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • rpc.taiko.tools: chainId: fetch failed
  • taiko-mainnet.4everland.org/v1/37fa9972c1b1cd5fab542c7bdd4cde2f: chainId: Invalid API Key.
  • taiko-mainnet.rpc.porters.xyz/taiko-public: chainId: fetch failed
  • taiko-json-rpc.stakely.io: chainId: fetch failed
  • taiko.therpc.io: chainId: fetch failed
  • lb.routeme.sh/rpc/evm/167000: chainId: rate limited
  • taiko-mainnet.gateway.tenderly.co: chainId: rate limited

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