The number your router app shows
is not your internet plan speed.
Most modern router apps display a "live" or "real-time" traffic number on their main screen. People — reasonably — assume that's their internet speed. It isn't. Per-vendor decoder for the big-six router apps.
What the dashboard is actually measuring
Every modern router app shows some version of three different numbers, often without making clear which is which:
- Live traffic: how many bits per second are currently flowing through the router right now. At idle this is tiny — maybe a few kbps for background syncing. Under active use (Netflix, downloads) it climbs to whatever the current activity demands. This is the number that confuses everyone.
- Plan capacity / WAN speed: what your ISP is theoretically delivering to the router. Some apps test this by running a real speed test against the vendor's servers; some apps just display whatever the modem reports negotiating.
- Peak observed: the highest traffic measured over some window (last hour, day, month). Less often shown but sometimes labeled "Today's peak."
The mistake: assuming the live-traffic number on the main screen is the plan capacity. If your Deco app shows "55 kbps / 54 kbps" on the home tab at idle, that does not mean you're paying for and receiving 55 kbps of internet. It means 55 kbps of traffic happens to be moving through right now — exactly what should be there for a quiet network.
Per-vendor decoder
TP-Link Deco
The number on the home screen, often near the top, often shown with up/down arrows.
Current real-time traffic, sampled every few seconds. Idle reads in the kbps range. Active use climbs to whatever the activity requires (Netflix HD ~5 Mbps, 4K ~25 Mbps).
To find actual plan capacity in the Deco app, tap More → Internet Connection → Speed Test. The app runs an Ookla-based test against the nearest server and reports your real plan speed.
The home-screen 'live' number is famously unreliable on TP-Link's older firmware versions — they were updating it slowly and frequently misreporting. Trust the explicit Speed Test result, not the live indicator.
Eero
The Activity section shows usage across last hour / day / week.
Aggregate bandwidth used, not throughput. If Eero reports '1.2 GB used today,' that's data volume, not the speed of any individual download. The unit (GB) gives this away — speed would be Mbps.
The Eero app's main 'Network Health' view shows the result of its automated background speed test, run by Eero Plus subscribers (or manually invokable on the free tier). This is your actual plan capacity, labeled 'Download' and 'Upload' with Mbps units.
Eero's Network Health view only refreshes when you explicitly tap it (on free tier) or on Eero's schedule (Eero Plus). The number you see may be a day or two old.
ASUS Router app
The bandwidth bar on the home tab. Animates in real time.
Live throughput across the WAN port, sampled every second. Reads accurately and reasonably close to actual traffic — better than TP-Link's equivalent, in our experience.
ASUS doesn't have a built-in speed test in the consumer router app. To check plan capacity, use a browser-based test (speed.cloudflare.com works well) from a device connected directly to the router via ethernet.
The ASUS app's live bar can swing rapidly even when the network feels stable — this is a visual artifact of frequent sampling, not a stability problem. Don't chase those swings.
Google Nest WiFi / Google Home
The 'Activity' tab shows per-device current usage in real time.
Live throughput per device. The aggregate at the top is current total throughput across all devices.
Tap the router tile → Test Wi-Fi → Test internet speed. Google Home runs a Measurement Lab speed test and reports plan capacity.
Google Home's speed test runs against Measurement Lab, which is sometimes geographically distant from your ISP's peering point. Results can read 10–20% slower than Cloudflare or Ookla for the same connection.
Netgear Nighthawk + Orbi apps
The Speedometer ring on the home screen.
A composite that mixes recent throughput and recent peak. Less granular than Eero or ASUS — feels more like a dashboard gauge than a precise reading.
Tap the speedometer → Internet Speed → Run Test. Netgear's speed test runs against the Ookla / Speedtest.net network and is generally accurate.
Netgear's app caches the last speed test result for days and re-displays it as the speedometer reading even when you haven't run a fresh test. Look for the 'Last tested' timestamp before trusting it.
Ubiquiti UniFi Controller / UniFi Network app
The Statistics dashboard shows throughput graphs broken down by client, network, and time range.
Granular, per-client, per-flow data. UniFi is the most accurate of the consumer-adjacent options — it's enterprise gear retrofitted for home, so the metrics layer is built right.
Settings → Internet → Speed Test. Runs against Ookla. The result is plan capacity.
UniFi's throughput graphs only count traffic that the controller actively observes — if a device is offline or on a non-managed VLAN, its traffic doesn't appear. The 'total' number is comprehensive only when all networks are managed by UniFi.
A clarifying analogy
Think of your internet plan as the size of a water pipe. The plan capacity (1 Gbps, 500 Mbps, whatever) is the maximum flow the pipe can sustain.
The "live" number on a router app is the current flow. When no one's running a tap, the pipe shows a trickle — that's normal. Mistaking the trickle for the pipe size is like measuring the diameter of a faucet at 3 AM when nothing's open and concluding the house has terrible plumbing.
To measure the pipe size, you need to open every tap and see how fast water actually flows. That's what a speed test does — it explicitly demands as much bandwidth as possible to find the real ceiling.
When the live number actually matters
The live indicator isn't useless. Three cases where it's the right thing to look at:
- Diagnosing background hogs. If your Wi-Fi feels slow and the live number reads 80 Mbps with no obvious user activity, something is using bandwidth in the background — a cloud backup, a stuck app, a large download. Per-device views (Deco, Eero, UniFi all have these) tell you which device.
- Confirming a fix worked. Disable a router feature, watch the live number under load, see if it climbed. Faster than running a full speed test for each change.
- Detecting peak-hour throttling. If the live number tops out at the same value during peak hours (7–11 PM) and is uncapped at 3 AM, your ISP is doing peak-hour traffic shaping or the local node is over-subscribed.
Don't confuse the dashboard's signal-strength bars either
Most router apps also show signal-strength indicators for connected devices — usually "Excellent / Good / Fair / Poor." These are about Wi-Fi link quality between the device and the router. They have nothing to do with your internet plan capacity. A device showing "Excellent" Wi-Fi signal can still get terrible internet speeds if the router-to-ISP link is the bottleneck.
Conversely, a device showing "Fair" Wi-Fi signal can have fine internet speeds if the available Wi-Fi bandwidth still exceeds the ISP plan. The two metrics live on different layers.
How to actually know what you're paying for vs getting
The reliable verification, in order:
- Plug a laptop directly into the router or modem via a known-good Cat6 cable.
- Disable Wi-Fi on the laptop so the test runs over wired only.
- Run Cloudflare Speed Test. It reports download, upload, latency, jitter, and loaded latency. The download number on this test is your real plan capacity (or close to it).
- Compare to what your ISP says you're paying for. A gap bigger than 20% is a delivery-gap problem; consult the ISP escalation playbook.
- Run the StabilityPulse stability test too — even when throughput matches your plan, jitter and loaded latency tell you whether the line will actually hold calls and gaming.
Once you've established the baseline, the router app's live indicator becomes a useful real-time tool rather than a confusing one — you know what it's measuring (current traffic, not capacity) and what it isn't.
When to be suspicious of your app's own speed test
The vendor-built speed tests inside these apps are generally accurate but have biases worth knowing:
- Eero, Google, Netgear: use third-party test infrastructure (Measurement Lab, Ookla). Results match independent tests within ~5%.
- Deco: uses TP-Link's own infrastructure in some regions. Results sometimes read more optimistically than independent tests.
- ASUS: doesn't ship a built-in test in the consumer app. Browser-based independent tests are the only path.
When in doubt, run two independent tests (Cloudflare + Ookla) and compare. If they roughly agree and your vendor's test disagrees, trust the independents.