Hi guys, we have not stopped trying to understand and fix what went wrong : Right now we need the owner of 172.110.20.43:17236 to please take that node offline. We have identified it as the node which is broadcasting (out) the error.