Seems that during the main-net update, there were many nodes doing updates to their twin information, hence some update requests where rejected (because blocks get full). the tfchain client used by rmb didn't handle this well and instead got stuck on the update forever (instead of failing)
Hence some nodes are now not reachable over rmb.
This issue is more related to the tfchain client, than rmb
Seems that during the main-net update, there were many nodes doing updates to their twin information, hence some update requests where rejected (because blocks get full). the tfchain client used by rmb didn't handle this well and instead got stuck on the update forever (instead of failing)
Hence some nodes are now not reachable over rmb.
This issue is more related to the tfchain client, than rmb
https://github.com/threefoldtech/tfchain/tree/development/clients/tfchain_client_rs