Router Log Interpreter
Find the entries in a router log that matter — and ignore the ones that fill it.
What you paste
Parsed in your browser — never uploadedResult
Nothing recognised in that log
No lines matched the patterns this knows. Router firmware varies enormously in wording — paste more of the log, including the lines around any disconnection.
What this cannot tell you
- The log itself is never displayed — only counts per pattern — so no MAC address or device name from it reaches the page or a shared result.
- Router firmware wording varies enormously. Lines this does not recognise are not reported, so paste generously around any disconnection rather than only the line you think matters.
- Counts patterns rather than reading the line. It cannot tell you why a line resynced, only that it did and how often.
- Parsed in your browser. Nothing is uploaded, and what you paste is not stored.
Take this with you
How this reads your output
Lines are matched against the patterns consumer router firmware uses and grouped by whether they matter, with the ones worth acting on sorted first regardless of how few there are. The sorting is the point. A router facing the internet logs every unsolicited inbound packet, and the firmware describes those as attacks — so a log is mostly firewall noise, and the three lines recording a line resync are buried under three hundred that mean nothing. Resyncs are what an ISP will act on: a log showing repeated disconnections is evidence, where a description of the symptom is not.
What the results mean
- Line resync
- A full disconnection and reconnection. The entry that matters, and the one to count and timestamp.
- Blocked inbound packet
- Background internet scanning that the firewall dropped. Every router sees it constantly.
- CRC or errored seconds
- Line quality between resyncs. Worth quoting alongside resync counts.
- DHCP activity
- Routine, and usually most of the log by volume.
Common problems and fixes
- The log is full of DoS attacks
- Those are dropped inbound packets, which every router facing the internet sees constantly. The firmware's wording is alarming and the entries mean nothing on their own.
- My connection drops but the log looks fine
- Look specifically for resync, retrain or loss of sync. If none appear, the drop may be wireless rather than the line — check for repeated disassociation from one device.
- Nothing was recognised
- Firmware wording varies a great deal. Paste more of the log, particularly the lines around the time a disconnection happened.
Frequently asked questions
Are the DoS attack entries in my router log real attacks?
They are real dropped packets and not a real attack. Every address on the internet is scanned continuously, and consumer firmware logs each dropped packet in language that suggests something targeted. The line means the firewall worked.
What should I send my ISP?
The resync entries with their timestamps. A log showing repeated line resyncs is evidence a provider will act on; a description of the internet being slow is not.
Is my MAC address exposed?
No. The log is never displayed back — only counts per pattern — so nothing from it reaches the page or a shared result.
Put this on your own site
Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.
<iframe src="https://runthetests.com/embed/router-log-interpreter/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="Router Log Interpreter" loading="lazy"></iframe>
Preview it at https://runthetests.com/embed/router-log-interpreter/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.