We have experienced cases where Blockbook servers will drop the websocket connection for whatever reason. The client should detect failure of the websocket and:
[x] try reconnection on the current client a limited number of attempts
[x] after exhausting all attempts, (mark the failed state of the server, see #46) and attempt to rotate and connect to the next server in the pool
Currently, the websocket will attempt to reconnect over and over without failing the server. This issue will be kept open to track the further-needed improvements.
We have experienced cases where Blockbook servers will drop the websocket connection for whatever reason. The client should detect failure of the websocket and: