In this guide
Use a connection-specific intervalSeparate transport recovery from application retryAdd the media consequenceA retransmission indicates transport recovery activity. With TCP’s reliable ordered service, an application can receive correct media bytes after a delay. The visible consequence may be slower delivery or no visible consequence if the player has enough buffer.
A counter alone therefore cannot prove that a video decoder received damaged frames. It also cannot tell you which router, wireless link or endpoint introduced the condition.
Use a connection-specific interval
Record the relevant media connection and counter values before and after the affected interval where supported diagnostics permit. Avoid attributing system-wide cumulative retransmissions to one player. Note whether the connection was reused, closed or replaced during the observation.
In an original hypothetical sample, a segment request takes four seconds instead of its usual one second while transport recovery occurs. If the player had twenty buffered seconds, playback may continue smoothly. If it had only two seconds, the same delay can contribute to an underrun. The counter’s existence is not the entire playback explanation.
Separate transport recovery from application retry
A player requesting the same URL again after a 503 response has made an application-level retry. TCP retransmitting transport data within an existing request is another mechanism. Logs can show both, but the word retry should retain its layer.
Likewise, a TCP segment is not an HLS segment. A finite HLS resource can span many network packets. Counting one retransmitted packet as one lost video segment would distort both the transport and media evidence.
Add the media consequence
Compare request completion, media duration and playable buffer trend over the same interval. If data arrived correctly and in time, report recovery without claiming a visible failure. If requests became late and the buffer emptied, report the correlated sequence while leaving the loss location unresolved.
If the picture shows persistent corruption despite successful complete delivery, preserve decoder errors and media structure evidence rather than assuming the retransmission counter explains it. Valid reliable delivery does not certify that the source’s encoded media was valid before transmission. A useful report keeps source validity, transport recovery and presentation behavior as separate findings.
| Observed event | Layer |
|---|---|
| Lost data retransmitted within a connection | TCP recovery |
| Player requests the resource again | Application retry |
| Complete bytes fail to decode | Media/decoder investigation |
| Late bytes exhaust playable buffer | Delivery deadline consequence |