Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Separate connection identity from one address
QUIC uses connection identifiers which can allow a connection to survive a change in endpoint IP address or port. RFC 9000 describes connection migration and path validation, including constraints around handshake completion and permitted active migration. This is a different question from whether an application simply uses UDP. The existence of migration in a standard does not establish that a particular media session or client supports the transition the viewer attempted.
Describe a network transition accurately
For an original observation plan, record a permitted playback session before a deliberate move between two available networks. Note the time of the network change and whether the application continued, paused or established a new session. Retain any transport diagnostics the application legitimately exposes. A brief continuation could reflect buffered media rather than successful migration, while a pause could have several causes. Do not infer the transport result from the picture alone.
Keep the new path as a separate condition
The standard notes that a new path may not support the previous sending rate, and migration involves renewed path related state. Therefore a successful connection transition would not prove identical performance on the new network. It also would not override account or territorial conditions imposed at the application layer. This article supplies vocabulary for a transition report and makes no claim that UK IPTV uses QUIC or supports movement between networks without interruption.