Check What the Speaker Uses When You Aren’t Listening

A Wired reporter checking household internet usage found that a Google Home Speaker had consumed 487 GB in ten days. That was nearly as much data as the rest of the home used between August and September. Google told Wired that a server misconfiguration had caused some speakers to download a software update repeatedly. The company said it had resolved the issue.

The explanation matters because an enormous traffic total does not establish that a speaker recorded conversations or uploaded private audio. Google described repeated downloads, not a newly discovered recording function. The account also does not establish a defect in every speaker. The speaker developed an appetite outside its job description, but the documented meal was software.

For a buyer, the useful question extends beyond whether Google fixed the bug. A connected product uses a connection someone else pays for. If an internet plan has a data cap, unnecessary downloads can consume an allowance intended for work, entertainment, and other household needs. An unlimited plan changes that calculation. Wired’s account does not establish an overage charge, and heavy data consumption alone does not prove that other devices suffered slower service.

Check what your router can actually show

Finding the culprit can carry its own cost. The reporter’s Eero setup listed connected devices without a subscription but did not provide per-device usage totals at that tier. Wired also described Asus routers that provide traffic analysis without a subscription. Those are different purchasing propositions: access to your own network’s measurements can be included with the hardware or reserved for a paid service. A speaker problem should not automatically become a router subscription.

Start with the router or internet provider tools you already have. Check whether they show individual devices, usage totals, and the measurement period. Confirm the device’s identity before assigning blame; an unfamiliar label is not a diagnosis. If the tools allow it, compare traffic across similar periods before and after temporarily disconnecting a suspected speaker. Disconnection also removes its useful functions, so treat that step as a test rather than a universal remedy.

If your plan has a cap, compare the provider’s billing-period total with any available device-level figures, and keep dated records of unexplained spikes. If a Google Home Speaker still shows excessive traffic after Google’s reported fix, take those records to support rather than assuming the old bug remains the cause. If usage looks ordinary and your allowance is comfortable, this report alone is not a reason to replace working equipment.