How Can You Tell If a Router Is Bad? Signs and Checks

You can tell if a router is bad by watching for clear, repeatable failures: frequent drops, slow speeds that don’t match your internet plan, and random disconnects or inability to reach specific devices. Check the basics first—overheating, a failed power supply, outdated firmware, and wrong Wi‑Fi settings—because these cause “bad router” symptoms that can be fixed quickly. If those checks don’t resolve the problems, you’ll know you’re dealing with a failing router and not a setup issue.

A router is likely bad if the Wi‑Fi drops constantly, speeds are far lower than expected across multiple devices, or the router won’t stay connected after basic troubleshooting. Start by checking power/firmware and then verify whether the problem follows the router or the internet connection. This guide will walk you through practical signs and tests so you can narrow down the culprit quickly.

If you’re dealing with frequent buffering, “connected but no internet,” random reboots, or inconsistent coverage at home, these checks will help. It also applies when you’ve already reset your device and still see the same behavior.

Common “Bad Router” Symptoms

A bad router usually reveals itself through repeated instability: disconnects, obvious performance collapse, or ongoing reboot/power-cycle behavior. If multiple symptoms line up at once—especially across Wi‑Fi and Ethernet—it’s a strong sign the router is the bottleneck rather than a single device.

In my troubleshooting workflow, I focus on separating radio problems (Wi‑Fi) from WAN/LAN problems (routing, DHCP, DNS) first, because a router can “look fine” while specific functions fail intermittently. A router can also degrade under load (many devices, long downloads, VPN-heavy work), which is why timing patterns (peak hours vs quiet hours) matter.

– Frequent Wi‑Fi disconnects, reconnect loops, or “connected, no internet” messages.

– Slow or uneven speeds that don’t match what your ISP plan should deliver (especially after rebooting everything).

– Random reboots, flashing error lights, overheating, or the router requiring power cycling often.

When a router is truly failing, you’ll often see repeated WAN-side errors or link drops reflected in the router’s admin status page or LED/WAN indicators.

If “connected but no internet” happens across multiple devices at the same time, the issue is usually upstream of the specific device—commonly WAN/DNS/DHCP handling.

Quick Router Checks You Can Do Immediately

You can often narrow a “bad router” claim quickly by running a disciplined power cycle and checking the physical and admin basics. If the router stabilizes after controlled steps, the cause is often firmware, heat, or a stuck WAN/LAN state rather than irreversible hardware failure.

According to IEEE 802.11ax (Wi‑Fi 6), channel widths can be 20/40/80/160 MHz, so an overly wide or conflicting Wi‑Fi channel setting can materially reduce real-world reliability.

Firmware updates can temporarily interrupt service because routers reboot or restart networking services during the upgrade process—so stability tests should be run after the update completes.

Do these in order:

– Power cycle in the right order: unplug modem and router, wait , then plug in modem first, then router once the modem is fully online.

– Inspect physical basics: power adapter securely seated, Ethernet cables firmly connected, no obvious damage, and router ventilation not blocked.

– Check the router’s status lights (or admin dashboard) for WAN/internet errors, firmware alerts, or repeated link drops.

What you’re really looking for (and why it matters)

A router can misbehave when its internal network services—often DHCP (IP assignment), routing/NAT (traffic forwarding), or DNS (name resolution)—get stuck. A correct power sequence can clear these states without changing configuration. In 2026, many home routers also run “watchdog” restart logic for failing subsystems; if you see constant reboot behavior, the router is likely the root cause.

Also watch heat: if the router sits inside a closed cabinet or has blocked vents, thermal throttling can cause intermittent radio dropouts or WAN instability. A router that repeatedly overheats is not “just old”—it can be actively failing.

Verify Whether It’s the Router or Your Internet

The fastest way to prove whether the router is bad is to test the same network behavior using wired vs Wi‑Fi and compare against the modem/ISP side. If Ethernet stays stable while Wi‑Fi collapses, the router’s wireless radios/settings are the more likely issue. If both wired and Wi‑Fi fail similarly, the router’s routing/DHCP/DNS path—or the modem/ISP link—is more suspect.

This is the step where we stop guessing and follow evidence. I recommend recording two or three timelines: when the failure starts, how long it lasts, and whether the modem shows any “offline/online” transitions.

DHCP uses UDP ports 67 (server) and 68 (client), so if clients can’t obtain an IP lease, the router LAN may appear “connected” while internet access fails.

According to RFC 2516, PPPoE uses EtherType 0x8863 (discovery) and 0x8864 (session), so PPPoE authentication failures can break internet access while leaving Wi‑Fi association intact.

A simple router vs internet decision

Use a wired test if you can—laptop/desktop + Ethernet directly into the router.

– If wired is stable but Wi‑Fi is unstable: suspect router wireless hardware, band steering, channel interference, or Wi‑Fi configuration.

– If wired is unstable too: suspect router WAN/LAN services, DNS/DHCP behavior, firmware bugs, or upstream modem/ISP issues.

– If the modem shows instability (reconnects/flapping): the “bad router” symptom may actually be coming from the internet side.

More likely a router problem

Failures match across multiple devices and persist after firmware updates and a correct modem→router power cycle.

More likely an internet/ISP problem

The modem reports repeated offline/online events or the same failures occur for multiple networks in your area.

More likely Wi‑Fi configuration/interference

Only one band (2.4 GHz or 5 GHz) fails, or one area/room consistently drops while wired remains stable.

Where speeds come from (and why “slow” still needs proof)

Compare speeds on multiple devices and, importantly, test both 2.4 GHz and 5 GHz (or Wi‑Fi 6/6E bands if supported). In many homes, a router can advertise fast Wi‑Fi but deliver poor throughput due to channel congestion, bandwidth settings, or antenna/radio issues. If every device drops at once, the router’s service path or WAN link is more suspect than a single client device.

Mandatory data table: common path components that trigger “router looks connected”

How to interpret the test results in 2026

If your router is “the culprit,” you’ll generally see consistent failures in the same path element(s)—often DHCP or DNS—across both Wi‑Fi and wired clients. If only one device suffers, you’re dealing with a device configuration, not a bad router.

If you notice issues only during peak usage, consider radio congestion, upstream ISP capacity, or bufferbloat (network queues growing during heavy load). In 2026, home routers with aggressive QoS/Smart Queue features can sometimes worsen stability when misconfigured, which is why the next section matters.

Check Settings That Mimic a “Bad Router”

A misconfiguration can look exactly like router hardware failure—especially when symptoms repeat after reboots or resets. Before you replace a router, audit WAN type, PPPoE credentials (if applicable), firmware level, and Wi‑Fi channel/bandwidth settings.

Many routers ship with defaults that are “good enough,” but small changes—like switching WAN mode, enabling power-saving, or altering channel width—can create instability that resembles a failing device. In practice, these issues are common in homes where ISP setups have been customized more than once.

– Look for common configuration problems: wrong WAN type, PPPoE username/password errors (if used), outdated firmware, or aggressive power-saving/Wi‑Fi scheduling features.

– Ensure firmware is up to date via the router admin page, and note: updating can temporarily interrupt service.

– Confirm Wi‑Fi settings: channel interference (especially on 2.4 GHz), channel width too wide for your environment, or band steering issues.

If PPPoE credentials are incorrect, a router may authenticate to Wi‑Fi clients while failing to establish the WAN PPP session, producing “connected but no internet” behavior.

Wide Wi‑Fi channel widths (80/160 MHz) can increase throughput but can reduce robustness in congested RF environments, contributing to dropouts that look like a bad router.

WAN and internet settings: the “hidden” cause

Start with WAN mode and authentication method. If your ISP uses PPPoE, the router needs correct username/password values to bring up the WAN session. According to RFC 2516, PPPoE discovery and session frames use EtherType 0x8863 and 0x8864, so failures here can break internet while leaving Wi‑Fi association intact (RFC 2516 (1999)).

If your ISP uses DHCP on the WAN, check that the WAN gets a valid IP/subnet/gateway from the modem/ISP. If your WAN is stuck in renewal loops, the router will repeatedly drop internet.

Wi‑Fi settings: “works sometimes” isn’t always hardware

Wi‑Fi dropouts can come from:

– channel overlap/interference (neighbors, microwaves, Bluetooth coexistence),

– channel width set too high (e.g., 160 MHz in a crowded area),

– band steering directing devices onto a band that struggles at your location.

According to IEEE 802.11ax-2019, 802.11ax supports channel widths like 20/40/80/160 MHz, which is why channel width choices impact real-world reliability (IEEE 802.11ax-2019).

What Can Go Wrong (and How to Avoid Mistakes)

The biggest mistake is replacing a router before you confirm whether the issue is actually wireless-only, modem/ISP-related, or configuration-related. In other words, “slow Wi‑Fi” can mean interference, distance, or congestion—not always router failure.

Another common error is using an incomplete test plan. If you only test from one phone in one room, you may miss that Ethernet remains stable or that only one band fails. A router can also seem stable until multiple devices connect or a single heavy stream starts—so time-of-day and load patterns are critical.

– Misdiagnosis from incomplete testing: “slow Wi‑Fi” can be caused by interference, distance, or a congested channel—not necessarily a router failure.

– Over-resetting without logging changes: after a factory reset, you may lose ISP credentials or custom network names/settings.

– Assuming hardware failure when firmware or ISP issues are the cause—especially if the modem also shows instability.

– Edge cases: some routers look “fine” but fail under certain loads (large downloads, multiple devices, VPN-heavy traffic). If you notice patterns only at peak times, consider congestion/interference before declaring the router bad.

A factory reset can restore defaults that remove ISP-specific settings, so it can inadvertently create “connected but no internet” until WAN credentials and options are reconfigured.

If Ethernet and Wi‑Fi show the same instability, a router hardware issue becomes more likely than a Wi‑Fi-only interference problem.

Quick “don’t do this” list

– Don’t judge a router after 2 minutes of uptime; many problems are intermittent.

– Don’t skip firmware updates if the admin UI shows known stability fixes (but test after the update completes).

– Don’t ignore IP addressing context: private IPv4 ranges are standardized in RFC 1918 (RFC 1918 (1996)), so if your gateway/subnet behavior looks inconsistent, investigate before assuming hardware death.

Verdict: When to Replace vs When to Troubleshoot Further

Replace the router when you’ve confirmed repeated instability across wired and wireless tests, it shows reboot/error behavior, and controlled troubleshooting (including firmware updates and a proper modem→router power cycle) doesn’t improve stability. If wired Ethernet is stable but Wi‑Fi is unreliable—or the problem is isolated to one room/band—replacement is usually the wrong first move.

The goal is to make a fair, evidence-based call. In 2026, many routers are capable and feature-rich, but that also means there are more settings that can break stability. So treat replacement as the end of the line, not the beginning.

If the router shows repeated reboots/errors, fails basic connectivity tests across Ethernet and Wi‑Fi, or you still see the same instability after firmware updates and controlled power cycling, it’s reasonable to treat the router as suspect—and consider replacement.

That said, if wired Ethernet is stable or the issue only happens in one room/one device type, you may be dealing with Wi‑Fi range/interference or a device-specific problem instead. Skip replacement (and focus on settings/placement) if your router is otherwise stable and only one band/channel is affected.

When the router is failing at the routing/DHCP/DNS layer, both wired and Wi‑Fi clients typically show similar “connected but no internet” symptoms.

When only one band (or only Wi‑Fi) fails while Ethernet stays stable, the router’s wireless configuration or RF environment is more likely than total router hardware failure.

Router “Bad?” Quick Scan Checklist

Use this as a scan-and-act list. If you hit several items in a single day, you can confidently narrow the router as the suspect—especially when wired tests confirm the same behavior.

– [ ] Wi‑Fi disconnects or “connected, no internet” frequently

– [ ] Router reboots or overheats / has error indicators

– [ ] Speeds are consistently poor on multiple devices

– [ ] Wired Ethernet test is unstable too (stronger sign)

– [ ] Firmware is up to date and issue persists

– [ ] After power cycle (modem first, then router), stability doesn’t improve

If wired testing is stable, you can usually deprioritize WAN routing failure and focus on router Wi‑Fi radio settings and local RF interference.

If stability does not improve after firmware updates and a correct power sequence, the odds increase that the router’s hardware or internal networking services are failing.

Sources

– IEEE 802.11ax-2019, channel width support (20/40/80/160 MHz) (IEEE 802.11ax-2019)

– RFC 2516 (1999), “A Method for Transmitting PPP Information Over Ethernet Networks” (RFC 2516 (1999))

– RFC 2131 (1997) and RFC 2132 (1997), DHCP basics including UDP ports used by clients/servers (RFC 2131 (1997), RFC 2132 (1997))

– RFC 1035 (1987), DNS message format and port usage for DNS operations (RFC 1035 (1987))

– RFC 1918 (1996), private IPv4 address space ranges (RFC 1918 (1996))

A “bad router” diagnosis is most reliable when you verify patterns across both wired and wireless connections, audit WAN and Wi‑Fi settings that can mimic hardware failure, and only then decide whether replacement makes sense. If wired tests align with Wi‑Fi failures—or the router repeatedly reboots/errors after firmware updates—treat the router as the likely culprit. If Ethernet is stable but Wi‑Fi is not, focus on band/channel choices, interference, and placement before you assume the router is dead.

Frequently Asked Questions

What are the common signs a router is bad?

Common signs include frequent Wi‑Fi drops, slow speeds even when you’re near the router, and devices that randomly disconnect. You may also notice that the router runs hot, the status lights behave erratically, or performance improves only after rebooting. If you consistently see issues across multiple devices and apps, it can point to a failing router rather than your internet service.

How can you tell if your router is the cause of slow internet?

Start by running an internet speed test on a device connected via Ethernet (if possible) and again over Wi‑Fi. If Ethernet is significantly faster but Wi‑Fi is poor, the router’s wireless components or firmware may be failing. Also test at different times and locations in your home—if throughput keeps degrading or varies wildly without any changes to your ISP, the router may be the bottleneck.

Why does my Wi‑Fi keep disconnecting, and could it mean the router is failing?

Random disconnects can be caused by router overheating, unstable firmware, or failing internal hardware like the Wi‑Fi radio. If the issue happens across many devices and networks, and the router requires frequent resets to restore stability, that’s a strong indicator. Still, it’s worth checking for interference from nearby networks and confirming your modem/ISP connection is stable before concluding the router is bad.

Which tests should I run to diagnose a bad router at home?

Check for local network issues by rebooting the router and modem separately (modem first, then router) and retesting speeds and connection stability. Review the router’s event logs/status pages for errors, firmware update warnings, or repeated WAN/LAN drop events. If you have a spare router or can temporarily use one, compare results—consistent improvement with another router is one of the clearest ways to confirm the original router is faulty.

What’s the best way to confirm whether you need a router replacement?

Compare performance using a wired connection and multiple Wi‑Fi devices, and document the results (speed test results and how often connections drop). If you’ve tried firmware updates, proper placement, changing Wi‑Fi channels (or bands), and the router still performs poorly, replacement is often the most effective fix. When the router is older, shows hardware overheating, or can’t maintain stable Wi‑Fi despite troubleshooting, it’s usually time to invest in a reliable new router.

📅 Last Updated: October 28, 2026 | Topic: how can you tell if a router is bad | Content verified for accuracy and freshness.

---

References

1. Router
2. Wireless router
3. Wireless LAN
4. Wi-Fi
5. Wireless access point
6. Packet loss
7. Latency
8. https://scholar.google.com/scholar?q=how+to+diagnose+failed+wireless+router  Google Scholar
9. https://scholar.google.com/scholar?q=wireless+router+failure+symptoms+packet+loss  Google Scholar
10. https://scholar.google.com/scholar?q=home+network+troubleshooting+wireless+latency+packet+loss+router  Google Scholar