Is binance's web socket api down? could not connect to websockert api: (even tested with library examples) java.net.ConnectException: Failed to connect to stream.binance.com/88.198.36.214:9443

I’m using binance java api library in github to connect to binance’s api, but getting ConnectionRefusedException.
Is there anything wrong with binance websocket api? I even getting error with library’s examples.
I tested with this library> and got same exception!

Thanks.

Haven’t received other reports and it’s running well with:
websocat -v 'wss://stream.binance.com:9443/ws/bnbusdt@kline_1m'
You can also try with https://binance-exchange.github.io/websocket-demo/.
Must be a local connection issue or with the use of library.

1 Like

Looks like problem solved, now everything is “on time” and there are no disconnections.


I’ve noticed this problem too, about 10 hours ago ticker stream started throwing regular exceptions (every 1-2 min) and incoming data are not sent every 1s like they supposed to be.
Kline streams are fine.
My listener was working for months and there never was such problems (disconnections from time to time happens, but not such regular and with exception - malformed frame).
Someone should take a look at this.
That’s how my log looks like right now. Socket is disconneting (due to malformed frame) every minute or two.

2021-05-28 18:47:55.581: Socket is dead, restarting...
2021-05-28 18:48:42.886: Socket is dead, restarting...
2021-05-28 18:50:09.221: Socket is dead, restarting...
2021-05-28 18:51:30.548: Socket is dead, restarting...
2021-05-28 18:52:45.245: Socket is dead, restarting...
2021-05-28 18:53:45.040: Socket is dead, restarting...
2021-05-28 18:54:45.780: Socket is dead, restarting...
2021-05-28 18:56:18.684: Socket is dead, restarting...

Between disconnections I receive only few live data events:

Live: 28.05.2021 16:54:57|804
Live: 28.05.2021 16:55:02|814
Live: 28.05.2021 16:55:15|783
Live: 28.05.2021 16:55:20|780
Live: 28.05.2021 16:55:31|868
Live: 28.05.2021 16:55:39|836
Live: 28.05.2021 16:55:48|812

Definitely not “live data” - time (local time zone)|symbols

For me it looks like server is overloaded, because data is not sent regularly and malformed framed are simply cut (server does not sent all data)