Node is unhealthy (-32005)
Last updated:
At a glance
| Property | Value |
|---|---|
| Code | -32005 |
| Message | Node is unhealthy |
| Category | network |
Cause
The node is behind the cluster by more than its health threshold (N slots) or is still catching up after start/snapshot. It returns unhealthy rather than serving stale data.
Solution
- Retry against a healthy endpoint.
- Compare the node's `getSlot` to the cluster tip to gauge lag.
- For your own node, wait for catch-up or restore from a fresher snapshot.
Example
{
"id": 1,
"error": {
"code": -32005,
"message": "Node is unhealthy: behind by 250 slots"
},
"jsonrpc": "2.0"
}FAQ
- Why does "Node is unhealthy" happen?
- The node is behind the cluster by more than its health threshold (N slots) or is still catching up after start/snapshot. It returns unhealthy rather than serving stale data.
- How do I fix "Node is unhealthy"?
- Retry against a healthy endpoint. Compare the node's `getSlot` to the cluster tip to gauge lag. For your own node, wait for catch-up or restore from a fresher snapshot.
- What is RPC error -32005?
- -32005 means: Node is unhealthy. The node is behind the cluster by more than its health threshold (N slots) or is still catching up after start/snapshot. It returns unhealthy rather than serving stale data.