Key Takeaways
Why Methodical Troubleshooting Outperforms Random Fixes
Home network problems tend to produce the same symptom — no internet — regardless of their actual cause. That surface similarity leads many people to cycle through random fixes: restarting devices in no particular order, switching devices on and off, or immediately calling ISP support without any diagnostic data. This approach wastes time and rarely produces a lasting resolution.
A structured, layered approach works because home connectivity follows a predictable path: your ISP delivers a signal to your modem, the modem passes it to your router, and the router distributes it to your devices over wired or wireless connections. A problem at any one of these layers produces downstream failures — but the fix at each layer is different. Identifying exactly where the chain breaks is what makes troubleshooting efficient.
The steps below move from the outside in: ISP and modem first, then local network, then individual devices. This sequence prevents you from spending time adjusting router settings when the actual issue is an ISP outage, or vice versa.
Document Your Baseline Performance
Run a speed test when your connection is working normally and save the results. Having a baseline makes it much easier to identify when performance has genuinely degraded versus when your expectations may not match your plan's actual tier.
Before you begin, gather what you'll need:
What you will need
And make sure you have the right tools on hand:
Ethernet cable
Used to connect a device directly to the modem or router to test whether a problem is Wi-Fi-related or network-wide.
Web browser with speed test access
Used to run a speed test (e.g., via fast.com or speedtest.net) to measure actual download and upload performance.
Router admin panel login credentials
Needed to access router settings, check firmware version, review connected devices, and change wireless channel settings.
Smartphone or secondary device
Used as an independent test device to confirm whether a connectivity issue is isolated to one device or affects the whole network.
Working Through the Layers: From ISP to Device
Follow the steps below in order. Each one either resolves the problem or produces information that narrows down the cause for the next step. Resist the urge to skip ahead — the value of this process is precisely its sequence.
Check for a known outage in your area
Before touching any hardware, visit your ISP's outage map or status page — most carriers maintain one accessible via mobile data or a secondary device. If a widespread outage is confirmed, no amount of local troubleshooting will restore service; your only recourse is to wait for the provider to resolve it.
Also check whether your service account is in good standing. A lapsed payment can trigger an automatic suspension that mimics a hardware failure.
Restart your modem and router in the correct sequence
Power down your router first, then your modem (or gateway). Wait a full 60 seconds — this allows the modem to fully release its connection with your ISP's infrastructure. Then power the modem back on and wait for it to fully connect (indicator lights stabilize) before powering the router back on.
This sequence ensures the router receives a fresh IP address assignment from the modem rather than inheriting a stale or conflicted one.
Test the modem's direct connection with a wired device
Plug a laptop or desktop directly into the modem using an Ethernet cable, bypassing the router entirely. If internet access is restored, the problem lies within your router or Wi-Fi network — not with the ISP signal. If the wired connection to the modem also fails, the issue is upstream: either the modem itself or the ISP's delivery to your home.
Understanding this split is the most important diagnostic step in the entire process. For more context on how these devices relate, see our guide to modems, routers, and gateways.
Run a speed test and compare against your plan
With a wired connection active (ideally direct to the modem or router), run a speed test using a reliable tool. Compare the result against the speeds specified in your ISP plan. Sustained speeds below 50–60% of your advertised tier, during non-peak hours, warrant a call to your provider.
Keep in mind that advertised speeds are typically maximums, not guarantees — but a consistent, large gap between promised and delivered performance is a legitimate service issue worth escalating.
Isolate whether the problem is Wi-Fi-specific
If the wired connection is healthy but wireless devices are struggling, the issue is within your local Wi-Fi environment. Common causes include channel congestion from neighboring networks, physical obstructions, or a router that needs a firmware update. Log into your router's admin panel to check for available updates and to review which wireless channel your network is currently using.
Switching from a congested channel to one with less interference — particularly on the 2.4 GHz band — can meaningfully improve performance without any hardware changes. For a deeper look at improving whole-home coverage, see our guide on Wi-Fi layout and placement principles.
Test with a second device to isolate device-specific issues
If one device has connectivity problems but others on the same network work normally, the fault is almost certainly with that specific device — not your network. Common device-level fixes include forgetting and rejoining the Wi-Fi network, flushing the DNS cache, or checking whether a VPN or firewall application is interfering with the connection.
On Windows, running the built-in network troubleshooter or using ipconfig /release and ipconfig /renew in the command prompt can resolve IP address conflicts. On macOS, renewing your DHCP lease from the Network settings panel accomplishes the same goal.
Contact your ISP with specific diagnostic data
If you've worked through these steps and the problem remains unresolved at the modem or ISP level, call your provider's technical support line. Come prepared: note down the exact symptoms, when the problem started, what you've already tested, your speed test results, and whether indicator lights on your modem show any error states (a red or blinking WAN light is particularly relevant).
Specific, documented observations move you past first-tier scripted troubleshooting faster and increase the likelihood of a technician visit being scheduled if one is warranted. For background on connection types and what your ISP is actually delivering, see Home Internet Explained.
Don't Skip the Sequence
Troubleshooting network hardware out of order — restarting the router before the modem, or skipping device isolation — often produces misleading results. Follow the steps from the outside in: ISP connection first, then your local network, then individual devices. Each layer informs the next.
If you resolve the issue at the Wi-Fi layer but find that dead zones or weak signals are a recurring problem, our guide to whole-home Wi-Fi coverage covers placement and equipment principles that address the root cause. For those setting up a network from scratch, the home network setup checklist is a useful starting point. If you're curious whether a wired connection might eliminate your Wi-Fi headaches entirely, see our comparison of wired vs. wireless home internet.
Avoid Factory Resets Without Preparation
A factory reset on your router wipes all saved settings, including your Wi-Fi network name, password, and any custom configurations. Only perform a reset as a last resort, and make sure you have your ISP account credentials and router login information on hand before doing so.