Catch the busy minute
A game console that downloaded 80 GB yesterday may be doing nothing during today's frozen video call. A laptop uploading a small batch of photos could be the relevant device now. To find the source of a slowdown, match a device's current transfer rate to the moment the problem happens, then check whether pausing that transfer changes the experience.
This guide uses the eero mobile app on an existing home eero network, with access already set up for its owner or administrator. It covers internet traffic across wired and wireless devices. It does not require installing monitoring software on every computer or buying eero Plus.
There is one hard boundary: eero says live and historical data usage are unavailable in bridge mode. If another router handles your network and the eeros operate as access points, use that router's documented traffic view instead. Do not change routing mode just to expose a graph.
Start with the device reading, then widen the view
Open the app while the slowdown is happening. Leave the affected call or stream running if practical, and avoid starting a speed test during observation: that adds another large transfer. Keep a brief note of the time and symptom so you can compare the same situation after changing one thing.
- Open Devices in the eero app and tap a likely device. The Home tab also provides access to devices. Include Ethernet-connected computers and consoles in your search; a wired device can still consume the shared internet connection.
- On its device page, find Activity. Record both download and upload rates, keeping the displayed units. eero's monitoring instructions say live readings refresh every five seconds. Watch several refreshes rather than deciding from one number.
- Check the other plausible devices in turn. An idle reading is a momentary observation: streaming downloads arrive in bursts. A device can briefly appear idle even while someone is watching a programme.
For a simultaneous overview, eero's bandwidth instructions currently give this route: Home → Internet → the right arrow beside Uploaded Data → Show live usage, under Data Usage. The resulting Live Data Usage page shows total download, total upload and device activity.
If that route is absent, return to individual devices. Official eero pages also describe usage through the Activity tab, so their navigation descriptions are not completely aligned. Missing controls do not establish that traffic is zero. Confirm you have opened the intended network, check for an app update, and consult eero support if the documented device view is missing. Bridge mode remains a separate limitation.
Read the direction before blaming the largest number
Mbps describes a transfer rate; GB describes accumulated data. Neither is interchangeable with a Wi-Fi connection's advertised link speed. A device's large weekly download total cannot tell you whether it is occupying the connection this minute.
Hypothetical example: a household connection has about 100 Mbps of usable download capacity and 10 Mbps of usable upload capacity. The TV is receiving 15 Mbps while a laptop is sending 9 Mbps. The TV has the larger number, but the laptop is using roughly 90% of the available upload capacity. Pausing its optional upload is a more useful first experiment for an impaired outgoing call than switching off the TV.
Those capacities and readings are invented to explain the comparison, not measurements or a universal congestion threshold. Compare upload with upload capacity and download with download capacity. Do not run a fresh speed test alongside the transfers to establish spare capacity; it competes with them.
The usage screen identifies a device, not the particular app responsible. Once the laptop becomes a candidate, inspect its own open backup, sync or download applications. Avoid assuming that all traffic from a familiar device is expected, or that an unfamiliar name proves an intruder.
Turn an ambiguous name into a physical device
Open the candidate's device page. eero's device-information reference documents manufacturer, hostname, IP addresses and MAC address. Use those as clues together. A component manufacturer's name can be less recognizable than the brand printed on the case.
On a device you own, open its network details and compare the address for its active home-network connection with the eero entry. Use the address shown for that connection; a phone's private Wi-Fi address may differ from its factory address. Wired and wireless interfaces can also have different addresses. No need to disable address privacy just to label the entry.
If the identity remains unclear, ask the household and try a reversible observation on a known, nonessential device: stop its download in the application, then look for the corresponding change in eero. Correlation makes it a candidate; repeat the change before treating it as confirmed. Do not disconnect medical equipment, security equipment or someone else's work session to identify a name.
After confirming it, tap the device's name or symbol to open Appearance and assign a useful nickname, such as “Living-room console.” Keep a note of the old name if helpful. This organizational change can be reversed later and does not limit its traffic.
Pause one transfer and watch what changes
Ask the device's user to pause an optional transfer through its own application. Use Pause or a bandwidth limit if provided; do not cancel a backup or close an updater mid-installation. Leave other household activity as steady as possible.
- The rate drops and the symptom improves: the transfer is a credible contributor. Resume briefly, when convenient, and see whether the symptom returns. Then arrange a quieter time or use that application's transfer limit.
- The rate drops but the symptom remains: the device was busy, but that has not explained the problem. Restore its transfer and investigate another candidate or the affected connection.
- The rate does not drop: allow several refreshes and check that the pause actually took effect. Another application on the same device may still be transferring. Do not escalate straight to blocking the whole device.
Finish by resuming anything paused and confirming that its job progresses. A successful diagnosis should leave the household with a workable schedule or limit, not an unnoticed stalled backup. Write down the device, transfer, approximate readings and before/after symptom; that is more useful than “the internet was slow.”
If the busy period has already passed
Open Activity and review weekly usage by device. eero provides weekly history to all customers; daily and monthly views with up to three months of history require eero Plus. Use the Activity reference to distinguish usage totals from speed-test results. A “Fastest Download” result is not a list of current bandwidth consumers.
History helps shortlist devices for the next recurrence. It cannot reconstruct whether two transfers overlapped during a particular frozen call. Profile totals can also hide the individual culprit; unassigned devices appear under Other Devices when viewing by profile.
Finally, eero's usage figures exclude local transfers between devices. A quiet internet graph does not rule out congestion from a large local copy or a wireless problem. If no internet transfer follows the slowdown, move to separating the Wi-Fi link from the internet connection, carrying your observations forward.
Sources, versions & scope
The steps describe the documented controls and expected checks; they are not a claim that every device or software release has been physically tested. Platform and version differences are stated with the procedure.
