Using a WebsocketProvider whose websocket is not open can lead to avoidable stalling.

An efficient usage of FallbackProvider may look like having a websocket provider as the first provider, followed by JSON-RPC providers as backups. Such setup can avoid HTTP/S overhead. But if the websocket provider closes or takes a while to connect, FallbackProvider will wait for the timeout before moving to the fallbacks.

We can read the websocket's readyState to avoid this issue and quickly fallback.