WAN Observer WAN Observer, with a W-shaped measurement trace and sampled point.
v0.5.3 Run Speedtest fixed for the dashboard

Speed-test history that lives on your router

Scheduled and on-demand tests, run by the router itself and checked against the plan you pay for. When it is slow again, you have the record.

Download v0.5.3 View on GitHub

MIT licensed. Experimental: tested on a GL.iNet Flint 2, firmware 4.11.0.

WAN Observer status: latest test good, 420 Mbps download, 41.7 Mbps upload, 7.8 ms idle latency, 25 ms under load; 12 tests in 7 days, 11 good and 1 failed.
Real capture from a Flint 2. Values unaltered.

“The internet is slow again.”

By the time you run a test, it is usually fine. WAN Observer keeps testing on the router at times you choose, so you can see when it happened and by how much.

  1. Install two opkg packages
  2. Set your plan and schedule
  3. Collect a history on the router
  4. Export a PDF or CSV for support

Inside the router page

A native page in the GL.iNet admin panel, under Flow Control.

Download and upload charts for 7 days: readings sit just above the dashed plan lines of 400 and 40 Mbps, with one failed attempt marked in red below each chart.
  • Your plan as the baseline. Results under your threshold are marked slow.
  • Failures apart. Never charted as zero.
  • Real times. Gaps between tests are not measured.
  • 24 hours, 7 or 30 days. Latency, jitter and loss when reported.
Testing settings dialog: scheduled tests on, test every 2 hours, all day; 388 MB measured per test, estimated at 12 tests a day, 4.7 GB a day and 141 GB a month; monthly data limit empty; follow-up tests off.
  • Every 15 minutes to 12 hours. All day or overnight, in UTC or router time.
  • Follow-ups. Up to 3 extra tests after a slow or failed result.
  • Data use up front. An optional monthly limit stops new tests; one can go over.
  • Quality history. GL Network Quality every minute, kept 30 days, no extra WAN tests.

PDF report

A4, for the selected period, with an optional appendix of every test.

CSV data

Every row behind it, for your own analysis or a ticket.

  • Built in your browser. From the router’s history; nothing is uploaded.
  • Complete. Failed attempts and coverage included, timestamps in UTC.
  • Honest gaps. Unknown values stay unknown. Quality history is not in the PDF yet.

Privacy, source and limits

Stays on your router

History and settings live on the router; exports are built in your browser. Only the speed test reaches Ookla’s servers. IP and MAC addresses, hostnames and ISP labels are discarded on import.

Privacy details

Open source

MIT licensed, no account and no telemetry. Two opkg packages on POSIX shell and jq, with no Python, database or container on the router.

Read the source

Honest about limits

Tested on a Flint 2 with firmware 4.11.0. Tests are samples, not outage monitoring, and reports are not certified proof. Frequent tests use real data.

Limitations

Install in four steps

Needs SSH/root access, opkg with jq and coreutils-timeout, and a permitted Ookla Speedtest CLI. Installing runs no tests.

Download v0.5.3 Setup guide
  1. Download both packages and SHA256SUMS, then verify with sha256sum -c
  2. Install both on the router
     opkg install wan-observer_*.ipk wan-observer-glinet_*.ipk
  3. Configure the collector over SSH, then enable the schedule
  4. Open Flow Control → WAN Observer