From 265d3417f671cdddcae7c9f076c6cb44751fbcfe Mon Sep 17 00:00:00 2001 From: R0GGER Date: Fri, 20 Mar 2026 23:09:09 +0100 Subject: [PATCH] =?UTF-8?q?=20Added=20new=2030=E2=80=91day=20uptime=20moni?= =?UTF-8?q?toring?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I recently replaced Uptime Kuma with Gatus, which enables new and simpler smart tools such as 30‑day uptime. --- testing_process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/testing_process.md b/testing_process.md index 7567699..893412b 100644 --- a/testing_process.md +++ b/testing_process.md @@ -12,7 +12,7 @@ Before a server is added to the public list, it must pass a comprehensive testin - iPerf3 performance test 2. **Monitoring Period** - - [30-day](https://30d-uptime.iperf3serverlist.net/?max=90) observation period + - [30-day](https://30d-uptime.iperf3serverlist.net) observation period - Minimum 90% uptime requirement - Consistent performance across all tests @@ -29,7 +29,7 @@ All listed servers undergo: ## Removal In my commitment to maintaining a reliable server list, I remove servers that: -- Drop below 90% uptime in a 30-day period, [uptime.iperf3serverlist.net](https://uptime.iperf3serverlist.net/) and [30d-uptime.iperf3serverlist.net](https://30d-uptime.iperf3serverlist.net/?max=90) +- Drop below 90% uptime in a 30-day period, [uptime.iperf3serverlist.net](https://uptime.iperf3serverlist.net/) and [30d-uptime.iperf3serverlist.net](https://30d-uptime.iperf3serverlist.net) - Fail consecutive automated tests - Show persistent connectivity issues - Port accessibility problems