Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Follow the fetching state
A browser can have enough previously obtained media to advance while no new media request is active. The networkState property describes the media element fetching activity. MDN lists empty, idle, loading and no source states. In particular, NETWORK_IDLE describes an active element with a selected resource which is not using the network at that moment. Reading idle as disconnected would confuse an application state with the condition of the entire connection.
Use two observations together
For an original diagnostic example, suppose the position advances from ten to fifteen seconds while networkState remains idle in two samples. That is consistent with playback using already available data; it is not proof of a five second network outage. Conversely, loading only says downloading is taking place. It does not establish that the material is arriving early enough, that the decoder accepts it, or that the selected programme is correct.
Record the transition instead of refreshing blindly
Write the symbolic state, media position and visible symptom before taking an action. Then record whether idle changes to loading as playback continues. If no source is reported, inspect source selection rather than repeatedly restarting a router. This procedure gives a developer a narrower question: was fetching intentionally paused, still active, or unable to select a source? It does not turn one property into a complete explanation of a streaming failure or an account entitlement check.