Do I need a new router? Prove whether the router is the bottleneck before spending money on replacement hardware or mesh Wi‑Fi by comparing wired speed, Wi‑Fi coverage, device load and router stability.
Router upgrade guide
Use the test results to decide whether to keep the router, improve coverage, add an access point, or replace unstable hardware.
Start here
Choose the closest result. Each route leads to a buying decision rather than a generic “fix” list.
Evidence → decision
The cards below combine the symptom, evidence and buying decision so the same information is not repeated across separate Issue, Validate and Fix sections.
When Ethernet reaches the expected package speed and a modern device is fast beside the router, the router is processing traffic correctly. Replacing it is unlikely to improve one slow device or provider-side evening congestion.
Evidence to confirm: several devices are fast close to the router and the Broadband Speed Test is healthy over Ethernet.
Healthy close-range Wi-Fi with several weak distant rooms points to coverage rather than failing router hardware. Dense walls and floors can defeat modern radios, so relocating the router or adding a correctly positioned access point may be better than replacing it.
Evidence to confirm: the same modern device is fast beside the router and consistently slow only in the weak area.
A repeatable reboot, reset uptime, complete light cycle or loss of new connections under sustained traffic is strong evidence of router or power-supply instability. A warm case alone is not proof; the failure must match the heat, memory or connection-load pattern.
Evidence to confirm: several devices fail together, router uptime resets, or logs show memory, conntrack or thermal warnings.
A router upgrade is relevant when an Ethernet loaded-latency test shows large ping increases and the existing hardware cannot provide effective SQM. A faster Wi-Fi specification alone will not solve upstream queueing or poor traffic management.
Evidence to confirm: run the Bufferbloat Test and compare idle with loaded latency before buying.
A 100Mbps device link, one slow computer, changing ONT or DSL lights, and repeatable evening-wide slowdowns can all make the router look guilty. Replacement hardware will not repair a cable ceiling, optical fault, copper instability or provider congestion.
Evidence to confirm: use the one-device guide, ONT light guide, evening slowdown guide or whole-home disconnection guide.
A router cannot remove latency that already exists before traffic reaches it. FTTC interleaving, retransmission, mobile-network routing, ONT faults and provider backhaul delay must be diagnosed at the correct layer.
Evidence to confirm: compare idle and loaded Ethernet latency with the Ping Test, then check packet loss if responsiveness breaks up.
Test before buying
A new router only helps when the current router is the proven bottleneck. It can improve weak Wi-Fi coverage, multi-device airtime efficiency, local stability or loaded latency, but it cannot repair an external line fault, ONT problem or provider congestion.
Run the Broadband Speed Test and Ping Test over Ethernet and confirm the device negotiated the expected link speed.
Use the same modern device beside the router and in the weakest room.
Run the Bufferbloat Test with other traffic paused, then repeat while the connection is busy.
Watch whether the router restarts, becomes unresponsive or loses lights during sustained traffic.
Check whether several devices fail, ONT or DSL lights change, or wired performance drops only at peak time.
Under the hood
Hardware exhaustion is proven by matching failures with connection-table pressure, unavailable memory, sustained CPU load, thermal warnings or repeated reboots. One high counter, one warm casing reading or low “free” memory value is not enough on its own.
free -m
grep -E 'MemTotal|MemAvailable|SwapFree' /proc/meminfo
cat /proc/sys/net/netfilter/nf_conntrack_count
cat /proc/sys/net/netfilter/nf_conntrack_maxMemAvailable, not only free memory. A conntrack count near the configured maximum matters when it coincides with table-full messages or failed new connections.logread | grep -Ei 'out of memory|oom|conntrack|table full|thermal|overheat'top
cat /sys/class/thermal/thermal_zone*/temp 2>/dev/nullBuy for the proven limitation
Buying rule: purchase for the failed layer you proved—not the largest advertised Wi-Fi number.
Common questions
A replacement is justified when several devices fail close to the router, the router reboots or overheats, wired performance is limited by the router, or loaded latency remains poor and the existing hardware cannot run suitable queue management.
It may improve coverage when the existing router has weak radios or poor placement, but one router cannot overcome every wall or floor. Larger homes may need a correctly positioned access point or mesh system.
Not when the same wired device repeatedly slows at peak time with household traffic paused. That pattern points more strongly towards the broadband line or provider path.
Only when loaded-latency tests prove the problem and the current router cannot provide effective SQM or QoS. Upload saturation can sometimes be reduced without replacing hardware.
No. A single slow device usually needs its own Wi-Fi adapter, software, driver or hardware investigated before the router is replaced.