RouteViewNet is a local-first network and memory health monitor for Linux. It watches your connection and your computer around the clock, scores their health from 0 to 100, and explains problems in plain English. No cloud. No account. No telemetry.
curl -fsSL https://raw.githubusercontent.com/kaanyinaele/routeviewnet/main/install.sh | sudo sh
Free and open source (MIT) · Two ways to install · Runs entirely on your machine
Overview
"The Wi-Fi is slow" has a dozen possible causes: your router, your provider, the DNS address book, a bad cable, or a computer that is simply out of memory. Guessing means restarting things at random. RouteViewNet measures each link in the chain continuously, so when something breaks you can see exactly which step failed and what to do about it.
A deterministic 0 to 100 health score computed from every check: router reachability, internet reachability, DNS speed, packet loss, memory, swap, and processor load. 90 or above is healthy; every lost point is explained.
The three-step path every web page takes, each checked every few seconds with response times. Which one fails tells you where the problem lives: your home network, your provider, or the address book.
Download and upload rates for every network interface, with automatic detection of the primary one on multi-homed machines. History from 15 minutes to 7 days, plus error and drop counters that expose bad cables, weak Wi-Fi, and overloaded links.
See which programs moved the most data in any time window, with a view of every app that used 20 MB or more. Counted from the kernel's own connection counters and attributed to the owning process.
Continuous latency and packet-loss probes to well-known reference addresses (configurable), plus DNS lookup timing for both IPv4 and IPv6 records, charted over time.
Every device your computer talks to, with vendor lookup, optional hostnames, nicknames you assign, and a trusted flag. An unfamiliar device on your Wi-Fi raises a gentle alert.
System RAM (counted honestly: Linux cache does not count as used), swap pressure, 1/5/15-minute load against your core count, and the top memory consumers by name, so the culprit is one glance away.
A problem must be seen twice in a row to open an alert, and alerts resolve themselves when the signal recovers. Debounced, deduplicated, and never requiring a dismiss button.
Rule-based diagnosis of the currently open alerts: a one-line likely cause, the evidence behind it, and ordered suggested actions. "Your gateway is fine, DNS is slow; check your resolver."
Every knob lives in the dashboard: alert sensitivity (memory percentage, DNS latency, packet loss), check intervals and targets, per-collector toggles, data retention, and privacy switches. Changes apply the moment you save; the few that need a restart say so explicitly.
RouteViewNet lives in your applications menu with its own window and icon, not just a browser tab. If the background monitor is ever stopped, the app offers to start it with your system's normal password prompt. The browser dashboard at localhost:4545 keeps working too.
The daemon reports its own memory footprint in the dashboard, so you can verify the monitoring tool is not the thing slowing you down.
All three steps healthy. Watching.
Per-app usage in any time window, straight from the kernel's connection counters.
Pick your way: a one-line install, or build it from source. Whichever you choose, the background monitor starts immediately and survives reboots.
Launch RouteViewNet from your applications menu (a native desktop window) or visit localhost:4545 in a browser.
Glance at the score. If something is wrong, the Troubleshoot page tells you where and what to try.
curl -fsSL https://raw.githubusercontent.com/kaanyinaele/routeviewnet/main/install.sh | sudo sh
A single Go daemon, SQLite storage, a React dashboard embedded in the binary, systemd-managed. Hot-reloadable settings from the dashboard.
Shows devices this machine talks to, not a full LAN scan. Per-app usage counts direct (TCP) connections only. Load average only for CPU. No authentication in v1, so keep it local.
No. It typically uses less memory than one browser tab, and it proves that on its own System page.
No, the monitor runs in the background; the window is just a viewer.
Debian and Ubuntu with systemd; Go 1.24 or newer to build from source.
Yes, MIT licensed.
Not out of the box; v1 has no authentication, so it stays local by default.