TriportRPC

State of Solana RPC — Q2 2026

Last updated:

TL;DR

An independent, multi-region look at Solana and EVM RPC providers: who supports what, and how they perform on latency and uptime. Performance figures populate as our black-box prober collects samples.

Provider landscape

ProviderChainsDASp50 24h (ms)Uptime 24h (%)
Chainstackethereum, polygon, solanaNo
Ankrethereum, polygon, solanaNo
Blockdaemonethereum, polygon, solanaNo
OnFinalityethereum, polygonNo
Tatumethereum, polygon, solanaNo
NOWNodesethereum, polygon, solanaNo
Groveethereum, polygon, solanaNo
PublicNodeethereum, polygon, solanaNo
Allnodesethereum, polygon, solanaNo
Moralisethereum, polygonNo
ShyftsolanaYes
Coinbase Developer Platformethereum, polygon, solanaNo

Key findings

  1. The provider set spans Solana plus EVM chains; DAS support is a key differentiator for NFT workloads.
  2. Latency and uptime are measured per region — tail latency (p95/p99) matters as much as p50 for trading workloads.
  3. Transparent, per-method credit pricing makes cost predictable; see the RPC cost calculator.

Methodology

  1. A prober in each region runs a fixed set of standard public RPC/DAS/WS calls.
  2. Each call is measured once (wall-clock); a timeout is a failed sample — retries never heal a measurement.
  3. Samples roll up into p50/p95/p99 (successful calls only) plus uptime and error rate per window.
  4. Comparable paid tiers are configured per provider and recorded in the methodology.

See the live benchmarks for current figures and CSV export.

FAQ

How is this measured?
A black-box prober runs standard public RPC/DAS calls against each provider from multiple regions and records wall-clock latency, success and response size.
How often is it updated?
The report is refreshed quarterly; the underlying benchmarks update continuously on /benchmarks.
Are these vendor-sponsored numbers?
No — figures are independently measured against public endpoints on comparable paid tiers.