Gnosis RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Gnosis RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 4 free public Gnosis RPC endpoints measured, 76 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/gnosis-rpc. Chain ID 100. 4 public endpoints, no key: gnosis-rpc.publicnode.com, gateway.tenderly.co, gnosis.drpc.org, rpc.gnosischain.com. 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 →
Gnosis is where official does not mean fast: the chain-official `rpc.gnosischain.com` measures 168 ms p50 on the 3-region average against 76 ms for PublicNode, and several third-party gateways sit in between. 4 no-key providers, the same `eth_getBlockByNumber` call every 60 seconds, three regions.
Methodology
Gnosis: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 76 ms; the chain-official endpoint measures 168 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Gnosis endpoint that sustains continuous probing, 4 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Gnosis-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Gnosis RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 76 ms | 92 ms | 280 ms | 100.00% |
| 2 | Tenderly | 106 ms | 112 ms | 118 ms | 100.00% |
| 3 | dRPC | 113 ms | 128 ms | 178 ms | 99.26% |
| 4 | Gnosis | 168 ms | 493 ms | 598 ms | 100.00% |
Public Gnosis RPC endpoints measured
Chain ID 100, currency GNO. The 4 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.
PublicNodehttps://gnosis-rpc.publicnode.com76 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/gnosis106 ms100.0%
dRPChttps://gnosis.drpc.org113 ms99.3%
Gnosishttps://rpc.gnosischain.com168 ms100.0%
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.
Frequently asked
Which Gnosis RPCs work without an API key?
The 4 providers on this page are listed with their URLs in the endpoints table above. Nodies was delisted in July 2026 when its Gnosis endpoint moved behind a paid plan. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Should I use rpc.gnosischain.com as my Gnosis RPC?
Only as a fallback. It measures 168 ms at the median across three regions against 76 ms for the leader, though its reliability and head freshness are fine. The measured leaders above serve the same chain at 76 ms; keep the official endpoint in the rotation for redundancy rather than as primary.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities