Record the interruption
Note when the stream stopped, when it resumed and whether the target remained the same. Keep the order reference and visible status with this timeline. A single screenshot after reconnection cannot explain how long the broadcast was unavailable.
Read the applicable condition
Check what the selected offer says about interruptions, resumptions and included time. Do not assume that a timer pauses or resets automatically. If the terms are unclear, ask support how the recorded event affects the request.
Keep follow-up work separate
Before ordering an extension or replacement, resolve what remains under the existing request. Otherwise the two periods may overlap or be charged under different assumptions. Preserve the original timeline even after the stream returns to normal.
Decision checklist
| Decision | What to check |
|---|---|
| Timeline | Disconnect and reconnection times |
| Terms | How interrupted time is treated |
| Follow-up | Remaining scope before another request |
Worked example
In an illustrative hour-long broadcast, a connection loss creates a twelve-minute gap. Record the actual times and ask how that gap is treated; do not automatically claim twelve replacement minutes without checking the service terms.
Example figures explain the decision; they are not current prices or promised results.