Tech

Diagnosing a Slow or Dropping Home Internet Connection

Home router with amber warning lights sitting on a desk with ethernet cables

Key Takeaways

  • Most home internet problems can be traced to one of four sources: the device, the router, the modem, or the ISP.
  • Rebooting your router and modem resolves a surprising number of temporary slowdowns and drops.
  • A wired ethernet connection is the fastest way to determine whether Wi-Fi is the bottleneck.
  • Running a speed test at different times of day helps distinguish congestion from a hardware fault.
  • If the problem only affects one device, the issue is almost certainly local — not your ISP.
20–45 min

Summary

18 items · 20–45 minutes

Why diagnosing internet problems in order matters

A slow or dropping home connection can come from a dozen different places — your device, your router, your modem, the cable running to your house, or a fault at your ISP's end. The most common mistake people make is jumping straight to calling their internet provider without ruling out local causes first, or conversely, spending hours fiddling with their router when the ISP's infrastructure is actually the problem.

Working through a structured checklist saves time and gives you concrete information — speed readings, timing patterns, wired vs. wireless comparisons — that makes troubleshooting far more effective, whether you're doing it yourself or describing the issue to a support technician.

If some of the terms below feel unfamiliar, the Home Network Glossary covers the key vocabulary you'll encounter, from DNS to latency to modem vs. router. It's worth a quick skim before you start.

Required

Ethernet cable

Bypasses Wi-Fi entirely so you can isolate whether the problem is wireless or affects your whole connection.

Required

Speed test website (e.g. Fast.com or Speedtest.net)

Measures your actual download speed, upload speed, and latency at any point in your troubleshooting process.

Required

Router admin panel

Lets you check connected devices, update firmware, and view Wi-Fi channel settings — typically accessed via a browser at 192.168.1.1 or 192.168.0.1.

Required

ISP outage map or status page

Quickly shows whether a service disruption in your area is responsible for the problem.

Optional

Wi-Fi analyzer app

Scans nearby wireless networks and shows which channels are congested, helping you pick a less crowded channel for your router.

How to work through this checklist

Start at the top of each group and work downward. The checklist is arranged so that the most common, easiest-to-fix causes come first. Many connection problems are resolved in the first group alone — a simple reboot of both the modem and router clears temporary faults more often than most people expect.

The single most diagnostic question you can ask is: does the problem affect every device, or just one? If only one device is slow, the problem is almost certainly local to that device and has nothing to do with your ISP. If every device is affected, the problem likely sits at the router, modem, or ISP level.

Wired speeds should match your plan

If a speed test over ethernet shows speeds dramatically lower than your subscribed plan — consistently and at multiple times of day — the fault most likely lies with your ISP or modem, not your router or devices. Document results and contact your ISP with specifics. Vague complaints are harder for support teams to act on than timestamped speed test data.

It's also worth knowing that many perceived speed problems are actually misconceptions about what affects performance. The common myths about internet speed article is a useful companion read — it addresses questions like whether having more devices on your network automatically slows things down.

Start with the basics

Restart your modem and router by unplugging both for 30 seconds, then plugging the modem in first and waiting 60 seconds before turning on the router. Must
Check whether the slowdown affects every device in your home or just one — this single question determines where to focus next. Must
Look at your router's indicator lights and compare them to the pattern described in your router's manual; a solid or blinking amber WAN light often signals a connection problem upstream. Must
Check your ISP's status page or outage map to rule out a service disruption in your area before spending time on local troubleshooting. Must

Test your actual speeds

Run a speed test (such as Fast.com or Speedtest.net) from a device connected via ethernet to get a baseline reading unaffected by Wi-Fi variables. Must
Compare your measured download and upload speeds against the plan speed listed on your ISP bill — significant shortfalls warrant a call to your provider. Must
Run the same speed test at different times of day (morning, evening peak hours) to check whether congestion is the culprit rather than a hardware fault. Should
Note your ping (latency) result — numbers consistently above 100 ms on a wired connection suggest a problem between you and your ISP, not just bandwidth. Should

Isolate Wi-Fi vs. wired issues

Plug a laptop directly into the router using an ethernet cable and re-run your speed test; if speeds improve dramatically, Wi-Fi is the weak point. Must
Move your device closer to the router and test again — if speeds improve noticeably, signal range or interference is limiting your wireless performance. Must
Check which Wi-Fi band your device is connected to (2.4 GHz vs. 5 GHz); the 5 GHz band is faster at short range while 2.4 GHz travels farther through walls. Should
Identify nearby sources of wireless interference — microwaves, cordless phones, and neighboring Wi-Fi networks can all degrade performance on the 2.4 GHz band. Nice to have

Check devices and software

Restart the specific slow device and re-test; background updates, open tabs, or a hung app can quietly consume bandwidth without obvious signs. Must
Open your device's network or task manager and look for any app consuming unusually high upload or download activity in the background. Should
Ensure your router firmware is up to date — manufacturers regularly release updates that fix stability bugs and improve performance. Should

Escalate to your ISP if needed

Document your speed test results (date, time, wired vs. wireless, measured vs. plan speed) before calling your ISP — this data makes the conversation more productive. Must
Ask your ISP to run a line test remotely; they can often detect signal degradation or noise on your line without sending a technician. Must
Request a technician visit if remote tests reveal an issue, or if your modem is more than a few years old and may no longer meet your plan's technical requirements. Should

When to call your ISP — and what to tell them

If you've worked through this checklist and the problem persists on a wired connection at multiple times of day, your ISP is the logical next step. Go into that call prepared: have your account number ready, along with a written record of at least three speed test results showing the date, time, measured speeds, and whether the test was wired or wireless.

Ask the support agent specifically to run a line test (sometimes called a signal test or diagnostic). This checks for noise, signal attenuation, or packet loss on the physical line between your home and the ISP's equipment. If they detect a fault, push for a technician visit rather than a second round of remote troubleshooting.

Don't overlook your modem's age

An older modem may not support the speeds included in a newer internet plan, creating a hard ceiling on performance that no router upgrade will fix. Check with your ISP whether your modem model is still certified for your current plan tier. If your ISP supplied the modem, ask them to verify it meets your plan's requirements.

If your connection type is unclear to you — for instance, you're not sure whether you have cable, DSL, or fibre — the breakdown of home internet types explains the differences in plain language. Understanding your connection type helps you ask the right questions and interpret what a technician tells you.

Tech Editorial Team is the collective byline for our editorial team and contributor network. Articles published under this byline or an editorial pen name are researched, written, and reviewed according to our editorial standards for clarity, consistency, and independence before publication.

View all articles by Tech Editorial Team →
Disclaimer: The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.