WebSockets streams updates stop providing incremental data

[PhilAlain]

Bittrex WebSockets streams updates stop providing data - Version 7.0.9 tested - but issue also existed in prior versions.

In some cases, Bittrex WebSocket streams stop providing incremental data and the last dataset remains endlessly valid.

We have tested the following: OrderBook and Trades updates on different physical machines, subscribing to several MarketPairs.

At some point - 05/03/2022 17:26:28 - in our test, something happens - necessarily on Bittrex side - since different physical machines / IPs / software instances / MarketPairs subscriptions were running simultaneously Bittrex.net.

After, there are no more OrderBook or Trades updates on all machines and all MarketPairs.
Bittrex.Net keeps endlessly the last dataset as valid.

Some detection should occurr, to restart the websocket.

We could provide more detailed logs and reproduce, but we need to know which logs are needed.

[JKorf]

Hi, I've fixed an issue with reconnecting in the latest version, plus I also added a no data timeout of 30 seconds (the SignalR server sends a ping every 10s), so should the server disconnect while not closing the socket it should now timeout properly. That is unless the server keeps sending pings every 10s, but not the data, but at that point I don't think I can do much about it.

Let me know if your issues are fixed with v7.0.10

[PhilAlain]

Hi Jan,
Please find below the result of my Bittrex analysis in trace mode :

1. For some unknown reason (no error spotted in the log, no unknown message fromBittrex), Bittrex stops sending "orderBook" updates 06:50:39.956 in the attachment.
2. All other private subscriptions keep incoming "order", "balance"
3. About 2 hours later 08:43:16.739 Bittrex sends again a new "orderBook" update
4. Your program detects this is a first item in the sequence, but skips it endlessly
5. About 4 more hours later, Bittrex closes the Websocket, a new Websocket is created and resynchronization occurs.

I have attached an anonymized log extract.
Log.log

I also can run additional tests with more logs but I need some guidance :-)
Hope this helps,
Philipp

[JKorf]

Hi Philipp, sorry for the delayed response.
Looking at the logs, I think there is some weird stuff going on on the Bittrex side. Normally the updates should appear in order where each sequence number of the update is bigger than the last. After the 2 hour no data being send Bittrex then sends an update with Sequence = 1, which doesn't make any sense to me. Because the sequence number is smaller than the previous recorded one, the update is skipped by the library.

I think you should contact Bittrex to see if they can explain this, because I can't.

[Dimasik007]

Hey, I am having the same issue with Bittrex orderbook websocket where it randomly stops pushing orderbook changes. Did anyone manage to find a solution to this or got a response from Bittrex dev team?