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 5 free public Fraxtal RPC endpoints measured, 34 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/fraxtal-rpc. Chain ID 252. 5 public endpoints, no key: rpc.frax.com, fraxtal-rpc.publicnode.com, gateway.tenderly.co, api.blockvectra.com, 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 5 no-key providers: PublicNode, dRPC, Tenderly and Frax's own `rpc.frax.com`. The 5-provider floor it just clears is the cluster's deliberate admission bar, chains that could not field 5 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: 5 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Fraxtal leads at 34 ms; the chain-official endpoint measures 34 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, 5 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.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
- Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Fraxtal-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain="fraxtal". Provider coverage: 5 no-key public-read endpoints live today, each listed with its URL in the endpoints table on this page. Exclusions follow the cluster-wide rules documented on the parent benchmark.
Results: 5 free public Fraxtal RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | FraxtalFrax-operated public RPC, Fraxtal mainnet only | 34 ms | 71 ms | 156 ms | 100.00% (n=4321) |
| 2 | PublicNodeAllnodes-operated, 70+ chains, archive on most | 80 ms | 96 ms | 213 ms | 99.98% (n=4320) |
| 3 | TenderlyMulti-chain public gateway, no key | 97 ms | 111 ms | 120 ms | 100.00% (n=4321) |
| 4 | BlockVectraBlockVectra keyless public Fraxtal endpoint (3 req/s per IP, 1,000-block history window) | 113 ms | 137 ms | 331 ms | 99.98% (n=4320) |
| 5 | dRPCDecentralized RPC mesh, consensus-checked | 131 ms | 185 ms | 240 ms | 99.61% (n=4319) |
Public Fraxtal RPC endpoints measured
Chain ID 252, currency FRAX. The 5 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.com34 ms100.0%
PublicNodehttps://fraxtal-rpc.publicnode.com80 ms100.0%Tenderly
https://gateway.tenderly.co/public/fraxtal97 ms100.0%BlockVectra
https://api.blockvectra.com/v1/fraxtal_mainnet/public113 ms100.0%
dRPChttps://fraxtal.drpc.org131 ms99.6%
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 5 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 5 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 5 solid providers. The cluster only ships chains where the comparison is honest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities