A dual-stack network supports both IPv4 and IPv6, and connection setup may involve trying alternative addresses. If one path responds poorly, startup can take longer even when playback is stable afterward. Check whether the delay happens before media starts, after every channel change or throughout viewing. Use supported diagnostics to compare address families and record the affected hostname. Do not assume that changing DNS or disabling a protocol everywhere is the correct response to every slow start.
Locate the delay in startup
Measure roughly how long the player waits before showing its first picture, and note whether a loading indicator continues once video begins. A slow initial connection differs from a stream that repeatedly exhausts its buffer. Authentication, a fresh licence or server processing can also delay startup. Compare another source in the same player to see whether the pattern belongs to one endpoint. Keep that evidence separate from an idle speed test that never exercises the same request sequence.
Understand alternative connection attempts
A dual-stack hostname may offer addresses for both families. Clients differ in how they schedule and fall back between connection attempts, so identical network settings can produce different behaviour across apps. An address record existing is not proof that its route is healthy. If a supported diagnostic can test each family independently, record lookup and connection outcomes. Do not equate a successful IPv4 browser visit with evidence that the player chosen IPv6 route is equally successful on its own.
Avoid a broad permanent workaround
Record original network settings before any documented family-specific comparison. Prefer a device-level test and return the configuration afterward. If one route repeatedly adds delay, send the responsible support team timestamps and the hostname rather than private tokens or a full playlist. If both routes connect promptly, investigate the next startup stage instead. The goal is to isolate an address-family issue, not to leave the entire home in a changed state after a single coincidental improvement during testing.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
For example, one app might wait before every channel start but then play smoothly. A repeatable timeout on the affected IPv6 endpoint alongside quick IPv4 connection would support a path investigation. It would not explain picture judder that continues after media is already arriving steadily.
Questions about this topic
Does dual-stack always make startup slower?
No. Behaviour depends on working routes and client connection handling.
Can two players behave differently on one network?
Yes. Their address selection and fallback implementations can differ.
