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.
****** IMPORTANT ******
I have been working with support and DeroBoy this morning to try and help with the network problems that we've been seeing. To that end, I have created a network of 6 geo-diverse nodes dedicated purely to running Dero daemons. The nodes have each other as priority nodes, and it is requested that all pools add them as priority nodes too. End users may also add them as priority nodes to your local daemon which will help everything to stay in sync.
They are located in: New Jersey US, Los Angeles US, Dallas US, London UK, Amsterdam NL, and Singapore.
IP addresses:
45.63.6.91
108.61.220.229
207.148.5.250
45.77.89.64
45.76.42.165
45.77.242.137
To add them to your pool's derod startup command line:
--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
I will be watching them carefully to ensure that they stay in sync and running fast. So far no problems noted, and they're under very low load. Any problems please let me know.