iPerf3 servers will only allow one iPerf connection at a time. Multiple tests at the same time is not supported. If a test is in progress, the following message is displayed: "iperf3: error - the server is busy running a test. try again later"
| Europe | |||||||
|---|---|---|---|---|---|---|---|
| iPerf3 server | Localization | Data center | Hosting | Speed | Port | IP version | Contact |
| ping.online.net ping6.online.net ping-90ms.online.net ping6-90ms.online.net |
France Île-de-France |
Scaleway Vitry DC3 |
 |
100 Gbit/s | 5200 TCP/UDP to 5209 TCP/UDP |
IPv4 or IPv6 | mikmak |
| iperf3.moji.fr | France Île-de-France |
DC Moji |  |
100 Gbit/s | 5200 TCP/UDP to 5240 TCP/UDP |
IPv4 and IPv6 | @nemavdotio |
| iperf.par2.as49434.net | France Île-de-France |
DC Harmony Hosting |  |
40 Gbit/s | 9200 TCP/UDP to 9240 TCP/UDP |
IPv4 and IPv6 | @g_marsot |
| paris.testdebit.info lille.testdebit.info lyon.testdebit.info aix-marseille.testdebit.info bordeaux.testdebit.info |
France Paris France Lille France Lyon France Aix-en-Provence France Bordeaux |
Data centers Bouygues Telecom |
 |
10 Gbit/s 10 Gbit/s 10 Gbit/s 10 Gbit/s 10 Gbit/s |
9200 TCP/UDP to 9240 TCP/UDP |
IPv4 and IPv6 | @lafibreinfo |
| speedtest.serverius.net (Port 5002: add -p 5002) |
Netherlands | Serverius data center |
 |
10 Gbit/s | 5002 TCP/UDP | IPv4 and IPv6 | @serveriusbv |
| nl.iperf.014.fr | Netherlands | NextGenWebs data center |
 |
1 Gbit/s | 10415 TCP/UDP to 10420 TCP/UDP |
IPv4 only | @014_fr |
| ch.iperf.014.fr | Switzerland Zurich |
HostHatch data center |
|
3 Gbit/s | 15315 TCP/UDP to 15320 TCP/UDP |
IPv4 only | @014_fr |
| iperf.eenet.ee | Estonia | EENet Tartu |  |
5201 TCP/UDP | IPv4 only | @EENet_HITSA | |
| iperf.astra.in.ua | Ukraine Lviv |
Astra Lviv |  |
10 Gbit/s | 5201 TCP/UDP to 5206 TCP/UDP |
IPv4 and IPv6 | noc@astra.in.ua |
| iperf.volia.net | Ukraine | Volia Kiev |  |
5201 TCP/UDP | IPv4 only | @voliaofficial | |
| Asia | |||||||
| iPerf3 server | Localization | Data center | Hosting | Speed | Port | IP version | Contact |
| speedtest.uztelecom.uz | Uzbekistan Tashkent |
Infosystems |  |
10 Gbit/s | 5200 TCP/UDP to 5209 TCP/UDP |
IPv4 and IPv6 | @KhurshidSuyunov |
| iperf.it-north.net | Kazakhstan |
Petropavl |  |
1 Gbit/s | 5200 TCP/UDP to 5209 TCP/UDP |
IPv4 only | Brauninger A.F. |
| iperf.biznetnetworks.com | Indonesia |
Biznet - Midplaza Cimanggis |
 |
1 Gbit/s | 5201 TCP to 5203 TCP |
IPv4 and IPv6 | Biznet Networks |
| Oceania | |||||||
| iPerf3 server | Localization | Data center | Hosting | Speed | Port | IP version | Contact |
| speedtest-iperf-akl.vetta.online |
New Zealand Auckland |
Vetta Online Auckland |
 |
10 Gbit/s | 5200 TCP to 5209 TCP |
IPv4 only | contact |
| Americas | |||||||
| iPerf3 server | Localization | Data center | Hosting | Speed | Port | IP version | Contact |
| iperf.scottlinux.com | USA California |
Hurricane Fremont 2 |
 |
1 Gbit/s | 5201 TCP/UDP | IPv4 and IPv6 | @scottlinux |
| iperf.he.net | USA California |
Hurricane Fremont 1 |
 |
5201 TCP/UDP | IPv4 and IPv6 | HE forums | |
To add / remove a public iPerf3 server, please report them to @lafibreinfo
iPerf3 not allow multiple tests to a server => it is necessary to start several iPerf processes for not having the message iperf3: error - the server is busy running a test. try again later
Systemd script to start 41 iPerf3 server (port 9200 to port 9240).
sudo adduser iperf --disabled-login --gecos iperf
sudo nano /etc/systemd/system/iperf3-server@.service
[Unit] Description=iperf3 server on port %i After=syslog.target network.target [Service] ExecStart=/usr/bin/iperf3 -s -1 -p %i Restart=always RuntimeMaxSec=3600 User=iperf [Install] WantedBy=multi-user.target DefaultInstance=5201
The "Restart = always" allows to restart iperf3 after one hour (RuntimeMaxSec = 3600) to limit the cases of no response or when the iperf3 server has ended abruptly.
sudo systemctl daemon-reload
To activate iperf3 when the server starts up:
for p in $(seq 9200 9240); do sudo systemctl enable iperf3-server@$p ; done
$ for p in $(seq 9200 9240); do sudo systemctl enable iperf3-server@$p ; done Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9200.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9201.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9202.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9203.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9204.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9205.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9206.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9207.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9208.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9209.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9210.service → /etc/systemd/system/iperf3-server@.service. Created symlink /etc/systemd/system/multi-user.target.wants/iperf3-server@9211.service → /etc/systemd/system/iperf3-server@.service. ...
sudo reboot
To view the status and logs of iPerf3 :
sudo systemctl status iperf3-server@*
sudo journalctl -u iperf3-server@*
To disable iperf3 when starting the server :
for p in $(seq 9200 9240); do sudo systemctl disable iperf3-server@$p ; done
NetEm (already enabled in the Linux kernel) provides Network Emulation functionality for testing protocols by emulating the properties of wide area networks.
To simulate an additional latency of 80 ms, just type sudo tc qdisc add dev eth0 root netem delay 80ms
It just adds a fixed amount of delay to all packets going out of the local Ethernet.
To stop the additional latency, just type sudo tc qdisc change dev eth0 root netem delay 0ms
Lines to add to the file /etc/rc.local before exit 0, to add 40ms of latency :
# Add +40ms latency tc qdisc add dev eth0 root netem delay 40ms
Note: If your network interface is not eth0, replace eth0 with the name of your network interface