Skip to content

Solana method

getHealth

Reports whether the node considers itself caught up with the cluster.

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

This method has not been measured in this window.

It is scheduled but no observation has landed yet.

What it does

Returns the string `"ok"` when healthy. When not, it returns a JSON-RPC error rather than a different string — which surprises callers expecting a status field.

A node is unhealthy when it has fallen more than a configured number of slots behind the cluster's highest known slot.

Returns

"ok", or a JSON-RPC error when unhealthy.

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

As JSON-RPC

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

Response

{
  "jsonrpc": "2.0",
  "result": "ok",
  "id": 1
}

Things that bite

  • An unhealthy node answers with an error, so treating any error as unreachable conflates a lagging node with an unreachable one.
  • Behind a load balancer this describes whichever node answered, not the pool.

Why it is measured

The self-reported counterpart to head lag, and worth recording where the two disagree — a node calling itself healthy while sitting slots behind the cohort is more interesting than either fact alone.

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

6h window · generated 2026-08-24 17:26:44 UTC · 0 providers