WebSocket closed with 1006: why trading bots lose connection without an error code

Short summary

WebSocket 1006 (abnormal closure) occurs when TCP drops without a close frame—typically from proxy timeouts, rate limiting, or network issues. You can't prevent 1006 but can handle it safely: implement application-level heartbeats (ping/pong every 10–15 seconds), use exponential backoff with jitter on reconnect, and re-sync only missing state rather than aggressively reconnecting. Log patterns and time gaps, not raw errors, to diagnose root cause.

• •1006 is a TCP disconnect without a WebSocket close frame, not a bug—caused by proxy idle timeouts, rate limiting, or infrastructure events
• •Prevent detection delays with application-level heartbeats every 10–15 seconds; implement exponential backoff + jitter on reconnect
• •Re-sync only changed state post-reconnect; log patterns and message gaps to distinguish idle timeouts from sudden drops

Generated with AI, which can make mistakes.