This message was deleted.

This is a good suggestion Steven! I've added a ticket for this here. While it's tricky to detect for sure, we can definitely update that field the moment the client missed a ping timeout.

Great. Could livekit add specific reasons for the poor connection quality, such as high ping, slow internet, or reconnecting? During our tests, we've experienced sudden drops in connection quality (logged on RoomEvent.ConnectionQualityChanged) that result in false positive result when detecting reconnect state on remote participant (as mentioned before), as video streaming continues working on all participants.. This issue happens alot when being tested by my US coworker, but rarely happened in Indonesia, Singapore, Australia or Pakistan. This reason will help alot when debugging the issue.