Welcome to the SEACOM iPerf3 speed test service

This service is made available for more advanced speed test requirements, where additional detail and granular control of the speed test experience is required by our Internet customers.

Please carefully read the guidelines below on usage of this service:

  • Do not abuse this service.
  • Availability of this service is guaranteed.
  • iPerf3 has been deployed for this service. Only iPerf3 clients are supported. Neither iPerf1 nor iPerf2 clients are supported.
  • Both IPv4 and IPv6 connections are supported for this service.
  • If you are on a properly configured IPv6 network, the tests will be conducted over an IPv6 transport by default. You may override this by using the "-4" option if you prefer to run the test over IPv4.
  • Both TCP and UDP connections are supported.
  • iPerf3 allows only one connection at a time. To overcome this in order to support multiple tests simultaneously, we are running iPerf3 on ten (10) separate ports on each iPerf3 test server. If you happen to connect to a port that is in active use, you will receive the following error: "iperf3: error - the server is busy running a test. try again later". To workaround that, either wait and try again later, or connect to one of the other supported ports.
  • The iPerf3 default port is 5201, and is supported in the range of ports available for this service.
  • In general UDP tests will perform much better than TCP tests. For ultimate throughput tests, particularly over high-latency paths, we recommend you run UDP tests.
  • The client-side connection example below runs a 10-second UDP speed test toward Maputo on port 5209 at 25Mbps of bandwidth:
  • iperf3 -c iperf3.maputo.seacomnet.com -u -i 1 -t 10 -b 25M -p 5209

  • The client-side connection example below runs a 5-second UDP speed test toward London at 400Mbps of bandwidth over IPv6 (the default port is used as the "-p" option is not specified):
  • iperf3 -c iperf3.london.seacomnet.com -u -i 1 -t 5 -b 400M -6


CityServer AddressSystemAvailable BandwidthPortServer MTUIP Protocol Version
Amsterdamiperf3.amsterdam.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Cape Towniperf3.cape-town.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Dar Es Salaamiperf3.dar-es-salaam.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Durbaniperf3.durban.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Frankfurtiperf3.frankfurt.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Johannesburgiperf3.johannesburg.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Kampalaiperf3.kampala.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Londoniperf3.london.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Maputoiperf3.maputo.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Marseilleiperf3.marseille.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Mombasaiperf3.mombasa.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Mtunziniiperf3.mtunzini.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Nairobiiperf3.nairobi.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Sloughiperf3.slough.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6
Stockholmiperf3.stockholm.seacomnet.comFreeBSD 10.31Gbps5200 - 5209: TCP/UDP9000IPv4 & IPv6