Katana public RPC endpoints, tested
Every keyless Katana (chain ID 747474) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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. 5 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://katana.drpc.org | 23 ms | 3 blocks | under 1,000 | archive (1M+) |
| https://katana.rpc.sentio.xyz | 169 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.katana.network | 158 ms | 10 blocks | 10,000+ | archive (1M+) |
| https://rpc.katanarpc.com | 165 ms | 6 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/katana (SwiftNodes, keyless: 2 req/s) | 187 ms | 5 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
katana.drpc.org: first head after 472 ms - does not stream
rpc.swiftnodes.io/ws/katana(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
katana.gateway.tenderly.co: chainId: rate limitedlb.routeme.sh/rpc/evm/747474: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Katana endpoint, limits and status: Katana RPC, uptime history.