Web socket streams reconnection doesn't follow Binance limit.

[bvvinai]

I have subscribed to around 100 assets using binance-connector-go following the 5 req/sec websocket limit and after the 23H mark, the reconnection logic doesnt follow the limit. Im getting the following error.

Is there any workaround or shd I write the connection logic on my own?

2026/01/29 19:47:51 Resubscribed to stream ontusdt@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream sceth@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream xrptusd@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream xlmusdc@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream ltcusdc@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream zilusdt@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream batusdt@ticker on reconnection

2026/01/29 19:47:51 Resubscribed to stream adausdc@ticker on reconnection

2026/01/29 19:47:51 WebSocket read error: websocket: close 1008 (policy violation): Too many requests

2026/01/29 19:47:51 WebSocket read error: websocket: close 1008 (policy violation): Too many requests

2026/01/29 19:47:51 WebSocket read error: websocket: close 1008 (policy violation): Too many requests

2026/01/29 19:47:51 WebSocket read error: websocket: close 1008 (policy violation): Too many requests

2026/01/29 19:47:52 Resubscribing to stream ID: 0 on reconnection

2026/01/29 19:47:52 Resubscribing with payload: map[id:bb9b23fb-6d0d-4f29-8597-55274c381e9f method:userDataStream.subscribe

params:map]

[alplabin]

Hey @bvvinai, Thank you for reporting this issue. The fix has been implemented in Binance/Common v2. Please give it a try and let us know if you encounter any further problems.