Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage 
Regardless of that, the rest of network is probably synchronized.
Regardless of that, the rest of network is probably synchronized.Did you delete or replace data.mdb as I emphasized a page back?
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.
Hi Cotinco,
It's a little bit early here so I'm sorry if I missed anything. I've been looking into the priority nodes and they appear to be in sync at the moment.
I ran into the blockchain sync issue myself yesterday and found that deleting the p2pstate.bin and the imbd file did it for me. However, YMMV and I'm willing to do what it takes to help you get up and running to your satisfaction. It's still about 3am here so when I'm online in 4 - 5 hours I will be available again for the day on Slack at your convenience.
It sounds like your file may be corrupted. I just resynced my blockchain before I started this post to confirm that it's updating correctly with the new nodes. Perhaps try running the following in your command interface when you're ready to start fresh.
derod.exe --add-priority-node 89.38.97.110:18090 --add-priority-node 212.8.242.60:18090 --add-priority-node 85.217.170.245:18090 --add-priority-node 89.38.96.169:18090 --add-priority-node 45.63.6.91:18090 --add-priority-node 108.61.220.229:18090 --add-priority-node 207.148.5.250:18090 --add-priority-node 45.77.89.64:18090 --add-priority-node 45.76.42.165:18090 --add-priority-node 45.77.242.137:18090