For the complete documentation index, see llms.txt. This page is also available as Markdown.

system_health - Bittensor

Example code for the system_health JSON-RPC method. Complete guide on how to use system_health JSON-RPC in GetBlock Web3 documentation.

Returns node health information — peer count, syncing state, and whether the node should have peers. A core liveness probe for Substrate infrastructure.

Substrate native JSON-RPC method. Call against a GetBlock endpoint configured for the Substrate interface. For typed SDK access, use Polkadot.js (TypeScript) or substrateinterface (Python).

Parameters

  • None

Request Example

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "system_health",
    "params": [],
    "id": "getblock.io"
}'
import axios from 'axios';

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "system_health",
    "params": [],
    "id": "getblock.io"
});

const config = {
    method: 'post',
    url: 'https://go.getblock.io/<ACCESS-TOKEN>/',
    headers: {
        'Content-Type': 'application/json'
    },
    data: data
};

axios(config)
    .then(response => console.log(JSON.stringify(response.data, null, 2)))
    .catch(error => console.log(error));

Response Example

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": {
        "peers": 12,
        "isSyncing": false,
        "shouldHavePeers": true
    }
}

Response Parameters

Field
Type
Description

result.peers

integer

Number of connected P2P peers

result.isSyncing

boolean

true if the node is still catching up; false if at chain tip

result.shouldHavePeers

boolean

false for solo/dev chains; true for networked chains

Use Cases

  • Liveness probes in production infrastructure

  • Routing reads only to fully-synced nodes (isSyncing: false)

  • Detecting nodes with peer connectivity problems

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

-32601

Method not found

Method does not exist on this interface — check whether you're calling a Substrate method on an EVM endpoint or vice versa

-32603

Internal error

Server-side error while processing the request

429

Too Many Requests

Rate limit exceeded for your plan

SDK Integration

Last updated

Was this helpful?