Is it ok now? The reason was probably the typical scenario: peers.dat collects a number of peers which are getting invalid after a while. When restarting the client is working through this list, each one with a certain timeout. So it simply takes some time until good ones are found. After having stopped your client you could delete peers.dat in order to speed up the next boot. Disadvantage: the good peers among the list are gone then. Btw, if you ever run into the situation that your client seems stuck a simple restart usually helps (basically for the same reason as just mentioned).

@all, I've been sponsoring today a new permanent seed node to further improve the initial sync.

Many greetings

trenton


PS: most or all of the addnode entries from the "historical" postings probably don't work any longer and cause startup delays. I suggest to remove these addnodes completely from your frozen.conf.