Amazing, @Frederik — thanks for
Amazing, @Frederik — thanks for confirming it's an issue on your end, and we're looking forward to a fix! 
.getWebSocketsAutoResponseTimestamp(mysocket) is too old. There have definitely been more recent ping/pongs that our clients have received from the auto-response, but it looks like the last auto-response timestamp still isn't reliably getting updated .getWebSocketsAutoResponseTimestamp() bug seemed to be fixed briefly yesterday afternoon, but today the bug is back again. Was a roll-out attempted but rolled back, perhaps?.getWebSocketsAutoResponseTimestamp(mysocket).getWebSocketsAutoResponseTimestamp()