RPC speed test
Benchmark your RPC endpoints, from your connection
Paste any JSON-RPC URLs, public gateways or your own keyed endpoints, then pick a duration, and watch them race. Every probe fires directly from your browser with the same anti-cache payload as our public RPC benchmarks, so the numbers are comparable to the leaderboards.
No install, no signup. Your URLs and API keys never leave this browser tab. Requests go straight from you to the provider. The probe engine is open source so you can verify exactly what runs.
1 · Endpoints
Prefill with the endpoints we already benchmark. Pick a chain:
2 · Duration
0 endpoints ready · HTTPS only · runs entirely in your browser
Methodology
Each endpoint receives an identical eth_getBlockByNumber("latest", false) POST with a rotating request id, so no edge cache can answer without touching a real node. One warmup request absorbs the TCP + TLS handshake, then all endpoints are probed once per second in staggered, randomized rounds until the clock runs out, so request bursts never align and network wake-ups hit every endpoint evenly. Responses are classified ok / http_err / jsonrpc_err / timeout, and an endpoint reporting a block more than 20 behind the best tip in the same round is flagged stale. Latency percentiles use ok responses only, exactly like the public benchmark methodology. Results reflect your device, network and location. That is the point: it is the latency your application would actually see.
Everything on this page is open source: browser probe engine and the rpc-capabilities harness that runs the same probe from datacenters for the public leaderboards.
Frequently asked
Is it safe to paste an RPC URL with my API key?
Yes. Every probe fires directly from your browser to the provider. Your URLs and keys are never sent to OpenChainBench servers, never logged, and never leave the browser tab. The probe engine is open source, so you can verify exactly what runs.
Why do my numbers differ from the public benchmark pages?
The public benchmarks probe from fixed datacenter regions every 60 seconds around the clock. This tool measures from your device, your network and your location right now. Both use the same anti-cache probe and classification, so the numbers are comparable, but the vantage point is yours. That is the point: it is the latency your application would actually see.
Which chains and endpoints can I test?
Any HTTPS JSON-RPC endpoint that speaks the standard eth_ methods, on any EVM chain: public gateways, your own keyed Alchemy, Chainstack or QuickNode URLs, or a self-hosted node with CORS enabled. The chain picker prefills the exact no-key cohort that the public per-chain benchmarks rank, across 87 EVM chains.
Why does an endpoint show as browser-blocked?
Some endpoints do not send CORS headers, so browsers refuse to call them. This is a property of the endpoint, not of the test: dapps cannot call those endpoints from a browser either. The tool shows an equivalent curl command so you can measure them from a terminal, and the public benchmarks cover them from datacenter probes.