Checking your internet network speed on Ubuntu is one of those tiny tasks that can save you from a surprisingly large amount of confusion. Is your video call freezing because your ISP is having a bad day? Is your Wi-Fi slower than a sleepy turtle? Is your Ubuntu server actually limited by the network, or is your application just being dramatic? A good speed test can help you separate real network problems from random digital gremlins.

The good news: Ubuntu gives you several reliable ways to test internet speed, network throughput, Wi-Fi quality, Ethernet link speed, and real-time bandwidth usage. You can use friendly browser-based tools, fast command-line utilities, built-in network information, or advanced tools like iperf3 for local network testing. The best method depends on what you want to know: your internet download speed, upload speed, latency, LAN performance, or the maximum link speed of your network card.

This guide walks through the most practical methods to check your internet speed on Ubuntu, including GUI options, terminal commands, server-friendly tools, and troubleshooting tips. Whether you are using Ubuntu Desktop, Ubuntu Server, or a minimal VPS, you will find a method that fits your setup.

What “Internet Speed” Really Means on Ubuntu

Before running commands like a caffeinated sysadmin, it helps to understand what you are measuring. Internet speed is not just one number. Most tools report several values:

Download speed

Download speed measures how quickly your Ubuntu machine receives data from the internet. This affects streaming, downloading packages, loading websites, syncing files, and pulling Docker images. It is usually measured in Mbps, meaning megabits per second.

Upload speed

Upload speed measures how quickly your system sends data to the internet. This matters for video calls, cloud backups, file sharing, live streaming, and hosting services.

Ping or latency

Ping measures how long it takes for data to travel from your computer to a server and back. Lower latency is better for gaming, remote desktop, SSH sessions, and voice calls. A fast download speed with terrible latency is like owning a sports car that only turns left after three seconds.

Jitter and packet loss

Jitter is variation in latency. Packet loss means some data never arrives. These are especially important for real-time apps. If your video meetings sound like a robot trapped in a blender, jitter or packet loss may be involved.

Link speed versus internet speed

Your Ethernet or Wi-Fi link speed is not the same as your actual internet speed. For example, your Ethernet adapter may show a 1000 Mbps link, but your ISP plan may only provide 300 Mbps. Link speed tells you the connection rate between your Ubuntu device and router or switch. Internet speed tells you what you actually get beyond your home or office network.

Method 1: Check Internet Speed on Ubuntu Using a Browser

The easiest method is to open a browser and use a web-based speed test. This works well on Ubuntu Desktop if you have Firefox, Chrome, Chromium, or another browser installed.

Steps

1. Close heavy apps such as cloud sync tools, streaming services, game launchers, and large downloads.
2. Connect to the network you want to test.
3. Open your browser.
4. Run a speed test using a reliable testing website.
5. Repeat the test two or three times and compare the results.

Browser tests are convenient because they are visual and beginner-friendly. They usually show download speed, upload speed, ping, and sometimes server location. However, browser tests are not ideal for headless Ubuntu servers, automated testing, or situations where browser extensions and background tabs may affect performance.

For best results, test once on Wi-Fi and once on Ethernet if possible. If Ethernet is much faster, your ISP may be fine and your Wi-Fi may be the actual troublemaker.

Method 2: Use Ookla Speedtest CLI on Ubuntu

For many Ubuntu users, the most practical terminal-based option is Ookla Speedtest CLI. It lets you check download speed, upload speed, latency, and server details directly from the command line. This is especially useful on Ubuntu Server, VPS machines, remote desktops, and systems where you want repeatable results.

Install Speedtest CLI with Snap

On many Ubuntu systems, Snap is already available. You can install Speedtest CLI with:

Then run:

The first run may ask you to accept the license and privacy notice. After that, it will choose a nearby test server and display the result.

Install Speedtest CLI with APT Repository

Some users prefer the official package repository method. A common installation flow is:

Run the test:

List nearby servers

To list available Speedtest servers, use:

To test against a specific server, use its server ID:

This is helpful when your automatic server selection gives odd results. A nearby server is usually best, but testing different servers can reveal routing problems or ISP congestion.

Export results for scripts

If you want to save results, use JSON output:

You can redirect the result to a file:

This makes Speedtest CLI useful for logging network performance over time. For example, you could run a test every hour and compare whether your connection drops during peak evening hours.

Method 3: Use the Classic speedtest-cli Package

Ubuntu repositories may include a Python-based tool called speedtest-cli. It is simple, easy to install, and widely used. However, it is different from Ookla’s official speedtest CLI package, so results and features may vary.

Install speedtest-cli

Run a basic test

For a shorter output, run:

Example output may look like this:

This method is fine for quick checks, especially on systems where you do not want to add another repository. For more consistent testing with the official Speedtest service, use Ookla Speedtest CLI instead.

Method 4: Test Speed with FAST.com from the Terminal

FAST.com is a simple speed test service powered by Netflix infrastructure. It focuses heavily on download speed, which makes it useful for checking streaming-style performance. On Ubuntu, you can use the unofficial fast-cli tool if you have Node.js and npm installed.

Install Node.js and npm

Install fast-cli

Run a download speed test

Test both download and upload

FAST.com is great when you want a quick second opinion. If Speedtest says your internet is fine but streaming still buffers, FAST.com can help compare real-world performance to a major content delivery network.

Method 5: Check Local Network Throughput with iperf3

Sometimes your internet is not the problem. Your local network might be the bottleneck. That is where iperf3 shines. It measures throughput between two devices, such as a laptop and a home server, or two Ubuntu machines on the same LAN.

Unlike internet speed tests, iperf3 requires one device to act as a server and another as a client.

Install iperf3 on both machines

Start iperf3 server on one machine

Run the test from another machine

Replace SERVER_IP_ADDRESS with the local IP address of the machine running the server. For example:

Test upload and download direction

To reverse the direction of the test, use:

This is useful because network performance may differ depending on direction. If one direction is fast and the other is slow, the issue may involve drivers, Wi-Fi signal, duplex settings, router behavior, or system load.

Method 6: Check Ethernet Link Speed with ethtool

If you use a wired connection, checking the Ethernet link speed is essential. You may be paying for gigabit internet, but if your Ubuntu machine negotiates at 100 Mbps, your speed test will never reach gigabit speeds. The usual suspects are older cables, bad connectors, router ports, or adapter negotiation issues.

Find your network interface name

You may see names like enp3s0, eno1, or eth0. Modern Ubuntu systems often use predictable interface names rather than the old eth0 style.

Install ethtool

Check link speed

Look for lines like:

If the speed says 100Mb/s but you expected 1000Mb/s, try a different Ethernet cable, a different router port, or a direct connection to another known-good switch. A Cat 5e or Cat 6 cable is usually recommended for gigabit Ethernet.

Method 7: Use nmcli to View Network Status

nmcli is the command-line interface for NetworkManager. On Ubuntu Desktop, NetworkManager usually handles wired and wireless connections. On some server setups, Netplan may configure NetworkManager or systemd-networkd underneath.

Show devices

This displays network devices, connection state, and active profiles.

Show detailed information for a device

To inspect a specific interface:

List Wi-Fi networks

This can show nearby Wi-Fi networks, signal strength, security type, and connection rate information. It is handy when diagnosing weak Wi-Fi or choosing between 2.4 GHz and 5 GHz networks.

Method 8: Monitor Real-Time Bandwidth with nload

A speed test gives you a snapshot. A bandwidth monitor shows what your system is doing right now. If your speed test looks slow, another process may already be using your connection. That sneaky cloud backup may be eating bandwidth like it skipped breakfast.

Install nload

Run nload

Use the arrow keys to switch between interfaces. nload displays incoming and outgoing traffic in real time, along with total transferred data and current bandwidth usage.

This is not the same as an internet speed test. Instead, it helps you see whether your Ubuntu system is actively downloading, uploading, or sitting peacefully like a well-behaved penguin.

Method 9: Check Speed on Ubuntu Desktop Using Settings

If you prefer the graphical interface, Ubuntu Desktop provides network information through the Settings app.

For Wi-Fi

1. Open Settings.
2. Go to Wi-Fi.
3. Click the gear icon next to the connected network.
4. Review connection details such as signal strength, IP address, security, and related network information.

For wired Ethernet

1. Open Settings.
2. Go to Network.
3. Select your wired connection.
4. Click the gear icon to view details.

The GUI is useful for quick checks, but terminal tools usually provide more detail and are easier to copy, compare, automate, or use over SSH.

How to Get More Accurate Speed Test Results on Ubuntu

Speed testing is simple, but accurate speed testing requires a little discipline. Otherwise, your results may be as trustworthy as a weather forecast from a goldfish.

Use Ethernet when possible

Wi-Fi performance changes constantly because of distance, walls, interference, router placement, channel congestion, and device hardware. Ethernet gives you a cleaner baseline.

Close bandwidth-heavy applications

Pause cloud backups, system updates, torrents, game downloads, streaming apps, and browser tabs playing video. On Ubuntu, you can use nload, bmon, or system monitor tools to check for active traffic.

Test multiple times

Run tests at different times of day. Evening slowdowns may point to ISP congestion. Morning tests may be cleaner. If you only test once, you may capture a temporary hiccup instead of the real pattern.

Choose nearby and consistent servers

For Speedtest CLI, compare automatic server selection with a manually selected server. If one server reports poor results but others look fine, the issue may be the test route rather than your connection.

Compare tools

Use more than one method. For example, run Ookla Speedtest CLI, FAST.com, and a package download from Ubuntu mirrors. If all results are slow, the issue is probably real. If only one tool is slow, the test server or route may be the problem.

Common Problems and What They Mean

Speed is much lower on Wi-Fi than Ethernet

This usually points to Wi-Fi signal quality, router placement, interference, or using a slower Wi-Fi band. Move closer to the router, try 5 GHz or 6 GHz if available, reduce obstacles, or test another device.

Ethernet is stuck at 100 Mbps

Check ethtool. If your link speed is 100 Mbps instead of 1000 Mbps, replace the cable, try another port, and confirm your router or switch supports gigabit speeds.

Download is fast but upload is slow

Many internet plans are asymmetrical, meaning download speed is much higher than upload speed. If upload is far below your plan, test with Ethernet, restart your router, and check whether another device is uploading in the background.

Ping is high but download speed is fine

This can happen during network congestion, bufferbloat, poor Wi-Fi signal, or heavy uploads. Try pausing uploads and testing again. If latency drops, your connection may need better quality-of-service settings on the router.

Results are different between tools

That is normal. Different tools use different servers, test methods, routes, and measurement logic. Treat speed tests as evidence, not absolute truth carved into a stone tablet by the Linux penguin.

Best Commands Summary

Practical Experience: What I’ve Learned from Checking Network Speed on Ubuntu

After testing network speed on many Ubuntu desktops, laptops, servers, and VPS environments, one lesson stands out: the first speed test rarely tells the whole story. It gives you a clue, not a verdict. A single slow result can come from Wi-Fi interference, a busy test server, a background update, a weak router, a poor cable, or even a temporary route issue between your ISP and the test location.

The most useful habit is to test in layers. First, check the internet speed with a simple tool like Speedtest CLI. If the result looks normal, the public internet connection is probably fine. If it looks slow, test again with another server or a different tool like FAST.com. When two or three tools agree, you can trust the pattern more.

Next, check the local connection. On wired Ubuntu machines, ethtool has saved me countless times. A user might complain that gigabit internet only reaches 94 Mbps, and the cause turns out to be a link negotiated at 100 Mbps. That usually means a cable problem, a weak connector, or a router port that is not negotiating correctly. Replacing the cable often feels too simple, but it works more often than people expect.

On Wi-Fi, the story is different. Ubuntu may be perfectly healthy while the wireless environment is chaos. Walls, microwaves, neighboring routers, cheap USB Wi-Fi adapters, and distance can all ruin performance. A laptop might get 400 Mbps in the same room as the router and 40 Mbps two rooms away. That is not Ubuntu being moody; that is physics wearing a hoodie.

For servers, I prefer command-line tests because they are repeatable. Browser speed tests are fine for desktops, but servers need tools that work over SSH. Speedtest CLI is good for internet speed. iperf3 is better for LAN testing. nload is excellent when I suspect something is already consuming bandwidth. Sometimes the “slow internet” problem is actually an unattended backup, a container pulling images, or a package upgrade quietly doing its job.

Another practical tip is to test during different hours. Home connections often slow down in the evening when everyone nearby is streaming, gaming, and pretending they are not the reason the network is congested. If your Ubuntu speed test is fast at 8 a.m. but slow at 9 p.m., the pattern matters. It may be ISP congestion rather than your computer.

Finally, always compare speed test results with real usage. If Speedtest shows 900 Mbps but package downloads crawl, try a different Ubuntu mirror. If FAST.com is slow but other tests are fast, the route to Netflix infrastructure may be the issue. If only one application is slow, the network may not be the villain. Ubuntu gives you enough tools to investigate calmly instead of randomly rebooting everything and hoping the internet gods are pleased.

Conclusion

Checking your internet network speed on Ubuntu is easy once you know which tool fits the job. Use a browser test for quick desktop checks, Ookla Speedtest CLI for reliable terminal results, FAST.com for a simple streaming-focused comparison, iperf3 for local network throughput, ethtool for Ethernet link speed, nmcli for connection status, and nload for real-time bandwidth monitoring.

The smartest approach is not to rely on one number. Test more than once, compare tools, use Ethernet when possible, and check whether your local network is limiting your internet connection. With the right Ubuntu commands, you can diagnose slow speeds faster, talk to your ISP with better evidence, and avoid blaming your computer when the real problem is a tired cable hiding behind the desk.