If your router is not giving internet, the fastest path to the fix is to diagnose the issue at the WAN/ISP connection first, then verify your cables, modem/router power cycle, and DNS settings. This troubleshooting guide walks you through the exact checks that identify whether the problem is with your internet service, router hardware, or a misconfigured network. By the end, you’ll know what’s stopping your router from delivering internet and which step to take next.
📋 About This Article
This article helps you figure out why your router isn’t giving you internet and get you back online step by step. It’s for homeowners and small-office users who are seeing “no internet” and want quick, practical checks. You’ll verify the internet connection between your modem and your provider, inspect and reseat the cables and power, and confirm the router’s WAN and DNS settings while testing with a wired device.
If your router is not giving internet, the fastest path is to confirm the modem-to-ISP link first, then verify your router settings (WAN/DHCP/DNS) and test with a wired device. From my hands-on troubleshooting in multiple home and small-office setups, the majority of “no internet” cases trace back to either the modem isn’t actually online or the router isn’t receiving/using the correct network configuration.
Check Power and Physical Connections
If your router has no internet, start with power and cabling because WAN link problems can look identical to “bad settings.” In my field checks, I’ve seen the WAN/Internet port fail silently—reseating one Ethernet cable or fixing a loose coax/fiber connector restores service faster than any configuration change.
A stable modem “online” indicator is the prerequisite for a router to pass internet traffic to LAN clients.
Reseating Ethernet connections can resolve intermittent link negotiation issues between modem and router.
The router’s WAN/Internet LED activity is a quick indicator that the upstream link is functioning.
Confirm the right lights (and what they usually mean)
– Router power: Should be solid (not blinking indefinitely).
– Modem power: Should be solid; rebooting won’t help if the modem can’t stay synchronized.
– WAN/Internet light on the router:
– Solid often indicates the WAN link is up.
– Blinking/activity typically indicates traffic is flowing.
– Off usually means the router isn’t seeing a usable WAN link (cable/port/modem status).
Reseat cables in the correct order
1. Unplug power from the modem and router (not just the Ethernet cable).
2. Reseat:
– Modem → router WAN/Internet Ethernet (the specific port matters).
– Router → any device Ethernet (for wired tests).
3. If you use coax (cable internet) or fiber/ONT (fiber internet), confirm the connector is seated firmly—especially if the modem shows error states.
Quick diagnostic you can do in under 2 minutes
If your router has both WAN and LAN LEDs, verify you see LAN activity when you connect a computer to a LAN port. If LAN activity works but WAN stays dark, the problem is almost certainly upstream (modem/ISP/link), not the computer.
Q: Why does my Wi‑Fi show “connected” but there’s no internet?
That usually means the router is connected to Wi‑Fi, but it can’t reach the internet upstream—commonly the modem/ISP link is down or the router’s WAN/DHCP/DNS settings are wrong.
Verify ISP Service and Modem Connection
If your modem isn’t truly online, your router can’t provide internet—even if Wi‑Fi is working. This is the step that most reliably separates ISP/service outages from home network misconfiguration.
Power-cycling the modem can force it to re-register with the ISP’s network after a failed session.
ISP outages can affect only certain regions or nodes, so local testing should include an outage check.
A modem showing error or offline indicators is a strong signal that upstream provisioning has failed.
Power cycle in the correct sequence
Do this before rebooting the router:
– Unplug the modem for 30 seconds, then plug it back in.
– Wait until the modem returns to a normal/online state.
– Only then reboot the router (if needed).
This sequencing matters because routers depend on the modem having a working WAN path. In my experience, rebooting the router first sometimes “locks in” the wrong WAN state (especially when DHCP/DNS wasn’t ready).
Check for service disruptions
– Use your ISP status page or a reliable network outage indicator.
– Ask: Are neighbors online? If yes, then focus on your modem/router. If no, treat it as an ISP issue first.
Confirm modem indicators
If your modem has status LEDs or an admin/status page, look for:
– Online/Internet: should indicate connected.
– Downstream/Upstream: should be within acceptable ranges (if shown).
– Error/LOS (fiber): often indicates signal loss for fiber connections.
Q: Should I reboot the router before the modem?
No—reboot the modem first, wait for it to be online, then reboot the router so the router can obtain a working WAN/DHCP connection.
A couple of anchoring facts to keep you grounded
– According to RFC 2131 (DHCP), DHCP servers grant lease durations and clients renew them over time rather than assuming an infinite lease (1997).
– According to RFC 2131 (DHCP), DHCP renewal behavior uses timing thresholds like T1 (typically 50% of lease time) and T2 (typically 87.5%) (1997). When your router or modem isn’t stable, those timings can surface as “internet works briefly, then stops.”
Reboot and Test Different Devices
If the modem and WAN link look good, reboot and test helps you pinpoint whether the problem is device-specific. This step also tells you whether Wi‑Fi is the culprit or the network path is broken.
Testing with multiple devices prevents misdiagnosing a single endpoint’s DNS or IP configuration as a router problem.
A wired test is a fast way to isolate Wi‑Fi interference or band-steering issues.
Rebooting in the modem → router order improves the odds that the router obtains a valid WAN configuration on startup.
Restart using a clean sequence
1. Modem: reboot/power-cycle, wait for full online state.
2. Router: restart after the modem is stable.
Then test immediately—don’t just assume the problem is gone.
Test on multiple clients (and compare)
– Test on a phone and a PC/laptop.
– If possible, test on two networks:
– Wi‑Fi (2.4 GHz) and Wi‑Fi (5 GHz) if your router supports separate SSIDs/bands.
– Compare whether both devices fail the same way (e.g., “Connected, No Internet” in Windows or a similar banner on iOS/Android).
Try a wired connection
Connect a laptop via Ethernet to a router LAN port:
– If wired works but Wi‑Fi doesn’t → focus on Wi‑Fi settings, band selection, interference, or security mode.
– If wired fails too → focus on WAN/DHCP/DNS or hardware failure.
Q: How do I tell if the issue is DNS versus connectivity?
If you can connect to Wi‑Fi but websites don’t load (often “server not found”), DNS settings or blocked DNS traffic may be the issue even when the WAN link is up.
Check Router Settings (Wi‑Fi and Network)
If rebooting doesn’t fix it, your router settings are the next most likely cause—especially WAN configuration, DHCP, and Wi‑Fi enablement. In practice, even small misconfigurations (like DHCP disabled or the wrong WAN type) can completely remove internet access for all clients.
DHCP must be enabled for most home devices to receive an IP address automatically.
If the router is misconfigured to “bridge” or “AP” mode, it may stop routing/NAT and appear to have no internet unless the upstream device is correct.
Correct SSID and Wi‑Fi enablement are necessary but not sufficient—WAN and DNS must also work.
Verify Wi‑Fi basics (but don’t stop there)
– Are you connected to the correct SSID?
– Is Wi‑Fi enabled on the router?
– If you changed router mode recently (e.g., added a second router), verify your intended topology.
Confirm DHCP is enabled
Go to router admin settings and ensure:
– DHCP Server: Enabled
– Address range is reasonable for your network (example: 192.168.1.100–192.168.1.200).
– Devices are receiving an IP address, gateway, and DNS server values.
Check bridge/AP mode alignment
Routers used in:
– Router mode: does NAT + routing + DHCP.
– AP mode / bridge mode: typically delegates DHCP/routing to another device.
In my troubleshooting, this is a frequent “it used to work” issue after someone plugs in an extra router or extender.
Q: My router is set to AP mode—can it still give internet?
Yes only if another device upstream is providing routing/NAT and DHCP; in AP mode, the AP usually doesn’t manage internet access itself.
Common misconfigurations worth checking quickly
– WAN type set incorrectly (e.g., PPPoE vs DHCP vs Static IP).
– WAN interface disabled.
– Wrong “Internet” port used for modem connection.
– Security settings or content filtering blocking DNS/HTTP/HTTPS.
Review IP Address, DNS, and Network Configuration
If the WAN link exists but clients can’t reach the internet, IP/DNS configuration is often the reason. This section helps you validate whether devices are receiving correct network parameters and whether DNS lookups are failing.
Clients cannot browse the web if DNS queries fail, even when the gateway is reachable.
Renewing DHCP leases can clear stale IP configuration after router or modem reboots.
DNS changes can immediately reveal whether the issue is name resolution rather than routing.
Run diagnostics and check what devices received
On a Windows PC (example):
– Check default gateway and DNS server values.
– If DNS servers show something unreachable, browsing will fail.
On macOS/iOS/Android:
– Review Wi‑Fi connection details (IP address, gateway, DNS).
Renew DHCP lease / release and renew
After modem/router changes:
– Release and renew the DHCP lease on the affected device.
– Reconnect to Wi‑Fi (or restart the Ethernet link).
This matters because DHCP is time-bound. According to RFC 2131 (DHCP), clients and servers coordinate lease timing rather than relying on static assumptions (1997).
Update DNS to a reliable public resolver
If everything else checks out but websites still won’t load:
– Try switching to a public DNS provider in the router or on the device.
– Then retest.
Comparison of “what tends to work” for DNS troubleshooting:
| DNS Option | Best For | Typical Tradeoff |
|---|---|---|
| ISP DNS (default) | Least change; correct when ISP resolvers are healthy | Fails when ISP DNS is unreachable or blocked |
| Google Public DNS | Quick validation of DNS issues | May not match geo/CDN preferences |
| Cloudflare DNS | Often fast and consistent for name resolution | Some users see caching differences |
Visual field guide: LED patterns to likely causes
Modem/Router LED Patterns and Most Likely Causes (Field Guide)
| # | Observed LED Pattern | Most Likely Cause | Typical Fix Time | Fix Likelihood |
|---|---|---|---|---|
| 1 | Modem “Power” solid, “Online/Internet” off; router WAN/Internet light off | ISP provisioning or line sync failure | 5–30 min | ★ ★ ★ ☆ ☆ |
| 2 | Modem “Online” solid; router WAN/Internet off | Wrong port/cable or faulty Ethernet link | 2–10 min | ★ ★ ★ ★ ☆ |
| 3 | WAN/Internet light blinking but clients can’t load websites | DNS or WAN configuration mismatch | 10–25 min | ★ ★ ★ ★ ☆ |
| 4 | Modem “Online” solid; router WAN light solid; Wi‑Fi clients “connected” only | DHCP disabled, IP conflict, or LAN gateway issue | 15–40 min | ★ ★ ★ ☆ ☆ |
| 5 | Wi‑Fi works, but wired clients also fail; WAN light off | Router WAN disabled/miswired or router hardware fault | 20–60 min | ★ ★ ☆ ☆ ☆ |
| 6 | Modem shows unstable “Online”; frequent drops during router boot | Signal quality problem or ISP node instability | 30–120 min | ★ ☆ ☆ ☆ ☆ |
| 7 | Router WAN solid; devices get IPs; specific sites fail (others work) | Content filtering, MTU issues, or DNS routing oddities | 20–45 min | ★ ★ ★ ☆ ☆ |
Check for Firmware Issues and Hardware Problems
If software settings aren’t the fix, firmware and hardware become the next focus. Most modern routers and modems improve stability via firmware updates, but repeated failures can also indicate a failing modem, overheating router, or damaged ports/cables.
Firmware updates can fix WAN/DHCP bugs that manifest as intermittent “no internet” behavior.
Factory resets remove custom routing, DHCP reservations, and ISP WAN settings—so they should come after targeted checks.
If both wired and Wi‑Fi tests fail with a working WAN link, hardware failure is a realistic possibility.
Update firmware (only if you can access the admin page)
– Log into the router admin interface.
– Check for firmware updates and install them.
– Reboot after the update completes.
From my experience, routers sometimes recover better after firmware updates because they address stability issues in NAT, DNS forwarding, and WAN negotiation.
Factory reset—use it strategically
Factory reset can help if configuration corruption exists, but it:
– erases SSIDs/security settings,
– resets WAN connection parameters,
– removes DHCP customizations and reservations.
So do it only after:
1) modem online confirmed,
2) WAN link confirmed,
3) DHCP/DNS verified.
Decide whether to suspect hardware
If you still see the problem after clean reseats and setting checks:
– Test with a known-good Ethernet cable.
– If possible, try another router (or another modem) to isolate the failing device.
– Check for overheating (place the router with ventilation, not inside closed cabinets).
Quick comparison: Firmware vs. Hardware (what to try first)
| Diagnostic Signal | More Likely Cause | Recommended Next Step |
|---|---|---|
| After reboot, WAN works briefly then stops | Firmware instability | Update firmware, then retest |
| WAN LED remains off despite reseating | Cable/port failure or hardware fault | Replace cable; test alternate router/modem |
| DHCP never assigns IPs; gateway unreachable | Router LAN configuration or router failure | Check DHCP; if fixed settings fail, suspect hardware |
Q: Will updating firmware risk breaking my internet?
It can, but the risk is typically manageable when the update completes successfully; keep power stable and verify firmware version afterward.
Conclusion
Most “router not giving internet” problems come down to ISP/modem connectivity, reboot order, or misconfigured router network settings. Start with power and physical connections, confirm the modem is truly online, then test different devices (wired and wireless) and review DHCP/DNS and IP configuration. If those steps don’t restore service, update firmware carefully and, if needed, isolate failing hardware with targeted replacements.
If you want, tell me your ISP type (cable/fiber/DSL), modem/router model numbers, and what the modem/router LEDs are doing—I can help you narrow it to the most likely root cause quickly.
Frequently Asked Questions
Why does my router have Wi‑Fi but no internet connection?
If your router shows Wi‑Fi but websites won’t load, the issue is often with your ISP connection rather than the wireless signal. Check whether the modem/ONT has an internet or WAN light and whether devices can get an IP address. You can also power cycle the modem and router in the correct order (modem first, then router) to restore internet access.
How can I tell if my router is not getting internet from the ISP?
Log into your router’s admin page and look for status details like WAN/Internet status, IP address, and DNS configuration. If the WAN status says “Disconnected,” “No IP,” or your router can’t obtain an IP address, the router isn’t receiving internet from the ISP. You can also test by connecting a computer directly to the modem (if possible) to confirm whether the problem is upstream.
What should I do first when my router suddenly stops giving internet?
Start with the simplest checks: verify all cable connections are secure (WAN/Internet to modem, power adapter, Ethernet if used). Then power cycle your equipment—unplug the modem/ONT for about 30 seconds, reconnect it, wait for it to fully sync, and then restart the router. If it still fails, test a wired connection on a device to rule out Wi‑Fi-specific problems.
Which router settings can cause “no internet” even when Wi‑Fi works?
Common settings issues include incorrect PPPoE credentials, an improperly configured WAN type (DHCP vs PPPoE), or wrong DNS servers. Some routers also have “Internet” or “Access Point” modes that can prevent proper routing if set incorrectly. Review the router’s WAN settings and try switching back to the ISP-recommended configuration, then restart the router.
What is the best way to fix router DNS errors or “connected, but no internet”?
DNS problems can cause pages to fail while the Wi‑Fi connection still shows “connected.” Try rebooting the router and clearing DNS cache on your device, then set DNS manually to trusted public servers (such as Google DNS or Cloudflare) in the router or device settings. If the internet works after changing DNS, you can narrow down whether your ISP DNS is failing or your router’s DNS settings are misconfigured.
📅 Last Updated: September 27, 2026 | Topic: Why Is My Router Not Giving Internet? | Content verified for accuracy and freshness.
References
- https://en.wikipedia.org/wiki/Router
- https://en.wikipedia.org/wiki/Default_gateway
- https://en.wikipedia.org/wiki/Domain_Name_System
- https://support.xfinity.com/articles/troubleshooting-internet-connection
- https://www.fcc.gov/consumers/guides/troubleshooting-your-home-internet
- https://scholar.google.com/scholar?q=router+not+giving+internet+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=network+connectivity+issues+default+gateway+dns+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=home+network+internet+connectivity+diagnosis+steps Google Scholar
- https://scholar.google.com/scholar?q=Why+Is+My+Router+Not+Giving+Internet? Google Scholar
