Thanks Remy, wallet syncing now with those addnodes. Confused why/how this worked though, was the "super" nodes given in config files supposed to prevent these issues?
Glad to know.
Yes exactly, you are right.
I did a fast test of supernode by pinging, and only one does not respond.
But this is a test that may not be significant, as the ping may be blocked
by a firewall, or the server may be on-line on but with the node frozen.
Looking in debug.log, the number of IP of some of the supernodes, seems to
have been seen not less than 48 hours ago.
But also this is a subjective test, not very reliable.
Shahim previously had complained about the fact that the hosting service imposed
limits on the use of server resources excessively low.
So as a mere guess we could imagine that the excess of these limits has resulted
in a freeze of the supernode daemon, and consequently also the freezing of the
updating of the Block Explorer.
But it is only a conjecture.
EDIT:
I did another test, this time using the wallet, and right now I get
repeatedly "connection timeout" on all 5 the nodes.
Fortunately, the network is able to go ahead even without the use of supernodes.