Why Isn't My Internet Working? Common Causes and How to Diagnose Them

Few things are more frustrating than sitting down to work, stream, or browse — and finding your internet has stopped working. The problem could be anywhere from your device to your router to your ISP's infrastructure, which is exactly why it feels so hard to pin down. Understanding the layers involved helps you figure out where the breakdown actually is.

How Your Internet Connection Actually Works

Your connection isn't a single thing — it's a chain. Data travels from your device, through your home network, through your modem, out to your ISP, and eventually to whatever server you're trying to reach. A failure at any point in that chain produces the same symptom: no internet.

That's why "the internet isn't working" is really shorthand for one of several distinct problems:

• Your device can't connect to the router
• Your router is connected locally but has no WAN (wide area network) access
• Your modem isn't communicating with your ISP
• Your ISP is experiencing an outage
• A DNS issue is preventing addresses from resolving (sites appear down but the connection is technically live)
• A specific site or service is down, not your internet

Each scenario looks identical from the user's perspective but requires a different fix.

Start With the Basics: Isolation and Elimination

Check Other Devices First

If only one device can't connect, the problem is almost certainly that device — its Wi-Fi adapter, network settings, or software. If every device on your network is affected, the issue is upstream: your router, modem, or ISP.

The Classic Restart (and Why It Works)

Routers and modems run embedded software that can get into bad states — memory fills up, DHCP leases expire, firmware bugs surface. A full power cycle (unplug, wait 30 seconds, plug back in — modem first, then router) clears those states. This resolves a surprising number of unexplained outages.

Check Your Router's Lights 🔦

Most routers have indicator lights that tell you exactly what's broken:

A red or unlit Internet/WAN light almost always means the problem is between your modem and your ISP — not your device or router.

Common Causes by Layer

Device-Level Issues

• Wi-Fi is toggled off — easy to accidentally enable airplane mode or disable Wi-Fi on a laptop
• Incorrect saved password — if you recently changed your Wi-Fi password, devices still remember the old one
• Driver or adapter issues — on Windows especially, a corrupted or outdated network driver can drop connectivity silently
• IP address conflicts — two devices assigned the same IP address can cause intermittent failures
• VPN interference — active VPN clients sometimes block all traffic when the VPN tunnel drops

Router and Home Network Issues

• Overheating — routers placed in enclosed spaces or near heat sources can throttle or shut down
• Firmware bugs — some firmware versions introduce instability; checking for updates (or rolling back) can help
• Channel congestion — in dense apartment buildings, dozens of networks competing on the same Wi-Fi channel can effectively kill performance without showing as "disconnected"
• MAC filtering or firewall rules — security settings that were changed and forgotten

Modem and ISP Issues

• Loose or damaged coax/phone cable — physical connections at the wall or back of the modem matter
• ISP outage — check your provider's outage page or a site like Downdetector from your phone's cellular data
• Provisioning issues — after a modem replacement or account change, ISPs sometimes need to re-authenticate your hardware
• Data cap reached — some plans throttle speeds to near-zero once a monthly cap is hit, which feels like an outage

DNS-Specific Problems

DNS (Domain Name System) translates human-readable addresses like google.com into IP addresses. If your DNS server is unreachable or slow, websites appear broken even though your internet connection is technically fine.

A quick test: if you can load a page by typing a raw IP address but not by domain name, DNS is the culprit. Switching to a public DNS server (Google's 8.8.8.8 or Cloudflare's 1.1.1.1) in your network settings is a common workaround.

Why the Same Symptom Has Different Fixes

Two people can experience "internet not working" in ways that require completely opposite solutions. One person's problem is a misconfigured device setting; another's is a damaged cable outside their building. One household's issue is a router that needs a firmware update; another's is an ISP provisioning error that requires a phone call.

The variables that determine which fix applies include:

• Connection type — fiber, cable, DSL, and fixed wireless have different failure modes
• Hardware age — older modems and routers are more prone to instability and may not support current ISP requirements
• Network complexity — mesh systems, network switches, and multiple access points add more potential failure points
• Number of affected devices — narrows down whether the issue is local or upstream
• When it started — after a storm, after a router restart, after a software update, or gradually over time each point to different causes
• Whether it's total loss or just slow — congestion, throttling, and interference cause degraded performance, not necessarily complete outage

🔍 Methodical elimination — starting at your device and working outward toward the ISP — is consistently more effective than guessing. The exact path through that process, and what you find at each step, depends entirely on your specific setup.