As I mentioned in Discord ...
The NYA node has still been showing a lot of disconnects since the provider did maintenance on it.
So I've created a new NYA node with a different provider.
nya.kano.is now points to the new node
This wont affect any mining other than: if your miner disconnects from NYA and reconnects, it will connect to the new NYA node.
However, to add to that:
I'll force a failover to the new node in about a day if miners are still pointed at the old node.
This will simply be to stop the old node accepting miners and then everyone still on the old node will reconnect to the new node.
Mine on!
So far there's only been a few % of workers that have reconnected to the new node, a lot less than I expected after the number of times it was showing miners disconnecting the other day.
Anyway, at 01:00 UTC (in a bit over 13.5 hours) I'll push everyone left on the old node over to the new node.
There's nothing for anyone to do, it will just be a failover off the old node for miners still pointing to the old NYA node and failback immediately to the new NYA node.
Of course, any miners already switched to the new NYA node will just continue mining uninterrupted.
Everyone else will be unaffected.