Inspector — your stream history
Studio → Inspector keeps a record of every time your encoder connected — broadcasts and bandwidth tests, which appear nowhere else.
Use it to answer questions the live page can’t: was last night actually unstable, or did it just feel that way? Did I drop, or was I kicked?
The session list
Sessions are listed newest first. If you’re publishing right now, that session is pulled out at the top with a live-updating chart. Each row shows:
- When it started, and how long it lasted
- A TEST chip if it was a bandwidth test
- Your encoder, resolution and frame rate
- How many unstable events were recorded
- A health icon — green if the session was clean, amber if something needs attention
A session in detail
Open a session for the full picture.
The chart
Bitrate and jitter over time. Drag across the chart to zoom into a window; zooming re-fetches finer detail rather than just stretching what’s on screen. Long sessions are summarised into a fixed number of points, and the chart tells you when you’re looking at a downsampled view.
The spec sheet
| Reading | Flagged when |
|---|---|
| Video codec, profile, level | — |
| Resolution and frame rate | — |
| Keyframe interval (GOP) | Above 2.5 seconds |
| Audio codec, sample rate, channels | — |
| Average, minimum, maximum and peak bitrate | Over your limit |
| Bitrate stability | Variation above 15% |
| Arrival jitter | Above 50 ms |
| Timestamp anomalies, unstable events | Any |
These are the same thresholds the Go Live page uses while you’re streaming, so a session never looks healthy live and unhealthy afterwards.
Why the session ended
If a session didn’t end because you stopped it, Inspector says why:
| Reason | What it means |
|---|---|
| Client | Your encoder closed the connection — you pressed Stop, or OBS gave up. |
| Timeout | Data stopped arriving and the connection timed out. Usually a network drop. |
| Kicked | The platform stopped your stream — most often the bitrate hard limit. |
| Protocol error | The stream sent something the ingest couldn’t accept. |
| Refused | The publish was rejected at connection time — see why a publish was refused. |
| Shutdown | The ingest server was restarted. |
| Abandoned | The session was left open with nothing arriving and was closed later by housekeeping. |
Session ID
Each session has a Session / Stream ID with a copy button. Quote it when you contact support — it’s the fastest way for staff to find exactly the broadcast you mean.
How long history is kept
Sessions are kept for about two weeks (14 days by default) and are then deleted along with their charts. If you want to keep evidence of a bad night — screenshot the chart or note the session ID before it ages out.