Blast public RPC endpoints, tested
Every keyless Blast (chain ID 81457) 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 19 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.blast.io | 5 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://blast.drpc.org | 23 ms | 0 blocks | under 1,000 | none |
| https://blast-rpc.publicnode.com | 24 ms | 3 blocks | 10,000+ | none |
| https://rpc.swiftnodes.io/rpc/blast (SwiftNodes, keyless: 2 req/s) | 29 ms | 3 blocks | 10,000+ | none |
| https://blast.api.pocket.network | 38 ms | 0 blocks | 10,000+ | none |
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
blast.drpc.org: first head after 926 ms - streams
blast-rpc.publicnode.com: first head after 1109 ms - streams
blast.api.pocket.network: first head after 1840 ms - does not stream
blast.gasswap.org: connection failed (connect) - does not stream
blast.callstaticrpc.com: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/blast(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.ankr.com/blast: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403blastl2-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API insteblast.blockpi.network/v1/rpc/public: no answer (HTTP 521)li-fi-blast.intustechno.workers.dev/rpc: wrong chain (1)blast.gasswap.org: chainId: fetch failedblast.din.dev/rpc: chainId: fetch failedendpoints.omniatech.io/v1/blast/mainnet/public: no answer (HTTP 521)blast-public.nodies.app: no answer (HTTP 403)rpc.owlracle.info/blast/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)blast.therpc.io: chainId: fetch failedblast-mainnet.rpc.sentio.xyz: no answer (HTTP 404)lb.routeme.sh/rpc/evm/81457: chainId: rate limitedblast.gateway.tenderly.co: chainId: rate limitedapi-blast-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Blast endpoint, limits and status: Blast RPC, uptime history.