Connection Induced Rebuffering Ratio (CIRR) measures the percentage of total video viewing time (playTime plus all rebuffering) during which viewers experienced nonseek rebuffering or connection induced rebuffering.
-
seekRebufferingTime = R1
-
nonseekRebufferingTime= R2
-
rebufferingTime=R1 + R2
-
playTime=P1 + P2 + P3 + P4
The playTime is the total time during which the reported player-state is "playing". The nonseekRebufferingTime (R2) or CIRT is the total time during which the reported player-state is "buffering", and does not include the buffering time before the first frame of a video is displayed, buffering (R1) following user-initiated seeks (S1) and any paused time. The CIRT metric displays the total nonseekRebufferingTime during a specified interval for use in the Streaming Performance Index.
If rebuffering starts 10 seconds or more after seek end, this rebuffering is also counted as connection induced rebuffering (R2). Otherwise, it is counted toward seek-induced rebuffering (R1).
This metric aggregates the session rebuffering during the selected interval.
CIRR occurs when video playing outpaces the rate of buffering and the player needs to wait for the buffer to refill due to nonseek or connection-induced rebuffering. A high CIRR or a significant increase in this metric can be an indication of declining overall network performance and the likelihood of viewer abandonment.
Note: Zero CIRR Ended Plays % measures the percentage of ended plays which had zero connection induced rebuffering.
Connection Induced Rebuffering Ratio is available in the following formats:
- Connection Induced Rebuffering Ratio summary: the average CIRR is the total time spent in nonseek rebuffering divided by the total viewing time (playTime + rebufferingTime) during the selected time period.
- Connection Induced Rebuffering Ratio time series: a time series for the selected time period, where each point is the CIRR for all plays during that specific interval.
High Rebuffering (high CIRR or CIRT) is available as a Streaming Performance Index (SPI) threshold setting and displayed as an Improvement Opportunity in the Overview dashboard. Based on the SPI threshold setting, High Rebuffering also appears as a metric in Trends and other dashboards. For more details, see Overview Dashboard.
Distribution
- Ended Plays vs Connection Induced Rebuffering Ratio Distribution (only available in Custom dashboards): a distribution by preset buckets, where each bucket is the CIRR that occurred for the respective amount of Ended Plays. This distribution can help you to understand your audience tolerance for non-seek rebuffering and illustrates the actual impact of any non-seek rebuffering outliers on the average non-seek rebuffering.
- Play Duration vs Connection Induced Rebuffering Ratio Distribution (only available in Custom dashboards): a distribution by preset buckets, where each bucket is the CIRR range that occurred within the respective play durations. This distribution can help you to understand your audience tolerance for non-seek rebuffering and the actual impact of any non-seek rebuffering outliers on the average non-seek rebuffering.
You can use metric filtering to diagnose only the sessions that had high percentage of dropped frames. For more details on metric filters, see Metric filtering.
Related Support
|
Metric |
Description |
|---|---|
| Dashboards |
|
| Dimensions | Use MetricLens dimensions to filter this metric by metadata segments for enhanced root cause analysis. For example, limiting data to specific ISP and player dimensions can narrow the root cause of a higher Connection Induced Rebuffering Ratio to a known provider and player type. |
| Diagnostics |
The Diagnostic page presents detailed information about the Connection Induced Rebuffering Ratio and the specific errors in selected time ranges. You can also apply Filters to see where failures are occurring, for example by CDN/Resource and ASN, and which assets are affected most often. For more information about diagnosis with this metric, see Diagnostics. |
| Manual Alert Support |
Yes. Receive alerts when CIRR exceeds set limits based on customizable alert conditions. This event may fire multiple times per video view. For more information about setting alerts for this metric, see Alerts. |
| AI Alert Support | No. |
| Metric Adjustments |
If a session has continuous non-seek re-buffering for 90 seconds, the play is treated as expired. Conviva VSI Video reports the Connection Induce Rebuffering Time (CIRT) for the expired session as zero due to the session expiration, and reports the session as a Connection Induced Interrupted Play due to the rebuffering. Micro rebuffering, continuous rebuffering less than 200 milliseconds, is not excluded. |
For more metric definitions, see the Metric Dictionary.