Speedtest Monitor

Self-hosted internet speed monitor that runs Cloudflare Speed Test on a configurable schedule and tracks connection performance over time.

  • Network Services
  • Tools & Utilities
Self-hosted internet speed monitor that runs Cloudflare Speed Test on a configurable schedule and tracks connection performance over time. It stores every measurement in SQLite and serves a live dashboard over WebSocket, with alerts (webhook, ntfy, Discord, Slack, SMTP), authentication with local accounts and OpenID Connect (OIDC), and role-based access (admin / viewer).

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

52/100 Fair

Maintained
100last commit 6 days ago
Popular
165 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
1016 GB minimum RAM

Availability: platform listings confirmed today, links checked 18 days ago

GitHub stars
5
Open issues
0
Last commit
2026-11-15
Latest release
v1.24.5
License
MIT
Activity
declining

Checked 6 days ago - source: GitHub (Greite/speedtest-monitor)

Resources & Compatibility

Minimum requirements: 16 GB RAM.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Update the placeholder settings first Set PUID/PGID (the user and group IDs the container runs as), match the database username and password in both services, and replace the data folder paths before starting. If these are left blank or mismatched, the app can fail to start, store no speedtests, or have permission errors. source
  • Open ports 8080 and 8443 Keep 8080 open for normal web access and 8443 open if you want to use HTTPS. Without the right port, your browser won't be able to reach the Speedtest Tracker dashboard. source
  • Save your settings and history safely Keep the mapped config folder and the MariaDB volume backed up, because they hold your app settings, custom keys, and speedtest results. If they are deleted or corrupted, the app will effectively start fresh and your history will be gone. source
  • First-boot setup Set AUTH_SECRET and BETTER_AUTH_URL (the latter required when accessed behind a reverse proxy). Create the first admin via SPEEDTEST_ADMIN_EMAIL and SPEEDTEST_ADMIN_PASSWORD, or open the /setup page in the browser. Data persists to /data, mapped to /mnt/user/appdata/speedtest-monitor by default. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where is the data stored so I can back it up?

Speedtest-monitor stores measurements and settings in a SQLite database at /data/speedtest.db by default. You should persist that /data directory, and also /data/logs if you want to keep rotated log files.

What do I need to set when serving it behind a reverse proxy?

On first boot, set AUTH_SECRET and BETTER_AUTH_URL. BETTER_AUTH_URL is required when the app is accessed behind a reverse proxy.

Which port do I need to expose?

The dashboard and WebSocket are served from the same HTTP port. The default is PORT 3000.

How do I create the first admin account?

You can set SPEEDTEST_ADMIN_EMAIL and SPEEDTEST_ADMIN_PASSWORD on first boot. Alternatively, open the /setup page in the browser to create the first admin.

How should I tune the tests for a very high-bandwidth connection?

Raise SPEEDTEST_TEST_DURATION_S so each phase has more time, and increase SPEEDTEST_PARALLEL_STREAMS to help saturate high-bandwidth links. The docs suggest trying 16 parallel streams on a 10 Gbps link.

Answers sourced from ca.unraid.net, github.com

Community

Collected 49 days ago - public community threads