English
Speedtest Tracker Hosting
Automatically run internet speed tests on a schedule and chart your download, upload, and latency over time.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Speedtest Tracker’s official links and original website
Speedtest Tracker Website
More
Tech
- Docker image
- lscr.io/linuxserver/speedtest-tracker:latest
- Default port
- 80
How Speedtest Tracker works
Speedtest Tracker runs scheduled or manual network tests and records download rate, upload rate, latency, packet loss, the chosen test server, and timing information. Its dashboards turn those results into tables and charts so an operator can compare recent performance, view longer trends, and investigate whether a route changed after a provider or configuration event.
Test schedules and preferred servers can be configured, and notifications may be triggered when results cross defined thresholds. The catalogue uses SQLite in the persistent /config path and starts with admin@example.com and the password password. Those credentials must be changed immediately because the dashboard may reveal network characteristics and test history.
Key Speedtest Tracker features
A hosted Speedtest Tracker measures connectivity from the the hosting service application container to the selected speed-test infrastructure. It does not test the broadband line at a customer’s house, the Wi-Fi quality inside an office, or the path from an employee laptop. To measure another location, the tracker must run at that location or receive results from a suitable independent probe.
Each speed test transfers data and can consume bandwidth while it runs. Frequent schedules, several selected servers, concurrent activity, long result histories, and notification processing add load. Test-server capacity and routing can affect results, so a single reading should not be treated as proof of an outage or a contractual network measurement.
Who uses Speedtest Tracker
Infrastructure teams can watch the external route from a hosted service, network engineers can compare test servers over time, and operators can maintain a simple evidence trail around connectivity incidents. It can also help identify recurring time-of-day patterns from the deployment location.
Speedtest Tracker is not a distributed monitoring network, service-level measurement authority, packet-capture platform, Wi-Fi analyser, or substitute for provider diagnostics. Users should correlate results with independent monitoring, service logs, and measurements from the actual location affected by a complaint.
Self-hosting Speedtest Tracker: requirements and cost
Speedtest Tracker resource use depends on test frequency, transferred data, selected servers, history length, chart queries, concurrent dashboard users, and notification checks. PostgreSQL and MariaDB are Not required by the catalogue template; SQLite data and configuration persist under /config. The software has no separate application charge, while aggressive schedules can create avoidable network usage.
On AvaHost, Speedtest Tracker uses Plan 1 at €2. The hosted Speedtest Tracker package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Change the upstream admin@example.com / password login immediately. The package measures the hosted environment’s path and does not include remote probes, ISP diagnostics, Ookla service guarantees, or application email. Notifications that depend on mail are unavailable; any other supported notifier requires external credentials and separate approval.
F.A.Q
Speedtest Tracker starts at €2 on Plan 1. A conservative schedule and ordinary result history should fit that starting point. Test frequency, transferred data, server selection, retained records, dashboard queries, notification checks, and simultaneous users are the main factors to review before assigning more capacity.
The tests run from the hosted application environment to the selected test server. They describe that route and do not measure a customer’s home broadband, office Wi-Fi, employee device, or another data centre. Place an independent tracker or probe at each location whose connection you actually need to assess.
The catalogue starts with the upstream `admin@example.com` account and `password` credential. Sign in and replace the password immediately, then review access before sharing the hostname. A custom domain and automated HTTPS can be added, but the dashboard should still be limited to authorised viewers.
Application email is disabled across AvaHost services, so mail-based alerts are not available from this package. Other notifier integrations may require tokens or accounts from their respective providers. Configure only services you control, test threshold behaviour, and remember that a failed notification does not change the stored speed-test result.