Taiko RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Taiko RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 4 free public Taiko RPC endpoints measured, 73 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/taiko-rpc. Chain ID 167000. 4 public endpoints, no key: taiko-rpc.publicnode.com, rpc.taiko.xyz, taiko.drpc.org, gateway.tenderly.co. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Taiko, the based rollup where Ethereum validators sequence L2 blocks, fields 4 no-key providers. Our verification sweep caught one routing quirk worth encoding: Tenderly serves the chain only at the `taiko-mainnet` gateway slug, the plain `/taiko` path 404s. Probes run every 60 seconds from us-east, eu-west and Singapore with stale-head detection against the cross-provider tip.
Methodology
Taiko: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 73 ms; the chain-official endpoint measures 128 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Taiko endpoint that sustains continuous probing, 4 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Taiko-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Taiko RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 73 ms | 87 ms | 230 ms | 99.98% |
| 2 | Taiko | 128 ms | 141 ms | 491 ms | 99.95% |
| 3 | dRPC | 143 ms | 191 ms | 355 ms | 99.47% |
| 4 | Tenderly | 154 ms | 161 ms | 168 ms | 100.00% |
Public Taiko RPC endpoints measured
Chain ID 167000, currency ETH. The 4 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
PublicNodehttps://taiko-rpc.publicnode.com73 ms100.0%
Taikohttps://rpc.taiko.xyz128 ms100.0%
dRPChttps://taiko.drpc.org143 ms99.5%
Tenderlyhttps://gateway.tenderly.co/public/taiko-mainnet154 ms100.0%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which Taiko RPCs work without an API key?
The 4 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Which free Taiko RPC should production traffic use?
Start from PublicNode (73 ms on the 3-region average) and pair it with the runner-up as fallback; in a 4-provider field a single degradation reshuffles the board. If you configure Tenderly manually, note its gateway path is `taiko-mainnet`, the intuitive `/taiko` path 404s, a detail our probes encode but provider directories rarely do.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities