Fraxtal RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Fraxtal RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Fraxtal has the lowest median latency of the 4 free public Fraxtal RPC endpoints measured, 28 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/fraxtal-rpc. Chain ID 252. 4 public endpoints, no key: rpc.frax.com, fraxtal-rpc.publicnode.com, gateway.tenderly.co, fraxtal.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 →
Fraxtal, Frax's OP Stack rollup, fields 4 no-key providers: PublicNode, dRPC, Tenderly and Frax's own `rpc.frax.com`. The 4-provider floor it just clears is the cluster's deliberate admission bar, chains that could not field 4 keyless endpoints (Mode, Zora, Abstract) were left out of the expansion entirely rather than shipped as two-row leaderboards. Identical probes every 60 seconds, three regions.
Methodology
Fraxtal: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Fraxtal leads at 28 ms; the chain-official endpoint measures 28 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Fraxtal 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 Fraxtal-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Fraxtal RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Fraxtal | 28 ms | 43 ms | 205 ms | 100.00% |
| 2 | PublicNode | 75 ms | 90 ms | 320 ms | 100.00% |
| 3 | Tenderly | 106 ms | 112 ms | 120 ms | 100.00% |
| 4 | dRPC | 117 ms | 150 ms | 218 ms | 99.65% |
Public Fraxtal RPC endpoints measured
Chain ID 252, currency frxETH. 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.
Fraxtalhttps://rpc.frax.com28 ms100.0%
PublicNodehttps://fraxtal-rpc.publicnode.com75 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/fraxtal106 ms100.0%
dRPChttps://fraxtal.drpc.org117 ms99.7%
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 Fraxtal 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.
Why are chains like Mode, Zora or Sei missing from this cluster?
Each failed a specific admission test. Mode, Zora and Abstract could not field 4 keyless providers, below the bar for a meaningful leaderboard. Sei was excluded because dRPC caches `eth_getBlockByNumber` there, poisoning the exact probe we rank on. opBNB fell out because 1RPC returns 429 at our 60-second cadence, leaving only 4 solid providers. The cluster only ships chains where the comparison is honest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities