Media diagnostics · Primary-source explanation; no UK IPTV implementation or account test. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
A twenty millisecond round trip can be asymmetric
Imagine a packet taking three milliseconds from a home device to a remote endpoint and seventeen milliseconds on the return journey. Ignoring endpoint processing for this simplified example, the round trip is twenty milliseconds. Half is ten milliseconds, which matches neither actual direction. A second path taking ten milliseconds each way has the same round-trip total. The total alone cannot tell these two cases apart. These are invented timings, rather than a diagnosis of a particular broadband connection.
Choose the observation that answers the question
A round-trip observation remains useful for comparing the same endpoint over time, provided the method and conditions are recorded. It simply cannot identify the outbound and inbound contributions on its own. One-way measurement needs timestamps with known clock relationships and a defined packet type, source, destination and interval. RFC 7679 explains why directional measurements matter, including cases where routes or treatment differ between directions. A player downloading media may also interact with endpoints other than the target used by a simple echo test.
Report an estimate as an estimate
Write twenty milliseconds round trip when that is what the tool measured. If a calculation requires ten milliseconds as an assumed one-way value, label the symmetry assumption beside it. Do not turn the estimate into a claimed measured media delay. Programme latency can include encoding, packaging, buffering, decoding and display time as well as network transit. Separating these quantities gives support a specific observation to investigate instead of an apparently precise but unsupported explanation for late pictures.