How to Troubleshoot Slow Cable Internet Before Replacing Your Modem

I bought a new cable modem because my internet was struggling, and the first tests after activation looked just as bad. A technician later found an old TV filter and two stages of splitting in the coax feeding my modem. After the line was simplified, the first speed test on my phone still looked low. On Ethernet, I got much better results from other test servers, and the connection was working well by the time Mike Wieger and I talked about it on Home Gadget Geeks 449.

That 2020 troubleshooting call involved several changes, so I can’t assign the improvement to one piece of hardware. It did give me a better order of operations. Start with the symptom you can reproduce, take Wi-Fi out of the test, and gather enough evidence to decide whether the coax, the modem, or the rest of the network needs attention.

1. Write down what actually fails

Record the time, the device, whether it was wired or wireless, and what happened. A call that breaks up, a modem that goes offline, and a single slow download are different symptoms. On my show, the audience heard me while I could barely hear my co-host. That described the problem better than a single upload number, although it didn’t establish where the fault was.

Check your provider’s outage page. If service is up, repeat the activity on another device where possible. One device or app failing while others behave normally gives you a different starting point from multiple devices losing service together.

2. Run a repeatable Ethernet test

Connect a capable computer to a LAN port on the router or gateway, turn off Wi-Fi on the test computer, and pause cloud backups, large transfers, and remote streams. Check the Ethernet link speed. A link negotiated at 100 Mbps will cap the test below that rate even on a faster plan. Swap in a known-good cable or try another port if the negotiated speed is unexpectedly low.

Run several tests against the same nearby endpoint and record download, upload, and latency. Try a second nearby server with the same setup, then repeat during a time when the problem normally happens. An isolated slow endpoint can reflect that particular path. If wired results are consistently good but Wi-Fi is poor in a certain room, troubleshoot the wireless network first. If wired results are consistently poor across servers, you have a better case for looking upstream. Cox’s wired and wireless speed-testing guidance.

3. Check the accessible coax and capture modem readings

Check that the coax connectors at your modem and wall jack are hand-tight. Make a note of any accessible splitters, adapters, or obvious damage along the line. Ask the provider to inspect its outside enclosure, drop, and grounding hardware. If the home uses cable TV or MoCA, tell the technician before any coax components are changed, since those services may depend on the existing layout or filters.

If your modem exposes a status page, save screenshots during a bad period and, if possible, while it’s working normally. Look for downstream receive power, downstream signal-to-noise ratio, upstream transmit power, and channels that lose lock. The model’s documentation is the reference for its expected readings. Channel type and bonding matter, and a normal snapshot can miss an intermittent problem. ARRIS’s S33/S34 signal-level guide shows what those fields look like.

4. Give your ISP something it can investigate

Send the provider the affected times, the modem model, the results from at least two wired test endpoints, and any screenshots showing signal changes or loss of lock. Ask whether it can see modem disconnects or signal problems around those times. If the pattern calls for a visit, ask the technician to compare the incoming signal with the signal at the modem and check for unnecessary components in between.

Repeat the same wired test after the visit and try the activity that originally failed. If the trouble only occurred at a particular hour, test again during that window. Keep the before-and-after results so you have a useful record if it returns.

5. Decide whether the modem actually needs replacing

A replacement makes more sense if your provider says the current model is unsupported for your plan, it can’t be provisioned, or testing has isolated a fault to the unit. Confirm that the replacement is on your provider’s compatibility list for your service tier before ordering. If you swap hardware, use the same wired setup and endpoints afterward so the comparison tells you something. ARRIS troubleshooting and provider compatibility guidance.

Frequently asked questions

Can one bad speed test prove my modem is failing?

A single test measures the connection between one device and one endpoint at one moment. Repeat over Ethernet and across endpoints, then compare the results with the actual symptom.

Can a coax splitter affect cable internet?

A splitter adds signal loss to the coax path. Whether it matters depends on the signal reaching the modem and the rest of the installation. Ask the provider to measure both ends and identify which components your setup needs.

What if my download speed is fine but calls still break up?

Check upload and latency while a backup or remote stream is running, then pause it and repeat. If the issue persists while wired and with other traffic paused, record the time and report the call symptoms along with your test results.

Where can I hear the original troubleshooting story?

Start around [3:14] in HGG449. The technician visit starts around [9:12] and the test-server comparison around [12:55]. For a separate example of using network monitoring to track down sustained traffic, see HGG451 and the 6 TB sync failure.