Home networks and live TV: a quick pre-flight checklist

Start with path isolation: can the subscriber reproduce the issue on a single device wired directly to the router, with VPNs disabled and no ‘smart’ parental filters in the path? If yes on wired but no on Wi‑Fi, you have a LAN problem—not a feed problem.

DNS filtering and ad blockers sometimes break hostnames used for manifests or time services. Ask for a temporary switch to provider-default DNS as a controlled test; document the outcome rather than debating brands.

Double-NAT and carrier-grade NAT can interact badly with certain session timers. You do not need to become a ISP—but recognising the pattern (game consoles strict NAT plus IPTV glitches) points you quickly toward bridge mode or a single router boundary.

IPv6-only or broken IPv6 tunnels occasionally cause odd routing on some ISPs. A pragmatic test is IPv4-only on the router for a short window, if the household can tolerate it, to see if behaviour changes.

Close the loop with numbers: measured download headroom during peak hours, packet loss to a nearby major POP if the customer can run it, and whether other real-time apps (gaming, VoIP) show jitter at the same times. Facts reduce ping-pong tickets.