Skip to content

Solana method

getVersion

Returns the solana-core version and feature set of the node.

cheapCheap for a provider to serve — no state is read, or one key is.Primary specification (opens in a new tab)

How each provider handles it

3 providers

Provider support for getVersion on Solana
ProviderStatusSuccessMedian
PublicNodeSupported99.9%24 ms
TatumDegraded94.1%26 ms
Solana FoundationSupported99.8%18 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 day. 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.

When it degraded

A degradation is a bucket where a provider fell away from ITS OWN median for this method over the window, not from the cohort's. A provider that is consistently slower than its peers is not degraded — it is slower, which the ranking already says. Buckets with fewer than 20 samples are skipped, because a claim about a provider cannot rest on a handful of calls, and adjacent bad buckets are merged so one outage reads as one incident.

Solana Foundation

  • median rose to 52ms from a typical 15ms

    latency · 2026-09-09 00:00Z → 2026-09-10 00:00Z

  • median rose to 31ms from a typical 15ms

    latency · 2026-09-13 00:00Z

Tatum

  • success fell to 53.7% from a typical 96.4%

    availability · 2026-09-09 00:00Z → 2026-09-10 00:00Z

What it does

Reports the software version behind an endpoint, together with `feature-set` — a numeric identifier of the activated feature bundle the node is running.

Unlike Ethereum's client version string, this one is rarely rewritten by providers, so it is a reasonably reliable view of what software is actually serving.

Returns

Object with solana-core and feature-set.

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":"getVersion"}'

As JSON-RPC

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

Response

{
  "jsonrpc": "2.0",
  "result": {
    "solana-core": "2.1.11",
    "feature-set": 3271415109
  },
  "id": 1
}

Things that bite

  • A node whose feature-set differs from the cluster's is running a different activation set and can legitimately disagree about transaction outcomes.

Why it is measured

The cheapest Solana call, which makes it the baseline every other Solana latency figure is read against.

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

30d window · generated 2026-10-08 18:19:38 UTC · 3 providers