Gravity Alpha RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Gravity Alpha RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Gravity Foundation has the lowest median latency of the 2 free public Gravity Alpha RPC endpoints measured, 138 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/gravity-rpc. Chain ID 1625. 2 public endpoints, no key: rpc.gravity.xyz, gravity-alpha.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 →
Gravity Alpha Mainnet (chain 1625) is a high-throughput EVM L1 built by Galxe, the onchain loyalty and quest platform with over 20 million users. G is the native gas token. The Gravity Foundation's rpc.gravity.xyz and Ankr provide keyless access probed every 60 seconds from three regions.
Methodology
Gravity Alpha: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Gravity Foundation leads at 138 ms; the chain-official endpoint measures 138 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Gravity Alpha endpoint that sustains continuous probing, 2 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Gravity Alpha-scoped answer with per-region breakdowns as a first-class dimension.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
- Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Gravity Alpha-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="gravity"`. Provider coverage today: 2 no-key endpoints.
Results: 2 free public Gravity Alpha RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Gravity Foundation | 138 ms | 150 ms | 179 ms | 100.00% (n=4318) |
| 2 | dRPC | 269 ms | 447 ms | 526 ms | 99.98% (n=4317) |
Public Gravity Alpha RPC endpoints measured
Chain ID 1625, currency G. The 2 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.
Gravity Foundation
https://rpc.gravity.xyz138 ms100.0%
dRPChttps://gravity-alpha.drpc.org269 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://1625.rpc.thirdweb.com2.0 % success over 24 h
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities