How to check if your WiFi router is working: step-by-step diagnostics

A sudden internet outage always takes you by surprise. At this point, the main question arises: is the problem with the provider, or has the device distributing the network failed? Before calling technical support or rushing out to buy new equipment, it's important to run a basic diagnostic. Router — is a complex electronic device, and its failure can be either software or hardware related.

In this article, we'll explore all the available methods for pinpointing the source of a fault with high accuracy. You'll learn how to read signals. indicators, conduct connection tests via the command line and distinguish between a banal network overload and a physical failure routerProper diagnostics will save you time and money.

Users often confuse the lack of access to specific websites with complete hardware failure. It's important to understand the difference between a local network and the global internet. Local connections may work properly even if the provider has disabled the service.

Visual assessment of the status of indicators

The first and fastest way to understand what's going on with your device is to look at its front panel. LED indicators The LED (light emitting diode) is the router's "face," indicating the status of its systems. If all the lights are out, check that the power supply is plugged in and that the plug is firmly seated in the device's socket.

The normal state is when the power indicator is on (Power) and the wireless network indicator is flashing (WiFi). The WAN (or Internet) indicator, which indicates your connection to your ISP, should be lit or slowly blinking. If it's off or red, there may be a problem with the cable or settings.

There is an important difference in the behavior of the bulbs with different types of faults. If the indicator LAN (Local Area Network) does not light up when the cable is connected to the computer, this may indicate a burnt port or damaged cable.

⚠️ Attention: If the power indicator flashes rapidly or is dimly lit, this often indicates a faulty power supply or a power surge.

Pay special attention to the blinking pattern of the WiFi indicator. Random, very rapid blinking may indicate the device is in download or recovery mode, or its processor is overloaded with background tasks.

📊 Is your WAN/Internet indicator on?
Lights up green/blue
Flashing
It's red
It doesn't burn at all

Checking the physical connection and cables

Before delving into software settings, it's important to rule out physical damage. Cables are the weakest link in a home network. Often, the problem lies in a broken wire or a corroded contact on the RJ-45 connector.

Carefully inspect the cable going from the provider to the port WAN The router's cable should not be twisted, pinched by furniture, or have any visible kinks. Try removing the cable and reinserting it until you hear a distinctive click.

If possible, replace the patch cord connecting the router to the computer with a known-good one. Low-quality cables often cause packet loss, which can lead to unstable network performance or even complete network failure.

It's also worth checking the power supply. If it's getting hotter than usual or making a strange humming noise, its functionality is questionable. Unstable voltage at the router's input leads to constant reboots and malfunctions. Wi-Fi module.

Diagnostics via command line and Ping

The most accurate technical way to check the connection is to use a utility PingIt allows you to send data packets to a device's address and receive a response. This helps you determine whether your computer can see the router at the network level.

First, you need to find out the default gateway address. This is usually 192.168.0.1 or 192.168.1.1The exact address is on the sticker on the bottom of the device. Open the command prompt (in Windows, press Win + R, enter cmd and press Enter).

Enter the command ping 192.168.0.1 -t (replace the address with your own). If you see responses like Reply from 192.168.0.1: bytes=32 time=1ms TTL=64, then there is a connection to the router and it is working properly. If there is a message Request timed out, the computer cannot communicate with the device.

It's important to differentiate between timeouts. If the ping isn't reaching the router, but the phone has a Wi-Fi connection, the issue may be with the PC's network card or drivers. If the ping is working but the internet isn't working, look for problems with your ISP or PPPoE/L2TP settings.

Deciphering Ping Results

A response time of less than 5 ms is ideal for a local network. Values ​​above 100 ms or packet loss indicate heavy bandwidth utilization or hardware failure.

Web interface and device log analysis

If you can ping, try logging into the control panel. Enter the router's IP address into the browser's address bar. Successfully loading the login page is a good sign that web server the device is functioning.

After entering your login and password (by default, often admin/admin) Go to the "Status" section. This displays information about your WAN connection. If the status is "Connected" but there's no internet connection, your DNS settings may be corrupted or your bandwidth may be running low.

Please pay attention to the System Log section. Critical errors may be recorded there, for example, kernel panic or WiFi module loading errors. Repeated process restart messages indicate a software glitch.

The interface may not open if a proxy server is enabled in your browser or if cache has accumulated. Try opening the page in incognito mode. Access may also be blocked by an antivirus or firewall.

Checking the wireless network

Diagnosing the WiFi module deserves special attention. It's possible that the wired network (LAN) works, but the wireless one doesn't. Try finding your network from another device, such as a smartphone or tablet.

If the network is visible but won't connect, it's possible the DHCP client limit has been reached or the security settings have become corrupted. Try forgetting the network on your phone and re-entering the password. The "Incorrect password" or "Unable to obtain IP address" error will indicate the specific issue.

Check the signal strength in different rooms. A sharp drop in signal strength near the router may indicate problems with the antennas or a loose connection inside the router.

There's a simple test: create a hotspot on your smartphone and connect your laptop to it. If the internet works through your phone but not through the router, the issue is definitely with your router or ISP.

⚠️ Caution: If your router overheats and shuts down immediately when attempting to connect to WiFi, unplug it immediately. This indicates a short circuit inside the board.

Resetting and testing

If software failures prevent normal operation, a full reset will help (Reset). There's a small hole on the back panel. Press it with a paperclip and hold it for 10-15 seconds until the lights blink.

After the reset, the router will return to factory settings. You'll need to re-enter your provider information. If the device operates reliably after the reset and clean setup, the issue was a software conflict.

However, if the device still behaves strangely even after a reset (heating up, not detecting the cable, not broadcasting WiFi), the hardware is likely faulty. Specifically, the radio module or memory chip may have burned out.

☑️ Checklist before reset

Completed: 0 / 4

Table of main symptoms and solutions

To quickly identify the problem, use the summary table. It will help you match the observed symptoms with the most likely cause of the malfunction.

Symptom Probable cause Action
Only Power is on There is no connection to the provider or the WAN port is burned out. Check your provider's cable
All indicators are flashing Boot process or firmware failure Wait 5 minutes or reflash
There is WiFi, but no internet. PPPoE authorization error Check your login/password in the settings
The device is hot Overheating or malfunction of the power supply Let it cool down, check the power supply
The address 192.168.xx cannot be pinged. PC or router network card failure Check TCP/IP settings

When is it time to change equipment?

The average lifespan of a router under continuous operation is 3-5 years. Over time, capacitors dry out, memory degrades, and heat dissipation deteriorates. If a device only operates after a long warm-up period or, conversely, shuts down under load, its lifespan has been exhausted.

Frequent freezes requiring daily reboots are also a warning sign. Constant reboots wear out the flash memory where the firmware is stored, and eventually the router will simply stop turning on.

Modern WiFi 6 standards and requirements for speeds above 100 Mbps make older models (802.11n) are outdated. Even if such a router is technically sound, it can slow down new smartphones and TVs.

Finally, regularly checking your equipment's health helps prevent sudden connection interruptions. Use the diagnostic methods described to always stay online.

How to extend the life of a router?

Blow out dust from the device with compressed air every six months. Place the router vertically or on its feet for better air circulation. Avoid placing it on a radiator or in direct sunlight.

Why is the router on but there is no internet?

Most often, this means the local network is working, but there's no connection to the outside world. Causes include: a provider outage, the end of a paid period, incorrect PPPoE/L2TP settings in the router, or a broken cable in the entryway.

Is it possible to check a router without a computer?

Yes. Use your smartphone. Connect to the router's WiFi network. If your phone says "Connected, no internet access," launch your browser and try visiting any website. If the page doesn't load, but your phone connects to other WiFi networks normally, the problem is with the router.

What should I do if I forgot my router admin password?

If the standard (admin/admin) is not suitable, and you changed it and forgot, only a full reset with the button will help ResetAfter this, you will need to reconfigure the device.

How often should I reboot my router?

As a preventative measure, it's recommended to reboot the device once every 1-2 weeks. This clears RAM of errors and refreshes DHCP leases. Doing this daily isn't necessary.