TAC RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public TAC EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , TAC has the lowest median latency of the 3 free public TAC RPC endpoints measured, 44 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/tac-rpc. 3 public endpoints, no key: rpc.tac.build, rpc.ankr.com, tac.drpc.org. 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 →
TAC is an EVM L1 (chain 239) that also runs a Cosmos consensus layer. The endpoints on this page are the EVM JSON-RPC surface only: the TAC official RPC (rpc.tac.build), Ankr (rpc.ankr.com/tac), dRPC (tac.drpc.org) and Thirdweb (239.rpc.thirdweb.com), all four returning chain id 0xef on the 2026-10-07 sweep. Ankr appearing keyless is notable: it key-gates most chains we measure, and TAC is one of the few where its public route answers.
Methodology
TAC: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. TAC leads at 44 ms; the chain-official endpoint measures 44 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public TAC endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a TAC-scaled staleness gap (20 blocks at TAC's ~3 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the TAC-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public TAC RPC endpoints ranked by p50 latency (24h, 3 regions)
Public TAC RPC endpoints measured
The 3 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.
TAChttps://rpc.tac.build44 ms100.0%
Ankrhttps://rpc.ankr.com/tac55 ms100.0%
dRPChttps://tac.drpc.org122 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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://239.rpc.thirdweb.com0.8 % success over 24 h
Frequently asked
Which TAC RPCs work without an API key?
4 endpoints are probed on this chain: TAC (rpc.tac.build), Ankr (rpc.ankr.com/tac), dRPC (tac.drpc.org), Thirdweb (239.rpc.thirdweb.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` call returning a parsable response before inclusion.
How is TAC RPC latency measured here, technically?
One identical `eth_getBlockByNumber` call every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
TAC has a Cosmos layer too, so why only the EVM endpoints here?
Because they are different probes answering different questions. The EVM JSON-RPC surface takes `eth_getBlockByNumber`; a Cosmos consensus RPC takes Tendermint `status`. Mixing the two in one latency column would compare a call that reads an EVM block with a call that reads consensus state, which is not the same work. This page is the EVM surface, which is what a wallet or a contract call uses.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities