I replaced my router twice before realizing a 10-year-old cable was the real problem

Published Aug 22, 2026, 5:00 PM EDT Korbin is a Linux system administrator who spends most of his time in a terminal figuring out how things actually work. Over the last decade he's written hundreds of articles about Linux configuration, troubleshooting weird problems, and using open-source tools in the real world. He also works a lot with Windows systems and networking, especially in mixed environments where things don't always behave the way the documentation says they should. Writing things down is how he makes sense of it all and hopefully saves someone else a few hours. Routers always take the immediate blame for bad Wi-Fi, when in fact there is a list of suspects that should be investigated. I learned this the hard way. After a lengthy stream of router troubleshooting and replacing the device twice, the real culprit behind my network bottleneck finally revealed itself: an old Cat 5 Ethernet cable connecting my modem to my router. It's pretty embarrassing admitting that, because it's such a silly problem to overlook for that long. I honestly hadn't considered that an outdated cable could be mixed into my setup. Plus, since my router and modem live in the basement, I was convinced it was just a coverage problem, and I chased that line until I realized the real issue. A year of applying the wrong fix I threw money at new routers instead of addressing the real problem Mercusys mesh wifi system changed my life after I struggled with a WiFi extender for so long. The original complaint with my network really was a coverage problem, so I treated it like one. I had my router in the basement, sending signals through two floors and a bunch of walls. It's hard to get great coverage from any hardware with that kind of setup, but that's where the ISP fed the coax line into my house, and where my modem sat. My first attempt at solving the problem involved replacing the router and installing a mesh Wi-Fi network, which included two nodes upstairs. Signal strength instantly improved everywhere, but I still couldn't achieve the speeds I was paying my ISP for. Worse, the connection would drop completely whenever I tried to download a big file. Looking back, I realize that was because the Cat 5 cable was limited to 100 Mbps of throughput, and when the line got fully saturated, everything would stop working, even wired devices. After a while on that mesh network, I called my ISP to bump up my plan to 500Mbps, hoping that would address the lingering issue. Obviously, it didn't. And I wasn't getting anywhere near the advertised rate when I ran a speed test. So, I went back to the store to get an even better mesh Wi-Fi network. While wiring up the new router, I glanced at the cable in my hand. It had the words "Cat 5" printed right on it. I had used Cat 5e and Cat 6 cables elsewhere, and I knew that Cat 5 sounded outdated. When I checked online for the cable's maximum throughput, the bottleneck became clear. There was no reason to use that Ethernet cable, because I had spare Cat 5e cords lying around. I think it came from an ISP installation years earlier, and I'd just never considered that there'd be such an obsolete cable still surviving in my setup. The cable never made itself obvious It slowed everything down without outright failing What made the issue difficult to pin down was that the cable didn't fail loudly. Instead, it negotiated transfer speeds down to 100Mbps and kept working, just slowly. As for the times it'd take the network down completely, it was too easy to (erroneously) blame the router. Admittedly, I should've done a full inspection of my network setup and found the problem sooner, but I'd bought into the common way of thinking that Wi-Fi problems should be attributed to the router, and that replacing the device or paying the ISP more money ought to fix it. Swapping in a Cat 6 cable took all of ten seconds, and I instantly began receiving all the bandwidth I was paying for. I lived with this problem for well over a year, so if any of this sounds familiar, please take my experience as a sign to walk all your cabling and check for bottlenecks. A latency test won't reveal anything, but a big data transfer should expose the cracks, as it did in my situation. For any transfer that took five minutes or longer, there was about a 50% chance the entire network would come down. The router is usually the one responsible But it's not the only thing worth checking The instinct to blame the router didn't serve me well that time, but let's be honest: Wi-Fi problems are usually the router's fault. My network improved overall as soon as I migrated over to mesh Wi-Fi; it just didn't fix every problem. The dips in speed and occasional crashes should've been my clue that something else was wrong, but it was my first time using mesh Wi-Fi in my house, so I assumed I simply needed a stronger device. My biggest mistake was the order I did things in. Reading a cable jacket takes five seconds, whereas replacing my network with a mesh system took an afternoon and cost hundreds of dollars. The lesson I take away is to check the simplest things first, especially when it costs nothing to do so. My original mesh system was perfectly sufficient the entire time. I don't regret the newer one, since it's better gear and I'd have gotten there eventually, but I bought it for the wrong reason. Check the cheap stuff before buying expensive stuff A network is only as fast as its slowest link, and mine happened to be the old cable nobody looked at in the last 15 years. Two mesh systems and a plan upgrade didn't help me until I dropped in a four-dollar cable to replace the old one. For future troubleshooting, I now check the simplest and easiest things first.