New Google Home Speaker Bug Drives Hundreds of Gigabytes in Downloads
Some owners of the new Google Home Speaker are seeing constant background downloads totaling hundreds of gigabytes, including one case of more than 200GB in a single day The Verge. That volume is far above normal idle traffic for a smart speaker. Only a subset of units appears to be affected.
The reports surfaced over the last week in Reddit posts and in reporting by 9to5Google. 9to5Google published its account on Oct. 19, 2026 9to5Google. Most reports tie specifically to the new Home Speaker model.
Router data shows the difference clearly. One affected device used 132GB over the past month. An unaffected Home Speaker used just 2GB over the same period. The 200GB in one day report sits well above even that elevated level.
The suspected cause is a firmware update, the low-level software that runs the speaker, failing to download and install correctly. Google told 9to5Google that a fix is already rolling out.
The broader context here matters for anyone who runs connected devices at home or at work. An always-on device with automatic updates needs strict guardrails around its updater, known as OTA, or over-the-air, delivery. Download checks, retry limits, increasing delays between tries, and server-side throttling are standard practice. In my view, the key question is not that a retry loop can happen. It is why this one could move hundreds of gigabytes without warning the user or pausing itself.
Looking at what this means for owners who watch their networks, detection came from the router rather than the companion app. Users spotted the anomaly in router dashboards and usage meters. That pattern will be familiar to infrastructure teams, since endpoints often show little about update status. For tech-minded households, it is a reason to keep per-client traffic history enabled, even when a router defaults to a combined view.
On the practical side, there is also a cost angle beyond annoyance. On unmetered fiber the extra transfer may stay invisible until logs are checked. On metered or capacity-constrained links it can crowd out legitimate traffic and push a household toward overage charges. Capping background update traffic and asking for user confirmation after repeated install failures would prevent most of that harm without slowing normal patch speed.
The encouraging part is the response path. A server-controlled rollout can stop a faulty update and push a correction without user action. If that control plane works as described, most affected units should settle back to baseline traffic without manual resets or returns. For a category that lives in kitchens and bedrooms and is expected to simply work, quiet recovery matters as much as quiet operation.
