But seriously, no, no other reports of DNS issues
But seriously, no, no other reports of DNS issues

client disconnected error. 
ping text message should do the trick. You'd just need to modify your server code to ignore that message.https://websockets.readthedocs.io/en/stable/topics/keepalive.html
Browsers don’t enable a keepalive mechanism like websockets by default. As a consequence, they can fail to notice that a WebSocket connection is broken for an extended period of time, until the TCP connection times out. [...]
Unfortunately, the WebSocket API in browsers doesn’t expose the native Ping and Pong functionality in the WebSocket protocol. You have to roll your own in the application layer.


__cf_bm cookie is causing our Tiered Cache implementation to be skipped because there's a Set-Cookie header that we have zero control over apparently.client disconnected