Hosted by Singtel (Singapore) : 230.77 ms Here is the result from the version in the repository from Ubuntu 16.04 speedtest-cli Its probably down to the protocol that's being used. (Unfortunately, my GUI PCs are behind a homeplug connection, but trust me when I say the rest). I was messing with this - and have speedtest-cli and speedtest++ installed. I already tried pruging speedtest-cli, rebooting the server and so on.Īny idea what is going on here? How is it possible, the commandline spedtest fails this spectacular, while the rest of the network setup is just fine? Speedtest directly on the router too results in about 250 Mbit/s. Leads to a download speed of about 200 Mbit/s. But no, the connection speed is just fine. So far so good, but regarding the Debian server, directly connected to the router: speedtest-cli(server 15819) 3,88 Mbit/s down, 3,69Mbit/s up Speedtest from my notebook(Arch Linux), directly connected to the router: 310 Mbit/s

Speedtest from my PC(Windows 10), directly connected to the router: 370 Mbit/s My first thought was my server or speedtest in general have a problem, but here starts the fun part.

Since I use it to monitor my ISP connection stability, this is a problem. On my local homeserver(Debian 9.9), speedtest-cli and it's python pendant are freaking slow.

Debian 9.9 iso download