Is My Internet Down? How to Tell — and What's Actually Causing It

Few tech frustrations hit harder than opening a browser and getting nothing. Before you call your ISP or restart everything in sight, it helps to understand what "internet down" actually means — because the problem is rarely just one thing, and where the fault lies changes everything about how you fix it.

What Does "Internet Down" Actually Mean?

The phrase covers at least three distinct situations that feel identical from the user's seat:

• Your device has lost its connection to the router or modem
• Your local network is working, but the modem can't reach your ISP
• Your ISP's network is up, but a specific site or service is down

Treating all three the same way wastes time. Restarting your router won't fix a Netflix outage, and calling your ISP won't help if the problem is your Wi-Fi adapter.

Step One: Is It Just You, or Everything?

The fastest first check: try a different device on the same network. If your laptop has no internet but your phone does, the problem is device-specific — a driver issue, a misconfigured network setting, or a software conflict. If nothing on the network works, you've narrowed it to the router, modem, or the ISP connection itself.

Quick device-level checks:

• Is Wi-Fi enabled? (It sounds obvious — it's the most common cause)
• Is the device connected to the right network, not a neighbor's or a forgotten guest network?
• Has the device's IP address been assigned? A "169.254.x.x" address on Windows means DHCP failed — your router didn't hand your device a valid address

Step Two: Check the Physical Layer 🔌

Before any software troubleshooting, look at the hardware. Routers and modems have status lights that tell you more than most people realize:

If the internet or WAN light is off or flashing red, your modem isn't reaching your ISP. At that point, the problem is almost certainly outside your home — either a line fault, a local outage, or an account issue.

Step Three: Separate the Router from the Modem

Many households now use a gateway device — a single unit that combines modem and router functions. Others use separate hardware. This matters for diagnosis:

• If you have separate devices, you can plug a computer directly into the modem with an Ethernet cable and bypass the router entirely. If that gets internet, the router is at fault. If it doesn't, the modem or ISP connection is the problem.
• If you have a combined gateway, this bypass test isn't possible, and you're more dependent on the ISP's diagnostic tools or a technician visit.

Step Four: Check for an Outage Before Troubleshooting Anything Else

If multiple devices are down and the modem light looks unhappy, your ISP is the likely culprit. Most major providers have:

• A status page or outage map on their website (use mobile data to check it)
• An automated phone line that announces known outages
• Account portals that sometimes flag service interruptions

Third-party outage trackers aggregate user reports in real time and can confirm whether others in your area are experiencing the same issue — useful when the ISP's own page hasn't updated yet.

Step Five: The Restart Sequence (Done Right)

If there's no outage and the problem seems local, the restart order matters:

1. Power off the modem (unplug it — most don't have power buttons)
2. Power off the router if it's a separate device
3. Wait 30–60 seconds — long enough for the ISP's equipment to fully de-register your connection
4. Power the modem back on first, wait for the internet light to stabilize (can take 2–3 minutes)
5. Then power on the router
6. Test a device

Skipping the wait or restarting in the wrong order often means you're just cycling power without actually resetting the connection state.

When the Problem Is Selective — Only Some Sites Are Down

If most of the internet works but specific sites or apps don't load, the issue usually isn't your connection at all. It could be:

• DNS resolution failure — your router or ISP's DNS server can't translate a domain name into an IP address. Switching to a public DNS like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) at the router or device level can test this quickly.
• The site itself is down — services go offline. A quick check from a separate network (mobile data) confirms this.
• Routing issues mid-network — your data is reaching the internet but can't complete the path to a particular server. These are usually temporary and outside your control.

What Actually Determines How Hard This Is to Diagnose 🔍

The same symptoms can have very different causes depending on:

• Connection type — fiber, cable, DSL, and fixed wireless each have different failure modes and diagnostic steps
• Hardware age — older modems and routers are more prone to firmware bugs, overheating, and signal degradation
• ISP infrastructure quality — congestion, maintenance windows, and node reliability vary by provider and region
• Number of devices and network complexity — mesh systems, VPNs, and multiple access points introduce more potential failure points
• Technical access level — some ISP-provided modems lock users out of detailed status pages that would make diagnosis much faster

A fiber customer with a modern gateway and access to a detailed admin panel is in a very different diagnostic position than a DSL customer with a decade-old modem and no admin login credentials.

Understanding which of these situations you're in is the piece that determines whether you're looking at a two-minute fix or a call to your provider — and that depends entirely on what your specific setup looks like.