Testing Process
This webpage explains how I (about me) evaluate servers before listing them on iperf3serverlist.net and GitHub, and how I continuously monitor their performance.
Acceptance
Before a server is added to the public list, it must
pass a comprehensive testing process:
Initial Testing Phase
- Successful ping test (10s timeout)
- Port accessibility verification
- iPerf3 performance test
Monitoring Period
- 30-day observation period
- Minimum 90% uptime monitoring
- Consistent performance across all tests
Monitoring
All listed servers undergo:
- Weekly automated testing
- 15-minute interval uptime checks
- Full performance testing suite
Removal
In my commitment to maintaining a reliable server list, I remove servers that:
- Drop below 90% uptime in a 30-day period
- Fail consecutive automated tests
- Show persistent connectivity issues
- Port accessibility problems
- Display significant performance degradation
Test Results
Test results are collected and processed through multiple tools:
- Raw test results: test.iperf3serverlist.net
- Uptime monitoring: uptime.iperf3serverlist.net
- Results are filtered and analyzed in NocoDB, view results at: Pending List
Test Environment
All tests are performed from a dedicated testing environment:
- VPS running Debian 12
- 4 CPU cores (2 dedicated, 2 fair-shared)
- 16 GB DDR4 RAM
- 10Gb/s network connectivity
- Location: Amsterdam, NL (HostHatch)
