Why an explicit boundary exists
A presentation may join material with different timestamp sequences, track arrangements or encoding characteristics. The playlist can mark a boundary so that a player does not interpret the following segment as an uninterrupted continuation of the previous decoding state. RFC 8216 specifies which changes require or recommend this marker.
The useful distinction is between the media timeline and the connection. All HTTP requests could succeed while the player mishandles a timestamp transition. Conversely, a failed segment request can occur far from any marked boundary. A visible pause alone cannot distinguish those situations.
Counting the boundary correctly
A segment's discontinuity sequence is formed from the playlist's EXT-X-DISCONTINUITY-SEQUENCE value plus the number of preceding discontinuity tags. For example, a base value of seven followed by two such boundaries places a later segment in discontinuity sequence nine. This is an identifier, not nine seconds of delay.
As old entries leave a live window, the publisher has to preserve meaningful discontinuity numbering for the remaining material. Otherwise, an unchanged segment could appear to belong to another timeline. That is why removing an old marker is more consequential than deleting an ordinary comment.
Evidence that narrows a transition fault
For a repeatable pause, identify the content position and whether it occurs when material changes. A publisher or player developer can compare the neighbouring segments, their timestamps, the discontinuity marker and the responses that delivered them. This provides a narrower investigation than a general report that every advert buffers.
A viewer should avoid deleting the marker from a playlist to suppress an error. Removing the description does not repair the underlying timeline. Where playback controls permit, record whether a restart after the boundary succeeds, and keep the exact player version so the recipient can investigate the appropriate implementation.
Questions about this guide
Does a discontinuity mean a corrupt stream?
No. It can describe a legitimate transition. Incorrect marking or handling can cause problems.
Can it explain a failure at exactly the same boundary?
It can guide investigation, but timestamps, media changes and request results still need checking.