Solana Foundation Launches Official RPC Performance Dashboard at solana.com/data

The Solana Foundation published a live RPC performance benchmark at solana.com/data today, giving developers their first Foundation-operated side-by-side comparison of Alchemy, Helius hSOL$87.22-0.3%, QuickNode, and Triton One, four major providers measured under identical conditions from the same seven global regions by a party with no commercial stake in the ranking.

The launch arrives six days after Helius open-sourced its own benchmark, rpc-perf-dash, which covers the same four providers. The Foundation's tool is structurally different: it is operated and maintained by the Foundation itself, not by any provider that appears in the results.

Benchmarking Alchemy, Helius, QuickNode, and Triton One Side by Side

The RPC tab at solana.com/data surfaces four measurements for each provider in near real-time: round-trip latency, slot lag (how far behind the chain tip a provider's reported slot sits), request success rates broken down by method, and a liveness signal tracking whether a provider is reachable. The Foundation's announcement thread directed builders to "compare the approaches and find the provider that fits how you work."

Uniblock is listed as a coming-soon addition to the benchmarked set. Forward Industries, a Solana treasury company, described the launch as putting builders in a position to choose their RPC provider on verified performance data.

Seven Regions, Eleven Methods, No Cache

The underlying infrastructure is the RPC Latency Monitor, a Rust binary published under Apache 2.0 that runs continuously against each provider from seven locations: Virginia, Los Angeles, London, Frankfurt, Tokyo, Seoul, and Singapore. Monitoring instances run across GCP, AWS, and two bare-metal providers, diversifying the measurement footprint so no single cloud network path dominates the results.

Each region probes 11 standard JSON-RPC methods: getHealth, getSlot, getLatestBlockhash, getAccountInfo, getMultipleAccounts, getProgramAccounts, getTokenAccountsByOwner, getBlock (both recent and archival), getTransaction, and getSignaturesForAddress. The suite spans the full range of calls a production application makes, from lightweight health checks to heavier reads that stress a provider's indexing layer.

The design addresses gaming at several points. Every request includes a Cache-Control: no-cache header to prevent pre-cached responses from registering as fast answers. The block heights, transaction signatures, and account addresses used as query inputs rotate continuously from live chain data, so providers cannot pre-warm specific responses. Empty, null, or truncated payloads fail validation regardless of how quickly they arrive. For archival queries, responses are cross-checked against a majority-vote consensus across all providers; any result that disagrees with the consensus fails even if it arrives first.

The benchmark uses the highest observed processed slot across all participants, or a dedicated reference endpoint, as its chain-tip reference, so no single provider's slot view anchors the lag calculation.

Open-Source Infrastructure Behind the Dashboard

The RPC tab sits within a broader data platform. The Solana Data Aggregator, an open-source Python 3.12+ system, pulls from nine external data providers (Allium, Artemis, Blockworks, DefiLlama, Dune, RWA, Stakewiz, Token Terminal, and ValidatorsApp) and feeds the rest of solana.com/data: Overview, Network, Stablecoins, DeFi, and Tx Senders tabs. The RPC Latency Monitor publishes Prometheus metrics that a colocated Grafana Alloy agent scrapes and forwards to Grafana Cloud for rendering.

Both repositories are public and open for contribution.

Providers Can Add Themselves by Pull Request

The Foundation built the provider roster as an open list. Providers add themselves via pull request, submitting their endpoint to the configuration file using environment variable placeholders and sending credentials separately. Entries are ordered alphabetically, and the repository documentation specifies that new additions "accept equal treatment: the same check suite, regions, and cadence as every other provider, with no preferential routing."

Choosing an RPC Provider on Data, Not Marketing

Solana developers have had no shortage of RPC comparison tools, but nearly all have been produced by parties with a direct interest in the outcome. Provider-run benchmarks control which methods get tested, which regions are reported, and how edge cases are handled. Community-built tools and third-party aggregators fill some of the gap but vary in methodology and maintenance. The Foundation's version sits outside that dynamic entirely.

The dashboard does not issue a ranking or declare a winner. It publishes the measurements and leaves interpretation to the developer, whose criteria (slot freshness, method latency, geographic coverage, cost) will differ by application type. A trading bot that depends on minimal slot lag has different requirements from a wallet application primarily querying account balances or recent transaction history.