How to set SRT latency and buffer correctly
Why extra buffer can recover lost packets, how RTT affects the setting, and sensible values for stable and mobile networks.
Read statistics and tune your connection
While a stream is active, the dashboard shows live metrics. Longer history and sessions live under Usage – streaming hours for loyalty points also come from there.
Live metrics on the dashboard
- Bitrate (kbps) – current incoming bitrate at the relay
- Latency (ms) – SRT buffer latency between app and relay
- Packet loss (%) – below 1% ideal, above 5% critical
- RTT (ms) – round-trip time sender ↔ relay
How to read the values
Rules of thumb: Packet loss above 5% → unstable link: raise SRT buffer, check bonding, or lower bitrate. Above 30%, even SRT often cannot fully compensate.
- High RTT + high buffer = noticeable delay, but often more stable
- Bitrate collapses → check encoder, network or app
- Panel looks fine, destination stutters → more often push/destination or codec
Usage
Under Usage you see longer history and sessions. That feeds streaming hours into the loyalty system – the panel display remains authoritative.
Next steps
- SRTLA bonding when a single link is weak
- Best practices for codec and buffer
- Status page for sudden outages