How to check your Wi-Fi router's history: connection logs, websites, and device activity

Have you ever wondered which devices connected to your Wi-Fi, which websites users visited, or when exactly your router's load peaked? Router activity history isn't just a technical log, but a fully-fledged tool for monitoring security, optimizing your network, and even resolving family disputes about "who downloaded 100 GB overnight."

Unfortunately, most router manufacturers (TP-Link, ASUS, Keenetic etc.) do not store the history of visited websites directly - this function is usually taken over by providers or specialized programs. However device connection log, traffic statistics and even DNS query log (which indirectly indicates activity) are available in 90% of modern models. In this article, we'll look at all possible ways — from standard router settings to advanced tools like Wireshark.

Important: If you are looking for history specifically visited pages (For example, "who visited VKontakte"), this is impossible without additional software or settings on the provider's side. But we'll show you how to get as close to this goal as possible with what you have at hand.

1. Standard connection log in the router's web interface

The easiest way is to look into event log (System Log or System log) via the admin panel. All device connections, settings changes, and errors are recorded here. The instructions are universal for most brands, but the steps may vary slightly.

How to access the log:

• 🌐 Open your browser and enter the router's IP address (usually 192.168.0.1, 192.168.1.1 or 192.168.8.1).
• 🔑 Enter your login and password (by default it is often admin/admin or indicated on the device sticker).
• 📄 Find the section System Tools → Log (For TP-Link), Administration → System Log (For ASUS) or Monitoring → Log (For Keenetic).

What you will see in the log:

• ⏱️ Device connection/disconnection time (with MAC addresses).
• 📡 DHCP events (IP address allocation).
• ⚠️ Authentication errors (if someone tried to connect with an incorrect password).
• 🔄 Reboot the router.

⚠️ Attention: Router logs are stored for a limited time (from a few hours to 7 days) and are automatically cleared upon reboot. If you need long-term history, configure export logs to an external server (section 4).

Successful device connections (MAC addresses)

Failed login attempts (possible hacks)

Time of maximum network load

Settings change events (who and when logged into the admin panel) -->

2. List of connected devices (active and past)

If the log is too technical, you can take a look list of devicesthat have ever connected to your network. This method works even for routers without detailed logging.

Where to look:

• 📱 TP-Link: Wireless Mode → Wireless Mode Statistics or DHCP → Client List.
• 🖥️ ASUS: Network map (shows current connections) or Local Network → DHCP Client List.
• 🌍 Keenetic: Monitoring → Devices (with time filter).
• 🔗 Zyxel: Network → Local Network → DHCP Lease List.

What can you learn:

• 🆔 MAC addresses And IP addresses devices (even if they are currently disabled).
• 🕒 Last connection time (on some models).
• 📶 Connection type (Wi-Fi or cable).
• 📱 Device model (if the router supports MAC detection).

Keenetic routers and some ASUS models feature a "Device History" feature that displays connections over the past 30 days—a rare exception among consumer routers.

3. Traffic analysis by device (who downloads the most)

If you are interested not so much in “who connected” as in “who is loading the network”, then you need traffic statisticsMany routers can show how much data each device is consuming.

Where to watch:

• 📊 TP-Link: Traffic Statistics → Devices (requires enabling monitoring in settings).
• 📈 ASUS: Adaptive QoS → Traffic Monitoring or Tools → Traffic Statistics.
• 📉 Keenetic: Monitoring → Traffic (broken down by devices and applications).

What can be found out:

• 📥 Downloaded/Sent Data per day, week or month.
• 🎮 What applications consume the most traffic (torrents, YouTube, games).
• ⏰ Peak activity hours (when the network is overloaded).

⚠️ Attention: To collect traffic statistics you need it turn on in advance in the router settings. If the function is disabled, data collection will only begin after activation. In some models (for example, D-Link budget routers) this option does not exist at all.

Monitoring children/family members

Scan for viruses or network hacking

Optimizing Internet speed

Curiosity

Other-->

4. Export logs to an external server (for advanced users)

If the standard logs are not enough, you can configure automatic sending of logs to an external server or cloud. This is relevant for:

• 🏢 Office networks (employee control).
• 🛡️ High security requirements (search for attacks).
• 📊 Long-term storage of history (more than 30 days).

How to set up:

1. Turn on syslog in the router settings (section System Tools → Log Settings).
2. Specify the IP address of the server for logs (you can use free solutions like Papertrail or Graylog).
3. Set up filtering (for example, save only connection events).

Example setup for MikroTik:

/system logging add topics=wireless,info action=remote remote=192.168.1.100

It is easier to use for home users ready-made cloud services:

• 🔗 Pi-hole (ad blocker with DNS request logs).
• 🔍 OpenWRT + Collectd (for homemade firmware).
• 📦 PRTG Network Monitor (paid, but with a trial period).

What is syslog and why is it needed?

Syslog is a standard protocol for transmitting logs over a network. It allows router logs to be stored on an external server, protecting them from being lost when the device is rebooted. For example, if the router is hacked and reset, local logs will be lost, but remote logs will remain.

5. Viewing DNS query history (indirect method)

If your router doesn't store website history, you can try analyze DNS queriesEvery time a device accesses a website, it sends a request to resolve the domain name to an IP address. Many routers log these requests.

Where to look:

• 🔍 Keenetic: Monitoring → DNS Queries (shows domains, but without linking to devices).
• 🌐 ASUS with firmware Merlin: Tools → Syslog (filter by keyword dnsmasq).
• 📡 MikroTik: IP → DNS → Static → Log.

Limitations of the method:

• ❌ Doesn't show HTTPS traffic (domains are encrypted in SNI).
• ❌ Does not distinguish between devices (only a general log).
• ❌ Stored for a short time (usually 24 hours).

For detailed DNS analysis you can use specialized programs:

• 🖥️ Wireshark (interception of traffic on a PC).
• 📱 Fing (mobile application for network scanning).
• 🔧 dnstop (console utility for Linux).

⚠️ Attention: DNS query analysis may be disruptive privacy legislation (for example, Article 137 of the Criminal Code of the Russian Federation on violation of the privacy of correspondence). Use this method only for own devices or with the consent of network users.

6. Alternative methods: programs and services

If your router doesn't provide the necessary data, you can use third-party tools. They require more setup effort but offer more advanced features.

Top 5 Wi-Fi Monitoring Software:

• 🔍 GlassWire — shows traffic by devices and applications (Windows/macOS).
• 📊 PRTG Network Monitor — a professional tool with dashboards (there is a free version).
• 🛡️ OpenDNS — a service for filtering traffic with request logs.
• 🖥️ ntopng — open-source software for deep network analysis (installed on Raspberry Pi).
• 📱 WiFi Guard — a mobile application for scanning connected devices.

How it works GlassWire:

1. Install the program on a PC connected to the router via cable.
2. Select a network adapter (Wi-Fi or Ethernet).
3. Go to the tab Usage — the traffic of all devices on the network will be displayed here.

For complete control you can customize port mirroring on the router and analyze traffic through Wireshark. However, this requires support from the router (available in MikroTik, Ubiquiti and some models ASUS).

Common mistakes and how to avoid them

When attempting to view a router's activity history, users often encounter common issues. Let's look at the most common ones:

Problem 1: Logs are empty or reset

• 🔄 The router rebooted (logs are cleared).
• ⚙️ The logging feature is disabled in the settings.
• 🗑️ Log memory is full (set up automatic cleaning).

Problem 2: I can't see my browsing history.

• 🔒 Modern websites use HTTPS, their contents are not logged.
• 📵 The router does not support deep traffic analysis (additional programs are required).

Problem 3: MAC addresses of devices are not detected

• 🆔 The device was connected via a VPN or proxy.
• 🔄 MAC address is random (function MAC Randomization in smartphones).

FAQ: Answers to Frequently Asked Questions

Is it possible to see the history of visited websites through a router?

In 99% of cases - NoRouters don't store browser history, only:

• DNS queries (domains, not pages).
• IP addresses of connections (not linked to specific sites).

For a complete history, specialized programs are needed (Wireshark with HTTPS decoding) or settings on the provider side.

How do I find out who connected to my Wi-Fi at night?

Check:

1. System log in the router (connection time).
2. DHCP Client List (MAC addresses of devices).
3. Settings Parent Control (if time limits are enabled).

If you find an unfamiliar MAC address, block it in MAC filtering.

Is it possible to restore history after resetting the router?

No, local logs are deleted permanently when reset. The only ways are:

• If logs were sent to an external server (syslog).
• If the provider keeps a history (unlikely for home tariffs).

How to enable logging on a router TP-Link?

Go to:

1. System Tools → System Settings.
2. Turn on Keep a system log.
3. Set the logging level Information or Debugging.
4. Save the settings and check the section Log.

Is it legal to monitor other users' traffic on my network?

Legally gray question:

• ✅ Allowed to analyze own traffic (for example, to optimize the network).
• ⚠️ Collecting data about visited sites without consent may violate the law on persons (152-FZ).
• ❌ It is prohibited to distribute the information received or use it for blackmail.

It's enough for a home network oral consent all users.