Fraxtal public RPC endpoints, tested
Every keyless Fraxtal (chain ID 252) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 6 of 9 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://fraxtal-rpc.publicnode.com | 28 ms | 3 blocks | 10,000+ | recent only |
| https://rpc.frax.com | 36 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://fraxtal.drpc.org | 36 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://fraxtal.api.pocket.network | 47 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/fraxtal (SwiftNodes, keyless: 2 req/s) | 136 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://frax-mainnet.rpc.sentio.xyz | 168 ms | 0 blocks | 10,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
fraxtal-rpc.publicnode.com: first head after 856 ms - streams
fraxtal.drpc.org: first head after 1947 ms - does not stream
rpc.swiftnodes.io/ws/fraxtal(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
node.histori.xyz/fraxtal-mainnet/8ry9f6t9dct1se2hlagxnd9n2a: chainId: fetch failedlb.routeme.sh/rpc/evm/252: chainId: rate limitedfraxtal.gateway.tenderly.co: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Fraxtal endpoint, limits and status: Fraxtal RPC, uptime history.