The XDA piece pointing readers at their modem’s hidden status page landed on the real trick of ISP support calls: half the time, the modem already knows what’s wrong. Cable modems log SNR margin, downstream power, correctable and uncorrectable codeword errors; DSL modems log signal attenuation and CRC errors. Getting to that page is step one. Turning the numbers into a case that “my line is flaky, not my Wi-Fi” is what these seven modem diagnostics apps do.
We picked tools that catch three specific failure modes: intermittent latency that only shows up during a call, packet loss upstream of your router, and slow degradation of a cable or DSL line over weeks. The right tool depends on which of those you’re chasing.
What to look for in a modem diagnostics app
- Long-run graphing. A single ping test tells you almost nothing. You want minutes to weeks of latency, jitter, and loss plotted together.
- Traceroute-aware analysis. Loss at hop 3 is your ISP. Loss at your router is inside your house.
- Line-stat scraping. For DOCSIS cable and DSL, the modem’s status page has SNR, signal levels, and error counters that no ping tool can see.
- Cross-platform. Windows, macOS, and Linux; ideally headless so you can leave it running on a home lab.
- Low overhead. Diagnostics that use half your bandwidth defeat the purpose.
- Alerts. Something has to wake you when the line drops at 3am so you have a case for the ISP call the next morning.
Quick comparison
| App | Best for | Platforms | Free plan | Starting price | Rating |
|---|---|---|---|---|---|
| SmokePing | Long-run latency graphing | Linux, Docker | Yes, full | Free (open source) | Reference tool for 20+ years |
| PingPlotter | Interactive traceroute+ping | Windows, Mac | 14-day trial | $8.25/mo Standard | 4.5 on G2 |
| Fing Desktop | Home network overview | Windows, Mac | Yes, limited | Free (freemium) | 4.6 (App Store) |
| Wireshark | Deep packet inspection | Windows, Mac, Linux | Yes, full | Free (open source) | The reference sniffer |
| Etherape | Live network flow visualization | Linux, Mac | Yes, full | Free (open source) | Canonical open-source flow map |
| iperf3 | End-to-end throughput testing | Windows, Mac, Linux | Yes, full | Free (open source) | Reference for LAN and WAN tests |
| MTR / WinMTR | Real-time traceroute with loss | Windows, Mac, Linux | Yes, full | Free (open source) | Ships in most Linux distros |
The apps
1. SmokePing, best long-run graphing
SmokePing graphs latency to a target over time and uses smoke-plume shading to show jitter and packet loss. Twenty years of “why is my internet slow at 8pm” investigations have been solved by looking at a SmokePing graph. Runs headlessly on a home server, sends alerts by email or webhook, and stores months of data in RRDtool databases.
Where it falls short: The web UI is genuinely dated. Configuration is Perl-y and text-based. Not fun to set up on Windows.
Pricing:
- Free, open source (GPL v2).
Platforms: Linux natively; Docker image (linuxserver/smokeping) for anything that runs containers.
Download: oss.oetiker.ch/smokeping or github.com/oetiker/SmokePing.
Bottom line: The reference tool for “prove my line was bad.” Run it for a week, send the graph to your ISP.
2. PingPlotter, best interactive traceroute
PingPlotter shows every hop between your machine and a target, with per-hop latency and loss over time. Click any hop to see the timeline. Notify when a specific hop degrades, or export a session as a PDF ISP support will actually look at. Windows and macOS builds, no self-hosting required.
Where it falls short: Free tier is limited; the meaningful features (long-run graphing, multiple targets, alerts) are behind Standard or Pro subscriptions.
Pricing:
- Free tier available.
- Standard: $8.25/mo billed yearly.
- Pro: $16.65/mo billed yearly.
Platforms: Windows, macOS.
Download: pingplotter.com for Windows and macOS.
Bottom line: The right pick when you want to open a graph, click a hop, and know instantly whether the fault is in your house, your ISP, or the far endpoint.
3. Fing Desktop, best home-network overview
Fing Desktop discovers every device on your network, monitors internet quality, and runs speed tests on a schedule. Notifications for outages and slowdowns arrive on desktop and phone (Fing has iOS and Android apps that share data). Includes a hidden-device notifier that catches new gear on your Wi-Fi.
Where it falls short: Free tier is limited to basic monitoring. Paid Fing Premium (about $2.50/mo) adds ISP outage insights, but many features push you toward the Fing Agent or Fingbox device.
Pricing:
- Free with limited features.
- Fing Premium ~$2.50/mo.
Platforms: Windows, macOS. iOS and Android for phone monitoring.
Download: fing.com/products/fing-desktop for Windows and macOS.
Bottom line: The right pick if you want one tool that covers device inventory, speed tests, and outage alerts on the same dashboard.
4. Wireshark, best deep inspection
Wireshark captures and decodes every packet crossing your network interface. If you have to prove your modem is dropping packets versus your router is fumbling handshakes, this is the tool. Filters, session reconstruction, protocol decoders for hundreds of formats.
Where it falls short: Learning curve is real. Not designed for at-a-glance monitoring; you use it when you have a specific question.
Pricing:
- Free, open source (GPL v2).
Platforms: Windows, macOS, Linux.
Download: wireshark.org for Windows, macOS, and Linux.
Bottom line: Keep it installed. When something weird happens, Wireshark is what tells you exactly what.
5. Etherape, best live flow visualization
Etherape draws a live graph of active connections. Big nodes talk a lot, small ones talk a little, and the edges pulse with real traffic. Not for latency debugging, but the fastest way to see “why is my modem uploading 5 Mbps right now” when you weren’t expecting it.
Where it falls short: Linux and macOS only (Homebrew). Not a real diagnostic tool; more a “what’s happening right this second” visualizer.
Pricing:
- Free, open source (GPL v2).
Platforms: Linux, macOS.
Download: github.com/juhovh/etherape or your distro’s package manager (apt install etherape).
Bottom line: Not a fit for daily monitoring, but the fastest way to answer “what device is hogging my line right now.”
6. iperf3, best end-to-end throughput
iperf3 measures actual throughput between two endpoints. Run the server on your NAS or router (many routers include it), run the client on any machine, and get real Mbps numbers unaffected by whatever cloud speed test your ISP is optimizing against. Essential for verifying that a new modem or router actually delivers what its spec sheet claims.
Where it falls short: Not a diagnostic dashboard. Doesn’t graph over time. You run a test, read a number, done.
Pricing:
- Free, open source (BSD-3-Clause).
Platforms: Windows, macOS, Linux; also included in OPNsense, pfSense, and many routers.
Download: iperf.fr or your package manager.
Bottom line: The right pick when you need to prove your line delivers its rated speed against a controlled endpoint.
7. MTR / WinMTR, best real-time traceroute
MTR (My TraceRoute) combines ping and traceroute into one continuously updating view. WinMTR ports the same idea to Windows. You get every hop, its live latency, and its rolling loss percentage in one screen. Cheaper than PingPlotter, less pretty, but does the same job for a shell-comfortable user.
Where it falls short: Terminal-based. No long-run history unless you script the output.
Pricing:
- Free, open source (GPL v2 for MTR, WinMTR is BSD-2).
Platforms: Windows (WinMTR), macOS (Homebrew), Linux (in every distro).
Download: github.com/traviscross/mtr or WinMTR at sourceforge.
Bottom line: The right pick when you want PingPlotter’s answers for free and don’t need the polished UI.
How to pick the right one
If you have a home server that stays on: SmokePing in a container. Set it up once, let it graph forever, be ready when your ISP asks “how often does this happen?”
If your problem is intermittent and you want to see it live: PingPlotter (paid, polished) or MTR / WinMTR (free, terminal).
If you want a single dashboard for devices, speed, and outages: Fing Desktop, paired with the mobile app.
If you need to prove a specific packet-level failure to an ISP or vendor: Wireshark. Save the capture, hand it over.
If you’re troubleshooting throughput specifically (not latency): iperf3 between two known endpoints.
If your modem’s line stats matter (cable SNR, DSL attenuation): open the modem’s own status page first, then verify with these tools. Save screenshots each time so you can show trends over weeks.
FAQ
How do I find my ISP modem’s hidden status page?
Most consumer modems expose a diagnostic page at http://192.168.100.1 (cable) or http://192.168.1.1 (DSL and combined units). Some ISPs use http://mynetwork or a branded hostname. Check the sticker on the bottom of the modem for the exact address and login. On DOCSIS cable modems, the relevant section is called “Signal” or “Status” and lists Downstream Power, SNR, and Codewords.
What SNR margin is bad for a cable modem?
Downstream SNR below 33 dB usually indicates a line problem. Downstream power outside -7 dBmV to +7 dBmV is out of spec. Uncorrectable codeword counts that grow steadily over a day indicate a physical-layer fault the ISP should fix.
Is PingPlotter worth paying for?
If you diagnose networks frequently or need to send professional reports to an ISP, yes. For a one-off “why did my Zoom call drop yesterday” question, MTR or WinMTR gives you the same answer for free.
How do I know if my slow internet is my modem or my Wi-Fi?
Plug a laptop directly into the modem via Ethernet, run iperf3 or a speed test, then compare against a Wi-Fi test on the same machine. If Ethernet is fine and Wi-Fi is slow, the problem is the router or Wi-Fi environment. If both are slow, the line or modem is the issue.
Can these apps monitor my modem without an agent on it?
Yes. SmokePing, PingPlotter, MTR, and Fing Desktop treat the modem as a target and read its behavior externally. Some cable modems expose SNMP for direct scraping, but every tool on this list works fine without it.
