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 14, 2026, 7:48 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 | 26% | 78% | Download failure (54%) |
| South Korea | 14% | 53% | Download failure (96%) |
| Brazil | 6% | 72% | Manifest file failure (45%) |
| France | 6% | 59% | Download failure (69%) |
| United Kingdom | 4% | 74% | Download failure (54%) |
| Germany | 4% | 64% | Download failure (40%) |
| Argentina | 4% | 63% | Download failure (48%) |
| Spain | 4% | 49% | Manifest file failure (62%) |
| Japan | 4% | 87% | Download failure (66%) |
| Saudi Arabia | 4% | 57% | Manifest file failure (54%) |
| Netherlands | 3% | 76% | Manifest file failure (44%) |
| Thailand | 3% | 37% | Backend refusal (83%) |
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% | 69% | Download failure (55%) |
| Android | 37% | 64% | Manifest file failure (50%) |
| Electron | 0% | 100% | Set failure (100%) |
Failures
Top failure reasons
Download failure accounts for 45% 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 failure45%
The bundle download was interrupted — usually a network timeout, drop, or CDN reachability issue. Devices retry on the next launch.
-
02
Manifest file failure25%
A delta update file could not be fetched. Brief network issues or a missing asset are the usual causes; devices retry automatically.
-
03
Backend refusal11%
Capgo rejected an outdated updater (v4). Those devices need a store build with a newer plugin — not a transient outage.
-
04
Unzip failure6%
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 | 24% | 89% | Download failure (90%) |
| 8.51.13 | 11% | 54% | Download failure (42%) |
| 8.45.8 | 9% | 78% | Download failure (59%) |
| 8.43.10 | 6% | 83% | Download failure (47%) |
| 8.51.3 | 5% | 55% | Manifest file failure (65%) |
| 8.43.2 | 5% | 83% | Download failure (71%) |
| 7.45.10 | 5% | 77% | Download failure (62%) |
| 7.50.1 | 4% | 53% | Download failure (84%) |
| 8.50.2 | 4% | 44% | Manifest file failure (79%) |
| 7.42.3 | 2% | 80% | Download failure (83%) |