Why does monerod have few connections or peers?

monerod, the program that runs your Monero node, can have few peers simply because it only opens a limited number of outgoing connections and cannot accept incoming ones. A small peer count is not automatically a problem: what matters is whether your node stays connected and keeps up with new blocks.

Outgoing and incoming connections are different

A peer is another Monero node that exchanges blocks and transactions with yours. Your node can connect in two ways:

• Outgoing connections: Your node contacts another node. These usually work through a home router without any changes.
• Incoming connections: Another node contacts yours. These require your computer to be reachable from the internet.

Monero deliberately limits connections rather than contacting every available node. Your configured outgoing limit, software version, and network conditions all affect the number you see.

If you have several outgoing peers but no incoming peers, your node may be working normally. You do not need incoming connections to sync or support your own mining.

Your router or firewall may block incoming peers

The most common reason for zero incoming connections is that unsolicited traffic cannot reach your computer.

Possible causes include:

• Your computer’s firewall blocks Monero’s peer-to-peer port.
• Your router has no port-forwarding rule directing that traffic to your node.
• Your internet provider uses carrier-grade NAT, which means multiple customers share a public internet address.
• Your VPN does not support incoming connections.

For a standard Monero mainnet node, the default peer-to-peer port is TCP 18080, unless you changed it. Mainnet is the real Monero network, rather than a testing network.

You can allow that port through your firewall and configure your router if you want to accept peers. However, router port forwarding alone generally will not solve carrier-grade NAT.

Do not confuse the peer port with RPC, the interface that wallets and mining software use to ask your node for information. Opening RPC does not increase your peer count, and exposing unrestricted RPC to the internet is unsafe.

Check whether the node is actually struggling

In the monerod console, use:

• status to check synchronization and connection counts.
• print_cn to inspect active peer connections.

A newly started node may need a little time to find and connect to peers. Compare its block height—the number of blocks it knows about—with a current Monero explorer. New blocks arrive about every two minutes on average, not on an exact schedule.

If the node has no peers, repeatedly disconnects, or falls behind, check:

• Whether your internet connection is stable.
• Whether a firewall, VPN, or proxy blocks outgoing traffic.
• Whether you are using an up-to-date official Monero release.
• Whether startup settings limit connections or restrict the node to specific peers.
• Whether your computer’s date and time are correct.

What this means for solo mining and P2Pool

More peers do not directly increase your mining speed or reward rate. They can improve connectivity and resilience, but the important goal is receiving and forwarding blocks promptly.

For solo mining, your node needs to be synchronized. For P2Pool, remember that P2Pool has its own peer connections, separate from monerod. A low P2Pool peer count and a low Monero node peer count need separate checks.

The bottom line

If your node stays synchronized with several stable outgoing peers, a modest connection count is usually fine. Investigate missing connectivity or delayed blocks—not the peer number alone.