Author

Topic: Sudden spike in number of connections to my node (Read 727 times)

legendary
Activity: 3766
Merit: 1742
Join the world-leading crypto sportsbook NOW!
If you are using a vps to run bitcoind, maybe it was full of external WAN connections, but last saturday some of these connections turned off, and the UPnP management system assigned an higher priority to your bitcoind instance.

No, I'm not. And no upnp either.

So give us other details (current system setup, os, if your provider apply some restrictions on p2p connections, ecc...) that can help to find what thing has raised connections
legendary
Activity: 1974
Merit: 1029
If you are using a vps to run bitcoind, maybe it was full of external WAN connections, but last saturday some of these connections turned off, and the UPnP management system assigned an higher priority to your bitcoind instance.

No, I'm not. And no upnp either.
legendary
Activity: 3766
Merit: 1742
Join the world-leading crypto sportsbook NOW!
If you are using a vps to run bitcoind, maybe it was full of external WAN connections, but last saturday some of these connections turned off, and the UPnP management system assigned an higher priority to your bitcoind instance.
hero member
Activity: 518
Merit: 501
Perhaps someone found out about the node and was testing or trying to manipulate the node?
legendary
Activity: 1974
Merit: 1029
A couple of months ago (on march 5th, a little before the chart below starts) I added a "maxconnections=200" line to my bitcoind.conf and restarted the daemon. To my surprise, the number of connections stayed more or less in the same range as before, only a bit higher, but last saturday it spiked to ~200 out of the blue, with no apparent reason:



Does anyone have a clue why this might be?
Jump to: