public-iperf3-servers/testing_process.md

Testing Process

In this document, I outline exactly how I evaluate servers before adding them to iperf3serverlist.net and github.com/R0GGER/public-iperf3-servers and how I continuously monitor them.

Server Acceptance

Before a server is added to the public list, it must pass a comprehensive testing process:

1. Initial Testing Phase

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

2. Monitoring Period

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

More information and test results at test.iperf3serverlist.net

Continuous Monitoring

All listed servers undergo:

• Weekly automated testing (Every Sunday, 02:00 AM +1 GMT)
• 15-minute interval uptime checks
• Full performance testing suite

Removal Criteria

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

If you have questions about my testing process, ideas or other feedback:

• Open an issue in this repository, github.com/R0GGER/public-iperf3-servers/issues

Test Environment

I perform all tests from my 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)

Thank you

Thank you Censys for providing me Research Access.