Interactive Troubleshooter

Published: Aug 31, 2026

Updated: Sep 1, 2026

Interactive: Internet Down - Is It ISP, Router, or Device?

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

An interactive root-cause diagnostic decision tree to systematically isolate complete or partial internet outages. Determine whether connectivity failure originates from your Internet Service Provider (ISP), router gateway, local network infrastructure, or client device settings.

Full Diagnostic Tree & Step-by-Step Overview

How widespread is the network connectivity failure across your devices?

All devices on the network lost internet access simultaneously
Only one specific device cannot connect, while other devices work fine
Devices connect to Wi-Fi/Ethernet, but domain names fail or loading is extremely slow

What is the current status of the WAN/Internet indicator LED on your ISP Modem or Optical Network Terminal (ONT)?

WAN/Internet light is RED, AMBER, Flashing, or completely OFF
WAN/Internet light is SOLID GREEN/BLUE, but router gives 'No Internet' warning

Diagnose Upstream ISP Outage or Fiber/Coax Physical Line Fault

Solution:

Root Cause: ISP Upstream Outage, Fiber/Coax Line Degradation, or Provisioning Lock

When the WAN/Internet status LED on your modem or Optical Network Terminal (ONT) turns red, amber, or off, the hardware has lost physical or logical sync with the ISP's CMTS (Cable Modem Termination System) or OLT (Optical Line Terminal).

Step-by-Step Fix:

1.Perform Hard Power Cycle on Modem/ONT:

Unplug the power cable from the modem/ONT and standalone router.

Wait 60 seconds to drain internal capacitors and clear stale handshakes at the ISP node.

Plug the modem/ONT back in and wait 3–5 minutes for the Online / DS/US / PON lights to stabilize before powering on the router.

2.Inspect Physical Fiber/Coax/Ethernet Connections:

Verify coaxial cable connectors are hand-tight with no bent center copper pins.

Inspect optical fiber patch cables for tight bends or cracks (do not bend fiber cables tighter than a 1-inch radius).

3.Verify ISP Status and MAC Provisioning:

Connect your smartphone to cellular data and check your ISP's official outage map or service status portal.

If you recently replaced your modem or router, call your ISP to register the device's WAN MAC Address for network authentication.

Reset Router Gateway Processes and Renew WAN IP Lease

Solution:

Root Cause: Router Gateway Memory Exhaustion, ARP Table Lock, or WAN IP Lease Expiration

If the modem shows an established ISP connection but local devices receive no internet, the router's internal gateway process has crashed, its Address Resolution Protocol (ARP) table is deadlocked, or the ISP-assigned public IP address lease expired without renewing.

Step-by-Step Fix:

1.Restart Router and Release/Renew WAN Lease:

Navigate to Advanced > WAN Settings and click Release, followed by Renew.

If inaccessible, perform a soft reboot via the admin UI or power cycle the standalone router.

2.Check Ethernet WAN Connection:

Inspect the RJ45 Ethernet cable connecting the modem's LAN port to the router's WAN (Internet) port.

Replace damaged Cat5e/Cat6 patch cables and ensure gigabit link lights illuminate on both ends.

3.Inspect Gateway DHCP Scope:

Ensure the router's internal DHCP server pool is active and has available IP addresses for clients.

What network address or error status is reported by the non-working device?

Device has an APIPA address (169.254.x.x) or 'No IP Address Assigned' error
Device has a valid IP (192.168.x.x), can ping '8.8.8.8', but websites fail to load

Reset Local Network Adapter TCP/IP Stack and Clear APIPA Lock

Solution:

Root Cause: Local Network Adapter DHCP Lease Failure or TCP/IP Stack Corruption

An IP address starting with 169.254.x.x indicates Automatic Private IP Addressing (APIPA). This occurs when the client device sends a DHCPDISCOVER packet but fails to receive a DHCPOFFER response from the router within the timeout window.

Step-by-Step Fix:

1.Reset Windows TCP/IP Stack and Winsock Catalog:

Open Command Prompt as Administrator and run:

cmd
   netsh winsock reset
   netsh int ip reset
   ipconfig /release
   ipconfig /renew

2.Flush DNS and Rebind Adapter (macOS):

Open Terminal and execute:

bash
   sudo killall -HUP mDNSResponder

Go to System Settings > Network > Wi-Fi/Ethernet > Details > TCP/IP and click Renew DHCP Lease.

3.Disable MAC Randomization or Re-Add Wi-Fi Profile:

Turn off Private Wi-Fi Address (iOS/macOS) or Random Hardware Addresses (Windows), then forget and reconnect to the network.

Configure Public DNS Resolvers and Disable Residual Proxies/VPNs

Solution:

Root Cause: Misconfigured Local DNS Resolvers, Broken Proxy, or Stuck VPN Adapter

When a device can ping public IP addresses directly (e.g., 8.8.8.8 or 1.1.1.1) but fails to load web pages in browsers, the network transport layer is operational, but Domain Name System (DNS) translation or local proxy routing is failing.

Step-by-Step Fix:

1.Configure Custom Public DNS Resolvers:

Open your OS network adapter settings.

Change DNS server assignment from Automatic to Manual and enter reliable public resolvers:

Primary DNS: 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google)

Secondary DNS: 1.0.0.1 or 8.8.4.4

2.Flush Local DNS Resolver Cache:

Windows: Open Command Prompt as Admin and run:

cmd
   ipconfig /flushdns

macOS: Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal.

3.Disable System Proxies and Residual VPN TAP Adapters:

Disable any third-party VPNs or Web Proxies under OS Network Settings.

In Windows, open sysdm.cpl or Device Manager and disable lingering virtual TAP/TUN network adapters.

What specific behavior characterizes the partial internet connection failure?

Domain names fail to resolve across all devices, but numeric IPs respond
Severe latency spikes, bufferbloat, packet loss, or random disconnects under load

Reconfigure Router Upstream DNS and Enable Encrypted DoH/DoT

Solution:

Root Cause: Upstream ISP DNS Server Outage or Port 53 Hijacking

If all devices on your network fail to resolve domain names (e.g., DNS_PROBE_FINISHED_NXDOMAIN) while direct IP routing remains functional, your ISP's recursive DNS servers are offline, slow, or experiencing routing loops.

Step-by-Step Fix:

1.Update Router-Wide DNS Settings:

Access your router administration console (e.g., 192.168.1.1).

Navigate to Network Settings > WAN/Internet Settings > DNS Settings.

Switch DNS from Get Automatically from ISP to static DNS servers:

Primary DNS: 1.1.1.1 (Cloudflare)

Secondary DNS: 8.8.8.8 (Google)

Tertiary DNS: 9.9.9.9 (Quad9)

2.Enable DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT):

Enable encrypted DNS in your browser settings (Chrome/Firefox/Edge > Settings > Security > Use Secure DNS) to bypass ISP Port 53 redirection or interception.

3.Clear Local Gateway DNS Forwarder Cache:

Reboot the router to clear its internal DNS forwarding cache table.

Optimize Router Bufferbloat (SQM) and Correct WAN Path MTU Size

Solution:

Root Cause: High Coax/DSL Signal-to-Noise Ratio (SNR) Degradation, Bufferbloat, or MTU Fragmentation

Intermittent connectivity drops, high ping jitter during uploads/downloads, or packet loss are caused by degraded physical line quality (poor SNR), unmanaged router queue congestion (Bufferbloat), or mismatched Maximum Transmission Unit (MTU) sizes.

Step-by-Step Fix:

1.Check Modem Signal Levels (Coax Cable):

Access your cable modem status page (commonly 192.168.100.1).

Check Downstream Power (should be between -7 dBmV and +7 dBmV) and SNR (should be >33 dB).

Check Upstream Power (should be between 35 dBmV and 49 dBmV). Out-of-spec values require technician repair.

2.Enable Smart Queue Management (SQM) for Bufferbloat:

Log into your router and look for QoS or SQM (Smart Queue Management).

Set upload/download speed limits to 85-90% of your advertised ISP bandwidth to prevent queue saturation during heavy traffic.

3.Perform Path MTU Discovery:

Determine optimal MTU size without fragmentation by running in Command Prompt:

cmd
   ping [www.google.com](https://www.google.com) -f -l 1472

Lower the byte length in increments of 10 until packet fragmentation stops, then add 28 (IP/ICMP headers) and set that value in your router WAN MTU settings (typically 1500 for Cable, 1492 for PPPoE/DSL).

Related Diagnostic Guides

Windows 11 Wi-Fi Connected but No Internet? How to Fix It

Google Account Suspicious Activity? How to Check for Unknown Devices

Microsoft Account Hacked? How to Recover and Secure Your Account

Fast Charging Not Working? How to Check USB PD and Quick Charge Support

Laptop Using Integrated Graphics Instead of Dedicated GPU? Here's How to Fix It

Subscribe to StepDiag

Embed Guide on Your Website