I noticed that on my monitoring nodes, nearly across the board (ignoring ones that already had full connection slots), the inbound connections steeply increased on 2026-03-31 at around 00:12 UTC (2026-03-31T00:12:00Z).
Node dave has a high limit of inbound connection slots. The number of inbound connections increased from 116 at 00:12 UTC by 32 to 148 at 00:15 UTC.
As of 2026-04-02T11:00:00Z, the connection levels are still elevated.
This exactly matches the time when my 22 outbound connections across multiple nodes to bitprojects (Many connections to bitproject.io nodes?) dropped.
Likely, all nodes on the network connected to bitprojects lost their outbound connections to bitprojects at the same time and all of them started looking for new outbounds at the same time.
This matches with the post from @bitprojects in Many connections to bitproject.io nodes? - #24 by bitprojects.
I guess this solves it.
In total, my nodes seem to have gained around 220 IPv4 peers.
However, I’ve also noticed a small increase of 15 in onion peers. I don’t think bitprojects had any nodes on Tor, but some of the nodes looking for new outbounds might have picked onions to connect to.
Don’t really notice something on the other networks. Possibly 10 new I2P peers, but there seems to be a lot of churn anyways.
Both my Mainnet nodes with “unlimited” incoming connections allowed, show an increase at the same time: (times are in CEST UTC+2)
sorry if this is a repost of the info, but I was handling 80k inbound connections right before shutdown. There were also several times over the last few months that I needed have some traditional maintenance windows where all of my nodes were unreachable for 15-45 minutes – should all correlate.
Correct I was 100% IPv4
