Fastest free X Layer RPC, live no-key EVM endpoint latency
RPCsThirdweb
No data in window
X Layer
Leads43 ms
- p99
- 117 ms
- rank
- #1
- samples
- 851
Per region
| Region | Thirdweb | X Layer |
|---|---|---|
| US-East | 714 ms | 43 ms |
| EU-West | 714 ms | 44 ms |
| Singapore | 715 ms | 44 ms |
Thirdweb vs X Layer
Thirdweb leads on 0 of 1 shared benchmarks, X Layer on 1. X Layer wins on Fastest free X Layer RPC, live no-key EVM endpoint latency (43 ms vs 715 ms).
Thirdweb
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).
X Layer
OKX's official public RPC (rpc.xlayer.tech) for X Layer (chain 196), the ZK-powered L2 built with Polygon CDK and operated by OKX. Standard EVM JSON-RPC, keyless, rate-limited per IP.
Side by side measurements
Frequently asked questions
Thirdweb vs X Layer: which one is better?
Thirdweb and X Layer are compared on 1 shared OpenChainBench benchmarks. X Layer leads on Fastest free X Layer RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
Which is faster on fastest free x layer rpc, live no-key evm endpoint latency, Thirdweb or X Layer?
On the Fastest free X Layer RPC, live no-key EVM endpoint latency benchmark, X Layer leads at 43 ms versus Thirdweb at 715 ms. Live measurement is updated continuously by the OpenChainBench harness.
How is the Thirdweb vs X Layer comparison measured?
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.
How this pair was selected
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.