Skip to content

Solana method

getClusterNodes

Returns every node the queried node knows about through gossip.

expensiveExpensive: scans a range or a large account set. Frequently restricted.Primary specification (opens in a new tab)

How each provider handles it

3 providers

Provider support for getClusterNodes on Solana
ProviderStatusSuccessMedian
Solana FoundationSupported100.0%73 ms
PublicNodeSupported100.0%170 ms
TatumDegraded95.8%147 ms

Success excludes calls the provider does not implement — an optional method a provider declines to offer is a capability fact, not a failure, and is never scored as one.

Over time

Median latency per hour. Gaps are periods with no measurement, drawn as gaps rather than joined across — a line through missing data invents a measurement that was never taken.

Logarithmic scale — each gridline is ten times the one below it. Click a provider in the legend to hide it.

What it does

A list of thousands of validators and RPC nodes, each with its identity pubkey, gossip address, and — where advertised — its RPC, TPU and pubsub endpoints.

It is a view of the network's shape from one vantage point. Two nodes will return slightly different lists, because gossip propagation is not instantaneous.

Returns

Array of node objects with pubkey, gossip, tpu, rpc, version, shredVersion.

Try it

Runnable as written, against a keyless public endpoint. Nothing here needs an API key.

Request

curl -s https://api.mainnet-beta.solana.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getClusterNodes"}'

As JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getClusterNodes"
}

Response

{
  "jsonrpc": "2.0",
  "result": [
    {
      "pubkey": "9QU2QSxhb24FUX3Tu2FbeeGkGvj6YgQfPwqBAuBQ5NRW",
      "gossip": "10.239.6.48:8001",
      "tpu": "10.239.6.48:8004",
      "rpc": "10.239.6.48:8899",
      "version": "2.1.11",
      "featureSet": 3271415109,
      "shredVersion": 50093
    }
  ],
  "id": 1
}

Things that bite

  • The response is around 1.5 MB. Many providers disable it outright, and that is a reasonable decision rather than a fault.
  • rpc is null for the large majority of nodes: validators do not usually expose a public RPC port.

Why it is measured

It is one of the two sources behind the validator map on this site, and its availability is itself a meaningful capability difference between providers.

Called every 3600 seconds per endpoint, with jitter so the fleet does not hit a provider in lockstep.

6h window · generated 2026-10-08 18:55:22 UTC · 3 providers