net_peerCount

net_peerCount returns the number of peers currently connected to a Polygon PoS node, encoded as a hex integer (for example "0x1a" for 26 peers). Those peers are the P2P connections the Bor client uses to receive new blocks and broadcast MATIC transactions across the Polygon network. A healthy peer count is a strong signal the node can keep up with Polygon's ~2-second block production. Query it against the Polygon mainnet endpoint at https://polygon.therpc.io/YOUR_API_KEY (chain ID 137, 0x89).

Use cases

• Monitor node connectivity in infrastructure health dashboards, plotting the connected-peer count of each Polygon node over time.
• Detect isolated nodes with too few peers, which on Polygon's fast block cadence risk falling behind on block propagation and serving stale data.

Parameters

此方法不需要任何参数，传入空数组 [] 即可。

Response

Example request

1curl https://polygon.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 Polygon playground.

Errors & troubleshooting

Common pitfalls

• Against a managed Polygon endpoint the value reflects a backend node's own peer count, not anything specific to your request or API key, so it is informational rather than per-client.
• A low peer count on a managed node does not necessarily mean your RPC calls will fail — providers maintain redundant, well-connected Polygon nodes, so the number is best read as one signal among several rather than a hard alarm.

Supported networks

• Mainnet — Chain ID: 137
• Amoy — Chain ID: 80002

See also

• net_listening
• net_version

1curl https://polygon.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":[]}'