Bitcoin Core IBD becomes extremely slow after ~68%; peers connect but stop delivering blocks
I'm currently doing the Initial Block Download (IBD) of a Bitcoin Core node. For most of the synchronization, everything behaved as expected. The node was using the resources I made available to it: CPU usage was high during validation, RAM usage increased according to the configured cache, network bandwidth was being used, and the synchronization rate varied roughly between 2% and 5% per hour , with a peak around 5%/h. I then left the node running for about a week while I was away. When I came back, it was around 68–69% synchronized , but the effective synchronization rate had fallen to approximately 0.03% per hour . This had apparently happened several days before I returned. Before leaving, the node was around 20%, so even a sustained 1%/h rate should have put it much further ahead after several days. There was also an unexpected power outage while I was away, which caused the node to shut down abruptly. However, I don't see any indication that the outage ...