Websocket, Spot, inconsistency in DOGE

Websocket
1

This is a bug report for the websocket API

I am connected on Binance API websocket and noticed data integrity errors in my database, the bid and ask prices sometimes started to overlap.
I am connected through: wss://stream.binance.com:9443/stream
I am listening to a total of 300 DEPTH streams: @depth@100ms

I’ve been searching for days, rewritten the entire code and even changed the backend from database to memcache.
The errors on my end are thrown like this:
04-16-2021 05:10:32.857309 XCBinance.php:1356->XCBinance-> [T:1,267.7753s d0.4392s] TEXT: DATA ERROR: DOGEUSDT - max bid 0.2402726 is larger than min ask 0.2402259. Requesting re-synchronization
04-16-2021 05:10:33.461701 XCBinance.php:1356->XCBinance-> [T:1,268.3797s d0.6044s] TEXT: DATA ERROR: DOGEUSDT - max bid 0.2402726 is larger than min ask 0.2402259. Requesting re-synchronization

As I understand this is something that should never happen in a continuous stream of depth updates, the highest bid price should never be larger than the smallest ask.

I am receiving these types of inconsistency errors every few seconds for the DOGE coin stream, it rarely happens on other streams as well but DOGE is all the time.
Given that DOGE is just one of 300 streams and neither the smallest nor the largest, this indicates the error is on Binance side.

Am I the only one noticing this ?

4

I added code to make sure I have a continuous stream of update IDs (so the IDs between messages need to be sequential without gaps).
It is still happening and it’s happening a lot with DOGE only.
DOGE throws that min/max inconsistency about once per minute, sometimes twice.

Does anyone here actually keep track of the orderbook by websocket ?

2

which stream are you watching?

3

I’m watching every single USDT stream in one connection.

I wrote together a better bug report but binance has no point of contact to submit it.
I’m updating my original post with the report.