How to check Internet Speed via Terminal?
Instead of going to sites like speedtest.net, I want to check my current Internet speed from the terminal on Ubuntu. How can I do it?
The results I'm getting with speedtest-cli are vastly under what I get from speedtest.net speedtest-cli Download 18.27 Mbits/s Upload 3.43 Mbits/s speedtest.net Download 59.38 Mbits/s Upload 12.14 Mbits/s I can't consider speedtest-cli to be in any way a valid test of network speed.
@user375058: The `speedtest-cli` uses the same servers (etc.) as SpeedTest.net. You should consider the `speedtest-cli` and `www.speedtest.net` to be equivalent, just with a different front-end. I would be surprised if you get *significantly* different results consistently if they both use the same server. If they aren't using the same server, then you have no basis for comparison. Lastly, my results for both utilities vary by a factor of 2-4 from run to run. I suggest you test 2-4 servers, and perform 3–4 runs for each server and compare tools.
@user375058: I actually just did what I suggested. See the link in my comment below for my results.
I recommend the speedtest-cli tool for this. I created a blog post (Measure Internet Connection Speed from the Linux Command Line) that goes into detail of downloading, installing and usage of it.
The short version is this: (no root required)
curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python -
Retrieving speedtest.net configuration... Retrieving speedtest.net server list... Testing from Comcast Cable (x.x.x.x)... Selecting best server based on ping... Hosted by FiberCloud, Inc (Seattle, WA) [12.03 km]: 44.028 ms Testing download speed........................................ Download: 32.29 Mbit/s Testing upload speed.................................................. Upload: 5.18 Mbit/s
Update in 2018:
pip install --user speedtest-cligets you a version that is probably newer than the one available from your distribution's repositories.
Update in 2016:
speedtest-cliis in Ubuntu repositories now. For Ubuntu 16.04 (Xenial) and later use:
sudo apt install speedtest-cli speedtest-cli
Can you summarize the important information from your blog post in your answer?
The blog post is just an explanation about the program and how to install it. The program is a tool for measuring speed just like speedtest.net does, using the same servers (and automatically location the nearest).
This doesnt seem to work properly. I have BT infinity 50bBit down and 20Mbit up. But the results show up as 0.53Mbit down and 0.2Mbit up. Huh? Incorrect decimal placing? using wget I get 4.27M/s (34Mbit) (some other server though)?
Installing git might be overkill for most Ask Ubuntu readers. You can just download the repo from https://github.com/sivel/speedtest-cli/archive/master.zip
As it has already been stated here: Since speedtest-cli is a python application, it is much easier to install by doing: `pip install speedtest-cli` or: `easy_install speedtest-cli` Depending on how Python is installed on your system, you may need to be root to do the above.
Here is a simple bash script I wrote for handy tool, using `notify-send` and `zenity` to display the output graphically instead of terminal: http://ubuntuone.com/49YdNJBRtYIdaS1eY8jrpw
Confirming that **speedtest-cli is broken**. Doesn't show speeds above 1Mbps. Doesn't transfer any info when claiming to do so.
This should really be the accepted answer...speedtest-cli is working fine for me; think @int_ua was either having compatibility problems or internet problems.
After using `pip install speedtest-cli` to install the script and then running it with `speedtest-cli` the scrit seems to freeze up while at the line `Testing download speed................` **How long should this test take?** It has been over 40 min now, while I was waiting I used speedtest.net and measured ping at 75ms, download speed at 6.36Mbps, and upload speed at 0.98Mbps. I am using Ubuntu 14.10 with python 2.7.8
This should be the right answer. Speed test means download AND upload. First answer ONLY measures the download speed, which is NOT a full picture of your internet connection speed. Especially if you are hosting something on that machine!
how can we select a server? I know of servers that can go beyond gigabit speeds.
@JemiloII: To get a list of all SpeetTest.net servers, type `./speedtest-cli --list` (use `grep` to find the server you're thinking of). It returns servers in the format `XXXX) Company Name (Location, State/Province/Country) [DDD.DD km]`, where XXXX is the server ID (numeric) and DDD.DD is the estimated distance in kilometers from your machine. Then, to perform the test with a given server, type `./speedtest-cli --server XXXX`, using the same numeric server ID you found in the previous step.
@Willoczy: it takes 5-25 seconds for me. In the SpeedTest.net web page, it sometimes complains that there's a missing Latency File. I don't know what's going on, but that message seems to exist for certain servers. I'd choose a different server manually. Perhaps the one you were using was having issues?
@int_ua: I can partially confirm that it is broken. I ran 3 tests via Speedtest.net and the `speedtest-cli` tool for 8 servers across North America. My results are tabulated here. There is a significant, systematic difference between the two approaches. That said, in about half the cases, it's not off by a very significant amount...but half the time it is. The biggest finding was that the upload speeds were consistently lower (usually 50-70% the speed) in the `speedtest-cli` run than the browser version. Odd.
The problem is still there in 2016. I did a few tests and have results similar (in nature) to those of @jvriesem. It is a pity as the tool would be very useful. I am wondering whether it can be used for comparisons (say, a few VPN servers - it would not really matter to know how fast they are but rather to be able to predictably compare them to get the fastest one)
You can also skip the `chmod` command and just run `python speedtest-cli`.
Don't work for me. Tested on `Linux Kali 4.3.0-kali1-amd64 #1 SMP Debian 4.3.3-7kali2 (2016-01-27) x86_64 GNU/Linux` with `Python 2.7.13`. With and without root previllages, the resuld is 0.00 D and 0.00 U speed. I even selected server using `speedtest-cli --server XXXX`
I have a 1000Mbps connection, gives me 7Mbps down 0.2Mbps up, I follow the test with my system updates, it dowloads it at 24Mbps... I tried both the command line and speedtest-cli
For me the `python script` works better than the `speedtest-cli`. I have tested on the same machine, with `python script` I got 93MB/92MB (almost the same for 3 different tests) and with `speedtest-cli` I got 91MB/32MB.
2018 Uprdate: speedtest-cli installed from Ubuntu repositories works as speedtest.net
try this on command line
wget --output-document=/dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip
try this too
got it from above link
For me on Ubuntu 14.10 with python 2.7.8 the command `wget --output-document=/dev/null http://speedtest.wdc01.softlayer.com/downloads/test500.zip` works much better than using `speedtset-cli` the later seems to freeze and ^C fails to interrupte the command. With wget I have no problems cutting the download shrot with ^C
Definitely not a good test for me. `speedtest-cli` gave a speed of about 12MB/s. This gave about 1.5MB/s.
Note that the test file is a 500 MB file. You can change the `test500.zip` to `test10.zip` (for example) to try a 10 MB file. I hear this also works with 100 MB.
Also, note that this only tests download speed, not upload. `speedtest-cli` seems like a better option.
`./tespeed.py` is working fine, although i would prefere `speedtest-cli` if it was working properly. But, beware to download files inside "SocksiPy" also. Tespeed is testing connection download and upload speed by using specific file sizes.
Note that speedtest.wdc01.softlayer.com is just one specific Speedtest server. There are thousands of them all over the world, and depending on where you are located, testing with this one may or may not give you correct results. Speedtest.net choses the server closest to you automatically, which should be more relevant. Ideally, you should use your browser's Dev Tools to figure out the hostname/URL speedtest.net choses in your case and use that in the wget line above instead of speedtest.wdc01.softlayer.com.
If you can't be bothered to install iperf , you could precede any command that shifts a known amount of data with the
timecommand and do a sum.
iperf is simple and easy to use.
It requires a client and server.
(on the server)
[email protected]$ iperf -s
(on the client)
[email protected]$ iperf -c server.domain ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.3 port 52143 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 113 MBytes 94.7 Mbits/sec
Those of you who don't have a remote server you can connect to, there are publicly available iperf servers: https://iperf.cc/
Well I use
wgetfor it. That little tool tells me nicely what speed I have.
To use it just point to a file in internet that is relatively bigger so that you can get a better estimate of it.
wget http://hostve.com/neobuntu/pics/Ubu1.aviwould start to download the Ubu1.avi file and show at what speed it is downloading.
Of course there are several recommendations:
Speed test yourself with good servers. In the case of my link the speed is less than 200KB so if you have a higher speed, the server will be the bottleneck for you, not your actual speed.
The highest speed you will see is the maximum speed that your connection and the server's connection can offer. If your connection is 512KB and the place where you are downloading is 400KB, your max connection will be 400KB because it is the max for the server you are downloading from.
You need to do the test at least 5 times to have a reliable speed check or at least do it for a minute or two. This will help you have a more accurate check.
You need to have at least 4 or 5 different testing sources to have a more accurate speed. Never test only from the same site as this can be affected by your distance to it, any problem in the server and the connections to it, etc. Always test from different servers.
This is an alternative to
wget. The downside of
wgetis the lack of parallel connections. To use aria2 we fist need to download it:
sudo apt-get install aria2
To use it is simple:
In the image, the -x 4 is how many parallel connections we wish to use. The CN parameter in the next line shows how many active parallel connections were permitted to download from that site. In this case CN is 4. But if we tried to have more connections we would get something like this:
We set 8 parallel connections but the site only allowed a maximum of 5 as shown by CN:5. This could be solved by the -j option which tells aria2c the maximum concurrent connections we want (Which by default is 5) but if the server has limited this, -j will not work.
wget is not (yet) able to do a segmented download, that is to download a single file using multiple (parallel) connections, so if your ISP is limiting the speed per 1 connection, you won't get accurate results... it would be a more precise test to use some other tool, that can at least use segmented download (like aria2)
This is NOT a speedtest, this is a DOWNLOAD speed test only! Internet speed test means down&up load! Second answer, and all others mentioning speedtest-cli have the correct approach.
@EmilBorconi You are correct but in real life, we are not doing benchmarking Internet speeds here, this are just your average current speed tests of any home user without the need for sites like speedtest. A download speed (Which is enough for anyone trying to see if they are having a bottleneck) is a good enough test. A full down/up speed test would check what the full scope of your speed is based on your ISP. So yeah that would be the best solution, but for any fast test scenario, even a simple wget would do the trick since normally people worry more about download speed than upload.
@LuisAlvarado sorry if I sounded rude, just I think people should be able to fully understand what they are asking / and what is the accepted answer. Lot's of newbies will look at forums and they will assume / pick / stop at the accepted answer, and they form a false image in their had. And yes download is more important then upload unless you are a facebook maniac who post selfies each 5 minutes, then start a fight with you ISP just because you tested the download which is good, but you have a crappy upload... Once again sorry if my tone was rude, did not want to insult...
@EmilBorconi don't worry friend, we appreciate your feedback and they help anybody that reads this in the future.
FYI, I had Axel (https://launchpad.net/ubuntu/+source/axel) installed already (using it for parallel connections), so it works fine for this purpose.
a simple one-liner that tests how long it takes to download 100MB (works on
t=$(date +"%s"); wget http://speedtest.tele2.net/100MB.zip -O ->/dev/null ; echo -n "MBit/s: "; expr 8 \* 100 / $(($(date +"%s")-$t))
- store the timestamp in $t
- download 100mb but don't store anything
8 * 100mb / $t
This worked great as I'm testing from a stateless read-only rootFS and `wget` wasn't outputting the speed.
Run several instances of wget with timeout command on large files:
#!/bin/bash timeout 5 wget -q url_1/100MB.zip & timeout 5 wget -q url_2/file.zip & timeout 5 wget -q url_3/sample.mov & timeout 5 wget -q url_4/speech.mp4 &
And then write a script to calculate the total bytes downloaded and divide 5 seconds you will get a bytes/sec figure. Should be quite accurate and you can add more instances to max your bandwidth.
I have yet to test the full script but the single line command "timeout 5 wget url" works, and you get a partially downloaded file as a result (if 5 secs is not enough to complete the download).
you can use
tespeed. it is a Terminal network speed test that uses servers from
Speedtest.net. It uses nearest test server but can also use one manually specified by the user.
git clone git://github.com/Janhouse/tespeed.git cd tespeed git submodule init git submodule update ./tespeed.py
for more info use :
it will provide more option for speed test.
I'm regularly using something like this:
% wget -O /dev/null --progress=dot:mega http://cachefly.cachefly.net/10mb.test ; date --2020-01-06 03:31:05-- http://cachefly.cachefly.net/10mb.test Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 2607:7700::18:0:1:cdea:afaf, 18.104.22.168 Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|2607:7700::18:0:1:cdea:afaf|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10485760 (10M) [application/octet-stream] Saving to: <</dev/null>> 0K ........ ........ ........ ........ ........ ........ 30% 3.02M 2s 3072K ........ ........ ........ ........ ........ ........ 60% 3.97M 1s 6144K ........ ........ ........ ........ ........ ........ 90% 3.94M 0s 9216K ........ ........ 100% 3.99M=2.8s 2020-01-06 03:31:08 (3.62 MB/s) - <</dev/null>> saved [10485760/10485760] Mon Jan 6 03:31:08 CST 2020 %
You can change the
4000mb, and possibly some other values.
You can also change the
--progress=dot:giga; this setting helps you see how fast the download is going, and preserve more than a single reading over the whole duration of the download, which is helpful for when you need to share the results with someone, or just save it for your own records as a sort of a graph.