Fastest free Sei RPC, live no-key EVM endpoint latency
RPCsSei Labs
Leads85 ms
- p99
- 281 ms
- rank
- #1
- samples
- 3,693
Thirdweb
No data in window
Per region
| Region | Sei Labs | Thirdweb |
|---|---|---|
| US-East | 84 ms | 594 ms |
| EU-West | 90 ms | 602 ms |
| Singapore | 80 ms | 599 ms |
Sei Labs leads on 1 of 1 shared benchmarks, Thirdweb on 0. Sei Labs wins on Fastest free Sei RPC, live no-key EVM endpoint latency (85 ms vs 598 ms).
Sei Labs' official public EVM RPC (evm-rpc.sei-apis.com) for the parallel-execution EVM layer on Sei's Cosmos SDK L1 (chain 1329). Standard EVM JSON-RPC, keyless, rate-limited per IP.
ThirdWeb operates a keyless public RPC gateway at `<chainid>.rpc.thirdweb.com` covering 2000+ EVM chains via chain-id routing. Free tier is rate-limited per IP with no signup; paid tiers unlock higher throughput and dedicated endpoints. Used keyless across 13 chains on the RPC latency cluster (arbitrum, ethereum, polygon, optimism, base, bnb, avalanche, linea, worldchain, kaia, ink, opbnb + more).
Sei Labs
Leads85 ms
Thirdweb
No data in window
Per region
| Region | Sei Labs | Thirdweb |
|---|---|---|
| US-East | 84 ms | 594 ms |
| EU-West | 90 ms | 602 ms |
| Singapore | 80 ms | 599 ms |
Sei Labs and Thirdweb are compared on 1 shared OpenChainBench benchmarks. Sei Labs leads on Fastest free Sei RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
On the Fastest free Sei RPC, live no-key EVM endpoint latency benchmark, Sei Labs leads at 85 ms versus Thirdweb at 598 ms. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.