Netperf Server List Verified ((link)) Jun 2026

This test measures the request/response performance, which is critical for interactive applications. It returns a result in "transactions per second" (tps); a higher tps indicates lower latency. This test helps validate the server's responsiveness.

netserver -p 12865 # default port # or netserver -p 12865 -d # daemon mode netperf server list verified

| Server Hostname | Geographic Location | Notes | |---|---|---| | netperf.bufferbloat.net | Atlanta, GA (US East) | Primary alias, also known as netperf-east | | netperf-east.bufferbloat.net | East Coast, US | Same as primary | | netperf-west.bufferbloat.net | California (US West) | Recommended for west coast tests | | netperf-eu.bufferbloat.net | Denmark (Europe) | Best for European users | | flent-fremont.bufferbloat.net | Fremont, CA | Also iperf2, irtt available | | flent-newark.bufferbloat.net | Newark, NJ | East coast alternative | | flent-dallas.bufferbloat.net | Dallas, TX | Central US location | | flent-london.bufferbloat.net | London, UK | UK and Western Europe | | flent-tokyo.bufferbloat.net | Tokyo, Japan | Asia-Pacific region | netserver -p 12865 # default port # or

: Use the reporting flags if you need to verify if the hardware (rather than the network) is the bottleneck. Best Practices for "Verified" Results Firewall Rules : Netperf defaults to port 12865 for control

Below is a guide to the few available public resources and how to verify a Netperf server yourself. Known Public Netperf & Flent Server Resources

Before running a long-duration benchmark, you must verify that the remote server is active and reachable on the correct port.

: Netperf defaults to port 12865 for control traffic and establishes dynamic ports for data transmission. Public enterprise firewalls almost universally block these ports.