Start with the reported time
If someone said “it froze around the 1:58 mark”, note that point before you open the report. Without a reference, look for the stretches where the diagnosis flagged network, rendering or encoding.
Cross-check the charts at the same minute
| What changed at the same time | Likely reading |
|---|---|
| bitrate dropped on every destination | input or local upload |
| only one platform reconnected | key, ingest or route for that output |
| CPU/GPU went up and encoding fell behind | machine with no headroom |
| render skipped went up in OBS | the scene or the game took over the GPU |
| audience dropped with no technical metric | content, player delay or incomplete data |
Correlation doesn't prove cause. A CPU spike in the same minute is a clue; the report calls it a likely cause because it can't see the router, the platform's server or each viewer's player.
Mark it during your next stream
Use Mark this moment when you notice stuttering, a heavy scene switch or a platform dropping. The marker shows up on the timeline and narrows the search later.
If you need to send the case, export the report or a safe diagnostic. Never send a stream key or the whole logs folder.