I'm starting to think about v2 and want your feedback and suggestions!

[alexjustesen]

🤔 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

• A completely redesigned dashboard with new charts and metrics
• A dashboard that has filters and remembers your date ranges
• A dashboard that can be embedded anywhere (like Home Assistant)
• Results that can be viewed outside of an admin panel

⚙️ Admin panel

• Dashboards and results will be moved out of the admin panel
• Manage (multiple) test and schedules from the IU

🧪 Testing tools

• Ookla tests (just like we have now)
• Ping tests
• Additional speedtest services / tools #976

📨 Notifications

• Consolidate notification channels down to just mail, database, webhook and Apprise
• Editable content notifications
• Summary/overview notifications
• Notifications for when tests return to being healthy
• Notifications for failed tests
• Only send a notification when X tests have failed or have breached thresholds

🔍 Miscellaneous

• SSO with Authelia and Authentik
• Run tests when poor ping results are detected
• Retry failed tests, including trying with a different server
• Debounce tests if a threshold was breached and try again after a period of time
• Thresholds for absolute and relative values, these will be configurable per test

🤯 Some wild ideas not set in stone

• Test nodes, put a node anywhere and have it report back to a central Speedtest Tracker instance
• Headless Speedtest Tracker with no UI, just configurable from environment variables

[AleksCee]

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.
Why? My example "Deutsche Telekom" is often take server down an new up or have some in maintenance and then some speedtest are failed... at now I manually change the lists if I figure it out.
Using this script to get the IDs:

#!/bin/bash

docker compose exec -it speedtest-tracker bash -c 'cd /app/www;php artisan app:ookla-list-servers "Deutsche"'
docker compose exec -it speedtest-tracker bash -c 'cd /app/www;php artisan app:ookla-list-servers "Deutsche"' | cut -f3 -d' '|egrep  '[[:digit:]]'|tr '\n' ','

[alexjustesen]

Out of curiosity why not let the Ookla CLI always pick the best server?

[AleksCee]

Because the Ookla gets servers which didn't get the full speed. If I use the random-pick I get 300-400mb lower speed a with the Telekom-Servers at my Vodafone 1GB Cable connection.

[svenvg93]

Think this might be partially covered when we add the retrying of failed tests. Then you can set all the server ID from DT and if one fails we can retry the next one. Would that be sufficient for you?

[AleksCee]

Yes, this should solve the problem.

[dvdpearson]

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.

[alexjustesen]

It's annoyed me too, it's in the cards for the next version 👍

[sym0nd0]

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?).

[alexjustesen]

I'm running pangolin in the lab but not as an oath provider, I'll look into both but no promises.

[te5s3rakt]

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.

[alexjustesen]

I think we might be able to do this with the pause feature I have planned, good idea 👍

[crivchri]

Hi,

Would it be possible to have Speedtest-Tracker running in a LXC container without Docker?
This would be really appreciated for Proxmox users.

Kind regards!

[alexjustesen]

Tbh, I have no way of testing this. I'll keep it in mind but I'll have to say a "probably not".

[crivchri]

Hi @alexjustesen,

Thank you for your response.

It would be a good start to have a way to install and run Speedtest-Tracker on any Linux system (without Docker). Would this be possible?

This would enable to use this in LXC containers, e.g. in Proxmox.

Kind regards

[svenvg93]

You can technically run it without Docker, but we don’t officially support that setup. If you’re interested, this discussion provides more context: #1131

Supporting bare-metal installs across various Linux distributions is difficult due to the number of components involved.

[Fabick75]

Hi @alexjustesen,

Thank you for your response.

It would be a good start to have a way to install and run Speedtest-Tracker on any Linux system (without Docker). Would this be possible?

This would enable to use this in LXC containers, e.g. in Proxmox.

Kind regards

Hi, I described how to install the tool directly in Linux, without Docker (you will find in the discussion reported by svenvg93) but as soon as possible I would to test all the process with the latest release and, because I'm using Proxmox, it's interesting to test in an lxc container...then maybe I will try to build a dedicated container.

[drVLecter]

hi,
helper scripts guys already done it.
I tested it and for the most part works okay - few minor things to iron out.
[(https://community-scripts.github.io/ProxmoxVE/scripts?id=speedtest-tracker)]

[zodac-personal]

Only send a notification when X tests have failed or have breached thresholds

SSO with Authelia and Authentik

These are the main two I'm looking for. Hoping to see them in v2 soon!

[tcn33]

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.

[Ja50n-Kru]

This is an excellent idea.

[andrewjamescarr]

Great idea!

[comprofix]

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.

[svenvg93]

All external notification services—like Gotify—will be handled through Apprise. This allows us to support a wide range of services without needing to integrate each one directly into the app.

Even when using a library, we’d still need to define how the app interacts with it. Apprise takes care of that for us. 😊

[comprofix]

Thanks for the clarification on Apprise. I was not fully aware of what it did. A quick look of their GitHub page, it looks like a God Send for notification services. Looking forward to seeing what V2 will bring us.

[skyeci-draytek]

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!

[alexjustesen]

iPerf is planned in the "Additional test tools", I use iPerf to test my 2/2g connection because it seems like Ookla is always under reporting it.

[Skyeci73]

Thanks. If we can specify our own command line parameters and schedule that would be amazing.

[b8z-io]

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)
but the Webhook works fine into Homeassistant.

Looking forward to ANY more improvements.

[svenvg93]

All external notification services—like Gotify—will be handled through Apprise. This allows us to support a wide range of services without needing to integrate each one directly into the app. You will be able to keep using Gotify,Apprise will just sit in between.

[damonmorgan]

Would like to be able to track/visualise packet loss

[alexjustesen]

Packet loss is apart of the Ookla dataset so it'll be in v2 👍

[Fabick75]

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.

[alexjustesen]

It was a late night idea and I'm really excited to see how it comes out!

[jnapieralski]

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)
Maybe this is the same as...

Retry failed tests, including trying with a different server

and you're way ahead of me

Thanks for your work on speedtest-tracker, it's a great tool.

[Snake16547]

I'm just looking for a proper notification option to push webhooks or pushover :)

[svenvg93]

Both are already possible in v1, Is there anything missing in the current implementation that you would like to see added?

[Snake16547]

Both are already possible in v1, Is there anything missing in the current implementation that you would like to see added?

I might be wrong but the current documentation says clearly that every other notification channel were deprecated

https://docs.speedtest-tracker.dev/settings/notifications

For my personal use case I just need a notification (Pushover would be nice or Telegram) when there is a threshold reached for download/up speed to get counter measures started to my ISP.

[svenvg93]

That statement in the docs is not very clear. In this case, deprecated means we are no longer adding new channels or making adjustments to the current ones, as they will be replaced by Apprise.

As Alex mentioned in the original post, Webhooks, Mail, and Database will remain in v2. All other channels will be removed and replaced by Apprise.

[Snake16547]

That statement in the docs is not very clear. In this case, deprecated means we are no longer adding new channels or making adjustments to the current ones, as they will be replaced by Apprise.

As Alex mentioned in the original post, Webhooks, Mail, and Database will remain in v2. All other channels will be removed and replaced by Apprise.

thats a bummer but hey maybe that would be my first time to participated in a project and bring this into the v2, if accpeted.

[svenvg93]

Every contribution is, of course, greatly appreciated.
In version 2, we won’t maintain separate notification channels for Pushover, Discord, Telegram, and others. Instead, we’ll integrate Apprise
, which acts as a bridge between the application and the notification services. This way, we don’t need to manage each channel individually, and it also gives us access to many additional services we don’t yet support.

In v2 there will be Mail, Database, Webhook and Apprise.

[akhi-init-self]

Option to exclude specific test servers would be great. Now we can select a specific one or select all. Not exclude a specific one

[svenvg93]

You can use the SPEEDTEST_BLOCKED_SERVERS environment variable to block a server if you want :)
https://docs.speedtest-tracker.dev/getting-started/environment-variables#speedtest

[henkiewie]

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.

[alexjustesen]

Planned 👍

[henkiewie]

i'ts already in and working 💯

[Noosan1]

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.

[drVLecter]

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:

• delete whole history
• delete everything older than X days
• set history to X amount of days or unlimited and autodelete everything older than max days set

[alexjustesen]

Pruning data isn't going anywhere. I'm not a hoarder and prune my records after a year.

[Patrick010]

Make login optional. I am the only user, login is unnecessary and annoying.

[alexjustesen]

I mentioned this in an issue a while ago but there are no plans to expose the admin panel/settings without authentication. Filament (panel package I'm using) bakes in authentication pretty deeply and I just don't have the time for that type of change ATM.

[Patrick010]

ok

[alexjustesen]

@Patrick010 what part of the admin panel are you going into a lot, the results?

[Patrick010]

Only the results tbh

[alexjustesen]

Aight, I have that captured in #917

[Patrick010]

Add the scheduler and other configurable options to the gui

[alexjustesen]

Soon TM

[Patrick010]

Display the time the next update is, not how long before it is going to run. It's too abstract.

[alexjustesen]

New banner is in v1.12.1 which shows the date and time of the next scheduled test instead of the human string.

[andrewjamescarr]

Accountability: I use Speedtest to hold my ISP to account, so how about:

• SLA Compliance Dashboard: Allow users to input their advertised plan speeds (e.g., 1000/50). The UI could then show the percentage of time the ISP met that target (e.g., "92% SLA Compliance this month").
• Refund Evidence Export: Generate a "Provider Report" PDF with high-quality graphs and raw data tables

Community Data: If the project implements the "Test Nodes" feature, it can go a step further into community data.

• Regional Benchmarks: An opt-in feature to share anonymized speed results (ISP + City + Speed) to a central leaderboard or map. This would help users see if a slowdown is unique to their home or a regional ISP outage.
• DownDetector Integration: Pull in data from DownDetector or Cloudflare Radar to overlay local outages on the user's personal speed charts.

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?

• Push Notifications via Browser: Bypassing the need for a separate notification service for simple mobile alerts.
• Mobile Dashboard: A simplified, "at-a-glance" UI that feels like a native app when saved to the home screen.

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.

[drVLecter]

gonna turn speedtesttracker into a ISPS hate this one trick meme :)

[labrown]

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.