✓ REAL DATA · Source: ex_algento.botim_pd.ads_botim_meet_call_quality_stats_di · Grafana “Meet Dashboard” (StarRocks) · daily · iOS · 2026-04-15 to 06-21
← Lighthouse Briefings · Analysis · Meet 4.11.0 iOS SDK · 2026-06-22
Meet · client_version 4.11.0 Call level · iOS daily trend REAL DATA

Meet 4.11.0 iOS SDK — bad-call rate halved, call success down ~5.6pp

4.11.0 shipped an iOS-only Meet SDK change. Daily on iOS, the 4.11.* bad-call rate settles around 31% versus ~59–63% for the older lines; over the same versions call success sits ~73–74%, below the ~78% old/4.10 baseline. Android (no SDK change) is flat.
Window
2026-04-15 → 06-21
iOS bad-call rate
~59% → ~31%
iOS call success
~78% → ~73%
Android (control)
bad-call ~63% flat

01 What happened

Meet 4.11.0 shipped an iOS-only SDK change; Android did not receive it. Versions are grouped into three daily series: old (pre-4.10, i.e. 4.4–4.9), 4.10.*, and 4.11.* (4.11.0–4.11.3, carrying the SDK change).

On iOS, once 4.11.* reaches daily volume (from 06-06), its daily bad-call rate sits at ~30–35%, while old and 4.10.* ride ~58–63% across the same days. The in-call transport sub-signals move with it (version-aggregate: socket_slow 26.6% → 3.2%, slow_join 10.8% → 0.5%, audio_freeze 13.0% → 0.4%).

Over the same versions, the iOS daily call-success rate for 4.11.* sits at ~73–74%, below the ~78% old/4.10 baseline (version-aggregate: 78.7% → 73.1%, i.e. join_failed 21.3% → 26.9%). On Android over the same window every one of these metrics is flat (bad-call 64.2% → 63.3%, call success 79.8% → 79.9%).

02 Data

iOS · call-volume share by version group · 100% / day Source: ads_botim_meet_call_quality_stats_di
old (4.4–4.9) 4.10.* 4.11.* (SDK change)
iOS rollout: 4.11.* rises from ~0% (06-06) to ~87% of daily calls by 06-21; old and 4.10.* recede in step. No volume floor (full population).
iOS · daily bad-call rate · by version group Source: ads_botim_meet_call_quality_stats_di
old (4.4–4.9) 4.10.* 4.11.* (SDK change)
One point per day. A group is plotted only on days it has ≥1,000 iOS calls (so 4.10.* starts 05/15, 4.11.* starts 06/06). 4.11.* settles ~31%; old and 4.10.* stay ~58–63%.
iOS · daily call-success rate · by version group Source: ads_botim_meet_call_quality_stats_di
old (4.4–4.9) 4.10.* 4.11.* (SDK change)
Same grouping and volume floor. 4.11.* tracks ~73–74%, below the ~78% old/4.10 band.
All bad-call sub-signals · daily trend · iOS · by version group Source: ads_botim_meet_call_quality_stats_di
old (4.4–4.9) 4.10.* 4.11.* (SDK change)
Join failed
Socket failed
Socket slow
Slow join
High RTT
Very high RTT
Audio freeze
Video freeze
Audio loss
Video loss
bad_call_total is the de-duplicated union of these flags (a call trips one or more). On 4.11.* every sub-signal collapses except join_failed, which stays ~25–26% (the call-success regression). y-axis auto-scaled per panel; same ≥1,000-call/day floor.

iOS · version-aggregate · 4.10.x vs 4.11.0 vs 4.11.1 (call level)

Metric (%) 4.10.x 4.11.0 4.11.1 4.10.x → 4.11.0
Call success78.7473.1174.59−5.63pp
join_failed21.2626.8925.41+5.63pp
Bad-call rate59.4231.9531.62−27.47pp
socket_slow26.603.234.10−23.37pp
slow_join10.770.480.91−10.29pp
audio_freeze13.010.440.88−12.57pp
calls (n)5,391,956558,9551,287,672

Android control · flat across versions (call level)

Metric (%) 4.10.x 4.11.0 4.11.1 4.11.2
Call success79.7979.8880.2580.55
Bad-call rate64.2363.3263.5262.93
socket_slow34.5533.9934.0533.73
calls (n)3,616,36336,931163,940211,998
Platform code follows the warehouse convention device_type 0 = iOS, 1 = Android. Note: the Grafana “Meet Dashboard” panel SQL labels these inverted (device_type=0 → Android); figures here use the corrected mapping.

03 Observed scope

04 Investigation

Status
Data-only briefing · owned by VoIP Quality
Tracking
PB / GH backlink to be added.
Analysis
Root cause, hypotheses, and follow-ups are tracked in PB — not in this briefing.