Blast RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Blast RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Blast has the lowest median latency of the 3 free public Blast RPC endpoints measured, 4 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/blast-rpc. Chain ID 81457. 3 public endpoints, no key: rpc.blast.io, blast-rpc.publicnode.com, blast.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 →
Read this carefully
The chain-official rpc.blast.io figure on this page reflects GCP co-location with our three probes, not a typical client path. Compare the gateways on the per-region tabs before choosing a primary.
Blast is the expansion's measurement cautionary tale. The chain-official `rpc.blast.io` answers in 4 ms on the 3-region average, a figure that only an anycast edge close to every probe origin can produce, which no single origin can do: Virginia, Amsterdam and Singapore are separated by 80+ ms round trips at the speed of light. The endpoint terminates at an edge network. Our stale-head detection confirms the blocks it serves are fresh, but a sub-5 ms number measures the edge handshake, not the chain. 3 no-key providers, identical probes, three regions.
Methodology
Blast: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Blast leads at 4 ms; the chain-official endpoint measures 4 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Blast endpoint that sustains continuous probing, 3 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 Blast-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Blast RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Blast | 4 ms | 4 ms | 5 ms | 100.00% |
| 2 | PublicNode | 71 ms | 79 ms | 159 ms | 100.00% |
| 3 | dRPC | 185 ms | 353 ms | 488 ms | 99.47% |
Public Blast RPC endpoints measured
Chain ID 81457, currency ETH. The 3 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.
Blasthttps://rpc.blast.io4 ms100.0%
PublicNodehttps://blast-rpc.publicnode.com71 ms100.0%
dRPChttps://blast.drpc.org185 ms99.5%
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 Blast RPCs work without an API key?
The 3 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.
Is rpc.blast.io really that fast, or is something else going on?
Blast runs geo-distributed RPC nodes inside major cloud datacenters (GCP us-east, GCP europe-west4/Frankfurt, GCP asia-southeast1/Singapore). Our Railway probes run in the same three GCP regions, so each probe hits the co-located Blast node with a sub-LAN round trip. The `x-node-id` response header confirms this: `blast_blast-mainnet_fra` from eu-west, `blast_blast-mainnet_sin` from Singapore. The blocks are fresh (not a cache hit) but the 4 ms figure reflects network co-location, not what a developer outside GCP infra will experience.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities