0G RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public 0G EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , 0G Labs has the lowest median latency of the 3 free public 0G RPC endpoints measured, 38 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/0g-rpc. 3 public endpoints, no key: evmrpc.0g.ai, 0g-rpc.publicnode.com, 0g.drpc.org. 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 →
0G is a data-availability and AI-oriented L1 (chain 16661) with a standard EVM JSON-RPC surface. It has the joint-widest keyless roster of the chains added on 2026-10-07: the 0G Labs official endpoint (evmrpc.0g.ai), dRPC (0g.drpc.org), PublicNode (0g-rpc.publicnode.com) and Thirdweb (16661.rpc.thirdweb.com), all returning chain id 0x4115. A roster this wide lets the ranking survive one endpoint having a bad day, which is not true of most chains at this size.
Methodology
0G: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. 0G Labs leads at 38 ms; the chain-official endpoint measures 38 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public 0G endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a 0G-scaled staleness gap (20 blocks at 0G's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the 0G-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public 0G RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | 0G Labs | 38 ms | 62 ms | 131 ms | 100.00% |
| 2 | PublicNode | 76 ms | 92 ms | 305 ms | 100.00% |
| 3 | dRPC | 124 ms | 167 ms | 216 ms | 100.00% |
Public 0G RPC endpoints measured
The 3 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.
0G Labshttps://evmrpc.0g.ai38 ms100.0%
PublicNodehttps://0g-rpc.publicnode.com76 ms100.0%
dRPChttps://0g.drpc.org124 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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://16661.rpc.thirdweb.com0.0 % success over 24 h
Frequently asked
Which 0G RPCs work without an API key?
4 endpoints are probed on this chain: 0G Labs (evmrpc.0g.ai), dRPC (0g.drpc.org), PublicNode (0g-rpc.publicnode.com), Thirdweb (16661.rpc.thirdweb.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` call returning a parsable response before inclusion.
How is 0G RPC latency measured here, technically?
One identical `eth_getBlockByNumber` call every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Does 0G's EVM endpoint cover its data-availability layer?
No. The endpoints on this page answer the EVM JSON-RPC surface, which is what a wallet or a contract call uses. 0G's storage and data-availability services expose their own APIs and are not measured here. This page answers one question only: how fast does a standard EVM head query come back, and from which origin.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities