Addrman age distribution

[b10c]

@stratospher

also compared alice’s current addrman with a few older snapshots I had (last week, nov 2025, aug and sep 2024). it’s interesting that the older snapshots had lots more 2 week - 1 month old addresses in the new table compared to the recent snapshots.

I think this might be related to the current address flooding happening on the network.

/python-bitcoinlib:0.12.2/ client getting addr-ratelimited (since 2026-04-10)

Since 2026-04-10 at about 16:30 UTC I’ve seen multiple IPv4 addresses connect to my monitoring nodes gossiping addresses via addr (and not addrv2) at a higher rate. These addresses are frequently rate-limited. IPs are: 130.60.24.200 (uzh.ch - University of Zurich) 3.102.33.26 (AWS New Zealand) 3.98.91.234 (AWS Canada) 51.20.80.202 (AWS Sweden) … [image] My node erin is receiving about 40 addresses per minute now. [image] Looking at the addrman of erin, the seems to be only the normal ba…

My observation there was:

@b10c

At 2026-04-13T13:47:00Z I received a addr message with exactly 10 entries. All timestamps were recent (not older than 10min). The IPs seemed reasonable from locations where real nodes could be hosted / run from, the ports were mostly 8333, and the services seemed to be reasonable ones too.

This is likely updating the timestamps in our tables.