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 Sep 7, 2026, 11:52 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
67%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 | 28% | 78% | Download failure (53%) |
| South Korea | 14% | 49% | Download failure (97%) |
| France | 6% | 59% | Download failure (59%) |
| Brazil | 5% | 70% | Manifest file failure (53%) |
| Germany | 4% | 62% | Download failure (35%) |
| Argentina | 4% | 65% | Update failure (34%) |
| Japan | 4% | 88% | Download failure (66%) |
| Saudi Arabia | 4% | 61% | Manifest file failure (60%) |
| United Kingdom | 3% | 71% | Download failure (52%) |
| Spain | 3% | 46% | Manifest file failure (63%) |
| Netherlands | 3% | 74% | Manifest file failure (45%) |
| Thailand | 3% | 32% | Backend refusal (87%) |
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 | 64% | 70% | Download failure (53%) |
| Android | 37% | 61% | Manifest file failure (55%) |
| Electron | 0% | 100% | Set failure (100%) |
Failures
Top failure reasons
Download failure accounts for 41% 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 failure41%
The bundle download was interrupted — usually a network timeout, drop, or CDN reachability issue. Devices retry on the next launch.
-
02
Manifest file failure27%
A delta update file could not be fetched. Brief network issues or a missing asset are the usual causes; devices retry automatically.
-
03
Backend refusal14%
Capgo rejected an outdated updater (v4). Those devices need a store build with a newer plugin — not a transient outage.
-
04
Unzip failure5%
The device could not unpack the bundle archive — often low storage or a corrupted download.
-
05
Cannot get bundle5%
Capgo could not build a valid download URL for the selected bundle.
-
06
Update failure5%
The bundle installed but the app never called notifyAppReady(), so Capgo rolled back automatically for safety.
-
07
Checksum failure4%
Downloaded bytes did not match the expected checksum, so Capgo discarded the update rather than risk a bad install.
-
08
Finish download failure2%
The download did not complete cleanly before install could start — typically connectivity or storage pressure mid-transfer.
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 | 25% | 89% | Download failure (91%) |
| 8.45.8 | 9% | 81% | Download failure (58%) |
| 8.43.10 | 6% | 84% | Download failure (45%) |
| 8.51.13 | 6% | 38% | Cannot get bundle (45%) |
| 7.45.10 | 5% | 82% | Download failure (65%) |
| 8.51.3 | 5% | 52% | Manifest file failure (74%) |
| 8.43.2 | 5% | 85% | Download failure (71%) |
| 7.50.1 | 4% | 51% | Download failure (72%) |
| 8.50.2 | 4% | 43% | Manifest file failure (80%) |
| 7.42.3 | 3% | 82% | Download failure (85%) |