net_peerCount

net_peerCount returns the number of peers an Avalanche C-Chain node is currently connected to, encoded as a hex integer — for example "0x1a" means 26 peers. Peer count is a quick proxy for how well a node is meshed into the network and able to receive blocks and broadcast transactions. On the C-Chain — the EVM chain where AVAX pays for gas, secured by Snowman/Avalanche consensus — a node with healthy peering keeps pace with the chain's one-to-two-second block cadence. Send the request to https://avalanche.therpc.io/YOUR_API_KEY (chain ID 43114, 0xa86a).

Use cases

• Track peer count over time in an infrastructure health dashboard to confirm your C-Chain nodes stay well connected to the AVAX network.
• Detect an isolated node early: a peer count that drops toward zero signals a node likely to fall behind on C-Chain block propagation and serve stale data.

Parameters

Este método no acepta parámetros. Pasa un array vacío [].

Response

Example request

1curl https://avalanche.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5    "jsonrpc": "2.0",
6    "method": "net_peerCount",
7    "params": [],
8    "id": 1
9  }'

Try it live in the Avalanche playground.

Errors & troubleshooting

Common pitfalls

• Through a managed endpoint like https://avalanche.therpc.io/YOUR_API_KEY, the returned count reflects a backend node's own peering, not anything specific to your request or your traffic.
• A low peer count on a managed, load-balanced node does not necessarily mean your RPC calls are degraded — the provider's fleet may still answer correctly. Reserve this metric for operators running their own AvalancheGo nodes.

Supported networks

• Mainnet — Chain ID: 43114
• Fuji

See also

• net_listening
• net_version

1curl https://avalanche.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"net_peerCount","params":[]}'