Sei RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Sei EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Sei Labs has the lowest median latency of the 2 free public Sei RPC endpoints measured, 61 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/sei-rpc. Chain ID 1329. 2 public endpoints, no key: evm-rpc.sei-apis.com, sei-evm-rpc.stakeme.pro. 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 →
Sei is a Cosmos SDK L1 (chain 1329) with a parallel-execution EVM layer bolted onto Tendermint consensus, launched by Sei Labs and positioned as a high-throughput trading chain. Standard EVM JSON-RPC on the EVM side; the Cosmos JSON-RPC would need a separate `Kind:"cosmos"` cluster entry as we did for Osmosis. 2 clean keyless providers measured: sei-official, Thirdweb, Stakeme. Excluded: dRPC (500 persistent internal error after 3 consecutive attempts), PublicNode (no `sei-evm` subdomain), Tenderly public (no `sei` route), BlockPI (`Apikey not found`), MeowRPC (defunct), AllThatNode + Basement Nodes + Node75 (host unresolvable or key-gated).
Methodology
Sei: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Sei Labs leads at 61 ms; the chain-official endpoint measures 61 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Sei endpoint that sustains continuous probing, 2 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Sei-scaled staleness gap (25 blocks at Sei's ~1 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Sei-scoped answer with per-region breakdowns as a first-class dimension.
Results: 2 free public Sei RPC endpoints ranked by p50 latency (24h, 3 regions)
Public Sei RPC endpoints measured
Chain ID 1329, currency SEI. The 2 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.
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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://sei.rpc.thirdweb.com1.2 % success over 24 h
Frequently asked
Which Sei RPCs work without an API key?
3 endpoints are probed on this chain, each listed with its URL in the endpoints table above. Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion.
How is Sei RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities