Identify the event stream rather than only the channel
RTBF’s July 2026 playback help explains that each programme has its own live item, aligned with television timing and a margin of about ten minutes before and after the expected slot. That is a timed event stream, not a personal recording guaranteed to remain available until every delayed viewer reaches its end. Keep the specific live item with a support report.
Account for a paused viewing position
The publisher explicitly names pausing or going back in the live stream as reasons the stream can stop before the viewer reaches the programme’s end. A delayed viewing position and the live item’s scheduled end are different clocks. If a viewer pauses for a break, resuming later does not establish that the service has extended the event window by the same amount.
An overrun can be another explanation
RTBF also says a live event, notably sport, can exceed its planned duration without Auvio’s timing having been adapted. Record whether the live programme itself ran late, rather than attributing every cutoff to the household network. The explanation does not prove the cause of an individual interruption, but it identifies a publisher-documented scheduling question worth distinguishing from buffering.
Find a separate replay where offered
After an event cutoff, inspect the programme’s actual replay offering rather than assuming the expired live item is a permanent archive. Availability and publication time remain programme-specific. Preserve the event, planned slot, approximate pause or rewind and point of cutoff for RTBF support. This article interprets the service’s published window; it does not measure an event stream or promise that a complete replay exists.
Questions, answered
Does pausing extend the live item’s scheduled end?
RTBF’s help warns delayed viewers can reach the event window’s end first.
Does this prove every cutoff is a scheduling issue?
No. Record the actual symptom and timing before drawing that conclusion.