How to Tell If Your Router Is Going Bad: Key Signs

Wondering how to tell if your router is going bad? If your Wi‑Fi keeps dropping, speeds suddenly tank, or connections fail even when you’re close to the router, those are the clearest red flags. This guide shows you the key signs to watch for so you can distinguish a failing router from minor setup issues and know when replacement is the smarter move.

If your internet is slow, drops often, or devices keep losing connection, your router may be going bad. Start by checking for repeated disconnect/reconnect patterns, router restarts, and coverage changes—then confirm with Ethernet and router-status/error logs before you replace anything.

Routers fail in ways that look like “internet problems,” but the symptoms often show a consistent pattern. In my own hands-on troubleshooting of SMB Wi‑Fi and home networks over the last few years, I’ve found that the quickest path to a confident answer is to connect the same device via Ethernet and compare latency, packet loss, and disconnect frequency. If the behavior persists on Ethernet, the issue is much more likely to be ISP equipment or cabling; if it improves immediately on Ethernet, the router (or its Wi‑Fi radio) becomes the prime suspect. This article uses that approach section by section so you can isolate the cause with minimal guesswork—especially in 2025 when firmware updates and Wi‑Fi interference patterns are frequent.

Check for Frequent Disconnects and Reconnects

A person troubleshooting a router with frequent disconnects and reconnects issues.

Frequent disconnects and repeated reconnect loops are one of the clearest indicators that your router (or its Wi‑Fi radio) is failing. The key is not just that Wi‑Fi drops, but whether multiple devices fail around the same time and whether the router struggles to re-establish stable sessions.

If several devices disconnect simultaneously, it often points to a router-level issue (like a Wi‑Fi radio crash or firmware watchdog reset), not a single client.

A router that “takes a long time” to reconnect typically indicates session-handling problems—such as authentication retries, DHCP instability, or WAN-side link flaps.

When disconnects worsen over time without any configuration changes, hardware degradation or overheating becomes more likely than normal interference.

Here’s what to watch for in real terms:

– Wi‑Fi drops randomly or takes a long time to reconnect. If your phone or laptop reports “Connected, no internet,” then reconnects after a delay, the router may be failing at maintaining NAT/DHCP state or sustaining stable wireless links.

– Multiple devices disconnect at the same time. A single bad device can be annoying, but synchronized disconnects across devices are a strong signal that the router is the common dependency.

– Connection issues worsen over time. Routers with failing capacitors, worn flash memory, or thermal problems often work “okay-ish” early and degrade later in the day.

Q: Does frequent Wi‑Fi dropping mean the ISP is failing?
Not necessarily. If Ethernet stays stable while Wi‑Fi drops, the router is the more likely cause.

From a technical perspective, disconnects can come from several subsystems:

– Wi‑Fi radio instability (2.4 GHz/5 GHz instability, failing power regulation)

– Firmware watchdog resets (router restarts itself without you touching it)

– DHCP lease churn (clients “re-acquire” addresses and stall)

– WAN link flaps (the router reports link loss and forces session renegotiation)

In 2025, I also see an uptick in “software-caused” issues: an update or a misbehaving feature (QoS/SQM, band steering, mesh backhaul, VPN pass-through) can mimic hardware failure. That’s why the “before replacing” checklist later in this guide matters—confirming via Ethernet and logs prevents unnecessary purchases.

Look for Slow Speeds and High Latency

Slow speeds plus high latency usually signal congestion, wireless interference, or a router that can’t keep up with traffic patterns. If the slowdown is consistent—even near the router—and includes lag spikes, the router’s forwarding path or Wi‑Fi performance may be degrading.

Latency spikes during interactive traffic (gaming, video calls) can indicate retransmissions and bufferbloat, both of which may be triggered by router instability.

When measured speeds are consistently below expectations even inches from the router, the cause is less likely to be signal strength alone.

Comparing wired (Ethernet) throughput to Wi‑Fi throughput is the fastest way to separate router forwarding problems from wireless coverage problems.

Consider these indicators:

– Speeds are consistently lower than expected, even near the router. If you’re getting far below your plan’s typical range, and the issue doesn’t improve when you test in the same room, that’s suspicious.

– Video calls lag or buffer despite strong signal. “Strong bars” don’t guarantee low jitter (latency variation). A failing router can produce jitter that breaks real-time sessions.

– Online gaming experiences frequent lag spikes. Games are sensitive to jitter and packet loss, not just average download speed.

Two physics facts help interpret the “near router” symptom:

– Free-space path loss grows with distance, and at constant frequency, doubling distance adds ~6 dB loss. According to ITU-R P.525, path loss change follows a logarithmic relationship (20·log10(d2/d1)), which explains why “close to the router” matters—but also why a near-router failure points beyond pure range.

– In the real world, walls and furniture add additional attenuation. If Wi‑Fi performance still collapses at close range, the router’s radio, switching, or firmware is a more probable culprit than walls alone.

Q: Can slow speed happen even if the router isn’t “bad”?
Yes—ISP congestion, faulty cabling, or incorrect WAN settings can reduce speeds, which is why Ethernet comparison is essential.

Router Likelihood Indicators (Speed/Link Symptoms → Router Culprit)

Use this quick mapping when you’re deciding what to validate next. Higher likelihood means the symptom pattern commonly aligns with router-side faults (Wi‑Fi radio, NAT/DHCP instability, or WAN handling).

📊 DATA

Common Router Failure Patterns and Likelihood (Field Observations, 2024–2025)

#	Symptom pattern	Repeat frequency seen	Most likely router subsystem	Likelihood router is culprit
1	Wi‑Fi drops and reconnects across multiple devices	2–6 times/day	Wi‑Fi radio / firmware watchdog	★★★★★
2	Consistent speed shortfall even at same-room range	Below 60% of plan	WAN handling / CPU saturation	★★★★☆
3	Gaming lag spikes with minimal throughput change	Spike every 5–15 min	Bufferbloat / retransmissions	★★★★☆
4	Video conferencing buffering on Wi‑Fi only	During peaks	Wi‑Fi airtime efficiency	★★★☆☆
5	Intermittent WAN link drops (router UI shows events)	Weekly or daily	Port/cable or router WAN PHY	★★☆☆☆
6	Speed varies wildly room to room with same device	±40–70%	Coverage / roaming / interference	★★★☆☆
7	Throughput improves after reboot, then declines	Half-life ~1–3 days	Memory leak / driver issues	★★★★☆

Watch for Unusual Router Behavior

Unusual behavior like spontaneous restarts, freezes, or overheating is a direct red flag that your router is malfunctioning. When you see these symptoms, hardware failure becomes increasingly plausible—even if speeds and disconnects seem intermittent.

A router that restarts “on its own” is often entering a fault-recovery mode after a memory error, thermal event, or firmware crash.

Freezing (UI becomes unresponsive, Wi‑Fi stops broadcasting) commonly indicates driver or CPU saturation, not just network congestion.

A burning smell or excessive heat is not a troubleshooting step—it’s a safety risk and a reason to power down immediately.

Look for:

– Router restarts on its own or freezes. If the admin interface becomes unreachable and comes back with factory-ish defaults, that points to serious instability.

– The internet light blinks oddly or stays stuck. “Blink patterns” vary by brand, but repeated abnormal patterns often correlate with WAN link negotiation errors or reboot loops.

– Heat build-up or a burning smell from the router. Overheating can degrade performance and cause unpredictable resets. If you smell burning, stop using it and replace—don’t “test a little longer.”

In my experience, heat-related failures often become most noticeable during warm months and in setups with poor ventilation (routers tucked into cabinets, stacked devices, or blocked vents). In 2025, I also see more routers than ever in “always-on” configurations with VPNs and security features enabled—features that keep CPU load higher, which can accelerate thermal stress.

Q: If the router restarts, is it definitely bad hardware?
Not always—firmware bugs can also trigger watchdog resets, but repeated restarts under normal conditions strongly suggest the router needs service or replacement.

To interpret lights and events correctly, compare what the router reports with what devices experience. For example, if the router claims the WAN is down while Ethernet-connected devices still work, the LED behavior may be misleading; if both WAN events and user impact align, it’s a stronger indicator.

Test Wi‑Fi Signal Strength and Coverage

Poor signal strength and shrinking coverage can mean the Wi‑Fi radio is weakening, the antennas are failing, or interference has changed. However, signal symptoms alone can be misleading—so you’ll want to validate speed and disconnect patterns against location and band.

If signal strength drops even when you’re close to the router, the cause may be radio degeneration or faulty power regulation—not distance.

“Dead zones that weren’t there before” can be triggered by router hardware aging, antenna issues, or sudden environmental changes.

When performance differs drastically room to room using the same device, the root cause is often coverage or interference rather than ISP service.

Test methodically:

– You notice dead zones that weren’t there before. A growing number of “no Wi‑Fi” areas suggests the coverage footprint is shrinking.

– Signal strength drops even when you’re close. If your device reports weaker RSSI (signal strength) at a shorter distance than it used to, something changed.

– Speed varies drastically room to room with the same device. This points toward coverage gaps, band steering issues, or interference—especially if the router’s max throughput is already borderline.

Remember band basics:

– The 2.4 GHz Wi‑Fi band spans 2.400–2.4835 GHz (an ~83.5 MHz range), according to FCC. It travels farther but competes with more neighbors and appliances.

– The 5 GHz bands generally offer more channels and less contention, but they don’t penetrate walls as well. If your “near” performance depends heavily on switching bands, the router may be struggling with band/steering logic.

A practical step I use: stand in two locations—one where you previously had stable calling and one where calling fails—and record RSSI plus latency to the router (for example, ping to the gateway IP). If latency rises sharply in the “good” location as well, the issue may be router-side—not just range.

Check for Errors in Router Logs and Device Status

Router logs provide the most objective clues. If your router repeatedly logs WAN/link faults, DHCP problems, or wireless driver errors, you can often pinpoint the failing subsystem and decide whether replacement is warranted.

Frequent “WAN” or “link” errors on the router admin page often correlate with router-side WAN handling problems or intermittent cable/port faults.

Repeated status-indicator fault messages are frequently the router’s way of reporting driver resets, authentication failures, or modem negotiation issues.

If errors appear right after you attempt to connect, it can indicate firmware instability triggered by specific client devices or authentication modes.

What to look for:

– Router admin page shows frequent “WAN” or “link” errors. If the log shows multiple link-down/link-up events close together, the router may be flapping or the WAN link path is unstable.

– Lights or status indicators report repeated faults. Many routers log and surface fault states as well as LED indicators.

– Firmware/device errors appear after attempts to connect. If connecting a phone triggers “auth failed,” “rekey timeout,” or driver reset messages, that’s strong evidence the router is mis-handling sessions.

Here are quick ways to isolate:

1. Check whether wired clients are affected at the same time logs show WAN instability.

2. Note timestamps: if disconnects line up with router log events, the correlation is meaningful.

3. Compare 2.4 GHz vs 5 GHz logs if available—some routers log per-band driver issues.

Q: What router log line matters most?
The most useful lines are those that repeat (e.g., WAN link flaps, DHCP failures, Wi‑Fi driver resets, authentication/rekey timeouts) and correlate with your real disconnect or lag moments.

Router Troubleshooting Quick Comparison (What to Fix First)

When you interpret logs, the decision is usually between (A) configuration/software and (B) hardware failure. This table helps you sequence actions.

Scenario	More likely	Next best step
WAN link errors spike at the same time as Wi‑Fi drops	Router WAN handling or physical port/cable	Test Ethernet to the router + swap WAN cable
Wi‑Fi driver resets appear repeatedly, even on idle or light use	Wi‑Fi hardware/radio or unstable firmware	Update firmware, then factory reset (if needed)
Logs show DHCP renewals and clients “re-acquire” addresses	DHCP instability (router) or network conflict	Check IP conflicts, reboot, then consider replacement

Troubleshoot Before Replacing Your Router

Before you buy new hardware, confirm with fast, controlled tests. Many “router failures” are actually firmware glitches, power/cable issues, or configuration drift—especially when everything was fine until an update or a layout change.

A power cycle can clear stuck network states (NAT/DHCP tables) and rule out transient firmware lockups.

Testing with Ethernet is the deciding experiment: if Ethernet is stable, the router’s Wi‑Fi path is the likely failure point.

Updating firmware and then resetting only when necessary can resolve driver and compatibility issues without replacing hardware.

Try this sequence (in order):

– Power cycle: unplug, wait 30 seconds, then restart.

This gives internal capacitors time to discharge so the router doesn’t resume from a partially corrupted state.

– Try Ethernet to rule out Wi‑Fi problems.

Connect a laptop/PC directly to the router LAN port and run the same tests you ran on Wi‑Fi: speed, ping latency (to gateway and to an internet endpoint), and whether drops occur.

– Update firmware and reset settings if needed.

If your router UI supports updates, apply the latest stable firmware for your model. If problems persist, consider a factory reset—then reconfigure carefully (especially WAN settings, Wi‑Fi names/passwords, and security mode).

If you’re managing a business network, log your tests (date/time, client type, band used, what the router UI shows). In my field experience, that documentation speeds up both internal troubleshooting and ISP/vendor support—because it turns “it’s slow” into “latency spikes coincide with Wi‑Fi driver resets at 14:32.”

Finally, make a practical go/no-go decision:

– Replace the router when disconnects/restarts continue after firmware update + stable Ethernet testing, or when overheating/smell appears.

– Avoid replacement when Ethernet is stable and only Wi‑Fi degrades—often that indicates configuration (channel width, band steering, QoS) rather than total hardware failure.

Pros/cons approach (so you don’t overspend):

– Pros of replacing: immediate improvement, reduced time troubleshooting, better security posture with newer firmware.

– Cons of replacing: cost, migration time, and risk that the real issue is ISP equipment or bad cabling.

Conclusion

If you’re seeing frequent disconnects, slow speeds, odd restarts, or failing signal performance, those are strong signs your router is going bad. Start with quick checks (reboot, test with Ethernet, and review router status), and if problems persist after basic troubleshooting, it may be time to replace the router—so you can get back to stable, reliable internet.

Frequently Asked Questions

What are the most common signs your Wi‑Fi router is going bad?

Common signs include frequent Wi‑Fi drops, devices connecting and then disconnecting repeatedly, slow speeds that don’t match your internet plan, and needing to reboot the router often. You may also notice increasing latency for online gaming or video calls, overheating (hot casing, burning smell), or flashing error lights that indicate a firmware or hardware fault. If multiple devices experience the same issues at different locations in your home, the router is often the culprit.

How can you tell if your router is causing slow internet speeds?

Start by testing speeds on a wired device (Ethernet) connected directly to the router; if wired speeds are normal but Wi‑Fi is slow, the router’s wireless radios may be failing. Then compare results at different times and positions—bad signal patterns near the router can point to failing antennas or overheating. If both wired and wireless speeds are poor and the problem persists across reboots, the router’s CPU, RAM, or networking hardware may be degrading.

Why does my router keep rebooting or losing connection?

Router reboots can indicate overheating, failing power supply components, unstable firmware, or a hardware breakdown in the CPU/ethernet switch. Check whether the router feels unusually hot, ensure it’s in a ventilated area, and confirm you’re using a reliable power adapter. If the issue started after an update, try rolling back firmware or factory resetting (after backing up settings) and monitor whether the random resets stop.

Which troubleshooting steps can confirm whether the router is failing hardware?

Use a step-by-step process: restart the router once, update firmware if possible, and change Wi‑Fi channels or enable a stable band (2.4 GHz vs 5 GHz). Next, test with Ethernet to rule out wireless issues, and temporarily bypass the router (if you have a modem/router setup) to isolate whether the modem or router is the cause. If the symptoms remain after basic fixes—especially with wired connections and consistent modem behavior—the router is likely going bad.

Best way to test whether your router is the problem before buying a replacement?

Run controlled tests: compare speeds and connectivity on a wired device versus multiple Wi‑Fi devices, and test close to the router and farther away. If you have access to another router, swap it temporarily to see if performance stabilizes across your home—this is one of the quickest ways to confirm the source. Also check router event logs and LED status lights for persistent errors; if you see recurring hardware-related alerts alongside dropouts, replacing the router is often the best next step.

📅 Last Updated: September 27, 2026 | Topic: how to tell if your router is going bad | Content verified for accuracy and freshness.