Our data
Live Update delivery data
Last 30 days of Capgo install success. Each rate uses app, device, and UTC-day outcomes — overall and by country, platform, and updater version. We publish failures too, with plain-language explanations from our docs.
Updated Aug 25, 2026, 1:24 AM UTC
Success rate
Daily install success
Each outcome is one app, device, and UTC day. If that combination eventually installs, it counts as success.
Success rate
68%Window
30 daysScope
All appsGeography
Success by country
Share of active devices, success rate, and leading failure by country. Success uses app/device/UTC-day outcomes.
| Country | Usage | Success | Top failure |
|---|---|---|---|
| United States | 30% | 78% | Download failure (49%) |
| South Korea | 12% | 54% | Download failure (96%) |
| France | 7% | 60% | Download failure (47%) |
| Brazil | 6% | 68% | Manifest file failure (52%) |
| Germany | 4% | 67% | Manifest file failure (64%) |
| Russia | 4% | 38% | Manifest file failure (91%) |
| Japan | 4% | 93% | Download failure (74%) |
| Netherlands | 3% | 71% | Manifest file failure (50%) |
| Thailand | 3% | 36% | Backend refusal (95%) |
| Argentina | 3% | 66% | Manifest file failure (51%) |
| Spain | 2% | 53% | Manifest file failure (56%) |
| Mexico | 2% | 47% | Manifest file failure (72%) |
Platforms
Success by device type
Share of active devices, success rate, and leading failure by platform. Success uses app/device/UTC-day outcomes.
| Platform | Usage | Success | Top failure |
|---|---|---|---|
| iOS | 67% | 73% | Download failure (50%) |
| Android | 34% | 58% | Manifest file failure (64%) |
| Electron | 0% | 100% | Set failure (100%) |
Failures
Top failure reasons
Download failure accounts for 34% of failures in this window.
Many failures are normal on real devices — flaky networks, intentional channel policies, and automatic rollbacks all show up here. We keep the list public so you can trust the numbers.
Code meanings follow our logs docs.
-
01
Download failure34%
The bundle download was interrupted — usually a network timeout, drop, or CDN reachability issue. Devices retry on the next launch.
-
02
Manifest file failure34%
A delta update file could not be fetched. Brief network issues or a missing asset are the usual causes; devices retry automatically.
-
03
Backend refusal18%
Capgo rejected an outdated updater (v4). Those devices need a store build with a newer plugin — not a transient outage.
-
04
Checksum failure5%
Downloaded bytes did not match the expected checksum, so Capgo discarded the update rather than risk a bad install.
-
05
Update failure5%
The bundle installed but the app never called notifyAppReady(), so Capgo rolled back automatically for safety.
-
06
Finish download failure3%
The download did not complete cleanly before install could start — typically connectivity or storage pressure mid-transfer.
-
07
Unzip failure2%
The device could not unpack the bundle archive — often low storage or a corrupted download.
-
08
Set failure1%
The device downloaded the bundle but failed to activate it as the next version.
Updater
Updater versions
Share of active devices, success rate, and leading failure by updater version. Success uses app/device/UTC-day outcomes.
| Version | Usage | Success | Top failure |
|---|---|---|---|
| 8.49.1 | 23% | 89% | Download failure (82%) |
| 8.45.8 | 10% | 97% | Download failure (87%) |
| 5.9.5 | 5% | 9% | Decrypt failure (100%) |
| 8.50.2 | 5% | 42% | Manifest file failure (80%) |
| 8.43.10 | 5% | 92% | Download failure (50%) |
| 7.45.10 | 4% | 91% | Download failure (86%) |
| 5.45.10 | 4% | — | Update failure (100%) |
| 7.50.1 | 3% | 46% | Download failure (50%) |
| 7.42.3 | 3% | 86% | Download failure (87%) |
| 8.43.2 | 3% | 82% | Download failure (85%) |