This section measures your server's network performance to various test servers around the world using iperf3. Each row represents a speed test from your server to a remote host operated by a well-connected provider. Results are shown separately for IPv4 and IPv6 (if supported).

For each location, the table shows:

Column	Meaning
Provider	The network provider running the test endpoint (e.g., Clouvider, Leaseweb).
Location (Link)	The geographic location of the test server and its advertised port speed (e.g., London, UK (10G)).
Send Speed	How fast your server can upload data to the remote endpoint.
Recv Speed	How fast your server can download data from the remote endpoint.
Ping	The measured round-trip latency (in milliseconds) to the test server.

• Gbits/sec and Mbits/sec show throughput (higher is better).
• A busy entry means the endpoint was overloaded and didn't return a reliable speed result.
• A -- in Ping means no latency value was recorded.

These tests give you a practical view of real-world network performance:

• Upload (Send) and download (Recv) bandwidth to different regions.
• Latency to each area.
• Differences between IPv4 and IPv6 connectivity.

They're useful for checking how well your VPS or server can push and pull data to major parts of the world and spotting issues like unusually low speeds or high latency in certain regions.

Notes

The ping values in the iperf3 table can give a good idea of the server's geographic region. Nearby locations usually have low latency. Distant locations have much higher latency. From this, you can often estimate where the server is without relying on IP geolocation.

If your server has strict firewall rules, make sure TCP ports 5200–5209 are open. The network test uses these ports, and blocking them can make the test servers show as "busy."