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 signed counter is not a physical packet factory
Consider an invented reporting interval with one hundred expected sequence positions and one hundred and two received packets after the receiver applies the relevant reporting rules. The subtraction expected minus received is minus two. This does not mean a network recovered two missing packets by creating new content. Extra received instances can include duplicates, and late arrivals can alter a later observation. The displayed field must be interpreted according to its actual definition rather than the everyday meaning of the word loss.
Check which loss number the interface exposes
RFC 3550 permits the cumulative loss count to be negative under its counting rules. Its interval fraction handling is different: a negative loss for that calculation is reported as zero, rather than a negative fraction. A dashboard could also clamp, aggregate or relabel values, so identify whether you have the raw signed field or a processed display. Do not treat a signed cumulative count and an independently calculated percentage as interchangeable measurements simply because both appear under a loss heading.
Keep the evidence useful
Record the source, report period, expected and received counts if available, and any evidence of duplication or reordering. A negative value alone does not reveal where duplicates originated or whether playback was affected. It also does not cancel a separate observation of missing or unusable media. If the purpose is to investigate a picture freeze, connect the report time to that symptom and collect the player error separately. No duplicate traffic or negative counter was observed on a UK IPTV account for this explanation.