I'm starting to think about v2 and want your feedback and suggestions! #2304
Replies: 23 comments 38 replies
-
|
A filter to automatic use only server like "Deutsche Telekom" or so... and if the search has more then one server a fallback to some other from the search list. And if this not work a fallback to a random server like the default. |
Beta Was this translation helpful? Give feedback.
-
|
I like speed-tracker! I've been using it for a while and it's helped me figure out when my ISP has been screwing me over. That being said, performance as a whole in the interface, latency of the app, mainly the UI, load time, and the slickness of the app has been the most deterrent reason why not to use it even more (and recommend it). I would suggest to keep performance top of mind as you think of the next iteration. And yeah, a simple, much slicker mobile view would be incredible. |
Beta Was this translation helpful? Give feedback.
-
|
You've mentioned Authentik and Authelia, can I also throw Pocket ID and Pangolin into the mix too, as they're both insanely popular now (possibly just OIDC will cover the lot?). |
Beta Was this translation helpful? Give feedback.
-
|
awareness of host servers, or other containers, network traffic would be cool, so you can do things like avoid speed test when sabnzdb is downloading for example. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Would it be possible to have Speedtest-Tracker running in a LXC container without Docker? Kind regards! |
Beta Was this translation helpful? Give feedback.
-
These are the main two I'm looking for. Hoping to see them in v2 soon! |
Beta Was this translation helpful? Give feedback.
-
|
Adaptive speedtest intervals - if there is a threshold breach, run subsequent tests at shorter intervals to get more granular info until things return to normal. |
Beta Was this translation helpful? Give feedback.
-
|
Need to keep Gotify notifications. There is a PHP library for interacting with Gotify via the Gotify REST API you can use to integrate so you you don't need a complete rewrite. Can we also look at throwing Azure/Entra ID into the mix with SSO. |
Beta Was this translation helpful? Give feedback.
-
|
would love to see the ability to use iperf servers rather than ookla. The ookla cli always under reports my connection for upload versus iperf which is accurate. I have an 8gb/8gb connection. The windows app, iperf reports the correct up and down but the cli is always incorrect for upload regardless of the server I use. fingers crossed! |
Beta Was this translation helpful? Give feedback.
-
|
Firstly, thank you for such an awesome service, I've almost become obsessed with it during my homelab journey, and it has become instrumental in me making huge performance improvements to my whole setup and family. 12 months ago I has a crappy Sky Broadband router giving 600Mbps wired max, with Wifi around 450Mbps to now running OPNsense (also running AdGuard, Unbound, Crowdsec and Suricata) and a TP-Link Deco XE75 Pro mesh system in AP mode, and I'm now getting 920Mbps wired (more than the 900 I'm paying for..!) and 850Mbps WiFi around my whole house. I do hourly speed tests (because why not) and have notifications set if it drops below 850Mbps. Be a shame to lose Gotify to be honest (might look into Apprise) Looking forward to ANY more improvements. |
Beta Was this translation helpful? Give feedback.
-
|
Would like to be able to track/visualise packet loss |
Beta Was this translation helpful? Give feedback.
-
|
I up vote for adding the nodes that do tests from a remote machine and reports data to a central process (like an agent but controlled from the central process). This would be awesome in a distribuited enviroment, for example, where many machines resides on different ISP networks and you could monitoring hourly the network performance with a single interface. |
Beta Was this translation helpful? Give feedback.
-
|
It's been mentioned or almost mentioned by others, but an option where if a test result falls below threshold, retry on a different server. (quickly-- before the next scheduled run)
and you're way ahead of me Thanks for your work on speedtest-tracker, it's a great tool. |
Beta Was this translation helpful? Give feedback.
-
|
I'm just looking for a proper notification option to push webhooks or pushover :) |
Beta Was this translation helpful? Give feedback.
-
|
Option to exclude specific test servers would be great. Now we can select a specific one or select all. Not exclude a specific one |
Beta Was this translation helpful? Give feedback.
-
|
I have been asking for this in the past. I would like to see the option to change the default time to display from 1 day to last week or last month. I only test one time per day so comparing always make me change 6 drop down boxes. |
Beta Was this translation helpful? Give feedback.
-
|
run custom server to test to. Example run server on homelab and then all my servers speed test to it to check my speeds throughout my remote network. |
Beta Was this translation helpful? Give feedback.
-
|
Most important for me to resume using it is data history pruning and settings. Good example is the UptimeKuma functionality - its clean and simple. It lets you click to:
|
Beta Was this translation helpful? Give feedback.
-
|
Make login optional. I am the only user, login is unnecessary and annoying. |
Beta Was this translation helpful? Give feedback.
-
|
Add the scheduler and other configurable options to the gui |
Beta Was this translation helpful? Give feedback.
-
|
Display the time the next update is, not how long before it is going to run. It's too abstract.
|
Beta Was this translation helpful? Give feedback.
-
|
Accountability: I use Speedtest to hold my ISP to account, so how about:
Community Data: If the project implements the "Test Nodes" feature, it can go a step further into community data.
Comparative Time-Shifting: A UI toggle to "Compare with this time last week/month" as an overlay on the current chart, making it easy to spot cyclical ISP congestion (e.g., "Friday night slowdowns"). Diagnostics: Traceroute History: When a test fails or returns poor results, the tracker could automatically run a traceroute and save it. This helps identify where in the hop chain the failure occurred (local router vs. ISP gateway vs. backbone). Native mobile experience?
Smart logic Conditional Testing: "Don't run tests if the network is busy." By integrating with router APIs (like pfSense, OPNSense, or Unifi), the tracker could wait until the current bandwidth usage is near zero to ensure the test is accurate and doesn't interrupt users. Advanced Networking Testing IPv4 vs. IPv6 Benchmarking: Testing both protocols separately to identify if an ISP’s IPv6 implementation is lagging or has higher latency than the legacy IPv4 route. |
Beta Was this translation helpful? Give feedback.
-
|
Add an option to lock all the graphs on the dashboard to the same time frame specification so when you change the time on one graph, they all change to the specified value. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🤔 Thinking about v2
Speedtest Tracker is almost 3 years old (🥳) and at this point I'm pretty happy with how v1 turned out and after one more planned feature (quota/data cap) I'm sticking a fork in v1 and turning my focus to v2.
Since it's early in the process I'm looking to capture some feedback from the community on features or changes that should be made to Speedtest Tracker.
Speedtest Tracker's mission will not change, it will remain self-hosted and it's primary goal is to monitor the health of your internet connection.
👀 What I already have planned
Note
This list doesn't include everything, just the notable changes. Anything that currently exists you should just assume will exist in the future.
📈 Dashboard/charts && UI
⚙️ Admin panel
🧪 Testing tools
📨 Notifications
mail,database,webhookandApprise🔍 Miscellaneous
🤯 Some wild ideas not set in stone
Beta Was this translation helpful? Give feedback.
All reactions