Fastest free Swellchain RPC, live no-key EVM endpoint latency
RPCsSentio
Leads184 ms
- p99
- 319 ms
- rank
- #2
- samples
- 1,206
Thirdweb
No data in window
Per region
| Region | Sentio | Thirdweb |
|---|---|---|
| US-East | 183 ms | 605 ms |
| EU-West | 176 ms | 609 ms |
| Singapore | 192 ms | 602 ms |
Sentio vs Thirdweb
Sentio leads on 1 of 1 shared benchmarks, Thirdweb on 0. Sentio wins on Fastest free Swellchain RPC, live no-key EVM endpoint latency (184 ms vs 605 ms).
Sentio
Sentio is a blockchain data and RPC infrastructure provider. Their public RPC node (swell-mainnet.rpc.sentio.xyz) supports Swellchain (chain 1923) without an API key.
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).
Side by side measurements
Frequently asked questions
Sentio vs Thirdweb: which one is better?
Sentio and Thirdweb are compared on 1 shared OpenChainBench benchmarks. Sentio leads on Fastest free Swellchain RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
Which is faster on fastest free swellchain rpc, live no-key evm endpoint latency, Sentio or Thirdweb?
On the Fastest free Swellchain RPC, live no-key EVM endpoint latency benchmark, Sentio leads at 184 ms versus Thirdweb at 605 ms. Live measurement is updated continuously by the OpenChainBench harness.
How is the Sentio vs Thirdweb 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.