Testing Process

How servers are evaluated before they are added to the public list, and how they are continuously monitored afterwards.

Acceptance

Before a server is added to the public list, it has to prove itself in a comprehensive testing process.

  1. Submitted Server is proposed
  2. Initial tests Ping, ports, iPerf3
  3. 30 days Monitoring period
  4. Listed Publicly available

Initial Testing Phase

  • Successful ping test (10s timeout)
  • Port accessibility verification
  • iPerf3 performance test

Monitoring Period

  • 30-day observation period
  • Minimum 90% uptime requirement
  • Consistent performance across all tests

Servers under test can be followed on pending.iperf3serverlist.net.

Monitoring

Being listed is not the finish line. All listed servers keep being tested:

15 minUptime check interval
WeeklyAutomated testing
FullPerformance testing suite

Live results are available on the uptime monitor.

Removal Criteria

To keep the server list reliable, servers are removed that:

  • Drop below 90% uptime in a 30-day period
  • Fail consecutive automated tests
  • Show persistent connectivity issues
  • Have port accessibility problems
  • Display significant performance degradation

Test Results

All results are public. Dive into the raw data:

Test Environment

All tests are performed from a dedicated HostHatch VPS:

  • 4 CPU cores (2 dedicated, 2 fair-shared)
  • 16 GB DDR4 RAM
  • 10 Gb/s network connectivity
  • Location: Amsterdam, NL

Sponsored by HostHatch.