time:2026-09-28T07:58:36Z	status:UNKNOWN	latency:7.995	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:65.593	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56310	target_addr:104.21.86.125:443
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:66.553	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56294	target_addr:104.21.86.125:443
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:67.024	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38586	target_addr:172.67.168.140:443
time:2026-09-28T07:58:36Z	status:FAILURE	latency:430.076	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:700.128	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:707.816	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:713.737	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:1085.360	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40918	target_addr:172.64.147.104:443
time:2026-09-28T07:58:36Z	status:HEALTHY	latency:1748.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:03:36Z	status:UNKNOWN	latency:8.432	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:66.753	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50220	target_addr:104.21.26.208:443
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:66.459	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57934	target_addr:104.21.86.125:443
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:67.013	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57942	target_addr:104.21.86.125:443
time:2026-09-28T08:03:36Z	status:FAILURE	latency:197.941	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:644.169	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:669.864	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:701.418	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:1085.551	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40486	target_addr:104.18.40.152:443
time:2026-09-28T08:03:36Z	status:HEALTHY	latency:1786.873	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:08:36Z	status:UNKNOWN	latency:7.353	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:70.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39488	target_addr:104.21.26.208:443
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:70.952	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48848	target_addr:172.67.219.211:443
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:83.837	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48850	target_addr:172.67.219.211:443
time:2026-09-28T08:08:36Z	status:FAILURE	latency:422.792	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:678.817	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:729.388	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:834.416	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:1080.646	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46992	target_addr:172.64.147.104:443
time:2026-09-28T08:08:36Z	status:HEALTHY	latency:1819.886	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:13:36Z	status:UNKNOWN	latency:7.818	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:65.802	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39976	target_addr:172.67.168.140:443
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:67.135	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45818	target_addr:172.67.219.211:443
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:67.615	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58506	target_addr:104.21.86.125:443
time:2026-09-28T08:13:36Z	status:FAILURE	latency:196.899	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:657.120	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:656.884	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:669.320	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:1081.396	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43642	target_addr:104.18.40.152:443
time:2026-09-28T08:13:36Z	status:HEALTHY	latency:1767.819	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:18:36Z	status:UNKNOWN	latency:10.429	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:67.812	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56288	target_addr:172.67.168.140:443
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:68.680	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34012	target_addr:172.67.219.211:443
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:68.982	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34024	target_addr:172.67.219.211:443
time:2026-09-28T08:18:36Z	status:FAILURE	latency:352.979	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:626.143	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:629.145	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:631.319	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:1081.125	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60242	target_addr:172.64.147.104:443
time:2026-09-28T08:18:36Z	status:HEALTHY	latency:1766.643	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:23:36Z	status:UNKNOWN	latency:8.032	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:67.907	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46486	target_addr:172.67.168.140:443
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:69.436	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44662	target_addr:172.67.219.211:443
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:69.412	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44670	target_addr:172.67.219.211:443
time:2026-09-28T08:23:36Z	status:FAILURE	latency:202.085	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:566.700	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:601.213	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:640.546	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:1079.743	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47250	target_addr:172.64.147.104:443
time:2026-09-28T08:23:36Z	status:HEALTHY	latency:1737.425	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:28:36Z	status:UNKNOWN	latency:8.866	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:67.863	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47482	target_addr:172.67.219.211:443
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:68.259	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45988	target_addr:172.67.168.140:443
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:75.057	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46166	target_addr:104.21.86.125:443
time:2026-09-28T08:28:36Z	status:FAILURE	latency:207.549	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:1067.334	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34416	target_addr:104.18.40.152:443
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:1624.832	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:1631.666	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:1636.081	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:28:36Z	status:HEALTHY	latency:1753.750	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:33:36Z	status:UNKNOWN	latency:8.374	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:68.749	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45686	target_addr:172.67.168.140:443
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:71.096	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48936	target_addr:104.21.86.125:443
time:2026-09-28T08:33:36Z	status:FAILURE	latency:513.979	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:709.573	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:713.174	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:1074.970	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38806	target_addr:172.64.147.104:443
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:1076.461	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34296	target_addr:172.67.219.211:443
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:1766.679	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:33:36Z	status:HEALTHY	latency:1812.815	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:38:36Z	status:UNKNOWN	latency:6.977	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:66.289	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34104	target_addr:172.67.219.211:443
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:67.130	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35248	target_addr:104.21.86.125:443
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:67.421	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43386	target_addr:172.67.168.140:443
time:2026-09-28T08:38:36Z	status:FAILURE	latency:199.267	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:716.816	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:743.905	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:1069.292	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47464	target_addr:104.18.40.152:443
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:1749.623	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:38:36Z	status:HEALTHY	latency:1755.347	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:43:36Z	status:UNKNOWN	latency:8.817	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:67.620	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58070	target_addr:172.67.219.211:443
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:67.029	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58084	target_addr:172.67.219.211:443
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:68.400	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47410	target_addr:172.67.168.140:443
time:2026-09-28T08:43:36Z	status:FAILURE	latency:442.314	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:619.815	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:623.293	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:629.536	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:1101.344	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34078	target_addr:104.18.40.152:443
time:2026-09-28T08:43:36Z	status:HEALTHY	latency:1820.000	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:48:36Z	status:UNKNOWN	latency:6.055	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:68.678	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33610	target_addr:104.21.26.208:443
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:69.705	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57676	target_addr:104.21.86.125:443
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:102.197	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57682	target_addr:104.21.86.125:443
time:2026-09-28T08:48:36Z	status:FAILURE	latency:503.877	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:652.114	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:701.761	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:714.451	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:1095.635	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56126	target_addr:104.18.40.152:443
time:2026-09-28T08:48:36Z	status:HEALTHY	latency:1767.216	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:53:36Z	status:UNKNOWN	latency:8.853	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:67.566	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56414	target_addr:104.21.86.125:443
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:68.484	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54906	target_addr:104.21.26.208:443
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:68.419	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45830	target_addr:172.67.219.211:443
time:2026-09-28T08:53:36Z	status:FAILURE	latency:197.942	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:636.893	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:642.009	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:668.228	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:1075.139	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51860	target_addr:104.18.40.152:443
time:2026-09-28T08:53:36Z	status:HEALTHY	latency:1778.970	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:67.124	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59058	target_addr:172.67.219.211:443
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:67.249	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59046	target_addr:172.67.219.211:443
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:71.966	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46026	target_addr:172.67.168.140:443
time:2026-09-28T08:58:37Z	status:UNKNOWN	latency:73.210	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:640.722	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:648.855	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:651.531	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:1069.800	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59944	target_addr:104.18.40.152:443
time:2026-09-28T08:58:37Z	status:FAILURE	latency:1312.717	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T08:58:37Z	status:HEALTHY	latency:1799.452	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:03:37Z	status:UNKNOWN	latency:38.715	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:69.042	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54986	target_addr:104.21.86.125:443
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:69.686	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54972	target_addr:104.21.86.125:443
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:69.639	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58320	target_addr:172.67.168.140:443
time:2026-09-28T09:03:37Z	status:FAILURE	latency:197.473	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:617.949	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:619.893	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:632.329	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:1069.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41578	target_addr:104.18.40.152:443
time:2026-09-28T09:03:37Z	status:HEALTHY	latency:1775.487	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:08:37Z	status:UNKNOWN	latency:7.186	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:67.517	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33814	target_addr:172.67.168.140:443
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:69.688	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52862	target_addr:172.67.219.211:443
time:2026-09-28T09:08:37Z	status:FAILURE	latency:553.519	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:637.976	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:697.755	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:770.434	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:1082.037	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55834	target_addr:172.64.147.104:443
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:1098.932	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52852	target_addr:172.67.219.211:443
time:2026-09-28T09:08:37Z	status:HEALTHY	latency:1832.878	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:13:37Z	status:UNKNOWN	latency:7.756	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:69.586	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50462	target_addr:104.21.86.125:443
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:70.363	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50450	target_addr:104.21.86.125:443
time:2026-09-28T09:13:37Z	status:FAILURE	latency:203.808	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:650.713	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:747.308	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:752.543	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:1082.504	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56198	target_addr:172.64.147.104:443
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:1083.588	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41598	target_addr:104.21.26.208:443
time:2026-09-28T09:13:37Z	status:HEALTHY	latency:1676.517	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:18:37Z	status:UNKNOWN	latency:37.273	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:67.929	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46888	target_addr:172.67.168.140:443
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:71.215	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52668	target_addr:104.21.86.125:443
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:81.898	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39232	target_addr:172.67.219.211:443
time:2026-09-28T09:18:37Z	status:FAILURE	latency:358.060	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:638.803	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:691.064	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:693.125	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:1073.752	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36204	target_addr:104.18.40.152:443
time:2026-09-28T09:18:37Z	status:HEALTHY	latency:1751.418	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:23:37Z	status:UNKNOWN	latency:6.450	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:67.949	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40798	target_addr:104.21.26.208:443
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:67.610	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36338	target_addr:172.67.219.211:443
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:68.121	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45596	target_addr:104.21.86.125:443
time:2026-09-28T09:23:37Z	status:FAILURE	latency:477.778	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:694.094	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:700.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:1080.801	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55350	target_addr:104.18.40.152:443
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:1715.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:23:37Z	status:HEALTHY	latency:2003.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:28:37Z	status:UNKNOWN	latency:8.305	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:68.465	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44970	target_addr:172.67.219.211:443
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:69.438	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46464	target_addr:104.21.26.208:443
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:71.295	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44980	target_addr:172.67.219.211:443
time:2026-09-28T09:28:37Z	status:FAILURE	latency:193.916	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:616.674	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:650.834	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:654.482	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:1080.150	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34138	target_addr:104.18.40.152:443
time:2026-09-28T09:28:37Z	status:HEALTHY	latency:1775.683	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:33:37Z	status:UNKNOWN	latency:11.795	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:68.205	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56108	target_addr:104.21.86.125:443
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:68.693	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56100	target_addr:104.21.86.125:443
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:69.055	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42330	target_addr:172.67.168.140:443
time:2026-09-28T09:33:37Z	status:FAILURE	latency:363.589	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:648.622	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:650.249	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:959.389	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:1080.318	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51254	target_addr:172.64.147.104:443
time:2026-09-28T09:33:37Z	status:HEALTHY	latency:1756.097	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:38:37Z	status:UNKNOWN	latency:7.636	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:68.074	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49112	target_addr:104.21.26.208:443
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:68.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44280	target_addr:172.67.219.211:443
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:69.681	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42406	target_addr:104.21.86.125:443
time:2026-09-28T09:38:37Z	status:FAILURE	latency:197.699	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:644.672	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:678.710	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:940.619	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:1086.683	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48166	target_addr:104.18.40.152:443
time:2026-09-28T09:38:37Z	status:HEALTHY	latency:1492.735	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:43:37Z	status:UNKNOWN	latency:8.007	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:66.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59470	target_addr:104.21.26.208:443
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:67.847	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53698	target_addr:172.67.219.211:443
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:67.656	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53434	target_addr:104.21.86.125:443
time:2026-09-28T09:43:37Z	status:FAILURE	latency:358.547	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:703.954	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:706.360	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:716.508	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:1093.474	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60122	target_addr:172.64.147.104:443
time:2026-09-28T09:43:37Z	status:HEALTHY	latency:1756.693	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:48:37Z	status:UNKNOWN	latency:33.322	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:67.330	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57376	target_addr:172.67.219.211:443
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:68.595	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52638	target_addr:104.21.26.208:443
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:69.339	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36458	target_addr:104.21.86.125:443
time:2026-09-28T09:48:37Z	status:FAILURE	latency:196.761	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:632.530	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:667.580	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:709.563	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:730.045	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:48:37Z	status:HEALTHY	latency:1093.369	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60228	target_addr:172.64.147.104:443
time:2026-09-28T09:53:37Z	status:UNKNOWN	latency:7.843	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:67.193	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48420	target_addr:172.67.219.211:443
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:67.176	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45318	target_addr:172.67.168.140:443
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:67.438	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54656	target_addr:104.21.86.125:443
time:2026-09-28T09:53:37Z	status:FAILURE	latency:468.682	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:692.556	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:703.681	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:1076.309	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58136	target_addr:172.64.147.104:443
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:1107.368	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:53:37Z	status:HEALTHY	latency:1814.224	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:58:37Z	status:UNKNOWN	latency:8.061	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:68.022	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35718	target_addr:172.67.219.211:443
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:68.688	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35732	target_addr:172.67.219.211:443
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:69.514	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55630	target_addr:104.21.26.208:443
time:2026-09-28T09:58:37Z	status:FAILURE	latency:435.264	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:596.861	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:927.203	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:1011.743	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:1067.926	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59706	target_addr:172.64.147.104:443
time:2026-09-28T09:58:37Z	status:HEALTHY	latency:1765.420	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:03:37Z	status:UNKNOWN	latency:7.100	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:67.510	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49234	target_addr:172.67.219.211:443
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:72.920	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49218	target_addr:172.67.219.211:443
time:2026-09-28T10:03:37Z	status:FAILURE	latency:205.031	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:642.357	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:713.820	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:775.824	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:1068.095	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56488	target_addr:172.64.147.104:443
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:1070.473	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59326	target_addr:104.21.26.208:443
time:2026-09-28T10:03:37Z	status:HEALTHY	latency:1788.640	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:08:37Z	status:UNKNOWN	latency:7.789	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:67.279	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34350	target_addr:172.67.219.211:443
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:69.318	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40308	target_addr:172.67.168.140:443
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:74.027	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34364	target_addr:172.67.219.211:443
time:2026-09-28T10:08:37Z	status:FAILURE	latency:466.993	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:655.710	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:710.059	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:1008.184	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:1072.141	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42120	target_addr:104.18.40.152:443
time:2026-09-28T10:08:37Z	status:HEALTHY	latency:1780.862	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:13:37Z	status:UNKNOWN	latency:36.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:66.425	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60628	target_addr:104.21.86.125:443
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:67.302	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60644	target_addr:104.21.86.125:443
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:67.848	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35312	target_addr:104.21.26.208:443
time:2026-09-28T10:13:37Z	status:FAILURE	latency:336.828	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:651.598	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:705.375	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:711.290	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:1067.304	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59160	target_addr:104.18.40.152:443
time:2026-09-28T10:13:37Z	status:HEALTHY	latency:1770.780	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:18:37Z	status:UNKNOWN	latency:34.305	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:68.186	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57662	target_addr:172.67.219.211:443
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:68.971	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36972	target_addr:104.21.26.208:443
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:68.862	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58138	target_addr:104.21.86.125:443
time:2026-09-28T10:18:37Z	status:FAILURE	latency:349.735	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:689.025	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:695.197	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:747.462	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:1081.920	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60694	target_addr:104.18.40.152:443
time:2026-09-28T10:18:37Z	status:HEALTHY	latency:1818.712	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:23:37Z	status:UNKNOWN	latency:7.843	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:23:37Z	status:FAILURE	latency:419.503	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1092.167	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44374	target_addr:172.64.147.104:443
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1094.388	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60646	target_addr:104.21.26.208:443
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1094.484	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38842	target_addr:172.67.219.211:443
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1095.372	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53570	target_addr:104.21.86.125:443
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1670.911	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1781.634	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1783.170	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:23:37Z	status:HEALTHY	latency:1833.334	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:28:37Z	status:UNKNOWN	latency:8.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:67.731	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53060	target_addr:104.21.86.125:443
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:69.901	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56532	target_addr:172.67.219.211:443
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:71.926	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42670	target_addr:172.67.168.140:443
time:2026-09-28T10:28:37Z	status:FAILURE	latency:348.166	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:670.485	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:685.060	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:685.713	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:1091.693	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51658	target_addr:104.18.40.152:443
time:2026-09-28T10:28:37Z	status:HEALTHY	latency:1754.391	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:33:37Z	status:UNKNOWN	latency:11.682	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:72.021	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58598	target_addr:172.67.168.140:443
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:73.075	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54244	target_addr:172.67.219.211:443
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:73.164	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54260	target_addr:172.67.219.211:443
time:2026-09-28T10:33:37Z	status:FAILURE	latency:489.061	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:722.501	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:724.839	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:726.050	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:1069.768	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48082	target_addr:172.64.147.104:443
time:2026-09-28T10:33:37Z	status:HEALTHY	latency:1737.690	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:38:37Z	status:UNKNOWN	latency:6.678	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:67.447	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57194	target_addr:172.67.219.211:443
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:66.980	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57196	target_addr:172.67.219.211:443
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:67.492	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35228	target_addr:104.21.26.208:443
time:2026-09-28T10:38:37Z	status:FAILURE	latency:345.291	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:658.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:747.738	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:784.159	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:1066.029	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43690	target_addr:172.64.147.104:443
time:2026-09-28T10:38:37Z	status:HEALTHY	latency:1743.454	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:43:37Z	status:UNKNOWN	latency:7.527	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:66.149	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50078	target_addr:172.67.219.211:443
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:67.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38806	target_addr:104.21.26.208:443
time:2026-09-28T10:43:37Z	status:FAILURE	latency:201.005	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:1065.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33570	target_addr:172.64.147.104:443
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:1099.731	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50092	target_addr:172.67.219.211:443
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:1191.329	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:1663.567	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:1805.462	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:43:37Z	status:HEALTHY	latency:2112.659	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:48:37Z	status:UNKNOWN	latency:7.682	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:65.922	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49680	target_addr:172.67.219.211:443
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:70.507	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56788	target_addr:172.67.168.140:443
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:80.749	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49686	target_addr:172.67.219.211:443
time:2026-09-28T10:48:37Z	status:FAILURE	latency:528.227	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:695.111	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:765.070	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:776.571	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:1066.882	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47738	target_addr:172.64.147.104:443
time:2026-09-28T10:48:37Z	status:HEALTHY	latency:1746.747	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:53:37Z	status:UNKNOWN	latency:6.271	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:66.153	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39130	target_addr:104.21.86.125:443
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:67.334	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39144	target_addr:104.21.86.125:443
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:68.759	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51074	target_addr:104.21.26.208:443
time:2026-09-28T10:53:37Z	status:FAILURE	latency:485.887	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:618.062	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:647.331	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:650.913	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:1070.087	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58342	target_addr:172.64.147.104:443
time:2026-09-28T10:53:37Z	status:HEALTHY	latency:1812.007	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:58:37Z	status:UNKNOWN	latency:14.548	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:65.715	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33192	target_addr:104.21.86.125:443
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:66.784	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40190	target_addr:172.67.168.140:443
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:68.590	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48216	target_addr:172.67.219.211:443
time:2026-09-28T10:58:37Z	status:FAILURE	latency:455.801	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:697.989	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:700.527	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:701.694	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:1068.753	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51366	target_addr:104.18.40.152:443
time:2026-09-28T10:58:37Z	status:HEALTHY	latency:1791.267	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:03:37Z	status:UNKNOWN	latency:32.378	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:66.900	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58832	target_addr:104.21.86.125:443
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:67.851	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41516	target_addr:104.21.26.208:443
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:68.758	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58838	target_addr:104.21.86.125:443
time:2026-09-28T11:03:37Z	status:FAILURE	latency:194.631	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:693.861	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:705.316	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:1068.125	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36712	target_addr:172.64.147.104:443
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:1090.965	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:03:37Z	status:HEALTHY	latency:1758.071	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:08:37Z	status:UNKNOWN	latency:44.135	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:66.149	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40760	target_addr:104.21.86.125:443
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:66.438	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33658	target_addr:172.67.219.211:443
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:69.830	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45788	target_addr:172.67.168.140:443
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:695.882	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:698.922	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:735.009	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:751.812	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:08:37Z	status:HEALTHY	latency:1068.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60500	target_addr:104.18.40.152:443
time:2026-09-28T11:08:37Z	status:FAILURE	latency:1449.366	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:13:37Z	status:UNKNOWN	latency:7.464	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:66.858	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54800	target_addr:104.21.86.125:443
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:67.744	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51132	target_addr:172.67.219.211:443
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:67.610	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43338	target_addr:172.67.168.140:443
time:2026-09-28T11:13:37Z	status:FAILURE	latency:200.607	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:700.745	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:706.666	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:706.629	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:1068.375	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54266	target_addr:172.64.147.104:443
time:2026-09-28T11:13:37Z	status:HEALTHY	latency:1789.235	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:18:37Z	status:UNKNOWN	latency:7.040	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:66.351	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59688	target_addr:104.21.86.125:443
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:68.403	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39138	target_addr:104.21.26.208:443
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:68.674	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53142	target_addr:172.67.219.211:443
time:2026-09-28T11:18:37Z	status:FAILURE	latency:322.168	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:671.569	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:695.694	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:715.231	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:1078.558	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50628	target_addr:172.64.147.104:443
time:2026-09-28T11:18:37Z	status:HEALTHY	latency:1794.915	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:23:37Z	status:UNKNOWN	latency:35.311	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:67.195	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49114	target_addr:104.21.86.125:443
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:69.330	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48838	target_addr:104.21.26.208:443
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:71.629	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49122	target_addr:104.21.86.125:443
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:650.160	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:743.512	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:745.986	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:1074.167	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33494	target_addr:172.64.147.104:443
time:2026-09-28T11:23:37Z	status:FAILURE	latency:1457.888	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:23:37Z	status:HEALTHY	latency:1781.182	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:28:37Z	status:UNKNOWN	latency:7.177	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:65.637	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38064	target_addr:104.21.26.208:443
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:68.967	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36746	target_addr:104.21.86.125:443
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:71.889	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36748	target_addr:104.21.86.125:443
time:2026-09-28T11:28:37Z	status:FAILURE	latency:465.729	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:620.909	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:918.538	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:923.350	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:1078.972	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37946	target_addr:104.18.40.152:443
time:2026-09-28T11:28:37Z	status:HEALTHY	latency:1773.982	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:33:37Z	status:UNKNOWN	latency:12.084	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:73.283	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56706	target_addr:172.67.219.211:443
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:73.792	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44496	target_addr:104.21.86.125:443
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:75.838	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32996	target_addr:104.21.26.208:443
time:2026-09-28T11:33:37Z	status:FAILURE	latency:483.716	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:646.277	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:697.236	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:712.226	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:1094.464	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57828	target_addr:104.18.40.152:443
time:2026-09-28T11:33:37Z	status:HEALTHY	latency:1794.648	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:38:37Z	status:UNKNOWN	latency:7.847	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:67.879	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60118	target_addr:104.21.86.125:443
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:67.975	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50282	target_addr:172.67.219.211:443
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:69.252	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50108	target_addr:104.21.26.208:443
time:2026-09-28T11:38:37Z	status:FAILURE	latency:356.591	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:696.067	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:743.967	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:991.952	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:1074.411	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35294	target_addr:104.18.40.152:443
time:2026-09-28T11:38:37Z	status:HEALTHY	latency:1741.183	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:43:37Z	status:UNKNOWN	latency:7.694	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:66.311	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36844	target_addr:104.21.86.125:443
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:67.402	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57944	target_addr:172.67.168.140:443
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:68.232	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36860	target_addr:104.21.86.125:443
time:2026-09-28T11:43:37Z	status:FAILURE	latency:201.484	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:659.525	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:710.901	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:712.235	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:1073.415	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38456	target_addr:104.18.40.152:443
time:2026-09-28T11:43:37Z	status:HEALTHY	latency:1736.088	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:48:37Z	status:UNKNOWN	latency:7.918	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:66.611	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56352	target_addr:104.21.86.125:443
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:66.541	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44388	target_addr:172.67.168.140:443
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:66.968	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56368	target_addr:104.21.86.125:443
time:2026-09-28T11:48:37Z	status:FAILURE	latency:442.690	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:702.354	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:719.302	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:762.083	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:953.199	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:48:37Z	status:HEALTHY	latency:1074.017	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36632	target_addr:172.64.147.104:443
time:2026-09-28T11:53:37Z	status:UNKNOWN	latency:7.887	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:69.411	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41514	target_addr:172.67.219.211:443
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:69.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55794	target_addr:104.21.26.208:443
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:69.748	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41518	target_addr:172.67.219.211:443
time:2026-09-28T11:53:37Z	status:FAILURE	latency:202.336	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:706.257	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:711.136	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:742.525	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:1085.568	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47296	target_addr:104.18.40.152:443
time:2026-09-28T11:53:37Z	status:HEALTHY	latency:1618.438	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:58:37Z	status:UNKNOWN	latency:30.933	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:66.702	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35382	target_addr:172.67.219.211:443
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:67.060	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49712	target_addr:104.21.26.208:443
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:67.789	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34960	target_addr:104.21.86.125:443
time:2026-09-28T11:58:37Z	status:FAILURE	latency:473.780	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:647.842	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:696.907	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:897.975	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:1065.449	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37778	target_addr:172.64.147.104:443
time:2026-09-28T11:58:37Z	status:HEALTHY	latency:1748.957	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:03:37Z	status:UNKNOWN	latency:6.807	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:66.348	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55812	target_addr:172.67.219.211:443
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:71.685	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34422	target_addr:104.21.26.208:443
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:73.688	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42320	target_addr:104.21.86.125:443
time:2026-09-28T12:03:37Z	status:FAILURE	latency:202.113	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:713.757	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:717.928	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:737.010	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:1074.818	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39262	target_addr:172.64.147.104:443
time:2026-09-28T12:03:37Z	status:HEALTHY	latency:1743.830	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:08:37Z	status:UNKNOWN	latency:6.460	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:68.451	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50028	target_addr:172.67.219.211:443
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:68.895	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50032	target_addr:172.67.219.211:443
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:75.403	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38038	target_addr:104.21.26.208:443
time:2026-09-28T12:08:37Z	status:FAILURE	latency:408.183	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:693.240	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:704.331	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:726.564	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:1073.368	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58956	target_addr:104.18.40.152:443
time:2026-09-28T12:08:37Z	status:HEALTHY	latency:2789.658	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:13:37Z	status:UNKNOWN	latency:8.238	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:65.391	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40398	target_addr:172.67.168.140:443
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:67.691	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44958	target_addr:172.67.219.211:443
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:68.857	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48528	target_addr:104.21.86.125:443
time:2026-09-28T12:13:37Z	status:FAILURE	latency:196.869	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:609.451	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:626.415	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:636.808	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:1105.211	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55396	target_addr:104.18.40.152:443
time:2026-09-28T12:13:37Z	status:HEALTHY	latency:1741.509	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:18:37Z	status:UNKNOWN	latency:37.974	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:67.219	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57108	target_addr:104.21.26.208:443
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:67.308	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39198	target_addr:104.21.86.125:443
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:68.036	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49764	target_addr:172.67.219.211:443
time:2026-09-28T12:18:37Z	status:FAILURE	latency:315.852	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:709.155	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:746.554	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:755.923	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:1073.042	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58002	target_addr:104.18.40.152:443
time:2026-09-28T12:18:37Z	status:HEALTHY	latency:1696.127	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:23:37Z	status:UNKNOWN	latency:39.244	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:65.759	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49204	target_addr:172.64.147.104:443
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:66.227	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48738	target_addr:172.67.219.211:443
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:67.782	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45566	target_addr:104.21.26.208:443
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:69.107	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56110	target_addr:104.21.86.125:443
time:2026-09-28T12:23:37Z	status:FAILURE	latency:208.244	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:630.513	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:646.087	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:928.526	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:23:37Z	status:HEALTHY	latency:1770.697	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:28:37Z	status:UNKNOWN	latency:34.967	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:64.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57808	target_addr:172.67.168.140:443
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:65.489	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38402	target_addr:172.67.219.211:443
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:66.947	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38412	target_addr:172.67.219.211:443
time:2026-09-28T12:28:37Z	status:FAILURE	latency:345.702	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:1007.493	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:1015.576	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:1017.705	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:1071.301	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46414	target_addr:172.64.147.104:443
time:2026-09-28T12:28:37Z	status:HEALTHY	latency:1797.341	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:33:37Z	status:UNKNOWN	latency:9.246	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:66.667	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55012	target_addr:104.21.86.125:443
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:69.005	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41396	target_addr:172.67.219.211:443
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:69.592	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43716	target_addr:104.21.26.208:443
time:2026-09-28T12:33:37Z	status:FAILURE	latency:381.077	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:632.396	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:648.052	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:844.960	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:1081.155	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36278	target_addr:104.18.40.152:443
time:2026-09-28T12:33:37Z	status:HEALTHY	latency:1480.545	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:38:37Z	status:UNKNOWN	latency:9.239	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:67.647	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42134	target_addr:104.21.86.125:443
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:71.122	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39206	target_addr:172.67.168.140:443
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:74.739	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34710	target_addr:172.67.219.211:443
time:2026-09-28T12:38:37Z	status:FAILURE	latency:379.150	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:716.344	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:718.318	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:1008.592	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:1072.740	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41192	target_addr:104.18.40.152:443
time:2026-09-28T12:38:37Z	status:HEALTHY	latency:1767.457	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:43:37Z	status:UNKNOWN	latency:7.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:67.871	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59498	target_addr:172.67.219.211:443
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:68.373	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59514	target_addr:172.67.219.211:443
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:69.335	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59116	target_addr:104.21.26.208:443
time:2026-09-28T12:43:37Z	status:FAILURE	latency:208.069	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:631.615	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:638.099	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:657.255	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:1077.326	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34720	target_addr:172.64.147.104:443
time:2026-09-28T12:43:37Z	status:HEALTHY	latency:1781.648	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:48:37Z	status:UNKNOWN	latency:7.407	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:65.140	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38398	target_addr:172.67.219.211:443
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:66.566	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36410	target_addr:172.67.168.140:443
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:68.102	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38400	target_addr:172.67.219.211:443
time:2026-09-28T12:48:37Z	status:FAILURE	latency:370.314	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:729.081	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:735.744	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:738.439	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:1080.723	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58388	target_addr:104.18.40.152:443
time:2026-09-28T12:48:37Z	status:HEALTHY	latency:1755.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:53:37Z	status:UNKNOWN	latency:36.757	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:66.915	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37718	target_addr:104.21.86.125:443
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:67.459	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36986	target_addr:172.67.168.140:443
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:69.413	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37732	target_addr:104.21.86.125:443
time:2026-09-28T12:53:37Z	status:FAILURE	latency:198.481	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:741.500	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:758.378	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:1028.541	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:1079.966	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43690	target_addr:104.18.40.152:443
time:2026-09-28T12:53:37Z	status:HEALTHY	latency:1562.475	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:58:37Z	status:UNKNOWN	latency:7.622	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:69.446	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36454	target_addr:104.21.86.125:443
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:69.920	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37286	target_addr:172.67.168.140:443
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:69.514	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39494	target_addr:172.67.219.211:443
time:2026-09-28T12:58:37Z	status:FAILURE	latency:520.518	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:729.063	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:739.084	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:748.256	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:1079.806	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60592	target_addr:172.64.147.104:443
time:2026-09-28T12:58:37Z	status:HEALTHY	latency:1749.237	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:03:37Z	status:UNKNOWN	latency:6.068	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:66.056	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37840	target_addr:172.67.219.211:443
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:66.373	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47712	target_addr:104.21.26.208:443
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:68.488	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52544	target_addr:104.21.86.125:443
time:2026-09-28T13:03:37Z	status:FAILURE	latency:205.166	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:633.483	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:656.514	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:955.094	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:1069.211	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51916	target_addr:172.64.147.104:443
time:2026-09-28T13:03:37Z	status:HEALTHY	latency:1641.787	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:08:37Z	status:UNKNOWN	latency:7.685	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:65.656	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51168	target_addr:172.67.219.211:443
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:65.799	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51176	target_addr:172.67.219.211:443
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:66.578	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34584	target_addr:104.21.26.208:443
time:2026-09-28T13:08:37Z	status:FAILURE	latency:371.378	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:830.349	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:1047.335	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:1069.242	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41076	target_addr:172.64.147.104:443
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:1530.362	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:08:37Z	status:HEALTHY	latency:1794.821	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:13:37Z	status:UNKNOWN	latency:6.976	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:68.117	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44596	target_addr:104.21.86.125:443
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:68.155	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44606	target_addr:104.21.86.125:443
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:70.025	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56920	target_addr:104.21.26.208:443
time:2026-09-28T13:13:37Z	status:FAILURE	latency:345.930	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:681.737	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:711.782	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:1014.953	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:1068.242	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37476	target_addr:104.18.40.152:443
time:2026-09-28T13:13:37Z	status:HEALTHY	latency:1763.016	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:18:37Z	status:UNKNOWN	latency:6.070	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:67.577	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43176	target_addr:104.21.26.208:443
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:68.008	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45386	target_addr:172.67.219.211:443
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:68.763	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38654	target_addr:104.21.86.125:443
time:2026-09-28T13:18:37Z	status:FAILURE	latency:384.724	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:771.116	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:778.161	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:803.580	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:1085.295	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39456	target_addr:104.18.40.152:443
time:2026-09-28T13:18:37Z	status:HEALTHY	latency:1771.064	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:23:37Z	status:UNKNOWN	latency:7.310	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:65.325	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39108	target_addr:104.21.86.125:443
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:66.545	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46064	target_addr:172.67.168.140:443
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:171.904	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39118	target_addr:104.21.86.125:443
time:2026-09-28T13:23:37Z	status:FAILURE	latency:503.818	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:712.714	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:1018.766	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:1083.860	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36648	target_addr:172.64.147.104:443
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:1088.081	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:23:37Z	status:HEALTHY	latency:2650.841	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:28:37Z	status:UNKNOWN	latency:7.961	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:65.953	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50198	target_addr:172.67.219.211:443
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:66.977	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44898	target_addr:172.67.168.140:443
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:67.459	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53686	target_addr:104.21.86.125:443
time:2026-09-28T13:28:37Z	status:FAILURE	latency:218.523	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:980.256	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:993.979	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:1067.809	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57214	target_addr:172.64.147.104:443
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:1144.926	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:28:37Z	status:HEALTHY	latency:1614.800	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:33:37Z	status:UNKNOWN	latency:7.969	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:66.680	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40800	target_addr:172.67.219.211:443
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:68.557	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43442	target_addr:172.67.168.140:443
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:71.022	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36576	target_addr:104.21.86.125:443
time:2026-09-28T13:33:37Z	status:FAILURE	latency:365.136	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:665.847	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:685.362	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:715.148	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:1091.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60766	target_addr:104.18.40.152:443
time:2026-09-28T13:33:37Z	status:HEALTHY	latency:1728.089	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:38:37Z	status:UNKNOWN	latency:8.348	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:65.937	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39246	target_addr:172.67.219.211:443
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:66.111	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55338	target_addr:104.21.26.208:443
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:67.364	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39234	target_addr:172.67.219.211:443
time:2026-09-28T13:38:37Z	status:FAILURE	latency:402.401	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:732.910	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:736.892	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:1077.769	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48564	target_addr:172.64.147.104:443
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:1533.536	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:38:37Z	status:HEALTHY	latency:5702.899	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:43:38Z	status:UNKNOWN	latency:7.035	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:66.885	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48662	target_addr:104.21.86.125:443
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:68.739	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47570	target_addr:104.21.26.208:443
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:79.578	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48650	target_addr:104.21.86.125:443
time:2026-09-28T13:43:38Z	status:FAILURE	latency:408.956	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:641.226	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:675.494	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:1073.056	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46122	target_addr:104.18.40.152:443
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:1284.074	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:43:38Z	status:HEALTHY	latency:1903.894	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:48:38Z	status:UNKNOWN	latency:6.866	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:67.429	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48592	target_addr:104.21.26.208:443
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:71.008	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48562	target_addr:172.67.219.211:443
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:73.132	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34090	target_addr:104.21.86.125:443
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:727.097	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:787.836	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:1080.244	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33214	target_addr:172.64.147.104:443
time:2026-09-28T13:48:38Z	status:FAILURE	latency:1357.422	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:1738.834	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:48:38Z	status:HEALTHY	latency:2115.693	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:68.811	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48500	target_addr:104.21.86.125:443
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:68.621	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39028	target_addr:104.21.26.208:443
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:86.726	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52468	target_addr:172.67.219.211:443
time:2026-09-28T13:53:38Z	status:UNKNOWN	latency:113.642	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:53:38Z	status:FAILURE	latency:467.025	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:706.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:722.998	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:730.739	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:1080.699	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47038	target_addr:172.64.147.104:443
time:2026-09-28T13:53:38Z	status:HEALTHY	latency:1824.658	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:58:38Z	status:UNKNOWN	latency:43.244	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:72.374	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60868	target_addr:172.67.219.211:443
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:73.017	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52756	target_addr:104.21.26.208:443
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:79.906	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39154	target_addr:104.21.86.125:443
time:2026-09-28T13:58:38Z	status:FAILURE	latency:367.455	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:714.589	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:717.085	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:757.936	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:1076.088	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42372	target_addr:104.18.40.152:443
time:2026-09-28T13:58:38Z	status:HEALTHY	latency:1825.353	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:03:38Z	status:UNKNOWN	latency:8.483	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:72.848	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41888	target_addr:172.67.168.140:443
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:72.952	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52946	target_addr:172.67.219.211:443
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:76.042	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52954	target_addr:172.67.219.211:443
time:2026-09-28T14:03:38Z	status:FAILURE	latency:500.586	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:616.685	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:666.367	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:686.538	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:1075.943	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52116	target_addr:104.18.40.152:443
time:2026-09-28T14:03:38Z	status:HEALTHY	latency:1798.863	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:08:38Z	status:UNKNOWN	latency:36.618	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:68.872	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43988	target_addr:104.21.86.125:443
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:74.385	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43996	target_addr:104.21.86.125:443
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:74.971	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42720	target_addr:104.21.26.208:443
time:2026-09-28T14:08:38Z	status:FAILURE	latency:225.555	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:627.425	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:647.390	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:673.854	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:1085.302	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53724	target_addr:172.64.147.104:443
time:2026-09-28T14:08:38Z	status:HEALTHY	latency:1863.364	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:13:38Z	status:UNKNOWN	latency:38.773	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:71.980	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41688	target_addr:104.21.26.208:443
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:73.047	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59730	target_addr:172.67.219.211:443
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:75.502	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59734	target_addr:172.67.219.211:443
time:2026-09-28T14:13:38Z	status:FAILURE	latency:495.210	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:728.697	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:795.430	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:1073.172	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41224	target_addr:172.64.147.104:443
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:1094.246	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:13:38Z	status:HEALTHY	latency:1806.964	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:18:38Z	status:UNKNOWN	latency:16.584	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:80.170	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38068	target_addr:172.67.219.211:443
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:82.700	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38062	target_addr:172.67.219.211:443
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:83.075	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49044	target_addr:172.67.168.140:443
time:2026-09-28T14:18:38Z	status:FAILURE	latency:223.262	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:709.730	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:763.863	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:951.660	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:1104.860	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51252	target_addr:104.18.40.152:443
time:2026-09-28T14:18:38Z	status:HEALTHY	latency:1448.614	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:23:38Z	status:UNKNOWN	latency:34.293	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:70.166	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34024	target_addr:104.21.26.208:443
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:73.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40706	target_addr:172.67.219.211:443
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:422.698	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40718	target_addr:172.67.219.211:443
time:2026-09-28T14:23:38Z	status:FAILURE	latency:529.666	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:652.590	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:686.207	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:695.536	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:1072.748	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47666	target_addr:104.18.40.152:443
time:2026-09-28T14:23:38Z	status:HEALTHY	latency:1623.897	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:28:38Z	status:UNKNOWN	latency:25.049	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:90.305	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57502	target_addr:104.21.86.125:443
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:93.179	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52166	target_addr:172.67.219.211:443
time:2026-09-28T14:28:38Z	status:FAILURE	latency:218.759	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:877.348	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:1077.381	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39698	target_addr:172.64.147.104:443
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:1088.801	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46646	target_addr:172.67.168.140:443
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:1633.504	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:1812.515	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:28:38Z	status:HEALTHY	latency:2092.402	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:33:38Z	status:UNKNOWN	latency:34.020	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:68.080	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43756	target_addr:172.67.219.211:443
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:70.510	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40896	target_addr:172.67.168.140:443
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:71.504	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60618	target_addr:104.21.86.125:443
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:661.343	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:677.755	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:682.706	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:1081.129	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39396	target_addr:172.64.147.104:443
time:2026-09-28T14:33:38Z	status:FAILURE	latency:1289.021	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:33:38Z	status:HEALTHY	latency:1765.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:38:38Z	status:UNKNOWN	latency:37.347	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:82.053	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51392	target_addr:172.67.219.211:443
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:89.096	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41352	target_addr:104.21.26.208:443
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:154.045	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51380	target_addr:172.67.219.211:443
time:2026-09-28T14:38:38Z	status:FAILURE	latency:463.210	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:784.766	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:816.273	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:1093.247	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56266	target_addr:104.18.40.152:443
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:1265.603	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:38:38Z	status:HEALTHY	latency:1746.957	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:43:38Z	status:UNKNOWN	latency:6.952	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:80.320	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49274	target_addr:104.21.26.208:443
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:83.986	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39776	target_addr:104.21.86.125:443
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:155.450	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49968	target_addr:172.67.219.211:443
time:2026-09-28T14:43:38Z	status:FAILURE	latency:687.709	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:801.463	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:1054.428	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:1069.050	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58522	target_addr:172.64.147.104:443
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:1240.280	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:43:38Z	status:HEALTHY	latency:1697.818	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:48:38Z	status:UNKNOWN	latency:8.234	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:71.729	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37878	target_addr:104.21.86.125:443
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:89.229	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51986	target_addr:172.67.168.140:443
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:99.033	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37870	target_addr:104.21.86.125:443
time:2026-09-28T14:48:38Z	status:FAILURE	latency:449.164	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:1069.711	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39008	target_addr:172.64.147.104:443
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:1734.916	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:6023.153	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:6029.586	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:48:38Z	status:HEALTHY	latency:6078.730	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:53:38Z	status:UNKNOWN	latency:7.525	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:84.769	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60688	target_addr:172.67.219.211:443
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:90.977	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57464	target_addr:104.21.26.208:443
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:155.435	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41650	target_addr:104.21.86.125:443
time:2026-09-28T14:53:38Z	status:FAILURE	latency:255.302	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:715.306	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:807.825	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:1083.343	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54524	target_addr:104.18.40.152:443
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:1098.344	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:53:38Z	status:HEALTHY	latency:1917.314	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:58:38Z	status:UNKNOWN	latency:7.351	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:68.624	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57094	target_addr:172.67.219.211:443
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:72.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39536	target_addr:172.67.168.140:443
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:77.021	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52362	target_addr:104.21.86.125:443
time:2026-09-28T14:58:38Z	status:FAILURE	latency:467.287	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:762.564	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:801.145	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:1082.942	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45358	target_addr:104.18.40.152:443
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:1083.640	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T14:58:38Z	status:HEALTHY	latency:1743.573	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:03:38Z	status:UNKNOWN	latency:38.715	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:73.378	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41910	target_addr:104.21.86.125:443
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:76.102	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41922	target_addr:104.21.86.125:443
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:84.041	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33016	target_addr:104.21.26.208:443
time:2026-09-28T15:03:38Z	status:FAILURE	latency:537.607	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:867.660	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:982.774	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:1075.220	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54400	target_addr:172.64.147.104:443
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:1247.707	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:03:38Z	status:HEALTHY	latency:2184.382	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:08:38Z	status:UNKNOWN	latency:7.520	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:71.899	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58672	target_addr:104.21.26.208:443
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:99.935	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53358	target_addr:172.67.219.211:443
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:167.458	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53344	target_addr:172.67.219.211:443
time:2026-09-28T15:08:38Z	status:FAILURE	latency:624.180	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:724.088	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:733.377	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:1178.399	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39378	target_addr:172.64.147.104:443
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:1713.402	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:08:38Z	status:HEALTHY	latency:1767.633	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:13:38Z	status:UNKNOWN	latency:35.803	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:74.948	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59614	target_addr:172.67.219.211:443
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:77.266	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42172	target_addr:104.21.26.208:443
time:2026-09-28T15:13:38Z	status:FAILURE	latency:409.677	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:472.971	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59626	target_addr:172.67.219.211:443
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:667.363	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:682.894	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:763.993	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:1097.107	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32860	target_addr:172.64.147.104:443
time:2026-09-28T15:13:38Z	status:HEALTHY	latency:1756.367	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:18:38Z	status:UNKNOWN	latency:7.115	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:72.368	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59394	target_addr:172.67.168.140:443
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:86.605	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44938	target_addr:104.21.86.125:443
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:422.759	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44952	target_addr:104.21.86.125:443
time:2026-09-28T15:18:38Z	status:FAILURE	latency:663.920	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:727.909	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:742.305	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:1098.002	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60078	target_addr:172.64.147.104:443
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:1105.014	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:18:38Z	status:HEALTHY	latency:1755.165	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:23:38Z	status:UNKNOWN	latency:32.122	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:70.361	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59138	target_addr:104.21.26.208:443
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:73.953	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59024	target_addr:172.67.219.211:443
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:169.200	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59038	target_addr:172.67.219.211:443
time:2026-09-28T15:23:38Z	status:FAILURE	latency:384.337	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:1095.979	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44192	target_addr:104.18.40.152:443
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:1098.458	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:1201.797	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:1602.895	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:23:38Z	status:HEALTHY	latency:1816.191	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:28:38Z	status:UNKNOWN	latency:8.445	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:77.157	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43550	target_addr:172.67.219.211:443
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:88.748	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40028	target_addr:104.21.86.125:443
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:183.098	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35500	target_addr:172.67.168.140:443
time:2026-09-28T15:28:38Z	status:FAILURE	latency:217.859	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:811.846	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:1064.712	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54406	target_addr:172.64.147.104:443
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:1080.434	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:1437.967	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:28:38Z	status:HEALTHY	latency:1754.959	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:33:38Z	status:UNKNOWN	latency:6.284	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:78.273	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52528	target_addr:104.21.86.125:443
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:153.592	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42486	target_addr:172.67.168.140:443
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:169.256	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49068	target_addr:172.67.219.211:443
time:2026-09-28T15:33:38Z	status:FAILURE	latency:443.771	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:1076.967	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58496	target_addr:104.18.40.152:443
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:1078.365	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:1080.996	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:1086.487	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:33:38Z	status:HEALTHY	latency:1766.671	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:38:38Z	status:UNKNOWN	latency:6.926	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:75.205	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49070	target_addr:104.21.26.208:443
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:93.840	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35266	target_addr:172.67.219.211:443
time:2026-09-28T15:38:38Z	status:FAILURE	latency:254.921	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:742.149	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:1083.564	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36018	target_addr:172.64.147.104:443
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:1117.879	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:1125.458	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46432	target_addr:104.21.86.125:443
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:1566.467	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:38:38Z	status:HEALTHY	latency:1581.357	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:43:38Z	status:UNKNOWN	latency:37.326	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:71.837	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52558	target_addr:104.21.26.208:443
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:118.650	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36702	target_addr:172.67.219.211:443
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:172.161	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36696	target_addr:172.67.219.211:443
time:2026-09-28T15:43:38Z	status:FAILURE	latency:399.889	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:708.123	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:1080.284	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43682	target_addr:172.64.147.104:443
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:1146.894	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:1260.057	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:43:38Z	status:HEALTHY	latency:1733.696	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:48:38Z	status:UNKNOWN	latency:7.864	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:89.278	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48790	target_addr:172.67.219.211:443
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:90.295	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47016	target_addr:104.21.26.208:443
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:703.932	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:727.845	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:48:38Z	status:FAILURE	latency:990.880	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:1087.623	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44348	target_addr:104.18.40.152:443
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:1150.179	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:1802.683	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:48:38Z	status:HEALTHY	latency:1880.002	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50924	target_addr:172.67.219.211:443
time:2026-09-28T15:53:38Z	status:UNKNOWN	latency:38.384	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:76.374	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50578	target_addr:104.21.86.125:443
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:88.196	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50562	target_addr:104.21.86.125:443
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:152.325	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56304	target_addr:104.21.26.208:443
time:2026-09-28T15:53:38Z	status:FAILURE	latency:403.538	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:704.748	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:1043.645	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:1078.409	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32816	target_addr:172.64.147.104:443
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:1282.683	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:53:38Z	status:HEALTHY	latency:1806.201	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:58:38Z	status:UNKNOWN	latency:7.692	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:73.296	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57550	target_addr:104.21.86.125:443
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:75.684	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50072	target_addr:172.67.168.140:443
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:87.583	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33672	target_addr:172.67.219.211:443
time:2026-09-28T15:58:38Z	status:FAILURE	latency:465.552	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:769.169	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:865.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:1086.477	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36728	target_addr:104.18.40.152:443
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:1138.250	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T15:58:38Z	status:HEALTHY	latency:1753.267	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:03:38Z	status:UNKNOWN	latency:8.826	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:82.626	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53930	target_addr:104.21.86.125:443
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:160.354	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40288	target_addr:172.67.168.140:443
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:168.637	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60344	target_addr:172.67.219.211:443
time:2026-09-28T16:03:38Z	status:FAILURE	latency:426.773	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:817.852	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:1086.495	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47334	target_addr:104.18.40.152:443
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:1284.470	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:1432.244	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:03:38Z	status:HEALTHY	latency:1779.702	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:85.617	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50138	target_addr:104.21.26.208:443
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:162.021	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59208	target_addr:172.67.219.211:443
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:169.869	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59200	target_addr:172.67.219.211:443
time:2026-09-28T16:08:38Z	status:UNKNOWN	latency:341.039	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:08:38Z	status:FAILURE	latency:619.330	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:1010.724	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:1052.393	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:1053.075	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:1087.590	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48800	target_addr:104.18.40.152:443
time:2026-09-28T16:08:38Z	status:HEALTHY	latency:1724.766	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:13:38Z	status:UNKNOWN	latency:38.479	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:87.774	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42264	target_addr:104.21.26.208:443
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:104.632	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43842	target_addr:104.21.86.125:443
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:106.725	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60716	target_addr:172.67.219.211:443
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:1068.133	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:1088.922	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37360	target_addr:172.64.147.104:443
time:2026-09-28T16:13:38Z	status:FAILURE	latency:1610.972	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:1611.081	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:1749.093	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:13:38Z	status:HEALTHY	latency:4249.535	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:18:38Z	status:UNKNOWN	latency:9.492	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:78.843	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41700	target_addr:172.67.219.211:443
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:131.061	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51554	target_addr:104.21.26.208:443
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:157.988	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41716	target_addr:172.67.219.211:443
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:779.303	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:18:38Z	status:FAILURE	latency:825.336	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:1088.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48338	target_addr:104.18.40.152:443
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:1238.091	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:1678.510	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:18:38Z	status:HEALTHY	latency:2192.659	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:23:38Z	status:UNKNOWN	latency:8.022	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:85.786	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46268	target_addr:104.21.86.125:443
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:126.978	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38922	target_addr:172.67.168.140:443
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:219.267	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58220	target_addr:172.67.219.211:443
time:2026-09-28T16:23:38Z	status:FAILURE	latency:332.139	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:706.934	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:1002.776	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:1362.107	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56268	target_addr:104.18.40.152:443
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:1672.337	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:23:38Z	status:HEALTHY	latency:1755.154	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:28:38Z	status:UNKNOWN	latency:7.159	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:88.496	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46984	target_addr:172.67.219.211:443
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:157.969	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59330	target_addr:172.67.168.140:443
time:2026-09-28T16:28:38Z	status:FAILURE	latency:413.184	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:689.753	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:1057.151	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:1090.631	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40870	target_addr:172.64.147.104:443
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:1285.918	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:1757.180	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:28:38Z	status:HEALTHY	latency:2248.286	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46688	target_addr:104.21.86.125:443
time:2026-09-28T16:33:38Z	status:UNKNOWN	latency:57.398	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:152.688	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32840	target_addr:104.21.86.125:443
time:2026-09-28T16:33:38Z	status:FAILURE	latency:798.723	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:1091.322	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56116	target_addr:172.64.147.104:443
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:1104.189	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55062	target_addr:172.67.219.211:443
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:1108.626	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50428	target_addr:104.21.26.208:443
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:1361.549	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:1964.017	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:2021.547	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:33:38Z	status:HEALTHY	latency:2084.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:38:38Z	status:UNKNOWN	latency:69.016	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:87.348	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60742	target_addr:104.21.26.208:443
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:95.792	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33784	target_addr:104.21.86.125:443
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:118.886	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33782	target_addr:104.21.86.125:443
time:2026-09-28T16:38:38Z	status:FAILURE	latency:378.691	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:776.752	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:825.291	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:1073.008	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43262	target_addr:104.18.40.152:443
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:1186.238	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:38:38Z	status:HEALTHY	latency:2851.614	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:43:38Z	status:UNKNOWN	latency:8.468	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:87.126	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37604	target_addr:172.67.168.140:443
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:120.534	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59722	target_addr:104.21.86.125:443
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:155.057	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59732	target_addr:104.21.86.125:443
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:1089.673	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53698	target_addr:172.64.147.104:443
time:2026-09-28T16:43:38Z	status:FAILURE	latency:1168.044	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:1583.113	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:1633.539	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:2221.085	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:43:38Z	status:HEALTHY	latency:2649.077	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:48:38Z	status:UNKNOWN	latency:9.212	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:68.603	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58190	target_addr:172.67.219.211:443
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:76.292	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58192	target_addr:172.67.219.211:443
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:175.252	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56656	target_addr:172.67.168.140:443
time:2026-09-28T16:48:38Z	status:FAILURE	latency:353.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:875.504	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:1006.262	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:1026.060	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:1089.223	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38160	target_addr:104.18.40.152:443
time:2026-09-28T16:48:38Z	status:HEALTHY	latency:1758.813	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:53:38Z	status:UNKNOWN	latency:7.239	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:76.293	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51856	target_addr:172.67.219.211:443
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:76.880	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37818	target_addr:104.21.86.125:443
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:88.063	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44758	target_addr:104.21.26.208:443
time:2026-09-28T16:53:38Z	status:FAILURE	latency:660.591	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:784.267	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:829.178	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:1082.593	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47278	target_addr:104.18.40.152:443
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:1128.448	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:53:38Z	status:HEALTHY	latency:1732.100	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:58:38Z	status:UNKNOWN	latency:7.767	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:81.501	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34470	target_addr:104.21.86.125:443
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:87.330	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38778	target_addr:172.67.168.140:443
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:156.241	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34468	target_addr:104.21.86.125:443
time:2026-09-28T16:58:38Z	status:FAILURE	latency:750.268	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:798.407	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:805.908	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:1067.740	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48138	target_addr:104.18.40.152:443
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:1673.664	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T16:58:38Z	status:HEALTHY	latency:1738.314	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:03:38Z	status:UNKNOWN	latency:7.208	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:73.091	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43198	target_addr:104.21.86.125:443
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:85.351	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43192	target_addr:104.21.86.125:443
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:151.857	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53206	target_addr:104.21.26.208:443
time:2026-09-28T17:03:38Z	status:FAILURE	latency:411.530	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:745.713	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:803.290	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:812.123	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:826.509	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:03:38Z	status:HEALTHY	latency:1068.791	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:104.18.40.152:443
time:2026-09-28T17:08:38Z	status:UNKNOWN	latency:7.140	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:82.988	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45428	target_addr:172.67.219.211:443
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:155.705	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49460	target_addr:104.21.26.208:443
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:158.933	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45434	target_addr:172.67.219.211:443
time:2026-09-28T17:08:38Z	status:FAILURE	latency:655.606	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:1067.029	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37652	target_addr:104.18.40.152:443
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:1103.472	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:1143.737	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:1146.903	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:08:38Z	status:HEALTHY	latency:1654.337	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:13:38Z	status:UNKNOWN	latency:9.134	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:73.419	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54616	target_addr:172.67.219.211:443
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:85.798	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50788	target_addr:104.21.86.125:443
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:152.303	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36122	target_addr:104.21.26.208:443
time:2026-09-28T17:13:38Z	status:FAILURE	latency:497.597	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:694.775	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:763.746	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:1047.535	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:1067.040	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47570	target_addr:172.64.147.104:443
time:2026-09-28T17:13:38Z	status:HEALTHY	latency:1819.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:18:38Z	status:UNKNOWN	latency:8.715	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:71.453	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44980	target_addr:104.21.86.125:443
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:84.456	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44994	target_addr:104.21.86.125:443
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:84.951	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39660	target_addr:172.67.168.140:443
time:2026-09-28T17:18:38Z	status:FAILURE	latency:399.154	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:771.799	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:807.574	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:822.911	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:1066.048	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50046	target_addr:104.18.40.152:443
time:2026-09-28T17:18:38Z	status:HEALTHY	latency:1192.764	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:23:38Z	status:UNKNOWN	latency:35.997	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:73.679	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34372	target_addr:172.67.168.140:443
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:86.267	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47722	target_addr:172.67.219.211:443
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:87.379	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47724	target_addr:172.67.219.211:443
time:2026-09-28T17:23:38Z	status:FAILURE	latency:546.116	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:657.315	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:689.971	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:708.251	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:1068.888	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58468	target_addr:104.18.40.152:443
time:2026-09-28T17:23:38Z	status:HEALTHY	latency:1803.516	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:28:38Z	status:UNKNOWN	latency:37.655	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:73.587	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58942	target_addr:104.21.86.125:443
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:74.536	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52942	target_addr:104.21.26.208:443
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:145.517	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58956	target_addr:104.21.86.125:443
time:2026-09-28T17:28:38Z	status:FAILURE	latency:261.926	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:861.333	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:865.997	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:1079.736	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39758	target_addr:104.18.40.152:443
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:1281.195	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:28:38Z	status:HEALTHY	latency:1650.268	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:33:38Z	status:UNKNOWN	latency:37.619	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:88.954	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47646	target_addr:172.67.168.140:443
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:152.298	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59226	target_addr:104.21.86.125:443
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:170.613	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54174	target_addr:172.67.219.211:443
time:2026-09-28T17:33:38Z	status:FAILURE	latency:634.725	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:719.769	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:807.154	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:1077.528	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33618	target_addr:172.64.147.104:443
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:1110.340	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:33:38Z	status:HEALTHY	latency:1729.618	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:38:38Z	status:UNKNOWN	latency:6.904	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:74.998	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58404	target_addr:172.67.219.211:443
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:84.842	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60526	target_addr:104.21.26.208:443
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:151.812	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42774	target_addr:104.21.86.125:443
time:2026-09-28T17:38:38Z	status:FAILURE	latency:255.079	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:715.333	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:1050.424	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:1067.881	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57130	target_addr:104.18.40.152:443
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:1141.531	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:38:38Z	status:HEALTHY	latency:1775.870	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:43:38Z	status:UNKNOWN	latency:6.806	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:87.812	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59642	target_addr:172.67.219.211:443
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:87.942	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46618	target_addr:104.21.86.125:443
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:144.054	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49970	target_addr:104.21.26.208:443
time:2026-09-28T17:43:38Z	status:FAILURE	latency:576.554	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:790.828	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:807.205	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:1036.746	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:1066.821	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39610	target_addr:172.64.147.104:443
time:2026-09-28T17:43:38Z	status:HEALTHY	latency:1787.881	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:48:38Z	status:UNKNOWN	latency:37.847	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:88.411	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53004	target_addr:172.67.219.211:443
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:142.879	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52998	target_addr:172.67.219.211:443
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:161.568	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58696	target_addr:172.67.168.140:443
time:2026-09-28T17:48:38Z	status:FAILURE	latency:637.387	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:691.172	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:980.954	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:1050.582	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:1095.713	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60568	target_addr:172.64.147.104:443
time:2026-09-28T17:48:38Z	status:HEALTHY	latency:1544.077	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:53:38Z	status:UNKNOWN	latency:6.862	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:77.393	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44786	target_addr:104.21.26.208:443
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:142.924	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48056	target_addr:104.21.86.125:443
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:158.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46792	target_addr:172.67.219.211:443
time:2026-09-28T17:53:38Z	status:FAILURE	latency:436.650	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:805.320	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:807.136	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:1074.462	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59076	target_addr:104.18.40.152:443
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:1198.234	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:53:38Z	status:HEALTHY	latency:1729.253	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:58:38Z	status:UNKNOWN	latency:7.682	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:71.585	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43148	target_addr:104.21.86.125:443
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:89.675	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37544	target_addr:104.21.26.208:443
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:90.955	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43152	target_addr:104.21.86.125:443
time:2026-09-28T17:58:38Z	status:FAILURE	latency:615.275	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:816.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:855.394	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:1068.652	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40922	target_addr:172.64.147.104:443
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:1541.006	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T17:58:38Z	status:HEALTHY	latency:1614.974	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:03:38Z	status:UNKNOWN	latency:8.093	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:74.732	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56838	target_addr:104.21.26.208:443
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:83.872	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49104	target_addr:172.67.219.211:443
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:151.466	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49100	target_addr:172.67.219.211:443
time:2026-09-28T18:03:38Z	status:FAILURE	latency:388.759	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:806.683	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:976.563	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:1088.666	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33960	target_addr:172.64.147.104:443
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:1556.185	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:03:38Z	status:HEALTHY	latency:26433.767	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:08:38Z	status:UNKNOWN	latency:7.409	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:70.588	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55120	target_addr:104.21.26.208:443
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:86.919	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54266	target_addr:172.67.219.211:443
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:169.522	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54258	target_addr:172.67.219.211:443
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:722.408	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:888.235	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:08:38Z	status:FAILURE	latency:928.778	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:1088.241	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45444	target_addr:104.18.40.152:443
time:2026-09-28T18:08:38Z	status:HEALTHY	latency:1712.894	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:08:38Z	status:FAILURE	latency:125468.178	target:https://go3-cn.blog/	message:524 	length:16	proto:HTTP/2.0	status_code:524
time:2026-09-28T18:13:38Z	status:UNKNOWN	latency:7.760	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:70.365	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55442	target_addr:104.21.86.125:443
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:85.688	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49432	target_addr:172.67.168.140:443
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:85.526	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55454	target_addr:104.21.86.125:443
time:2026-09-28T18:13:38Z	status:FAILURE	latency:211.096	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:1047.126	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:1065.704	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:1079.858	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53824	target_addr:172.64.147.104:443
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:1081.751	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:13:38Z	status:HEALTHY	latency:1591.173	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:18:39Z	status:UNKNOWN	latency:7.667	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:159.038	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38618	target_addr:104.21.26.208:443
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:169.517	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35568	target_addr:172.67.219.211:443
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:697.674	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:977.774	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:1067.838	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37406	target_addr:172.64.147.104:443
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:1169.817	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43628	target_addr:104.21.86.125:443
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:1189.821	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:18:39Z	status:FAILURE	latency:1383.727	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:18:39Z	status:HEALTHY	latency:1614.726	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:23:39Z	status:UNKNOWN	latency:38.977	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:150.133	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44376	target_addr:172.67.219.211:443
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:152.194	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39778	target_addr:104.21.86.125:443
time:2026-09-28T18:23:39Z	status:FAILURE	latency:639.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:1035.144	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:1084.040	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51442	target_addr:172.64.147.104:443
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:1228.826	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47512	target_addr:172.67.168.140:443
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:1666.022	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:3102.129	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:23:39Z	status:HEALTHY	latency:14059.179	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:28:39Z	status:UNKNOWN	latency:7.553	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:10.122	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57260	target_addr:172.64.147.104:443
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:85.941	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40350	target_addr:104.21.86.125:443
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:86.864	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34830	target_addr:172.67.168.140:443
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:161.081	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40344	target_addr:104.21.86.125:443
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:209.078	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:28:39Z	status:FAILURE	latency:447.827	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:746.518	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:818.431	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:28:39Z	status:HEALTHY	latency:1375.462	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:33:39Z	status:UNKNOWN	latency:7.499	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:13.001	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37066	target_addr:172.64.147.104:443
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:73.444	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59438	target_addr:172.67.168.140:443
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:74.269	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33880	target_addr:172.67.219.211:443
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:153.721	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33002	target_addr:104.21.86.125:443
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:169.026	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:33:39Z	status:FAILURE	latency:400.786	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:1056.108	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:1096.776	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:33:39Z	status:HEALTHY	latency:2071.058	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:11.798	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44618	target_addr:172.64.147.104:443
time:2026-09-28T18:38:39Z	status:UNKNOWN	latency:36.253	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:70.849	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54562	target_addr:172.67.219.211:443
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:78.465	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47972	target_addr:104.21.26.208:443
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:85.831	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50358	target_addr:104.21.86.125:443
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:249.425	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:705.518	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:38:39Z	status:FAILURE	latency:810.504	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:1088.807	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:38:39Z	status:HEALTHY	latency:4588.911	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:11.450	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50782	target_addr:172.64.147.104:443
time:2026-09-28T18:43:39Z	status:UNKNOWN	latency:32.735	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:72.228	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45182	target_addr:104.21.86.125:443
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:73.605	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42872	target_addr:172.67.219.211:443
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:152.686	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43574	target_addr:104.21.26.208:443
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:201.613	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:43:39Z	status:FAILURE	latency:646.967	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:798.858	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:1051.801	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:43:39Z	status:HEALTHY	latency:1200.782	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:48:39Z	status:UNKNOWN	latency:8.372	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:9.797	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58430	target_addr:104.18.40.152:443
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:78.179	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60032	target_addr:172.67.168.140:443
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:161.031	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43798	target_addr:104.21.86.125:443
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:183.460	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:48:39Z	status:FAILURE	latency:401.860	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:789.463	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:1070.270	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:1182.253	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43790	target_addr:104.21.86.125:443
time:2026-09-28T18:48:39Z	status:HEALTHY	latency:1684.816	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:53:39Z	status:UNKNOWN	latency:6.642	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:11.484	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40094	target_addr:172.64.147.104:443
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:69.212	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38352	target_addr:104.21.86.125:443
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:92.304	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56608	target_addr:172.67.168.140:443
time:2026-09-28T18:53:39Z	status:FAILURE	latency:252.131	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:275.511	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:841.406	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:847.640	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:1040.472	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:53:39Z	status:HEALTHY	latency:1176.120	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45398	target_addr:172.67.219.211:443
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:14.647	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55800	target_addr:172.64.147.104:443
time:2026-09-28T18:58:39Z	status:UNKNOWN	latency:32.259	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:73.864	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40378	target_addr:104.21.86.125:443
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:74.582	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55262	target_addr:172.67.168.140:443
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:86.201	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46136	target_addr:172.67.219.211:443
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:193.956	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:58:39Z	status:FAILURE	latency:207.807	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:726.959	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:1008.241	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T18:58:39Z	status:HEALTHY	latency:1144.154	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:13.654	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42000	target_addr:104.18.40.152:443
time:2026-09-28T19:03:39Z	status:UNKNOWN	latency:31.641	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:86.763	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36880	target_addr:104.21.26.208:443
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:101.236	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:159.399	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38942	target_addr:172.67.219.211:443
time:2026-09-28T19:03:39Z	status:FAILURE	latency:425.821	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:811.188	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:1118.537	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:1180.453	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38930	target_addr:172.67.219.211:443
time:2026-09-28T19:03:39Z	status:HEALTHY	latency:1610.767	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:11.659	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37996	target_addr:172.64.147.104:443
time:2026-09-28T19:08:39Z	status:UNKNOWN	latency:17.932	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:75.359	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50248	target_addr:172.67.219.211:443
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:88.389	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38780	target_addr:104.21.86.125:443
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:157.658	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40868	target_addr:104.21.26.208:443
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:207.300	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:08:39Z	status:FAILURE	latency:262.899	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:784.205	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:785.541	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:08:39Z	status:HEALTHY	latency:1438.319	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:13:39Z	status:UNKNOWN	latency:8.463	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:13.451	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56670	target_addr:104.18.40.152:443
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:96.933	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49326	target_addr:172.67.168.140:443
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:159.715	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50522	target_addr:172.67.219.211:443
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:170.389	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37364	target_addr:104.21.86.125:443
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:225.602	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:13:39Z	status:FAILURE	latency:455.925	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:721.708	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:737.360	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:13:39Z	status:HEALTHY	latency:773.550	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:18:39Z	status:UNKNOWN	latency:7.063	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:11.051	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52880	target_addr:104.18.40.152:443
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:78.040	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45162	target_addr:104.21.86.125:443
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:160.584	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43330	target_addr:172.67.168.140:443
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:169.750	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45170	target_addr:104.21.86.125:443
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:244.146	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:18:39Z	status:FAILURE	latency:660.375	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:745.263	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:819.628	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:18:39Z	status:HEALTHY	latency:1180.101	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:23:39Z	status:UNKNOWN	latency:6.959	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:11.035	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34976	target_addr:172.64.147.104:443
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:93.517	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38014	target_addr:172.67.219.211:443
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:152.498	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48342	target_addr:104.21.26.208:443
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:170.400	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53826	target_addr:104.21.86.125:443
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:223.156	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:23:39Z	status:FAILURE	latency:254.470	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:666.134	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:740.143	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:23:39Z	status:HEALTHY	latency:1071.848	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:9.482	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37376	target_addr:104.18.40.152:443
time:2026-09-28T19:28:39Z	status:UNKNOWN	latency:31.600	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:152.796	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36752	target_addr:172.67.219.211:443
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:162.979	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36756	target_addr:172.67.219.211:443
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:176.314	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48294	target_addr:104.21.26.208:443
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:223.264	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:28:39Z	status:FAILURE	latency:383.755	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:1050.653	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:1133.500	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:28:39Z	status:HEALTHY	latency:1425.530	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:33:39Z	status:UNKNOWN	latency:6.592	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:8.384	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51724	target_addr:104.18.40.152:443
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:152.217	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54114	target_addr:104.21.86.125:443
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:158.588	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54124	target_addr:104.21.86.125:443
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:161.859	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58680	target_addr:172.67.168.140:443
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:213.240	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:33:39Z	status:FAILURE	latency:269.085	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:708.464	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:980.038	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:33:39Z	status:HEALTHY	latency:1719.654	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:38:39Z	status:UNKNOWN	latency:8.026	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:11.213	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53918	target_addr:172.64.147.104:443
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:71.305	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48540	target_addr:104.21.26.208:443
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:91.795	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54994	target_addr:172.67.219.211:443
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:93.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50296	target_addr:104.21.86.125:443
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:194.430	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:38:39Z	status:FAILURE	latency:730.823	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:762.645	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:1070.978	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:38:39Z	status:HEALTHY	latency:8173.969	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:43:39Z	status:UNKNOWN	latency:8.231	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:14.384	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59832	target_addr:172.64.147.104:443
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:92.471	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44510	target_addr:104.21.86.125:443
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:154.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41692	target_addr:172.67.168.140:443
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:226.770	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:43:39Z	status:FAILURE	latency:492.854	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:794.596	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:1163.561	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:1514.064	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:43:39Z	status:HEALTHY	latency:2224.444	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45168	target_addr:172.67.219.211:443
time:2026-09-28T19:48:39Z	status:UNKNOWN	latency:7.438	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:13.519	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48470	target_addr:172.64.147.104:443
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:72.948	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49944	target_addr:104.21.26.208:443
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:163.259	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42618	target_addr:104.21.86.125:443
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:171.841	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46446	target_addr:172.67.219.211:443
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:213.386	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:48:39Z	status:FAILURE	latency:634.185	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:741.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:980.298	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:48:39Z	status:HEALTHY	latency:1025.153	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:53:39Z	status:UNKNOWN	latency:6.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:8.856	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45072	target_addr:172.64.147.104:443
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:22.172	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50246	target_addr:172.67.219.211:443
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:71.467	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38824	target_addr:172.67.168.140:443
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:158.833	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50254	target_addr:172.67.219.211:443
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:201.411	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:53:39Z	status:FAILURE	latency:262.065	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:805.983	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:850.174	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:53:39Z	status:HEALTHY	latency:1451.672	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:11.523	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57012	target_addr:104.18.40.152:443
time:2026-09-28T19:58:39Z	status:UNKNOWN	latency:38.774	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:91.587	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42304	target_addr:172.67.168.140:443
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:152.859	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46866	target_addr:172.67.219.211:443
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:170.353	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46878	target_addr:172.67.219.211:443
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:188.621	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:58:39Z	status:FAILURE	latency:653.740	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:701.243	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:1016.597	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T19:58:39Z	status:HEALTHY	latency:1109.340	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:03:39Z	status:UNKNOWN	latency:15.624	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:17.350	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33890	target_addr:104.18.40.152:443
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:82.342	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40290	target_addr:104.21.86.125:443
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:162.434	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48544	target_addr:104.21.26.208:443
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:244.366	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:481.023	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:979.317	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:990.393	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:03:39Z	status:HEALTHY	latency:3581.118	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42488	target_addr:172.67.219.211:443
time:2026-09-28T20:03:39Z	status:FAILURE	latency:5451.244	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:08:39Z	status:UNKNOWN	latency:7.250	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:9.617	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55050	target_addr:172.64.147.104:443
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:91.049	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54594	target_addr:104.21.26.208:443
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:158.690	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59132	target_addr:172.67.219.211:443
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:169.323	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59128	target_addr:172.67.219.211:443
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:208.178	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:08:39Z	status:FAILURE	latency:384.473	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:887.618	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:1104.137	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:08:39Z	status:HEALTHY	latency:1840.231	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:13:39Z	status:UNKNOWN	latency:7.221	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:8.482	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34740	target_addr:104.18.40.152:443
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:71.563	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58924	target_addr:172.67.219.211:443
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:74.031	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33852	target_addr:172.67.168.140:443
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:91.256	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34400	target_addr:104.21.86.125:443
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:188.912	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:13:39Z	status:FAILURE	latency:618.073	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:702.580	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:757.820	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:13:39Z	status:HEALTHY	latency:1469.064	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:18:39Z	status:UNKNOWN	latency:5.745	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:9.329	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52482	target_addr:172.64.147.104:443
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:25.175	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38516	target_addr:104.21.26.208:443
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:83.076	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51908	target_addr:172.67.219.211:443
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:89.967	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54430	target_addr:104.21.86.125:443
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:195.871	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:18:39Z	status:FAILURE	latency:481.031	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:1059.480	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:1295.231	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:18:39Z	status:HEALTHY	latency:1366.330	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:11.123	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37084	target_addr:172.64.147.104:443
time:2026-09-28T20:23:39Z	status:UNKNOWN	latency:15.163	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:17.308	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34906	target_addr:104.21.86.125:443
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:71.899	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46640	target_addr:172.67.168.140:443
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:89.277	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34910	target_addr:104.21.86.125:443
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:250.240	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:23:39Z	status:FAILURE	latency:479.972	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:652.063	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:711.541	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:23:39Z	status:HEALTHY	latency:754.010	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:10.746	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34932	target_addr:104.18.40.152:443
time:2026-09-28T20:28:39Z	status:UNKNOWN	latency:18.337	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:72.087	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52256	target_addr:104.21.86.125:443
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:80.672	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40818	target_addr:172.67.168.140:443
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:152.521	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54064	target_addr:172.67.219.211:443
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:188.912	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:28:39Z	status:FAILURE	latency:409.104	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:719.047	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:764.240	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:28:39Z	status:HEALTHY	latency:1605.743	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:33:39Z	status:UNKNOWN	latency:8.674	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:12.659	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55212	target_addr:172.64.147.104:443
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:72.899	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53130	target_addr:172.67.168.140:443
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:85.103	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37926	target_addr:172.67.219.211:443
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:106.065	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:156.221	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43884	target_addr:104.21.86.125:443
time:2026-09-28T20:33:39Z	status:FAILURE	latency:372.359	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:589.389	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:840.378	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:33:39Z	status:HEALTHY	latency:1105.877	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:15.488	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50824	target_addr:104.18.40.152:443
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:20.142	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37442	target_addr:172.67.219.211:443
time:2026-09-28T20:38:39Z	status:UNKNOWN	latency:35.811	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:97.681	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43382	target_addr:172.67.168.140:443
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:166.174	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37458	target_addr:172.67.219.211:443
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:200.856	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:38:39Z	status:FAILURE	latency:417.713	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:541.745	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:971.203	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:38:39Z	status:HEALTHY	latency:1109.503	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:43:39Z	status:UNKNOWN	latency:8.622	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:11.765	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35198	target_addr:104.18.40.152:443
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:71.032	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51772	target_addr:104.21.26.208:443
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:90.596	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40908	target_addr:104.21.86.125:443
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:92.091	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40910	target_addr:104.21.86.125:443
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:222.867	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:43:39Z	status:FAILURE	latency:411.623	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:738.892	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:769.405	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:43:39Z	status:HEALTHY	latency:1027.884	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:9.987	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56614	target_addr:104.18.40.152:443
time:2026-09-28T20:48:39Z	status:UNKNOWN	latency:37.376	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:78.858	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43660	target_addr:172.67.219.211:443
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:92.249	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43674	target_addr:172.67.219.211:443
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:98.825	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:164.353	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34594	target_addr:172.67.168.140:443
time:2026-09-28T20:48:39Z	status:FAILURE	latency:662.718	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:698.425	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:997.947	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:48:39Z	status:HEALTHY	latency:1022.388	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:15.510	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40306	target_addr:172.64.147.104:443
time:2026-09-28T20:53:39Z	status:UNKNOWN	latency:37.871	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:73.833	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39226	target_addr:172.67.219.211:443
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:152.890	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33690	target_addr:172.67.168.140:443
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:155.948	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39210	target_addr:172.67.219.211:443
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:208.220	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:53:39Z	status:FAILURE	latency:390.040	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:773.215	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:2169.707	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:53:39Z	status:HEALTHY	latency:2860.359	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:16.148	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42422	target_addr:104.18.40.152:443
time:2026-09-28T20:58:39Z	status:UNKNOWN	latency:38.923	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:74.018	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51792	target_addr:104.21.26.208:443
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:81.671	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58274	target_addr:104.21.86.125:443
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:160.017	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39328	target_addr:172.67.219.211:443
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:411.141	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:58:39Z	status:FAILURE	latency:421.843	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:758.989	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:1168.034	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T20:58:39Z	status:HEALTHY	latency:2612.440	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:03:39Z	status:UNKNOWN	latency:7.473	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:11.161	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50340	target_addr:172.64.147.104:443
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:87.048	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46058	target_addr:172.67.168.140:443
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:92.424	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55800	target_addr:172.67.219.211:443
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:172.931	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60044	target_addr:104.21.86.125:443
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:241.384	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:589.704	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:03:39Z	status:FAILURE	latency:605.560	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:630.112	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:03:39Z	status:HEALTHY	latency:10371.350	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:08:39Z	status:UNKNOWN	latency:8.045	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:13.264	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34838	target_addr:172.64.147.104:443
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:73.281	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57580	target_addr:104.21.26.208:443
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:85.808	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39550	target_addr:172.67.219.211:443
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:94.848	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39562	target_addr:172.67.219.211:443
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:219.228	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:398.430	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:08:39Z	status:FAILURE	latency:463.626	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:613.968	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:08:39Z	status:HEALTHY	latency:3658.161	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:13:39Z	status:UNKNOWN	latency:6.916	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:16.075	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38062	target_addr:104.18.40.152:443
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:75.706	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46094	target_addr:104.21.26.208:443
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:90.337	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44726	target_addr:172.67.219.211:443
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:91.420	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44738	target_addr:172.67.219.211:443
time:2026-09-28T21:13:39Z	status:FAILURE	latency:211.600	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:226.623	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:327.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:631.814	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:13:39Z	status:HEALTHY	latency:939.641	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:18:39Z	status:UNKNOWN	latency:7.932	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:11.726	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52310	target_addr:172.64.147.104:443
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:100.730	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35070	target_addr:172.67.219.211:443
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:161.811	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35058	target_addr:172.67.219.211:443
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:179.175	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44546	target_addr:104.21.26.208:443
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:222.243	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:288.671	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:360.894	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:18:39Z	status:FAILURE	latency:370.917	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:18:39Z	status:HEALTHY	latency:382.159	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:23:39Z	status:UNKNOWN	latency:9.945	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:10.689	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51984	target_addr:172.64.147.104:443
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:20.680	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47762	target_addr:104.21.86.125:443
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:88.241	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47768	target_addr:104.21.86.125:443
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:159.174	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59426	target_addr:172.67.168.140:443
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:225.533	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:302.219	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:410.275	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:23:39Z	status:FAILURE	latency:462.627	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:23:39Z	status:HEALTHY	latency:812.542	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:11.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60566	target_addr:104.18.40.152:443
time:2026-09-28T21:28:39Z	status:UNKNOWN	latency:16.050	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:18.684	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33254	target_addr:104.21.86.125:443
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:23.477	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48146	target_addr:172.67.168.140:443
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:89.852	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33248	target_addr:104.21.86.125:443
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:203.229	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:28:39Z	status:FAILURE	latency:355.255	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:496.719	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:516.727	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:28:39Z	status:HEALTHY	latency:2219.373	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:33:39Z	status:UNKNOWN	latency:6.681	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:12.943	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49924	target_addr:104.18.40.152:443
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:20.215	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41312	target_addr:104.21.26.208:443
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:74.492	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56330	target_addr:172.67.219.211:443
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:151.423	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35074	target_addr:104.21.86.125:443
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:249.840	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:354.825	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:33:39Z	status:FAILURE	latency:641.638	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:645.843	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:33:39Z	status:HEALTHY	latency:2345.444	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:38:39Z	status:UNKNOWN	latency:9.394	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:14.100	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56500	target_addr:104.18.40.152:443
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:23.698	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41244	target_addr:104.21.26.208:443
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:74.936	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49794	target_addr:104.21.86.125:443
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:80.188	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:95.870	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47866	target_addr:172.67.219.211:443
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:242.845	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:384.540	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:38:39Z	status:FAILURE	latency:420.134	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:38:39Z	status:HEALTHY	latency:582.467	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:43:39Z	status:UNKNOWN	latency:8.380	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:11.680	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42850	target_addr:104.18.40.152:443
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:21.642	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45222	target_addr:172.67.219.211:443
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:70.908	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42318	target_addr:104.21.86.125:443
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:86.290	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34796	target_addr:172.67.168.140:443
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:237.667	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:43:39Z	status:FAILURE	latency:398.093	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:837.779	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:885.425	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:43:39Z	status:HEALTHY	latency:998.200	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:48:39Z	status:UNKNOWN	latency:6.814	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:12.143	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49186	target_addr:172.64.147.104:443
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:27.606	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48278	target_addr:172.67.219.211:443
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:95.147	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48270	target_addr:172.67.219.211:443
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:161.234	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33626	target_addr:104.21.26.208:443
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:262.442	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:48:39Z	status:FAILURE	latency:435.096	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:1371.772	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:1417.190	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:48:39Z	status:HEALTHY	latency:1597.261	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:15.262	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56456	target_addr:104.18.40.152:443
time:2026-09-28T21:53:39Z	status:UNKNOWN	latency:17.621	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:75.824	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40944	target_addr:172.67.168.140:443
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:92.176	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56390	target_addr:104.21.86.125:443
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:161.329	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38360	target_addr:172.67.219.211:443
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:535.934	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:53:39Z	status:FAILURE	latency:598.743	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:1001.056	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:1014.995	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:53:39Z	status:HEALTHY	latency:1284.188	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:58:40Z	status:UNKNOWN	latency:8.117	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:13.812	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42816	target_addr:104.18.40.152:443
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:79.276	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38498	target_addr:104.21.86.125:443
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:156.442	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38482	target_addr:104.21.86.125:443
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:162.716	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56660	target_addr:172.67.168.140:443
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:281.627	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:58:40Z	status:FAILURE	latency:367.099	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:775.160	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:1326.572	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T21:58:40Z	status:HEALTHY	latency:1609.141	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:03:40Z	status:UNKNOWN	latency:8.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:11.852	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53216	target_addr:104.18.40.152:443
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:160.483	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34934	target_addr:104.21.26.208:443
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:166.512	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40952	target_addr:172.67.219.211:443
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:174.122	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39460	target_addr:104.21.86.125:443
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:208.641	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:03:40Z	status:FAILURE	latency:254.850	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:650.360	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:662.050	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:03:40Z	status:HEALTHY	latency:1321.079	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:08:40Z	status:UNKNOWN	latency:9.038	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:12.723	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37376	target_addr:172.64.147.104:443
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:18.817	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57672	target_addr:172.67.219.211:443
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:19.622	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57686	target_addr:172.67.219.211:443
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:90.477	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47248	target_addr:172.67.168.140:443
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:215.650	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:08:40Z	status:FAILURE	latency:390.712	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:702.620	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:1054.756	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:08:40Z	status:HEALTHY	latency:1304.110	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:13:40Z	status:UNKNOWN	latency:7.265	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:11.607	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41414	target_addr:172.64.147.104:443
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:89.654	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45608	target_addr:172.67.219.211:443
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:153.833	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49832	target_addr:104.21.26.208:443
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:162.218	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44642	target_addr:104.21.86.125:443
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:192.434	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:13:40Z	status:FAILURE	latency:466.733	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:755.826	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:785.741	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:13:40Z	status:HEALTHY	latency:1513.181	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:18:40Z	status:UNKNOWN	latency:8.157	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:13.367	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32780	target_addr:172.64.147.104:443
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:91.514	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50880	target_addr:104.21.26.208:443
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:165.004	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55148	target_addr:104.21.86.125:443
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:173.163	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50394	target_addr:172.67.219.211:443
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:221.197	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:18:40Z	status:FAILURE	latency:232.427	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:1059.712	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:1458.769	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:18:40Z	status:HEALTHY	latency:3893.783	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:23:40Z	status:UNKNOWN	latency:7.850	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:14.187	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54208	target_addr:104.18.40.152:443
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:71.170	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36870	target_addr:172.67.219.211:443
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:73.863	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42866	target_addr:172.67.168.140:443
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:85.859	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36874	target_addr:172.67.219.211:443
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:204.350	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:23:40Z	status:FAILURE	latency:399.767	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:505.023	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:522.791	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:23:40Z	status:HEALTHY	latency:981.284	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:28:40Z	status:UNKNOWN	latency:7.172	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:11.541	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35996	target_addr:172.64.147.104:443
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:70.189	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58048	target_addr:104.21.26.208:443
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:76.099	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58388	target_addr:172.67.219.211:443
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:152.477	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58390	target_addr:172.67.219.211:443
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:223.289	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:28:40Z	status:FAILURE	latency:448.128	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:973.249	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:1008.228	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:28:40Z	status:HEALTHY	latency:1356.709	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:33:40Z	status:UNKNOWN	latency:7.716	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:19.991	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56772	target_addr:172.64.147.104:443
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:87.192	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40668	target_addr:104.21.86.125:443
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:88.270	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52270	target_addr:172.67.219.211:443
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:96.373	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33304	target_addr:172.67.168.140:443
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:205.540	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:33:40Z	status:FAILURE	latency:206.073	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:528.019	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:534.753	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:33:40Z	status:HEALTHY	latency:1060.877	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:8.867	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38432	target_addr:104.18.40.152:443
time:2026-09-28T22:38:40Z	status:UNKNOWN	latency:21.514	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:78.673	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56498	target_addr:104.21.86.125:443
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:86.195	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56502	target_addr:104.21.86.125:443
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:104.676	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49354	target_addr:104.21.26.208:443
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:187.329	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:434.440	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:38:40Z	status:FAILURE	latency:655.467	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:670.905	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:38:40Z	status:HEALTHY	latency:723.373	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:43:40Z	status:UNKNOWN	latency:7.585	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:18.885	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34846	target_addr:104.18.40.152:443
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:73.610	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55876	target_addr:104.21.86.125:443
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:153.270	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53988	target_addr:104.21.26.208:443
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:170.662	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55888	target_addr:104.21.86.125:443
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:198.327	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:43:40Z	status:FAILURE	latency:387.785	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:775.754	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:782.722	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:43:40Z	status:HEALTHY	latency:1155.606	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:48:40Z	status:UNKNOWN	latency:5.893	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:16.040	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41432	target_addr:104.18.40.152:443
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:20.022	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34952	target_addr:172.67.219.211:443
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:83.679	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51714	target_addr:172.67.168.140:443
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:152.964	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34954	target_addr:172.67.219.211:443
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:224.606	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:48:40Z	status:FAILURE	latency:259.813	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:544.475	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:792.073	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:48:40Z	status:HEALTHY	latency:1056.228	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:53:40Z	status:UNKNOWN	latency:7.899	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:18.564	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33420	target_addr:104.18.40.152:443
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:87.112	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52702	target_addr:104.21.86.125:443
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:157.049	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52710	target_addr:104.21.86.125:443
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:169.917	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48630	target_addr:172.67.168.140:443
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:220.199	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:53:40Z	status:FAILURE	latency:712.821	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:958.977	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:1024.701	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:53:40Z	status:HEALTHY	latency:2645.259	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:58:40Z	status:UNKNOWN	latency:6.823	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:93.655	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48114	target_addr:172.67.219.211:443
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:152.088	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48104	target_addr:172.67.219.211:443
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:159.996	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48034	target_addr:104.21.26.208:443
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:223.812	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:227.619	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53186	target_addr:104.18.40.152:443
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:641.281	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:58:40Z	status:FAILURE	latency:654.507	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:696.863	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T22:58:40Z	status:HEALTHY	latency:956.943	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:03:40Z	status:UNKNOWN	latency:7.784	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:13.529	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45612	target_addr:172.64.147.104:443
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:72.153	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35392	target_addr:172.67.168.140:443
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:74.497	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37416	target_addr:104.21.86.125:443
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:164.770	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57338	target_addr:172.67.219.211:443
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:245.027	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:03:40Z	status:FAILURE	latency:480.410	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:892.333	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:1213.818	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:03:40Z	status:HEALTHY	latency:6113.699	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:08:40Z	status:UNKNOWN	latency:10.252	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:11.558	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55774	target_addr:172.64.147.104:443
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:91.097	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34978	target_addr:172.67.219.211:443
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:91.488	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34994	target_addr:172.67.219.211:443
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:159.064	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43696	target_addr:104.21.26.208:443
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:270.079	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:08:40Z	status:FAILURE	latency:442.019	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:798.583	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:1027.818	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:08:40Z	status:HEALTHY	latency:1061.983	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:11.824	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36102	target_addr:104.18.40.152:443
time:2026-09-28T23:13:40Z	status:UNKNOWN	latency:29.936	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:73.830	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46442	target_addr:172.67.219.211:443
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:91.569	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60038	target_addr:172.67.168.140:443
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:93.581	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43508	target_addr:104.21.86.125:443
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:460.078	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:13:40Z	status:FAILURE	latency:614.948	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:793.743	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:1077.124	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:13:40Z	status:HEALTHY	latency:1114.423	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:18:40Z	status:UNKNOWN	latency:6.642	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:16.251	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36204	target_addr:104.18.40.152:443
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:153.844	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56364	target_addr:172.67.219.211:443
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:162.471	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56348	target_addr:172.67.219.211:443
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:165.094	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58412	target_addr:172.67.168.140:443
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:230.062	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:18:40Z	status:FAILURE	latency:612.278	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:753.722	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:1022.286	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:18:40Z	status:HEALTHY	latency:3815.846	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:23:40Z	status:UNKNOWN	latency:7.212	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:11.109	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44096	target_addr:104.18.40.152:443
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:22.197	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35096	target_addr:104.21.86.125:443
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:78.156	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35090	target_addr:104.21.86.125:443
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:91.327	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45762	target_addr:104.21.26.208:443
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:213.420	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:23:40Z	status:FAILURE	latency:649.259	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:720.756	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:760.482	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:23:40Z	status:HEALTHY	latency:970.497	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:12.777	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42450	target_addr:104.18.40.152:443
time:2026-09-28T23:28:40Z	status:UNKNOWN	latency:23.162	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:89.577	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39384	target_addr:104.21.26.208:443
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:93.633	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53878	target_addr:104.21.86.125:443
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:153.575	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53872	target_addr:104.21.86.125:443
time:2026-09-28T23:28:40Z	status:FAILURE	latency:210.452	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:226.734	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:793.114	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:823.746	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:28:40Z	status:HEALTHY	latency:854.883	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:15.790	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47718	target_addr:172.64.147.104:443
time:2026-09-28T23:33:40Z	status:UNKNOWN	latency:37.009	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:71.150	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50152	target_addr:104.21.86.125:443
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:108.470	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38772	target_addr:104.21.26.208:443
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:151.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50148	target_addr:104.21.86.125:443
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:219.016	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:33:40Z	status:FAILURE	latency:406.801	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:450.940	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:705.963	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:33:40Z	status:HEALTHY	latency:1101.402	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:38:40Z	status:UNKNOWN	latency:7.604	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:12.158	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39520	target_addr:172.64.147.104:443
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:72.872	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48960	target_addr:104.21.86.125:443
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:79.746	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38482	target_addr:104.21.26.208:443
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:153.929	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48962	target_addr:104.21.86.125:443
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:210.620	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:472.787	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:38:40Z	status:FAILURE	latency:481.426	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:1039.215	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:38:40Z	status:HEALTHY	latency:1051.089	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:43:40Z	status:UNKNOWN	latency:8.702	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:11.422	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50390	target_addr:104.18.40.152:443
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:84.030	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39948	target_addr:172.67.219.211:443
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:94.084	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33326	target_addr:104.21.86.125:443
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:161.605	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60968	target_addr:172.67.168.140:443
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:197.774	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:43:40Z	status:FAILURE	latency:433.999	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:742.979	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:991.849	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:43:40Z	status:HEALTHY	latency:1231.235	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:10.929	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46218	target_addr:104.18.40.152:443
time:2026-09-28T23:48:40Z	status:UNKNOWN	latency:33.703	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:74.351	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43726	target_addr:172.67.219.211:443
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:76.012	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57458	target_addr:172.67.168.140:443
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:157.327	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43738	target_addr:172.67.219.211:443
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:228.394	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:48:40Z	status:FAILURE	latency:435.272	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:995.945	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:1153.717	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:48:40Z	status:HEALTHY	latency:5823.350	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:53:40Z	status:UNKNOWN	latency:7.888	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:11.154	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49086	target_addr:104.18.40.152:443
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:71.391	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56818	target_addr:104.21.86.125:443
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:78.166	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38192	target_addr:104.21.26.208:443
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:78.899	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36368	target_addr:172.67.219.211:443
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:219.031	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:53:40Z	status:FAILURE	latency:408.334	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:1119.965	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:1244.872	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:53:40Z	status:HEALTHY	latency:1736.735	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:58:40Z	status:UNKNOWN	latency:7.977	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:11.885	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40646	target_addr:172.64.147.104:443
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:73.175	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37416	target_addr:104.21.86.125:443
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:81.981	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59584	target_addr:172.67.219.211:443
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:153.503	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45294	target_addr:172.67.168.140:443
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:213.090	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:343.565	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:58:40Z	status:FAILURE	latency:567.826	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:1008.159	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-28T23:58:40Z	status:HEALTHY	latency:4160.779	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:03:40Z	status:UNKNOWN	latency:8.872	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:11.053	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52860	target_addr:172.64.147.104:443
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:21.722	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47246	target_addr:172.67.219.211:443
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:25.750	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48868	target_addr:172.67.168.140:443
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:161.942	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47234	target_addr:172.67.219.211:443
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:214.257	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:362.983	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:634.983	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:03:40Z	status:FAILURE	latency:643.017	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:03:40Z	status:HEALTHY	latency:756.623	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:08:40Z	status:UNKNOWN	latency:21.358	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:23.872	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59108	target_addr:172.64.147.104:443
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:71.345	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39012	target_addr:172.67.219.211:443
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:72.745	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36908	target_addr:104.21.86.125:443
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:84.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56008	target_addr:172.67.168.140:443
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:232.175	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:380.543	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:448.708	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:08:40Z	status:HEALTHY	latency:617.593	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:08:40Z	status:FAILURE	latency:624.747	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:13:40Z	status:UNKNOWN	latency:7.351	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:11.893	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57284	target_addr:104.18.40.152:443
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:21.793	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56534	target_addr:172.67.168.140:443
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:75.831	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40768	target_addr:172.67.219.211:443
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:150.455	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40756	target_addr:172.67.219.211:443
time:2026-09-29T00:13:40Z	status:FAILURE	latency:230.431	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:270.117	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:1091.431	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:13:40Z	status:HEALTHY	latency:1128.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:13:40Z	status:FAILURE	latency:20012.546	target:https://go3-cn.online/	message:[2606:4700:3033::ac43:8beb]:443: connection refused
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:13.105	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44996	target_addr:104.18.40.152:443
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:19.654	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51660	target_addr:172.67.219.211:443
time:2026-09-29T00:18:40Z	status:UNKNOWN	latency:33.947	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:73.222	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54292	target_addr:104.21.86.125:443
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:152.329	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59426	target_addr:104.21.26.208:443
time:2026-09-29T00:18:40Z	status:FAILURE	latency:213.028	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:236.806	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:1068.200	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:1097.276	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:18:40Z	status:HEALTHY	latency:1414.884	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:20.869	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56584	target_addr:172.64.147.104:443
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:73.275	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56920	target_addr:172.67.219.211:443
time:2026-09-29T00:23:40Z	status:UNKNOWN	latency:74.097	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:156.095	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40556	target_addr:104.21.86.125:443
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:173.674	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41874	target_addr:172.67.168.140:443
time:2026-09-29T00:23:40Z	status:FAILURE	latency:232.584	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:267.517	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:764.162	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:767.433	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:23:40Z	status:HEALTHY	latency:2344.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:28:40Z	status:UNKNOWN	latency:8.658	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:18.673	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42768	target_addr:104.18.40.152:443
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:75.631	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45270	target_addr:104.21.86.125:443
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:79.332	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36240	target_addr:172.67.168.140:443
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:95.632	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45272	target_addr:104.21.86.125:443
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:204.110	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:357.330	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:383.861	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:28:40Z	status:FAILURE	latency:403.872	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:28:40Z	status:HEALTHY	latency:646.041	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:14.871	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53930	target_addr:104.18.40.152:443
time:2026-09-29T00:33:40Z	status:UNKNOWN	latency:35.917	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:74.247	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57338	target_addr:104.21.26.208:443
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:93.132	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41080	target_addr:172.67.219.211:443
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:155.125	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41090	target_addr:172.67.219.211:443
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:228.944	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:33:40Z	status:FAILURE	latency:234.493	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:376.555	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:641.639	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:33:40Z	status:HEALTHY	latency:5609.205	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:38:40Z	status:UNKNOWN	latency:7.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:12.189	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58364	target_addr:172.64.147.104:443
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:19.509	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38282	target_addr:104.21.86.125:443
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:86.436	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50456	target_addr:104.21.26.208:443
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:154.162	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44124	target_addr:172.67.219.211:443
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:252.144	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:38:40Z	status:FAILURE	latency:663.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:774.859	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:1015.671	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:38:40Z	status:HEALTHY	latency:1419.586	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:28.312	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33498	target_addr:104.18.40.152:443
time:2026-09-29T00:43:40Z	status:UNKNOWN	latency:39.050	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:75.518	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36800	target_addr:104.21.26.208:443
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:170.327	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33464	target_addr:104.21.86.125:443
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:178.784	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53558	target_addr:172.67.219.211:443
time:2026-09-29T00:43:40Z	status:FAILURE	latency:217.699	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:808.333	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:822.677	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:1030.794	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:43:40Z	status:HEALTHY	latency:6762.580	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:48:40Z	status:UNKNOWN	latency:9.187	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:15.420	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45652	target_addr:104.18.40.152:443
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:72.237	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38340	target_addr:104.21.86.125:443
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:74.645	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38356	target_addr:104.21.86.125:443
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:157.758	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53824	target_addr:104.21.26.208:443
time:2026-09-29T00:48:40Z	status:FAILURE	latency:198.556	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:211.342	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:562.410	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:717.413	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:48:40Z	status:HEALTHY	latency:824.579	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:12.742	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54050	target_addr:104.18.40.152:443
time:2026-09-29T00:53:40Z	status:UNKNOWN	latency:36.791	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:84.750	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53890	target_addr:172.67.219.211:443
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:85.229	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53904	target_addr:172.67.219.211:443
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:167.827	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39708	target_addr:104.21.26.208:443
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:234.336	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:470.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:748.684	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:53:40Z	status:HEALTHY	latency:749.178	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:53:40Z	status:FAILURE	latency:1184.136	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:17.264	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47706	target_addr:172.64.147.104:443
time:2026-09-29T00:58:40Z	status:UNKNOWN	latency:35.919	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:94.979	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38074	target_addr:172.67.219.211:443
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:105.759	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42900	target_addr:104.21.86.125:443
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:169.597	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55146	target_addr:172.67.168.140:443
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:250.395	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:532.912	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:58:40Z	status:FAILURE	latency:604.990	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:708.508	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T00:58:40Z	status:HEALTHY	latency:1117.067	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:13.960	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46574	target_addr:104.18.40.152:443
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:21.542	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33974	target_addr:104.21.26.208:443
time:2026-09-29T01:03:40Z	status:UNKNOWN	latency:33.934	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:74.453	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34256	target_addr:172.67.219.211:443
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:165.276	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35344	target_addr:104.21.86.125:443
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:289.077	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:03:40Z	status:FAILURE	latency:608.636	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:714.997	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:1024.953	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:03:40Z	status:HEALTHY	latency:1130.606	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:12.743	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47494	target_addr:104.18.40.152:443
time:2026-09-29T01:08:40Z	status:UNKNOWN	latency:34.870	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:79.693	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48918	target_addr:172.67.219.211:443
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:89.646	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48910	target_addr:172.67.219.211:443
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:155.479	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60776	target_addr:104.21.26.208:443
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:379.936	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:566.831	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:594.322	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:08:40Z	status:HEALTHY	latency:810.840	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:08:40Z	status:FAILURE	latency:1642.684	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:13:40Z	status:UNKNOWN	latency:9.027	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:12.369	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42848	target_addr:104.18.40.152:443
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:30.187	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33742	target_addr:104.21.86.125:443
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:72.104	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33730	target_addr:104.21.86.125:443
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:85.795	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46760	target_addr:104.21.26.208:443
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:278.752	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:298.218	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:406.399	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:13:40Z	status:FAILURE	latency:475.141	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:13:40Z	status:HEALTHY	latency:617.099	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:21.448	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56114	target_addr:172.67.219.211:443
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:21.887	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32946	target_addr:104.18.40.152:443
time:2026-09-29T01:18:40Z	status:UNKNOWN	latency:39.261	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:86.586	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56126	target_addr:172.67.219.211:443
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:158.384	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46544	target_addr:172.67.168.140:443
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:257.329	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:477.757	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:18:40Z	status:FAILURE	latency:676.414	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:694.448	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:18:40Z	status:HEALTHY	latency:709.973	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:23:40Z	status:UNKNOWN	latency:9.372	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:12.993	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43170	target_addr:172.64.147.104:443
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:25.408	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40350	target_addr:104.21.26.208:443
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:79.446	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48578	target_addr:172.67.219.211:443
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:84.536	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59294	target_addr:104.21.86.125:443
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:141.014	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:764.702	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:1010.296	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:23:40Z	status:HEALTHY	latency:1242.654	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:23:40Z	status:FAILURE	latency:2361.818	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:28:40Z	status:UNKNOWN	latency:6.900	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:46.288	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57218	target_addr:172.64.147.104:443
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:73.473	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40690	target_addr:172.67.219.211:443
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:74.353	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57302	target_addr:104.21.26.208:443
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:86.338	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41306	target_addr:104.21.86.125:443
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:355.840	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:814.179	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:1115.587	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:28:40Z	status:FAILURE	latency:1432.793	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:28:40Z	status:HEALTHY	latency:1445.490	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:33:40Z	status:UNKNOWN	latency:9.507	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:11.545	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41416	target_addr:172.64.147.104:443
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:82.174	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36128	target_addr:104.21.86.125:443
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:156.478	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58644	target_addr:172.67.219.211:443
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:168.059	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36994	target_addr:104.21.26.208:443
time:2026-09-29T01:33:40Z	status:FAILURE	latency:208.142	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:251.462	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:566.092	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:731.003	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:33:40Z	status:HEALTHY	latency:1350.171	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:38:40Z	status:UNKNOWN	latency:39.224	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:77.113	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42142	target_addr:172.67.219.211:443
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:94.888	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56830	target_addr:172.67.168.140:443
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:152.524	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42140	target_addr:172.67.219.211:443
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:227.289	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:243.417	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43328	target_addr:104.18.40.152:443
time:2026-09-29T01:38:40Z	status:FAILURE	latency:454.501	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:673.792	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:960.302	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:38:40Z	status:HEALTHY	latency:1000.283	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:43:40Z	status:UNKNOWN	latency:7.620	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:11.432	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51858	target_addr:172.64.147.104:443
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:70.333	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36606	target_addr:104.21.26.208:443
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:70.434	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53688	target_addr:104.21.86.125:443
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:116.812	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:159.901	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34550	target_addr:172.67.219.211:443
time:2026-09-29T01:43:40Z	status:FAILURE	latency:412.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:718.459	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:1092.045	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:43:40Z	status:HEALTHY	latency:1581.122	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:14.726	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45910	target_addr:104.18.40.152:443
time:2026-09-29T01:48:40Z	status:UNKNOWN	latency:16.972	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:26.175	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60462	target_addr:104.21.86.125:443
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:86.575	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34656	target_addr:172.67.168.140:443
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:93.417	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53540	target_addr:172.67.219.211:443
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:269.995	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:48:40Z	status:FAILURE	latency:308.723	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:363.457	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:658.349	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:48:40Z	status:HEALTHY	latency:5370.042	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:53:40Z	status:UNKNOWN	latency:8.396	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:14.642	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51156	target_addr:172.64.147.104:443
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:74.990	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36054	target_addr:172.67.219.211:443
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:93.277	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52718	target_addr:104.21.86.125:443
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:162.744	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37792	target_addr:172.67.168.140:443
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:246.949	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:366.487	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:373.053	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:53:40Z	status:FAILURE	latency:643.076	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T01:53:40Z	status:HEALTHY	latency:5083.258	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:58:40Z	status:UNKNOWN	latency:8.831	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:15.112	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56980	target_addr:172.64.147.104:443
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:78.740	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60658	target_addr:104.21.26.208:443
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:90.961	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:92.259	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44390	target_addr:172.67.219.211:443
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:162.177	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45552	target_addr:104.21.86.125:443
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:295.828	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:360.738	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:58:40Z	status:HEALTHY	latency:364.187	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T01:58:40Z	status:FAILURE	latency:408.778	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:03:40Z	status:UNKNOWN	latency:10.293	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:12.679	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47054	target_addr:104.18.40.152:443
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:163.794	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45506	target_addr:172.67.219.211:443
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:163.762	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47754	target_addr:172.67.168.140:443
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:165.506	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50894	target_addr:104.21.86.125:443
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:227.920	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:03:40Z	status:FAILURE	latency:453.991	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:751.380	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:857.157	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:03:40Z	status:HEALTHY	latency:5908.564	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:08:41Z	status:UNKNOWN	latency:7.494	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:14.661	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38332	target_addr:172.64.147.104:443
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:69.639	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37828	target_addr:172.67.219.211:443
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:82.045	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54418	target_addr:104.21.86.125:443
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:164.473	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48978	target_addr:172.67.168.140:443
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:241.316	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:08:41Z	status:FAILURE	latency:686.232	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:731.059	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:994.114	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:08:41Z	status:HEALTHY	latency:1515.466	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:13:41Z	status:UNKNOWN	latency:11.012	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:11.558	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48778	target_addr:172.64.147.104:443
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:75.009	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42446	target_addr:104.21.86.125:443
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:79.119	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42438	target_addr:104.21.86.125:443
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:95.010	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57788	target_addr:172.67.168.140:443
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:113.660	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:300.367	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:375.135	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:13:41Z	status:FAILURE	latency:751.118	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:13:41Z	status:HEALTHY	latency:3852.773	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:18:41Z	status:UNKNOWN	latency:10.250	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:15.563	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36872	target_addr:172.64.147.104:443
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:25.320	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41938	target_addr:104.21.86.125:443
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:73.745	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49480	target_addr:172.67.219.211:443
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:154.170	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55080	target_addr:104.21.26.208:443
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:301.087	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:325.773	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:377.114	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:18:41Z	status:FAILURE	latency:642.737	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:18:41Z	status:HEALTHY	latency:1042.023	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:23:41Z	status:UNKNOWN	latency:9.222	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:13.005	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53032	target_addr:104.18.40.152:443
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:22.937	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54556	target_addr:172.67.219.211:443
time:2026-09-29T02:23:41Z	status:FAILURE	latency:66.417	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:73.898	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53778	target_addr:172.67.168.140:443
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:162.961	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53636	target_addr:104.21.86.125:443
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:286.243	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:358.028	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:378.884	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:23:41Z	status:HEALTHY	latency:390.140	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:14.757	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51714	target_addr:104.18.40.152:443
time:2026-09-29T02:28:41Z	status:UNKNOWN	latency:38.539	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:88.386	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59314	target_addr:104.21.86.125:443
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:95.007	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40048	target_addr:104.21.26.208:443
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:95.075	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39122	target_addr:172.67.219.211:443
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:267.007	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:737.098	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:754.804	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:28:41Z	status:HEALTHY	latency:993.160	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:28:41Z	status:FAILURE	latency:1409.709	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:27.089	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49294	target_addr:172.64.147.104:443
time:2026-09-29T02:33:41Z	status:UNKNOWN	latency:27.909	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:73.166	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39298	target_addr:104.21.86.125:443
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:124.303	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39302	target_addr:104.21.86.125:443
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:162.767	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39792	target_addr:104.21.26.208:443
time:2026-09-29T02:33:41Z	status:FAILURE	latency:349.625	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:685.713	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:788.948	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:791.004	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:33:41Z	status:HEALTHY	latency:1280.303	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:38:41Z	status:UNKNOWN	latency:10.296	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:13.746	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57078	target_addr:104.18.40.152:443
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:72.580	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55572	target_addr:104.21.86.125:443
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:72.295	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55920	target_addr:172.67.219.211:443
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:161.774	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51690	target_addr:104.21.26.208:443
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:283.639	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:38:41Z	status:FAILURE	latency:461.301	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:736.826	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:879.847	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:38:41Z	status:HEALTHY	latency:2028.134	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:9.596	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56854	target_addr:172.64.147.104:443
time:2026-09-29T02:43:41Z	status:UNKNOWN	latency:37.797	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:105.618	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35924	target_addr:104.21.86.125:443
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:124.078	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35936	target_addr:104.21.86.125:443
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:158.448	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36960	target_addr:104.21.26.208:443
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:266.995	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:43:41Z	status:FAILURE	latency:427.522	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:733.143	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:893.921	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:43:41Z	status:HEALTHY	latency:914.919	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:48:41Z	status:UNKNOWN	latency:7.086	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:11.500	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47726	target_addr:172.64.147.104:443
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:83.171	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35124	target_addr:104.21.86.125:443
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:95.078	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60668	target_addr:172.67.168.140:443
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:164.813	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35128	target_addr:104.21.86.125:443
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:204.258	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:48:41Z	status:FAILURE	latency:562.223	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:786.395	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:825.499	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:48:41Z	status:HEALTHY	latency:1843.406	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:53:41Z	status:UNKNOWN	latency:7.671	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:11.906	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46108	target_addr:172.64.147.104:443
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:73.950	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60656	target_addr:172.67.219.211:443
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:94.726	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60660	target_addr:172.67.219.211:443
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:167.614	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38788	target_addr:172.67.168.140:443
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:261.149	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:53:41Z	status:FAILURE	latency:352.277	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:367.084	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:385.013	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:53:41Z	status:HEALTHY	latency:648.339	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:58:41Z	status:UNKNOWN	latency:17.279	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:38.258	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53496	target_addr:172.64.147.104:443
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:72.475	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52014	target_addr:104.21.86.125:443
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:73.932	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49650	target_addr:104.21.26.208:443
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:115.841	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52124	target_addr:172.67.219.211:443
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:232.563	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:294.146	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:605.973	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:58:41Z	status:HEALTHY	latency:628.663	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T02:58:41Z	status:FAILURE	latency:635.757	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:03:41Z	status:UNKNOWN	latency:8.358	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:19.655	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56216	target_addr:172.64.147.104:443
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:92.331	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56302	target_addr:172.67.168.140:443
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:91.994	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46676	target_addr:172.67.219.211:443
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:254.633	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:341.541	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37016	target_addr:104.21.86.125:443
time:2026-09-29T03:03:41Z	status:FAILURE	latency:380.397	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:956.761	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:1013.346	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:03:41Z	status:HEALTHY	latency:1532.842	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:08:41Z	status:UNKNOWN	latency:8.553	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:11.881	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41250	target_addr:172.64.147.104:443
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:71.790	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49388	target_addr:104.21.86.125:443
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:77.131	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40274	target_addr:104.21.26.208:443
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:79.187	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49404	target_addr:104.21.86.125:443
time:2026-09-29T03:08:41Z	status:FAILURE	latency:207.036	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:247.419	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:963.923	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:1090.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:08:41Z	status:HEALTHY	latency:1404.885	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:13:41Z	status:UNKNOWN	latency:7.631	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:18.009	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40848	target_addr:104.18.40.152:443
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:94.745	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51842	target_addr:172.67.168.140:443
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:97.657	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34442	target_addr:104.21.86.125:443
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:154.768	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53616	target_addr:172.67.219.211:443
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:243.741	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:13:41Z	status:FAILURE	latency:720.402	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:758.524	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:1154.623	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:13:41Z	status:HEALTHY	latency:5770.296	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:18:41Z	status:UNKNOWN	latency:9.324	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:13.574	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51738	target_addr:172.64.147.104:443
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:80.493	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43630	target_addr:172.67.219.211:443
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:95.670	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36470	target_addr:104.21.86.125:443
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:158.615	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39008	target_addr:104.21.26.208:443
time:2026-09-29T03:18:41Z	status:FAILURE	latency:196.822	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:822.833	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:1025.005	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:1135.669	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:18:41Z	status:HEALTHY	latency:1367.963	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:23:41Z	status:UNKNOWN	latency:8.808	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:13.158	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35850	target_addr:172.64.147.104:443
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:106.266	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46474	target_addr:172.67.219.211:443
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:161.303	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34338	target_addr:172.67.168.140:443
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:163.982	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38902	target_addr:104.21.86.125:443
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:204.673	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:23:41Z	status:FAILURE	latency:440.493	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:1013.645	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:1213.549	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:23:41Z	status:HEALTHY	latency:1910.719	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:28:41Z	status:UNKNOWN	latency:8.558	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:17.874	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59120	target_addr:104.18.40.152:443
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:72.240	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34456	target_addr:104.21.86.125:443
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:86.862	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57900	target_addr:172.67.168.140:443
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:152.408	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38270	target_addr:172.67.219.211:443
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:221.281	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:28:41Z	status:FAILURE	latency:267.343	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:905.575	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:1106.895	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:28:41Z	status:HEALTHY	latency:4125.685	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:15.124	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40698	target_addr:172.64.147.104:443
time:2026-09-29T03:33:41Z	status:UNKNOWN	latency:36.382	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:84.798	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45042	target_addr:172.67.219.211:443
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:89.563	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57564	target_addr:104.21.26.208:443
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:100.899	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45040	target_addr:172.67.219.211:443
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:206.180	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:33:41Z	status:FAILURE	latency:875.534	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:1091.291	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:1269.320	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:33:41Z	status:HEALTHY	latency:1271.070	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:38:41Z	status:UNKNOWN	latency:8.150	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:31.904	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35720	target_addr:172.64.147.104:443
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:150.652	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58988	target_addr:104.21.86.125:443
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:150.960	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58982	target_addr:104.21.86.125:443
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:164.000	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60904	target_addr:104.21.26.208:443
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:230.185	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:635.828	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:38:41Z	status:FAILURE	latency:720.866	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:794.866	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:38:41Z	status:HEALTHY	latency:1402.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:43:41Z	status:UNKNOWN	latency:8.659	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:14.519	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37812	target_addr:172.64.147.104:443
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:69.879	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35302	target_addr:172.67.168.140:443
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:75.578	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57276	target_addr:104.21.86.125:443
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:157.456	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39946	target_addr:172.67.219.211:443
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:227.532	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:43:41Z	status:FAILURE	latency:445.019	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:729.227	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:754.792	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:43:41Z	status:HEALTHY	latency:980.777	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:48:41Z	status:UNKNOWN	latency:8.106	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:14.415	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52982	target_addr:172.64.147.104:443
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:83.732	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55214	target_addr:172.67.219.211:443
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:138.167	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:160.364	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53964	target_addr:172.67.168.140:443
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:197.553	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41540	target_addr:104.21.86.125:443
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:286.080	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:482.686	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:48:41Z	status:HEALTHY	latency:602.944	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:48:41Z	status:FAILURE	latency:742.379	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:53:41Z	status:UNKNOWN	latency:8.438	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:12.751	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50566	target_addr:172.64.147.104:443
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:69.803	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53232	target_addr:104.21.26.208:443
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:74.515	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50342	target_addr:172.67.219.211:443
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:155.079	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50352	target_addr:172.67.219.211:443
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:233.027	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:333.058	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:53:41Z	status:FAILURE	latency:427.589	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:437.261	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:53:41Z	status:HEALTHY	latency:925.958	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:58:41Z	status:UNKNOWN	latency:8.888	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:14.854	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45534	target_addr:172.64.147.104:443
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:92.697	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60998	target_addr:104.21.86.125:443
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:93.199	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32772	target_addr:104.21.86.125:443
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:100.729	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41650	target_addr:172.67.168.140:443
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:232.468	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:58:41Z	status:FAILURE	latency:361.968	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:1045.519	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:1138.869	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T03:58:41Z	status:HEALTHY	latency:2815.192	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:03:41Z	status:UNKNOWN	latency:6.730	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:13.385	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41572	target_addr:172.64.147.104:443
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:69.944	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35518	target_addr:104.21.86.125:443
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:107.764	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39582	target_addr:172.67.219.211:443
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:160.030	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47834	target_addr:104.21.26.208:443
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:434.756	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:03:41Z	status:FAILURE	latency:517.005	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:756.304	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:812.241	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:03:41Z	status:HEALTHY	latency:11086.323	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:08:41Z	status:UNKNOWN	latency:10.430	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:14.705	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58338	target_addr:172.64.147.104:443
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:158.111	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38320	target_addr:104.21.86.125:443
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:172.341	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38324	target_addr:104.21.86.125:443
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:304.110	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:08:41Z	status:FAILURE	latency:386.541	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:780.565	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:1191.072	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:5168.783	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54766	target_addr:104.21.26.208:443
time:2026-09-29T04:08:41Z	status:HEALTHY	latency:5897.222	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:13:41Z	status:UNKNOWN	latency:7.499	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:70.764	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33386	target_addr:104.21.86.125:443
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:93.801	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33396	target_addr:104.21.86.125:443
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:180.212	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59898	target_addr:104.18.40.152:443
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:234.290	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35930	target_addr:172.67.168.140:443
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:294.798	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:13:41Z	status:FAILURE	latency:370.055	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:716.084	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:725.314	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:13:41Z	status:HEALTHY	latency:1200.573	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:18:41Z	status:UNKNOWN	latency:7.928	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:72.152	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54654	target_addr:104.21.26.208:443
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:159.215	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52096	target_addr:172.67.219.211:443
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:209.495	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50802	target_addr:104.21.86.125:443
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:287.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37660	target_addr:172.64.147.104:443
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:367.851	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:391.798	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:631.473	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:18:41Z	status:HEALTHY	latency:716.678	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:18:41Z	status:FAILURE	latency:4641.636	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:23:41Z	status:UNKNOWN	latency:7.919	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:9.856	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52544	target_addr:104.18.40.152:443
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:93.387	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57618	target_addr:104.21.86.125:443
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:152.876	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57614	target_addr:104.21.86.125:443
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:159.663	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43802	target_addr:104.21.26.208:443
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:219.083	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:594.800	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:23:41Z	status:FAILURE	latency:663.490	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:1164.381	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:23:41Z	status:HEALTHY	latency:3208.073	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:28:41Z	status:UNKNOWN	latency:7.158	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:11.721	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55654	target_addr:172.64.147.104:443
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:83.784	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41828	target_addr:172.67.168.140:443
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:91.028	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48800	target_addr:172.67.219.211:443
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:103.785	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48816	target_addr:172.67.219.211:443
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:263.093	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:28:41Z	status:FAILURE	latency:697.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:726.418	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:834.869	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:28:41Z	status:HEALTHY	latency:1039.452	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:33:41Z	status:UNKNOWN	latency:9.075	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:12.629	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59332	target_addr:104.18.40.152:443
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:67.470	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46494	target_addr:104.21.26.208:443
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:93.519	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46428	target_addr:172.67.219.211:443
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:93.684	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46422	target_addr:172.67.219.211:443
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:251.892	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:33:41Z	status:FAILURE	latency:420.485	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:671.952	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:991.817	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:33:41Z	status:HEALTHY	latency:1170.690	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:12.087	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42648	target_addr:172.64.147.104:443
time:2026-09-29T04:38:41Z	status:UNKNOWN	latency:34.927	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:94.044	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43942	target_addr:172.67.219.211:443
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:95.754	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43938	target_addr:172.67.219.211:443
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:163.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52166	target_addr:104.21.26.208:443
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:279.753	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:38:41Z	status:FAILURE	latency:613.233	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:762.829	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:1004.451	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:38:41Z	status:HEALTHY	latency:1316.574	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:43:41Z	status:UNKNOWN	latency:6.818	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:10.574	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58572	target_addr:172.64.147.104:443
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:79.728	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59370	target_addr:172.67.219.211:443
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:90.538	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41196	target_addr:104.21.86.125:443
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:153.699	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49106	target_addr:104.21.26.208:443
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:213.433	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:43:41Z	status:FAILURE	latency:267.973	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:800.964	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:850.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:43:41Z	status:HEALTHY	latency:1015.847	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:48:41Z	status:UNKNOWN	latency:11.296	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:14.696	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35402	target_addr:172.64.147.104:443
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:72.747	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41814	target_addr:172.67.168.140:443
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:91.521	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53732	target_addr:104.21.86.125:443
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:151.140	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53730	target_addr:104.21.86.125:443
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:287.087	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:48:41Z	status:FAILURE	latency:650.527	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:1007.908	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:1028.362	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:48:41Z	status:HEALTHY	latency:3055.185	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:53:41Z	status:UNKNOWN	latency:8.351	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:12.037	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54272	target_addr:172.64.147.104:443
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:86.584	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54916	target_addr:104.21.26.208:443
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:96.783	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59268	target_addr:104.21.86.125:443
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:164.780	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51980	target_addr:172.67.219.211:443
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:181.314	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:53:41Z	status:FAILURE	latency:246.391	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:764.333	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:962.732	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:53:41Z	status:HEALTHY	latency:1121.615	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:11.042	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38722	target_addr:172.64.147.104:443
time:2026-09-29T04:58:41Z	status:UNKNOWN	latency:37.606	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:71.216	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58978	target_addr:104.21.86.125:443
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:73.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44474	target_addr:172.67.168.140:443
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:194.176	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58986	target_addr:104.21.86.125:443
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:216.482	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:58:41Z	status:FAILURE	latency:504.994	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:670.236	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:694.158	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T04:58:41Z	status:HEALTHY	latency:1819.787	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:03:41Z	status:UNKNOWN	latency:8.761	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:10.262	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40038	target_addr:104.18.40.152:443
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:162.685	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57896	target_addr:172.67.219.211:443
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:218.689	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:03:41Z	status:FAILURE	latency:257.714	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:1083.072	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59062	target_addr:104.21.86.125:443
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:1090.092	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57280	target_addr:104.21.26.208:443
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:1136.560	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:1554.672	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:03:41Z	status:HEALTHY	latency:11351.330	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:08:41Z	status:UNKNOWN	latency:9.195	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:18.210	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60234	target_addr:172.64.147.104:443
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:69.319	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33390	target_addr:172.67.168.140:443
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:77.365	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52858	target_addr:172.67.219.211:443
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:158.913	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49180	target_addr:104.21.86.125:443
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:214.998	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:08:41Z	status:FAILURE	latency:661.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:802.940	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:844.991	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:08:41Z	status:HEALTHY	latency:1102.040	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:13:41Z	status:UNKNOWN	latency:7.758	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:13.091	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55730	target_addr:104.18.40.152:443
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:86.818	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38204	target_addr:172.67.219.211:443
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:156.006	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38200	target_addr:172.67.219.211:443
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:157.903	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43726	target_addr:172.67.168.140:443
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:230.410	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:13:41Z	status:FAILURE	latency:518.371	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:679.658	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:687.643	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:13:41Z	status:HEALTHY	latency:1021.895	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:18:41Z	status:UNKNOWN	latency:6.950	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:13.003	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57754	target_addr:172.64.147.104:443
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:76.472	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55548	target_addr:172.67.168.140:443
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:83.420	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41250	target_addr:104.21.86.125:443
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:85.107	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35300	target_addr:172.67.219.211:443
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:236.244	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:18:41Z	status:FAILURE	latency:439.094	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:768.947	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:796.301	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:18:41Z	status:HEALTHY	latency:806.786	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:23:42Z	status:UNKNOWN	latency:9.107	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:13.587	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55986	target_addr:104.18.40.152:443
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:90.989	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38580	target_addr:172.67.168.140:443
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:155.055	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59998	target_addr:172.67.219.211:443
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:193.605	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59988	target_addr:172.67.219.211:443
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:219.652	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:23:42Z	status:FAILURE	latency:774.198	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:1186.316	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:1306.038	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:23:42Z	status:HEALTHY	latency:1513.104	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:28:42Z	status:UNKNOWN	latency:8.002	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:13.243	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34028	target_addr:172.64.147.104:443
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:76.312	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57996	target_addr:172.67.168.140:443
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:90.252	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36882	target_addr:172.67.219.211:443
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:155.622	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36886	target_addr:172.67.219.211:443
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:237.850	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:28:42Z	status:FAILURE	latency:789.419	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:1036.136	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:1237.874	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:28:42Z	status:HEALTHY	latency:2112.339	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:33:42Z	status:UNKNOWN	latency:8.255	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:11.501	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40720	target_addr:104.18.40.152:443
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:74.417	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50362	target_addr:104.21.86.125:443
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:91.626	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45294	target_addr:172.67.219.211:443
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:93.090	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53342	target_addr:172.67.168.140:443
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:200.755	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:33:42Z	status:FAILURE	latency:245.300	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:720.809	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:814.905	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:33:42Z	status:HEALTHY	latency:5660.285	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:38:42Z	status:UNKNOWN	latency:8.676	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:15.527	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60962	target_addr:104.18.40.152:443
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:78.578	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59214	target_addr:172.67.168.140:443
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:86.798	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57536	target_addr:172.67.219.211:443
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:91.860	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45368	target_addr:104.21.86.125:443
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:245.656	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:38:42Z	status:FAILURE	latency:572.823	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:1046.459	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:1142.268	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:38:42Z	status:HEALTHY	latency:5774.574	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:43:42Z	status:UNKNOWN	latency:7.208	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:10.179	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51422	target_addr:172.64.147.104:443
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:73.580	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48862	target_addr:172.67.219.211:443
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:83.693	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40850	target_addr:104.21.26.208:443
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:84.994	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48860	target_addr:172.67.219.211:443
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:235.608	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:43:42Z	status:FAILURE	latency:382.078	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:945.239	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:1292.208	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:43:42Z	status:HEALTHY	latency:1972.807	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:48:42Z	status:UNKNOWN	latency:7.917	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:12.782	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49594	target_addr:104.18.40.152:443
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:152.585	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35354	target_addr:172.67.219.211:443
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:155.813	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49406	target_addr:104.21.26.208:443
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:165.077	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33694	target_addr:104.21.86.125:443
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:222.888	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:48:42Z	status:FAILURE	latency:472.163	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:743.038	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:1002.080	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:48:42Z	status:HEALTHY	latency:1056.883	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:11.352	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33428	target_addr:172.64.147.104:443
time:2026-09-29T05:53:42Z	status:UNKNOWN	latency:21.765	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:105.057	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42366	target_addr:172.67.219.211:443
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:118.139	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:159.189	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42360	target_addr:172.67.219.211:443
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:159.851	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32956	target_addr:172.67.168.140:443
time:2026-09-29T05:53:42Z	status:FAILURE	latency:600.738	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:775.785	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:798.859	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:53:42Z	status:HEALTHY	latency:798.910	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:10.293	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33910	target_addr:104.18.40.152:443
time:2026-09-29T05:58:42Z	status:UNKNOWN	latency:34.330	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:83.815	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50722	target_addr:104.21.26.208:443
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:87.609	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42780	target_addr:104.21.86.125:443
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:113.687	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:161.117	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42770	target_addr:104.21.86.125:443
time:2026-09-29T05:58:42Z	status:FAILURE	latency:207.249	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:673.476	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:1300.712	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T05:58:42Z	status:HEALTHY	latency:1693.447	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:03:42Z	status:UNKNOWN	latency:9.250	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:17.024	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44440	target_addr:172.64.147.104:443
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:76.177	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39260	target_addr:104.21.86.125:443
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:77.325	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39246	target_addr:104.21.86.125:443
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:90.904	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38854	target_addr:104.21.26.208:443
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:254.996	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:677.443	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:03:42Z	status:FAILURE	latency:681.549	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:1096.895	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:03:42Z	status:HEALTHY	latency:1124.981	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:14.762	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36226	target_addr:172.64.147.104:443
time:2026-09-29T06:08:42Z	status:UNKNOWN	latency:38.397	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:69.675	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49236	target_addr:172.67.168.140:443
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:81.289	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55978	target_addr:104.21.86.125:443
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:140.695	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55994	target_addr:104.21.86.125:443
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:239.921	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:08:42Z	status:FAILURE	latency:275.118	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:721.937	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:1089.737	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:08:42Z	status:HEALTHY	latency:1414.752	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:13:42Z	status:UNKNOWN	latency:6.254	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:24.809	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49464	target_addr:104.18.40.152:443
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:67.118	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36020	target_addr:104.21.86.125:443
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:85.831	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39098	target_addr:172.67.168.140:443
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:157.608	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36034	target_addr:104.21.86.125:443
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:195.160	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:13:42Z	status:FAILURE	latency:466.027	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:692.677	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:695.764	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:13:42Z	status:HEALTHY	latency:799.711	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:18:42Z	status:UNKNOWN	latency:6.201	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:12.427	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54134	target_addr:172.64.147.104:443
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:87.683	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38644	target_addr:172.67.168.140:443
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:87.666	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45100	target_addr:104.21.86.125:443
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:154.627	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60794	target_addr:172.67.219.211:443
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:265.526	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:18:42Z	status:FAILURE	latency:272.802	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:1085.425	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:1202.935	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:18:42Z	status:HEALTHY	latency:1302.941	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:23:42Z	status:UNKNOWN	latency:8.450	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:9.348	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39628	target_addr:172.64.147.104:443
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:89.581	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59326	target_addr:172.67.219.211:443
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:162.129	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42812	target_addr:172.67.168.140:443
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:185.361	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53398	target_addr:104.21.86.125:443
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:241.048	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:23:42Z	status:FAILURE	latency:461.102	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:786.739	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:866.891	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:23:42Z	status:HEALTHY	latency:2195.202	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:28:42Z	status:UNKNOWN	latency:6.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:10.659	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58750	target_addr:172.64.147.104:443
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:81.746	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43696	target_addr:172.67.219.211:443
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:89.351	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35180	target_addr:104.21.86.125:443
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:90.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41700	target_addr:172.67.168.140:443
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:290.764	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:28:42Z	status:FAILURE	latency:639.533	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:684.691	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:757.265	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:28:42Z	status:HEALTHY	latency:985.953	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:15.731	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36502	target_addr:104.18.40.152:443
time:2026-09-29T06:33:42Z	status:UNKNOWN	latency:35.112	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:90.954	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36346	target_addr:172.67.219.211:443
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:91.582	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58286	target_addr:104.21.86.125:443
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:157.694	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60316	target_addr:104.21.26.208:443
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:181.412	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:33:42Z	status:FAILURE	latency:252.091	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:1029.151	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:1037.365	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:33:42Z	status:HEALTHY	latency:2536.194	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:11.911	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52058	target_addr:104.18.40.152:443
time:2026-09-29T06:38:42Z	status:UNKNOWN	latency:34.872	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:74.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43256	target_addr:104.21.86.125:443
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:85.804	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33696	target_addr:104.21.26.208:443
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:155.199	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43266	target_addr:104.21.86.125:443
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:233.653	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:38:42Z	status:FAILURE	latency:750.304	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:1007.549	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:1014.862	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:38:42Z	status:HEALTHY	latency:1350.222	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:43:42Z	status:UNKNOWN	latency:7.089	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:8.580	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39704	target_addr:104.18.40.152:443
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:66.851	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44858	target_addr:104.21.86.125:443
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:165.097	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38120	target_addr:172.67.219.211:443
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:180.951	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57892	target_addr:104.21.26.208:443
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:217.630	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:43:42Z	status:FAILURE	latency:250.078	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:815.955	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:1048.694	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:43:42Z	status:HEALTHY	latency:5477.298	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:8.343	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43896	target_addr:104.18.40.152:443
time:2026-09-29T06:48:42Z	status:UNKNOWN	latency:35.409	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:92.323	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50304	target_addr:104.21.86.125:443
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:150.329	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39212	target_addr:104.21.26.208:443
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:150.774	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44084	target_addr:172.67.219.211:443
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:217.515	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:274.854	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:312.158	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:48:42Z	status:FAILURE	latency:410.379	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:48:42Z	status:HEALTHY	latency:660.174	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:53:42Z	status:UNKNOWN	latency:7.217	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:10.095	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53966	target_addr:104.18.40.152:443
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:84.109	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44170	target_addr:172.67.168.140:443
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:151.651	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38656	target_addr:104.21.86.125:443
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:151.750	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56202	target_addr:172.67.219.211:443
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:246.012	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:263.589	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:684.538	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:53:42Z	status:FAILURE	latency:1388.641	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:53:42Z	status:HEALTHY	latency:5650.809	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:58:42Z	status:UNKNOWN	latency:10.628	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:11.612	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44490	target_addr:104.18.40.152:443
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:71.811	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58912	target_addr:172.67.168.140:443
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:162.502	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47052	target_addr:104.21.86.125:443
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:201.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47054	target_addr:104.21.86.125:443
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:211.189	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:58:42Z	status:FAILURE	latency:425.582	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:675.694	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:1016.033	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T06:58:42Z	status:HEALTHY	latency:1288.485	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:03:42Z	status:UNKNOWN	latency:9.435	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:9.501	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51472	target_addr:172.64.147.104:443
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:70.007	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52552	target_addr:104.21.26.208:443
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:75.771	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56066	target_addr:172.67.219.211:443
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:151.484	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35606	target_addr:104.21.86.125:443
time:2026-09-29T07:03:42Z	status:FAILURE	latency:268.295	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:439.807	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:931.614	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:1322.714	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:03:42Z	status:HEALTHY	latency:1331.219	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:08:42Z	status:UNKNOWN	latency:7.379	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:9.001	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51010	target_addr:104.18.40.152:443
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:76.012	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37686	target_addr:172.67.168.140:443
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:83.144	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53024	target_addr:172.67.219.211:443
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:91.980	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53014	target_addr:172.67.219.211:443
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:196.320	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:08:42Z	status:FAILURE	latency:414.063	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:795.194	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:1155.188	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:08:42Z	status:HEALTHY	latency:2589.378	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:13:42Z	status:UNKNOWN	latency:8.276	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:11.700	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37966	target_addr:172.64.147.104:443
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:85.302	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44038	target_addr:172.67.219.211:443
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:94.403	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40818	target_addr:172.67.168.140:443
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:97.590	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44054	target_addr:172.67.219.211:443
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:260.728	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:13:42Z	status:FAILURE	latency:557.526	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:773.569	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:970.983	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:13:42Z	status:HEALTHY	latency:4689.039	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:18:42Z	status:UNKNOWN	latency:8.282	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:10.431	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34578	target_addr:172.64.147.104:443
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:83.661	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42218	target_addr:172.67.219.211:443
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:92.960	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42230	target_addr:172.67.219.211:443
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:93.527	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33138	target_addr:104.21.26.208:443
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:236.576	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:18:42Z	status:FAILURE	latency:566.241	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:1029.065	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:1088.132	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:18:42Z	status:HEALTHY	latency:1105.214	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:23:42Z	status:UNKNOWN	latency:7.473	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:11.247	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40582	target_addr:104.18.40.152:443
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:75.852	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40018	target_addr:172.67.168.140:443
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:82.896	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34390	target_addr:172.67.219.211:443
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:83.152	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34380	target_addr:172.67.219.211:443
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:225.942	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:23:42Z	status:FAILURE	latency:347.250	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:738.294	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:811.431	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:23:42Z	status:HEALTHY	latency:1260.644	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:28:42Z	status:UNKNOWN	latency:7.398	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:10.313	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48178	target_addr:172.64.147.104:443
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:71.821	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46438	target_addr:172.67.219.211:443
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:90.354	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35822	target_addr:104.21.86.125:443
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:160.565	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53738	target_addr:172.67.168.140:443
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:270.572	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:28:42Z	status:FAILURE	latency:450.150	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:682.646	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:707.406	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:28:42Z	status:HEALTHY	latency:3270.814	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:10.554	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40702	target_addr:172.64.147.104:443
time:2026-09-29T07:33:42Z	status:UNKNOWN	latency:18.192	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:73.338	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34334	target_addr:104.21.86.125:443
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:78.337	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34332	target_addr:104.21.86.125:443
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:149.858	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46566	target_addr:104.21.26.208:443
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:199.127	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:33:42Z	status:FAILURE	latency:204.311	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:620.972	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:660.762	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:33:42Z	status:HEALTHY	latency:1044.178	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:38:42Z	status:UNKNOWN	latency:7.227	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:33.826	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55110	target_addr:104.18.40.152:443
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:94.130	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53072	target_addr:104.21.86.125:443
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:103.899	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40568	target_addr:172.67.168.140:443
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:156.214	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46600	target_addr:172.67.219.211:443
time:2026-09-29T07:38:42Z	status:FAILURE	latency:211.746	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:275.745	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:766.255	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:783.644	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:38:42Z	status:HEALTHY	latency:1152.914	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:43:42Z	status:UNKNOWN	latency:7.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:15.499	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38398	target_addr:172.64.147.104:443
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:74.778	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42200	target_addr:104.21.26.208:443
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:90.749	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38962	target_addr:172.67.219.211:443
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:98.645	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36622	target_addr:104.21.86.125:443
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:310.193	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:43:42Z	status:FAILURE	latency:492.223	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:786.225	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:797.655	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:43:42Z	status:HEALTHY	latency:932.323	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:48:42Z	status:UNKNOWN	latency:6.918	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:10.189	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40074	target_addr:172.64.147.104:443
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:83.150	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57334	target_addr:172.67.219.211:443
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:153.447	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57340	target_addr:172.67.219.211:443
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:155.712	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33006	target_addr:104.21.26.208:443
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:235.671	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:48:42Z	status:FAILURE	latency:453.780	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:815.708	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:848.196	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:48:42Z	status:HEALTHY	latency:1336.112	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:53:42Z	status:UNKNOWN	latency:9.986	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:14.518	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51916	target_addr:172.64.147.104:443
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:69.472	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49552	target_addr:172.67.168.140:443
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:167.594	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52320	target_addr:104.21.86.125:443
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:213.948	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:762.676	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:866.503	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:867.100	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:53:42Z	status:HEALTHY	latency:1166.830	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52334	target_addr:104.21.86.125:443
time:2026-09-29T07:53:42Z	status:FAILURE	latency:1623.339	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:58:42Z	status:UNKNOWN	latency:9.993	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:19.675	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37962	target_addr:104.18.40.152:443
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:74.263	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52240	target_addr:172.67.219.211:443
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:79.932	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52252	target_addr:172.67.219.211:443
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:162.148	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43794	target_addr:172.67.168.140:443
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:212.681	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:58:42Z	status:FAILURE	latency:416.637	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:683.853	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:1376.251	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T07:58:42Z	status:HEALTHY	latency:1644.563	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:03:42Z	status:UNKNOWN	latency:8.897	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:12.830	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49900	target_addr:172.64.147.104:443
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:90.563	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36334	target_addr:104.21.86.125:443
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:156.233	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36332	target_addr:104.21.86.125:443
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:157.007	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60754	target_addr:104.21.26.208:443
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:261.065	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:03:42Z	status:FAILURE	latency:480.845	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:573.359	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:713.901	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:03:42Z	status:HEALTHY	latency:1010.559	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:08:42Z	status:UNKNOWN	latency:10.988	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:45.877	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47106	target_addr:104.18.40.152:443
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:76.816	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52690	target_addr:104.21.26.208:443
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:95.067	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37012	target_addr:104.21.86.125:443
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:164.767	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56294	target_addr:172.67.219.211:443
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:394.812	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:08:42Z	status:FAILURE	latency:659.897	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:1003.405	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:1039.160	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:08:42Z	status:HEALTHY	latency:2357.294	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:13:42Z	status:UNKNOWN	latency:6.981	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:11.679	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33582	target_addr:172.64.147.104:443
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:91.225	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34344	target_addr:104.21.86.125:443
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:91.371	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53136	target_addr:104.21.26.208:443
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:157.893	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41292	target_addr:172.67.219.211:443
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:191.450	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:13:42Z	status:FAILURE	latency:520.794	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:962.035	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:1048.136	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:13:42Z	status:HEALTHY	latency:1196.202	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:18:42Z	status:UNKNOWN	latency:8.553	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:10.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59590	target_addr:104.18.40.152:443
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:77.094	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49094	target_addr:172.67.219.211:443
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:90.648	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56596	target_addr:104.21.86.125:443
time:2026-09-29T08:18:42Z	status:FAILURE	latency:201.184	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:284.606	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:534.379	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48422	target_addr:104.21.26.208:443
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:660.368	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:1031.753	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:18:42Z	status:HEALTHY	latency:1344.516	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:23:42Z	status:UNKNOWN	latency:37.765	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:51.767	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49050	target_addr:172.64.147.104:443
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:70.826	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34240	target_addr:104.21.86.125:443
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:90.642	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52390	target_addr:172.67.168.140:443
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:168.265	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34248	target_addr:104.21.86.125:443
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:223.864	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:23:42Z	status:FAILURE	latency:384.938	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:783.308	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:788.690	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:23:42Z	status:HEALTHY	latency:1005.566	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:28:42Z	status:UNKNOWN	latency:7.171	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:10.094	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44140	target_addr:172.64.147.104:443
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:76.025	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38104	target_addr:172.67.168.140:443
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:82.651	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56756	target_addr:172.67.219.211:443
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:92.082	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56768	target_addr:172.67.219.211:443
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:221.096	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:955.311	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:1058.069	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:28:42Z	status:FAILURE	latency:1192.506	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:28:42Z	status:HEALTHY	latency:2158.391	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:33:42Z	status:UNKNOWN	latency:7.955	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:12.929	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34788	target_addr:172.64.147.104:443
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:67.182	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50640	target_addr:104.21.86.125:443
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:69.257	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50652	target_addr:104.21.86.125:443
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:151.281	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55662	target_addr:172.67.168.140:443
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:235.321	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:33:42Z	status:FAILURE	latency:395.719	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:1109.017	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:1109.112	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:33:42Z	status:HEALTHY	latency:1401.503	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:38:42Z	status:UNKNOWN	latency:6.404	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:10.375	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45308	target_addr:104.18.40.152:443
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:69.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57796	target_addr:172.67.219.211:443
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:73.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35740	target_addr:104.21.26.208:443
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:168.440	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57798	target_addr:172.67.219.211:443
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:192.907	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:38:42Z	status:FAILURE	latency:363.990	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:751.024	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:754.979	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:38:42Z	status:HEALTHY	latency:985.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:43:42Z	status:UNKNOWN	latency:8.522	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:11.262	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38808	target_addr:104.18.40.152:443
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:75.342	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51996	target_addr:104.21.86.125:443
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:89.237	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51992	target_addr:104.21.86.125:443
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:92.059	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40118	target_addr:172.67.168.140:443
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:235.366	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:43:42Z	status:FAILURE	latency:267.897	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:701.788	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:823.127	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:43:42Z	status:HEALTHY	latency:1067.872	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:48:42Z	status:UNKNOWN	latency:6.680	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:12.812	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39982	target_addr:172.64.147.104:443
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:89.770	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55134	target_addr:104.21.86.125:443
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:90.801	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42722	target_addr:172.67.168.140:443
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:151.352	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54902	target_addr:172.67.219.211:443
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:195.701	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:48:42Z	status:FAILURE	latency:638.356	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:1101.400	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:1529.983	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:48:42Z	status:HEALTHY	latency:1565.390	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:53:42Z	status:UNKNOWN	latency:7.559	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:9.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54540	target_addr:172.64.147.104:443
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:72.259	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53802	target_addr:172.67.168.140:443
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:124.481	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43570	target_addr:104.21.86.125:443
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:198.802	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:53:42Z	status:FAILURE	latency:498.362	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:940.644	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:949.152	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:1189.444	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38084	target_addr:172.67.219.211:443
time:2026-09-29T08:53:42Z	status:HEALTHY	latency:1621.323	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:58:42Z	status:UNKNOWN	latency:6.665	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:10.214	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49048	target_addr:104.18.40.152:443
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:66.474	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41840	target_addr:172.67.219.211:443
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:77.046	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50576	target_addr:104.21.86.125:443
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:92.957	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56526	target_addr:172.67.168.140:443
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:238.456	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:58:42Z	status:FAILURE	latency:644.622	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:943.545	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:3831.734	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T08:58:42Z	status:HEALTHY	latency:5779.940	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:9.334	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39012	target_addr:104.18.40.152:443
time:2026-09-29T09:03:42Z	status:UNKNOWN	latency:35.741	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:70.048	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49990	target_addr:172.67.219.211:443
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:89.794	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49976	target_addr:172.67.219.211:443
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:91.161	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55150	target_addr:172.67.168.140:443
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:93.622	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:03:42Z	status:FAILURE	latency:224.255	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:912.960	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:1071.161	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:03:42Z	status:HEALTHY	latency:5711.094	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:08:42Z	status:UNKNOWN	latency:7.821	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:9.055	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58338	target_addr:104.18.40.152:443
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:78.237	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52062	target_addr:172.67.168.140:443
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:151.087	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57398	target_addr:172.67.219.211:443
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:164.532	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60372	target_addr:104.21.86.125:443
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:238.614	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:08:42Z	status:FAILURE	latency:399.061	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:730.253	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:864.985	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:08:42Z	status:HEALTHY	latency:1068.664	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:12.806	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60348	target_addr:104.18.40.152:443
time:2026-09-29T09:13:42Z	status:UNKNOWN	latency:39.238	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:71.320	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59946	target_addr:172.67.219.211:443
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:73.411	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59920	target_addr:104.21.26.208:443
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:151.533	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36720	target_addr:104.21.86.125:443
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:208.819	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:13:42Z	status:FAILURE	latency:246.845	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:820.841	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:820.462	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:13:42Z	status:HEALTHY	latency:821.604	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:18:42Z	status:UNKNOWN	latency:8.130	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:20.647	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42646	target_addr:104.18.40.152:443
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:86.795	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49454	target_addr:104.21.86.125:443
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:90.967	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59366	target_addr:172.67.168.140:443
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:154.399	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49464	target_addr:104.21.86.125:443
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:255.737	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:18:42Z	status:FAILURE	latency:337.124	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:829.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:837.354	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:18:42Z	status:HEALTHY	latency:839.732	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:23:42Z	status:UNKNOWN	latency:9.656	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:9.144	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50174	target_addr:172.64.147.104:443
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:74.025	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60768	target_addr:172.67.168.140:443
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:158.676	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53962	target_addr:104.21.86.125:443
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:163.468	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35256	target_addr:172.67.219.211:443
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:209.012	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:23:42Z	status:FAILURE	latency:656.592	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:745.510	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:1010.657	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:23:42Z	status:HEALTHY	latency:5694.820	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:28:42Z	status:UNKNOWN	latency:7.989	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:11.509	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44970	target_addr:104.18.40.152:443
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:68.946	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39584	target_addr:104.21.26.208:443
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:91.024	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47222	target_addr:172.67.219.211:443
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:98.557	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47226	target_addr:172.67.219.211:443
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:197.964	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:28:42Z	status:FAILURE	latency:476.259	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:810.972	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:1042.617	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:28:42Z	status:HEALTHY	latency:2592.988	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:33:42Z	status:UNKNOWN	latency:8.666	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:33:42Z	status:HEALTHY	latency:34.582	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59142	target_addr:172.64.147.104:443
time:2026-09-29T09:33:42Z	status:HEALTHY	latency:67.947	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41274	target_addr:172.67.219.211:443
time:2026-09-29T09:33:42Z	status:HEALTHY	latency:94.428	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44260	target_addr:104.21.26.208:443
time:2026-09-29T09:33:42Z	status:HEALTHY	latency:233.168	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:33:42Z	status:FAILURE	latency:678.280	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:33:42Z	status:HEALTHY	latency:1029.714	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:33:43Z	status:HEALTHY	latency:1064.041	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:33:43Z	status:HEALTHY	latency:1191.949	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34564	target_addr:104.21.86.125:443
time:2026-09-29T09:33:42Z	status:HEALTHY	latency:1301.289	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:38:42Z	status:UNKNOWN	latency:8.449	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:38:42Z	status:HEALTHY	latency:12.390	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47226	target_addr:104.18.40.152:443
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:89.519	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39154	target_addr:172.67.168.140:443
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:150.877	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51044	target_addr:104.21.86.125:443
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:165.198	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51054	target_addr:104.21.86.125:443
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:223.746	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:38:43Z	status:FAILURE	latency:645.018	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:816.711	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:1082.677	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:38:43Z	status:HEALTHY	latency:5699.904	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:9.947	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33756	target_addr:172.64.147.104:443
time:2026-09-29T09:43:43Z	status:UNKNOWN	latency:38.088	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:89.413	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56158	target_addr:172.67.219.211:443
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:90.426	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50580	target_addr:104.21.86.125:443
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:150.068	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45810	target_addr:172.67.168.140:443
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:189.086	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:43:43Z	status:FAILURE	latency:467.715	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:689.820	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:787.323	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:43:43Z	status:HEALTHY	latency:1324.791	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:48:43Z	status:UNKNOWN	latency:14.343	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:18.433	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33274	target_addr:172.64.147.104:443
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:87.934	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49172	target_addr:172.67.168.140:443
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:172.078	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54106	target_addr:172.67.219.211:443
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:176.494	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54118	target_addr:172.67.219.211:443
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:253.867	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:48:43Z	status:FAILURE	latency:518.831	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:1061.755	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:1094.675	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:48:43Z	status:HEALTHY	latency:8355.014	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:53:43Z	status:UNKNOWN	latency:12.313	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:19.162	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33510	target_addr:104.18.40.152:443
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:71.862	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52100	target_addr:104.21.26.208:443
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:99.656	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42794	target_addr:172.67.219.211:443
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:107.026	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58468	target_addr:104.21.86.125:443
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:203.434	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:53:43Z	status:FAILURE	latency:401.628	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:1482.890	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:1529.578	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:53:43Z	status:HEALTHY	latency:5561.487	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:58:43Z	status:UNKNOWN	latency:7.488	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:13.521	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36424	target_addr:104.18.40.152:443
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:66.738	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41606	target_addr:172.67.219.211:443
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:70.208	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53486	target_addr:104.21.86.125:443
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:154.645	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44298	target_addr:172.67.168.140:443
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:232.520	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:58:43Z	status:FAILURE	latency:576.019	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:1066.842	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:1358.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T09:58:43Z	status:HEALTHY	latency:1751.883	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:12.864	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42558	target_addr:104.18.40.152:443
time:2026-09-29T10:03:43Z	status:UNKNOWN	latency:18.265	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:72.515	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43572	target_addr:104.21.86.125:443
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:72.522	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60580	target_addr:172.67.168.140:443
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:92.094	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43570	target_addr:104.21.86.125:443
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:253.289	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:03:43Z	status:FAILURE	latency:431.878	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:744.638	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:1041.118	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:03:43Z	status:HEALTHY	latency:2279.873	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:08:43Z	status:UNKNOWN	latency:36.261	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:38.925	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46292	target_addr:172.64.147.104:443
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:82.632	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45924	target_addr:104.21.26.208:443
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:153.071	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51162	target_addr:104.21.86.125:443
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:157.161	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51146	target_addr:104.21.86.125:443
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:242.661	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:668.549	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:726.991	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:08:43Z	status:FAILURE	latency:1306.404	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:08:43Z	status:HEALTHY	latency:37183.817	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:13:43Z	status:UNKNOWN	latency:8.866	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:27.418	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59034	target_addr:172.64.147.104:443
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:66.578	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48402	target_addr:104.21.26.208:443
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:114.153	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57768	target_addr:104.21.86.125:443
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:185.437	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57756	target_addr:104.21.86.125:443
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:229.192	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:672.422	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:728.547	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:13:43Z	status:HEALTHY	latency:1059.250	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:13:43Z	status:FAILURE	latency:1616.088	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:18:43Z	status:UNKNOWN	latency:8.895	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:15.045	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40732	target_addr:104.18.40.152:443
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:68.689	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47690	target_addr:104.21.26.208:443
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:81.532	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47450	target_addr:104.21.86.125:443
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:92.136	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45050	target_addr:172.67.219.211:443
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:230.590	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:437.276	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:18:43Z	status:FAILURE	latency:475.218	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:947.738	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:18:43Z	status:HEALTHY	latency:2650.153	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:23:43Z	status:UNKNOWN	latency:7.297	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:10.111	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38404	target_addr:104.18.40.152:443
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:70.154	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56930	target_addr:172.67.219.211:443
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:71.908	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42452	target_addr:104.21.86.125:443
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:87.190	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48462	target_addr:104.21.26.208:443
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:211.187	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:817.417	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:997.600	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:23:43Z	status:HEALTHY	latency:1240.420	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:23:43Z	status:FAILURE	latency:1326.457	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:13.117	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37680	target_addr:172.64.147.104:443
time:2026-09-29T10:28:43Z	status:UNKNOWN	latency:37.164	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:68.983	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38860	target_addr:172.67.168.140:443
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:73.855	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42852	target_addr:172.67.219.211:443
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:90.828	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:104.21.86.125:443
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:210.806	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:28:43Z	status:FAILURE	latency:481.555	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:766.520	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:804.491	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:28:43Z	status:HEALTHY	latency:1027.236	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:33:43Z	status:UNKNOWN	latency:9.999	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:12.784	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58874	target_addr:172.64.147.104:443
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:70.764	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59178	target_addr:104.21.86.125:443
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:75.681	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42416	target_addr:172.67.168.140:443
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:89.198	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60396	target_addr:172.67.219.211:443
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:280.121	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:33:43Z	status:FAILURE	latency:375.931	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:644.500	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:698.871	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:33:43Z	status:HEALTHY	latency:874.793	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:38:43Z	status:UNKNOWN	latency:15.166	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:44.702	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40036	target_addr:172.64.147.104:443
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:66.440	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48506	target_addr:104.21.26.208:443
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:69.213	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40738	target_addr:172.67.219.211:443
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:89.943	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40726	target_addr:172.67.219.211:443
time:2026-09-29T10:38:43Z	status:FAILURE	latency:200.099	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:233.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:726.065	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:736.558	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:38:43Z	status:HEALTHY	latency:5638.605	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:43:43Z	status:UNKNOWN	latency:8.084	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:14.126	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49320	target_addr:172.64.147.104:443
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:70.091	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56520	target_addr:172.67.168.140:443
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:71.662	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60934	target_addr:104.21.86.125:443
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:91.069	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52460	target_addr:172.67.219.211:443
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:218.624	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:43:43Z	status:FAILURE	latency:559.893	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:717.962	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:776.308	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:43:43Z	status:HEALTHY	latency:993.115	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:48:43Z	status:UNKNOWN	latency:7.769	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:30.468	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52742	target_addr:172.64.147.104:443
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:67.538	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55986	target_addr:104.21.26.208:443
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:69.365	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54262	target_addr:104.21.86.125:443
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:90.296	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36268	target_addr:172.67.219.211:443
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:236.122	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:48:43Z	status:FAILURE	latency:278.440	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:693.054	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:698.605	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:48:43Z	status:HEALTHY	latency:699.921	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:53:43Z	status:UNKNOWN	latency:6.129	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:9.844	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43364	target_addr:104.18.40.152:443
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:66.366	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35036	target_addr:104.21.86.125:443
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:89.717	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35032	target_addr:104.21.86.125:443
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:89.993	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54554	target_addr:104.21.26.208:443
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:232.632	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:53:43Z	status:FAILURE	latency:453.489	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:722.216	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:723.992	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:53:43Z	status:HEALTHY	latency:744.119	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:58:43Z	status:UNKNOWN	latency:8.875	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:41.505	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39582	target_addr:104.18.40.152:443
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:69.764	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43956	target_addr:172.67.219.211:443
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:92.480	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43942	target_addr:172.67.219.211:443
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:93.550	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48274	target_addr:172.67.168.140:443
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:210.324	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:58:43Z	status:FAILURE	latency:317.950	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:721.495	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:761.550	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T10:58:43Z	status:HEALTHY	latency:2645.540	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:03:43Z	status:UNKNOWN	latency:8.115	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:16.636	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52146	target_addr:104.18.40.152:443
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:69.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48224	target_addr:104.21.86.125:443
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:86.911	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59878	target_addr:172.67.219.211:443
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:95.959	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60000	target_addr:172.67.168.140:443
time:2026-09-29T11:03:43Z	status:FAILURE	latency:207.801	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:226.744	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:696.032	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:753.513	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:03:43Z	status:HEALTHY	latency:5699.601	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:08:43Z	status:UNKNOWN	latency:8.272	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:13.370	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51284	target_addr:172.64.147.104:443
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:67.778	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50894	target_addr:172.67.219.211:443
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:69.288	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34334	target_addr:172.67.168.140:443
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:78.976	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33286	target_addr:104.21.86.125:443
time:2026-09-29T11:08:43Z	status:FAILURE	latency:219.730	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:230.270	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:624.608	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:647.045	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:08:43Z	status:HEALTHY	latency:10743.754	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:13:43Z	status:UNKNOWN	latency:6.967	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:9.425	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35224	target_addr:172.64.147.104:443
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:66.629	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39262	target_addr:104.21.26.208:443
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:66.355	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49222	target_addr:104.21.86.125:443
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:70.243	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49230	target_addr:104.21.86.125:443
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:212.805	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:13:43Z	status:FAILURE	latency:387.815	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:713.910	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:787.616	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:13:43Z	status:HEALTHY	latency:5768.127	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:18:43Z	status:UNKNOWN	latency:9.457	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:12.536	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47410	target_addr:172.64.147.104:443
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:68.140	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52394	target_addr:104.21.26.208:443
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:68.428	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54318	target_addr:104.21.86.125:443
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:69.100	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52590	target_addr:172.67.219.211:443
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:222.290	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:18:43Z	status:FAILURE	latency:231.596	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:599.403	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:739.774	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:18:43Z	status:HEALTHY	latency:754.934	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:23:43Z	status:UNKNOWN	latency:8.405	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:13.705	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41892	target_addr:172.64.147.104:443
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:67.222	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52400	target_addr:104.21.86.125:443
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:90.957	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34422	target_addr:104.21.26.208:443
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:204.689	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:23:43Z	status:FAILURE	latency:483.364	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:520.962	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:653.879	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:1099.458	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52410	target_addr:104.21.86.125:443
time:2026-09-29T11:23:43Z	status:HEALTHY	latency:1660.049	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:28:43Z	status:UNKNOWN	latency:8.367	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:9.876	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48142	target_addr:172.64.147.104:443
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:70.868	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46550	target_addr:172.67.219.211:443
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:89.655	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58524	target_addr:104.21.86.125:443
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:90.245	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48634	target_addr:172.67.168.140:443
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:206.816	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:28:43Z	status:FAILURE	latency:414.605	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:660.738	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:867.519	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:28:43Z	status:HEALTHY	latency:914.035	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:33:43Z	status:UNKNOWN	latency:6.716	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:10.880	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41694	target_addr:172.64.147.104:443
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:67.036	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50410	target_addr:172.67.219.211:443
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:73.499	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56312	target_addr:104.21.26.208:443
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:83.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:86.217	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50422	target_addr:172.67.219.211:443
time:2026-09-29T11:33:43Z	status:FAILURE	latency:197.925	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:917.304	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:989.103	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:33:43Z	status:HEALTHY	latency:998.073	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:38:43Z	status:UNKNOWN	latency:7.377	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:9.497	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59740	target_addr:172.64.147.104:443
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:65.944	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60036	target_addr:104.21.86.125:443
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:66.870	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60046	target_addr:104.21.86.125:443
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:68.046	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45336	target_addr:172.67.168.140:443
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:339.884	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:38:43Z	status:FAILURE	latency:441.484	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:618.852	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:1086.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:38:43Z	status:HEALTHY	latency:1097.800	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:43:43Z	status:UNKNOWN	latency:9.197	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:12.372	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36380	target_addr:172.64.147.104:443
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:67.316	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52780	target_addr:172.67.219.211:443
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:73.722	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52792	target_addr:172.67.219.211:443
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:91.157	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59390	target_addr:172.67.168.140:443
time:2026-09-29T11:43:43Z	status:FAILURE	latency:203.268	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:276.906	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:809.548	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:993.446	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:43:43Z	status:HEALTHY	latency:1099.563	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:48:43Z	status:UNKNOWN	latency:6.712	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:9.873	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50352	target_addr:104.18.40.152:443
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:65.614	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40218	target_addr:172.67.168.140:443
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:66.029	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35044	target_addr:104.21.86.125:443
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:92.166	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59988	target_addr:172.67.219.211:443
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:197.232	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:48:43Z	status:FAILURE	latency:427.012	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:706.732	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:747.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:48:43Z	status:HEALTHY	latency:939.740	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:10.971	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34476	target_addr:104.18.40.152:443
time:2026-09-29T11:53:43Z	status:UNKNOWN	latency:40.409	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:67.161	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40128	target_addr:172.67.168.140:443
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:68.684	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37626	target_addr:172.67.219.211:443
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:91.754	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37622	target_addr:172.67.219.211:443
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:229.509	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:53:43Z	status:FAILURE	latency:268.098	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:733.059	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:820.076	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:53:43Z	status:HEALTHY	latency:956.418	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:9.397	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33468	target_addr:172.64.147.104:443
time:2026-09-29T11:58:43Z	status:UNKNOWN	latency:16.186	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:66.547	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42138	target_addr:172.67.168.140:443
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:88.217	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56146	target_addr:104.21.86.125:443
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:89.352	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56130	target_addr:104.21.86.125:443
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:219.573	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:58:43Z	status:FAILURE	latency:401.313	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:684.011	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:726.789	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T11:58:43Z	status:HEALTHY	latency:1071.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:9.188	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56820	target_addr:104.18.40.152:443
time:2026-09-29T12:03:43Z	status:UNKNOWN	latency:43.079	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:69.335	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35078	target_addr:104.21.86.125:443
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:92.266	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41016	target_addr:104.21.26.208:443
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:93.056	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35082	target_addr:104.21.86.125:443
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:221.878	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:03:43Z	status:FAILURE	latency:407.639	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:833.106	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:1033.191	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:03:43Z	status:HEALTHY	latency:1315.113	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:08:43Z	status:UNKNOWN	latency:7.070	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:11.956	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44286	target_addr:104.18.40.152:443
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:66.280	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40978	target_addr:104.21.86.125:443
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:70.133	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54308	target_addr:172.67.168.140:443
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:92.897	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47688	target_addr:172.67.219.211:443
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:332.272	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:08:43Z	status:FAILURE	latency:423.576	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:727.057	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:833.265	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:08:43Z	status:HEALTHY	latency:1016.311	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:12.116	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45192	target_addr:104.18.40.152:443
time:2026-09-29T12:13:43Z	status:UNKNOWN	latency:34.989	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:67.219	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57690	target_addr:172.67.219.211:443
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:241.879	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:750.849	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:1090.827	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57700	target_addr:172.67.219.211:443
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:1090.868	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59142	target_addr:104.21.26.208:443
time:2026-09-29T12:13:43Z	status:FAILURE	latency:1348.554	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:1798.834	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:13:43Z	status:HEALTHY	latency:1800.320	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:9.355	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59326	target_addr:104.18.40.152:443
time:2026-09-29T12:18:43Z	status:UNKNOWN	latency:17.751	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:67.980	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41644	target_addr:104.21.86.125:443
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:79.772	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41650	target_addr:104.21.86.125:443
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:91.435	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36572	target_addr:104.21.26.208:443
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:187.765	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:677.671	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:726.050	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:18:43Z	status:HEALTHY	latency:726.425	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:18:43Z	status:FAILURE	latency:1383.607	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:23:43Z	status:UNKNOWN	latency:7.514	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:56.640	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58632	target_addr:172.64.147.104:443
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:67.714	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43112	target_addr:172.67.219.211:443
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:69.306	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43124	target_addr:172.67.219.211:443
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:94.272	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51748	target_addr:172.67.168.140:443
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:235.959	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:23:43Z	status:FAILURE	latency:297.040	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:665.455	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:798.444	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:23:43Z	status:HEALTHY	latency:935.060	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:28:43Z	status:UNKNOWN	latency:5.659	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:10.908	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54482	target_addr:104.18.40.152:443
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:65.431	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50730	target_addr:104.21.86.125:443
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:67.474	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50732	target_addr:104.21.86.125:443
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:72.500	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45486	target_addr:104.21.26.208:443
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:214.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:304.024	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:339.805	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:28:43Z	status:FAILURE	latency:374.539	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:28:43Z	status:HEALTHY	latency:444.598	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:33:43Z	status:UNKNOWN	latency:9.301	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:19.154	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43020	target_addr:172.64.147.104:443
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:72.194	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35118	target_addr:104.21.26.208:443
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:92.898	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48098	target_addr:104.21.86.125:443
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:116.475	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45874	target_addr:172.67.219.211:443
time:2026-09-29T12:33:43Z	status:FAILURE	latency:202.436	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:215.994	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:287.354	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:374.507	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:33:43Z	status:HEALTHY	latency:574.066	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:38:43Z	status:UNKNOWN	latency:7.889	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:15.604	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34520	target_addr:104.18.40.152:443
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:67.678	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60364	target_addr:172.67.219.211:443
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:91.018	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33558	target_addr:104.21.86.125:443
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:91.383	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56948	target_addr:172.67.168.140:443
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:159.892	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:270.834	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:378.724	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:38:43Z	status:FAILURE	latency:513.927	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:38:43Z	status:HEALTHY	latency:581.688	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:41:10Z	status:FAILURE	latency:0.000	target:ayd:endpoint:status.html	message:write tcp 172.17.0.2:9000->172.17.0.1:36822: write: broken pipe
time:2026-09-29T12:43:43Z	status:UNKNOWN	latency:7.671	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:12.822	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57978	target_addr:172.64.147.104:443
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:67.230	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41244	target_addr:172.67.168.140:443
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:67.684	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35102	target_addr:172.67.219.211:443
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:71.174	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35100	target_addr:172.67.219.211:443
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:261.620	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:273.309	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:278.278	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:43:43Z	status:HEALTHY	latency:433.162	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:43:43Z	status:FAILURE	latency:438.844	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:48:43Z	status:UNKNOWN	latency:8.822	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:10.464	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49174	target_addr:104.18.40.152:443
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:69.341	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48562	target_addr:104.21.86.125:443
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:78.119	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49612	target_addr:172.67.168.140:443
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:93.995	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48576	target_addr:104.21.86.125:443
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:259.266	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:266.591	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:269.365	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:48:43Z	status:FAILURE	latency:532.386	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:48:43Z	status:HEALTHY	latency:1033.622	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:53:43Z	status:UNKNOWN	latency:8.221	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:11.417	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47486	target_addr:104.18.40.152:443
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:66.366	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59876	target_addr:172.67.168.140:443
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:66.113	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35066	target_addr:172.67.219.211:443
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:71.774	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35072	target_addr:172.67.219.211:443
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:101.907	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:259.647	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:269.952	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:53:43Z	status:FAILURE	latency:349.523	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:53:43Z	status:HEALTHY	latency:379.381	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:58:44Z	status:UNKNOWN	latency:8.949	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:12.956	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50012	target_addr:104.18.40.152:443
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:68.702	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46134	target_addr:172.67.219.211:443
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:79.606	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46142	target_addr:172.67.219.211:443
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:85.638	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58290	target_addr:172.67.168.140:443
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:221.149	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:58:44Z	status:FAILURE	latency:248.034	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:266.461	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:306.363	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T12:58:44Z	status:HEALTHY	latency:552.551	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:15.546	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36954	target_addr:172.64.147.104:443
time:2026-09-29T13:03:44Z	status:UNKNOWN	latency:38.784	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:68.505	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58700	target_addr:172.67.219.211:443
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:73.105	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58702	target_addr:172.67.219.211:443
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:79.504	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56424	target_addr:172.67.168.140:443
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:277.719	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:664.774	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:687.301	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:03:44Z	status:HEALTHY	latency:999.348	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:03:44Z	status:FAILURE	latency:1346.644	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:08:44Z	status:UNKNOWN	latency:8.287	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:10.649	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56604	target_addr:172.64.147.104:443
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:69.234	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41234	target_addr:172.67.219.211:443
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:71.526	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41458	target_addr:172.67.168.140:443
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:71.483	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41218	target_addr:172.67.219.211:443
time:2026-09-29T13:08:44Z	status:FAILURE	latency:206.288	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:235.596	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:659.354	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:706.534	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:08:44Z	status:HEALTHY	latency:768.448	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:11.778	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53090	target_addr:172.64.147.104:443
time:2026-09-29T13:13:44Z	status:UNKNOWN	latency:14.377	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:68.041	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48768	target_addr:104.21.86.125:443
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:68.105	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48770	target_addr:104.21.86.125:443
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:91.682	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41854	target_addr:104.21.26.208:443
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:224.246	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:13:44Z	status:FAILURE	latency:414.991	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:635.354	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:655.195	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:13:44Z	status:HEALTHY	latency:742.457	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:18:44Z	status:UNKNOWN	latency:7.810	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:12.340	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38942	target_addr:104.18.40.152:443
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:67.147	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53450	target_addr:104.21.86.125:443
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:68.179	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38210	target_addr:172.67.219.211:443
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:79.951	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55978	target_addr:172.67.168.140:443
time:2026-09-29T13:18:44Z	status:FAILURE	latency:195.070	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:271.430	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:325.809	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:377.804	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:18:44Z	status:HEALTHY	latency:20338.961	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:10.841	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57388	target_addr:104.18.40.152:443
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:18.152	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60422	target_addr:172.67.219.211:443
time:2026-09-29T13:23:44Z	status:UNKNOWN	latency:40.210	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:67.552	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51874	target_addr:104.21.86.125:443
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:67.443	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47626	target_addr:172.67.168.140:443
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:215.818	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:265.272	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:273.551	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:23:44Z	status:FAILURE	latency:470.632	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:23:44Z	status:HEALTHY	latency:5388.732	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:28:44Z	status:UNKNOWN	latency:7.634	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:10.971	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44484	target_addr:104.18.40.152:443
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:34.796	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41090	target_addr:172.67.168.140:443
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:67.743	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47054	target_addr:172.67.219.211:443
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:79.082	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:96.353	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46074	target_addr:104.21.86.125:443
time:2026-09-29T13:28:44Z	status:FAILURE	latency:223.803	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:235.952	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:287.677	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:28:44Z	status:HEALTHY	latency:347.313	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:33:44Z	status:UNKNOWN	latency:7.526	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:9.510	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41964	target_addr:104.18.40.152:443
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:68.587	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54616	target_addr:104.21.86.125:443
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:87.932	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58930	target_addr:172.67.168.140:443
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:89.035	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:93.239	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54628	target_addr:104.21.86.125:443
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:264.971	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:272.735	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:33:44Z	status:HEALTHY	latency:299.581	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:33:44Z	status:FAILURE	latency:483.242	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:38:44Z	status:UNKNOWN	latency:9.579	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:12.258	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45416	target_addr:104.18.40.152:443
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:24.646	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57238	target_addr:172.67.168.140:443
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:38.238	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54252	target_addr:104.21.86.125:443
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:71.917	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54262	target_addr:104.21.86.125:443
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:244.071	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:277.393	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:338.544	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:38:44Z	status:HEALTHY	latency:377.060	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:38:44Z	status:FAILURE	latency:388.030	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:43:44Z	status:UNKNOWN	latency:8.657	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:11.112	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52666	target_addr:172.64.147.104:443
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:21.449	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50580	target_addr:104.21.26.208:443
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:83.148	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51216	target_addr:172.67.219.211:443
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:87.883	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41416	target_addr:104.21.86.125:443
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:259.322	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:43:44Z	status:FAILURE	latency:329.388	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:610.956	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:612.866	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:43:44Z	status:HEALTHY	latency:641.944	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:48:44Z	status:UNKNOWN	latency:7.634	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:13.485	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43988	target_addr:172.64.147.104:443
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:19.513	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59060	target_addr:104.21.86.125:443
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:33.205	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33170	target_addr:172.67.168.140:443
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:90.817	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55722	target_addr:172.67.219.211:443
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:242.186	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:825.699	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:48:44Z	status:FAILURE	latency:1273.485	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:1398.782	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:48:44Z	status:HEALTHY	latency:5536.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:9.279	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46782	target_addr:172.64.147.104:443
time:2026-09-29T13:53:44Z	status:UNKNOWN	latency:36.702	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:67.598	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37920	target_addr:172.67.219.211:443
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:93.890	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37934	target_addr:172.67.219.211:443
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:158.136	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40286	target_addr:104.21.26.208:443
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:221.989	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:53:44Z	status:FAILURE	latency:255.227	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:563.473	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:737.987	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:53:44Z	status:HEALTHY	latency:1004.172	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:58:44Z	status:UNKNOWN	latency:7.481	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:18.330	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54960	target_addr:172.67.168.140:443
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:35.170	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33908	target_addr:104.18.40.152:443
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:83.177	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:91.019	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41602	target_addr:104.21.86.125:443
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:91.536	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41618	target_addr:104.21.86.125:443
time:2026-09-29T13:58:44Z	status:FAILURE	latency:352.282	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:889.426	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:899.525	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T13:58:44Z	status:HEALTHY	latency:1376.863	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:11.299	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58970	target_addr:104.18.40.152:443
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:71.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40440	target_addr:172.67.219.211:443
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:90.827	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40428	target_addr:172.67.219.211:443
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:91.255	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57842	target_addr:104.21.26.208:443
time:2026-09-29T14:03:44Z	status:UNKNOWN	latency:93.267	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:237.107	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:03:44Z	status:FAILURE	latency:423.244	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:705.961	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:844.675	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:03:44Z	status:HEALTHY	latency:5566.156	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:08:44Z	status:UNKNOWN	latency:9.220	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:12.300	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51140	target_addr:172.64.147.104:443
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:70.652	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37236	target_addr:104.21.26.208:443
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:75.501	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51350	target_addr:104.21.86.125:443
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:92.670	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59268	target_addr:172.67.219.211:443
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:246.641	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:465.732	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:1003.579	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:08:44Z	status:FAILURE	latency:1646.998	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:08:44Z	status:HEALTHY	latency:6380.454	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:13:44Z	status:UNKNOWN	latency:6.205	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:10.969	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42146	target_addr:172.64.147.104:443
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:20.477	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60260	target_addr:104.21.26.208:443
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:90.750	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45802	target_addr:172.67.219.211:443
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:156.054	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37300	target_addr:104.21.86.125:443
time:2026-09-29T14:13:44Z	status:FAILURE	latency:270.634	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:273.538	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:569.669	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:835.621	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:13:44Z	status:HEALTHY	latency:1038.596	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:12.343	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60288	target_addr:104.18.40.152:443
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:20.840	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40220	target_addr:172.67.219.211:443
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:20.713	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55782	target_addr:104.21.86.125:443
time:2026-09-29T14:18:44Z	status:UNKNOWN	latency:70.234	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:92.123	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33294	target_addr:104.21.26.208:443
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:242.288	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:18:44Z	status:FAILURE	latency:497.714	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:792.038	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:836.068	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:18:44Z	status:HEALTHY	latency:1782.507	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:20.524	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34596	target_addr:104.18.40.152:443
time:2026-09-29T14:23:44Z	status:UNKNOWN	latency:33.880	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:70.022	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36434	target_addr:172.67.219.211:443
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:75.145	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36422	target_addr:172.67.219.211:443
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:86.757	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51222	target_addr:104.21.26.208:443
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:216.038	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:526.256	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:696.653	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:23:44Z	status:HEALTHY	latency:835.458	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:23:44Z	status:FAILURE	latency:1618.129	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:16.234	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33824	target_addr:172.64.147.104:443
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:18.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59642	target_addr:172.67.219.211:443
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:35.042	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47388	target_addr:172.67.168.140:443
time:2026-09-29T14:28:44Z	status:UNKNOWN	latency:38.962	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:70.054	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59656	target_addr:172.67.219.211:443
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:188.022	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:28:44Z	status:FAILURE	latency:272.613	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:784.926	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:852.106	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:28:44Z	status:HEALTHY	latency:880.266	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:33:44Z	status:UNKNOWN	latency:7.156	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:9.237	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52956	target_addr:172.64.147.104:443
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:69.817	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57828	target_addr:104.21.26.208:443
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:89.687	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37182	target_addr:172.67.219.211:443
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:157.821	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34500	target_addr:104.21.86.125:443
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:231.445	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:33:44Z	status:FAILURE	latency:363.847	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:608.235	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:865.156	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:33:44Z	status:HEALTHY	latency:1398.200	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:38:44Z	status:UNKNOWN	latency:7.560	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:11.366	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45974	target_addr:104.18.40.152:443
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:66.919	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57458	target_addr:172.67.219.211:443
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:76.045	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57462	target_addr:172.67.219.211:443
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:93.215	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47246	target_addr:172.67.168.140:443
time:2026-09-29T14:38:44Z	status:FAILURE	latency:205.428	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:235.131	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:1365.006	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:2224.052	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:38:44Z	status:HEALTHY	latency:3532.781	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:43:44Z	status:UNKNOWN	latency:7.018	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:9.129	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57270	target_addr:172.64.147.104:443
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:20.597	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41996	target_addr:172.67.219.211:443
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:66.486	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41980	target_addr:172.67.219.211:443
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:73.673	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60162	target_addr:104.21.26.208:443
time:2026-09-29T14:43:44Z	status:FAILURE	latency:206.085	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:224.862	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:555.965	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:589.631	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:43:44Z	status:HEALTHY	latency:1068.782	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:48:44Z	status:UNKNOWN	latency:7.968	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:12.692	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49444	target_addr:172.64.147.104:443
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:20.610	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39706	target_addr:104.21.86.125:443
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:24.283	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58380	target_addr:104.21.26.208:443
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:82.533	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39558	target_addr:172.67.219.211:443
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:199.570	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:48:44Z	status:FAILURE	latency:417.240	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:470.578	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:474.324	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:48:44Z	status:HEALTHY	latency:693.067	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:8.775	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57158	target_addr:104.18.40.152:443
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:16.771	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33964	target_addr:172.67.168.140:443
time:2026-09-29T14:53:44Z	status:UNKNOWN	latency:35.276	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:90.869	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56030	target_addr:172.67.219.211:443
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:156.243	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35880	target_addr:104.21.86.125:443
time:2026-09-29T14:53:44Z	status:FAILURE	latency:198.222	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:229.713	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:483.413	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:501.207	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:53:44Z	status:HEALTHY	latency:747.125	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:58:44Z	status:UNKNOWN	latency:6.513	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:11.469	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59754	target_addr:172.64.147.104:443
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:19.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36454	target_addr:104.21.26.208:443
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:66.110	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58628	target_addr:104.21.86.125:443
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:93.925	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58636	target_addr:104.21.86.125:443
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:216.333	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:58:44Z	status:FAILURE	latency:217.020	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:727.624	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:1169.855	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T14:58:44Z	status:HEALTHY	latency:1407.941	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:03:44Z	status:UNKNOWN	latency:7.060	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:9.794	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56918	target_addr:172.64.147.104:443
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:17.576	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41924	target_addr:104.21.86.125:443
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:92.213	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40372	target_addr:104.21.26.208:443
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:152.645	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41934	target_addr:104.21.86.125:443
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:239.666	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:03:44Z	status:FAILURE	latency:321.241	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:760.262	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:1152.901	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:03:44Z	status:HEALTHY	latency:1173.379	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:11.870	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37816	target_addr:104.18.40.152:443
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:17.192	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41142	target_addr:172.67.219.211:443
time:2026-09-29T15:08:44Z	status:UNKNOWN	latency:19.469	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:24.242	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41154	target_addr:172.67.219.211:443
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:92.020	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49442	target_addr:172.67.168.140:443
time:2026-09-29T15:08:44Z	status:FAILURE	latency:255.383	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:288.437	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:833.947	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:08:44Z	status:HEALTHY	latency:979.597	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:08:44Z	status:FAILURE	latency:10390.932	target:https://go3-cn.online/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-09-29T15:13:44Z	status:UNKNOWN	latency:7.329	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:10.707	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52068	target_addr:172.64.147.104:443
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:19.007	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33264	target_addr:104.21.86.125:443
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:21.922	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33272	target_addr:104.21.86.125:443
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:153.097	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56620	target_addr:104.21.26.208:443
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:204.339	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:13:44Z	status:FAILURE	latency:416.493	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:541.773	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:807.716	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:13:44Z	status:HEALTHY	latency:830.130	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:18:44Z	status:UNKNOWN	latency:7.355	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:10.253	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42278	target_addr:172.64.147.104:443
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:17.958	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42588	target_addr:172.67.219.211:443
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:23.382	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44062	target_addr:104.21.86.125:443
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:25.085	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44648	target_addr:104.21.26.208:443
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:314.728	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:18:44Z	status:FAILURE	latency:415.439	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:680.216	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:731.078	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:18:44Z	status:HEALTHY	latency:736.884	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:23:44Z	status:UNKNOWN	latency:9.639	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:12.134	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57806	target_addr:172.64.147.104:443
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:74.262	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55138	target_addr:104.21.86.125:443
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:161.895	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47706	target_addr:172.67.168.140:443
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:166.138	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55148	target_addr:104.21.86.125:443
time:2026-09-29T15:23:44Z	status:FAILURE	latency:245.657	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:258.560	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:488.483	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:1137.423	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:23:44Z	status:HEALTHY	latency:1362.740	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:28:44Z	status:UNKNOWN	latency:6.577	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:8.972	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36380	target_addr:172.64.147.104:443
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:19.990	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46826	target_addr:104.21.86.125:443
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:67.292	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46842	target_addr:104.21.86.125:443
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:74.010	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35064	target_addr:172.67.168.140:443
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:283.636	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:28:44Z	status:FAILURE	latency:543.068	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:707.706	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:802.691	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:28:44Z	status:HEALTHY	latency:1241.806	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:9.554	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34556	target_addr:172.64.147.104:443
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:18.073	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40292	target_addr:172.67.219.211:443
time:2026-09-29T15:33:44Z	status:UNKNOWN	latency:42.440	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:91.898	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40294	target_addr:172.67.219.211:443
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:94.896	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42872	target_addr:104.21.26.208:443
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:202.528	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:33:44Z	status:FAILURE	latency:461.598	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:671.602	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:686.952	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:33:44Z	status:HEALTHY	latency:1141.208	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:38:44Z	status:UNKNOWN	latency:11.188	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:11.257	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36480	target_addr:104.18.40.152:443
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:17.432	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34576	target_addr:172.67.168.140:443
time:2026-09-29T15:38:44Z	status:FAILURE	latency:55.443	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:79.195	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52526	target_addr:172.67.219.211:443
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:92.073	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:158.084	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44862	target_addr:104.21.86.125:443
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:550.903	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:752.116	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:38:44Z	status:HEALTHY	latency:786.371	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:43:44Z	status:UNKNOWN	latency:7.007	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:8.866	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46058	target_addr:172.64.147.104:443
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:18.270	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38866	target_addr:104.21.86.125:443
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:26.334	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57448	target_addr:172.67.168.140:443
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:80.518	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38876	target_addr:104.21.86.125:443
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:267.827	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:43:44Z	status:FAILURE	latency:333.362	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:415.524	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:510.948	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:43:44Z	status:HEALTHY	latency:1199.959	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:48:44Z	status:UNKNOWN	latency:9.362	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:15.345	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47170	target_addr:104.18.40.152:443
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:21.874	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52820	target_addr:104.21.86.125:443
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:91.247	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33678	target_addr:104.21.26.208:443
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:152.661	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52804	target_addr:104.21.86.125:443
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:349.324	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:48:44Z	status:FAILURE	latency:427.977	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:476.069	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:646.231	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:48:44Z	status:HEALTHY	latency:4788.909	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:13.227	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45452	target_addr:104.18.40.152:443
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:17.154	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57066	target_addr:172.67.168.140:443
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:19.025	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57002	target_addr:172.67.219.211:443
time:2026-09-29T15:53:44Z	status:UNKNOWN	latency:35.869	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:67.353	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39478	target_addr:104.21.86.125:443
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:250.145	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:53:44Z	status:FAILURE	latency:275.810	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:547.959	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:754.990	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:53:44Z	status:HEALTHY	latency:785.401	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:58:44Z	status:UNKNOWN	latency:8.689	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:11.909	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60026	target_addr:172.64.147.104:443
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:20.089	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53392	target_addr:172.67.168.140:443
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:76.120	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49174	target_addr:104.21.86.125:443
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:87.595	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55338	target_addr:172.67.219.211:443
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:238.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:58:44Z	status:FAILURE	latency:500.037	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:518.808	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:527.248	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T15:58:44Z	status:HEALTHY	latency:786.692	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:03:44Z	status:UNKNOWN	latency:8.733	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:16.134	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42784	target_addr:172.64.147.104:443
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:154.864	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44752	target_addr:172.67.219.211:443
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:157.136	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48926	target_addr:104.21.86.125:443
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:179.728	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55314	target_addr:172.67.168.140:443
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:264.583	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:03:44Z	status:FAILURE	latency:435.955	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:800.626	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:1078.863	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:03:44Z	status:HEALTHY	latency:1089.333	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:08:44Z	status:UNKNOWN	latency:8.860	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:11.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38932	target_addr:104.18.40.152:443
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:159.720	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51810	target_addr:104.21.86.125:443
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:162.911	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52538	target_addr:172.67.168.140:443
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:207.464	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:08:44Z	status:FAILURE	latency:720.825	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:1050.866	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:1539.025	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:1659.491	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:08:44Z	status:HEALTHY	latency:2206.330	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48790	target_addr:172.67.219.211:443
time:2026-09-29T16:13:44Z	status:UNKNOWN	latency:7.140	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:99.941	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35304	target_addr:104.18.40.152:443
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:146.675	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48678	target_addr:172.67.219.211:443
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:162.192	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50690	target_addr:172.67.168.140:443
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:195.866	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48192	target_addr:104.21.86.125:443
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:205.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:13:44Z	status:FAILURE	latency:697.727	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:990.234	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:13:44Z	status:HEALTHY	latency:1092.434	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:13:44Z	status:FAILURE	latency:20007.900	target:https://go3-cn.online/	message:[2606:4700:3037::6815:3ee6]:443: connection refused
time:2026-09-29T16:18:44Z	status:UNKNOWN	latency:6.429	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:10.634	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48544	target_addr:104.18.40.152:443
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:77.193	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52730	target_addr:172.67.219.211:443
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:144.766	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33334	target_addr:104.21.26.208:443
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:165.074	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52738	target_addr:172.67.219.211:443
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:202.574	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:18:44Z	status:FAILURE	latency:554.517	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:1072.855	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:1093.966	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:18:44Z	status:HEALTHY	latency:1169.513	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:23:44Z	status:UNKNOWN	latency:8.924	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:10.985	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41558	target_addr:172.64.147.104:443
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:146.203	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54838	target_addr:104.21.26.208:443
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:160.603	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37212	target_addr:172.67.219.211:443
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:174.028	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59612	target_addr:104.21.86.125:443
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:220.870	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:23:44Z	status:FAILURE	latency:672.978	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:745.944	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:1081.207	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:23:44Z	status:HEALTHY	latency:1111.022	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:28:44Z	status:UNKNOWN	latency:7.435	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:10.610	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33584	target_addr:104.18.40.152:443
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:147.178	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49360	target_addr:172.67.219.211:443
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:154.064	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34988	target_addr:172.67.168.140:443
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:158.378	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42374	target_addr:104.21.86.125:443
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:249.147	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:28:44Z	status:FAILURE	latency:697.647	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:1190.103	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:1196.110	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:28:44Z	status:HEALTHY	latency:6200.923	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:33:44Z	status:UNKNOWN	latency:9.536	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:41.925	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45266	target_addr:172.64.147.104:443
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:153.253	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50686	target_addr:172.67.219.211:443
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:165.578	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48256	target_addr:172.67.168.140:443
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:178.493	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49874	target_addr:104.21.86.125:443
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:239.609	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:33:44Z	status:FAILURE	latency:751.256	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:1063.772	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:1104.169	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:33:44Z	status:HEALTHY	latency:3131.857	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:10.525	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46314	target_addr:104.18.40.152:443
time:2026-09-29T16:38:45Z	status:UNKNOWN	latency:57.180	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:167.026	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59650	target_addr:172.67.219.211:443
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:168.006	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34932	target_addr:104.21.26.208:443
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:177.859	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59640	target_addr:172.67.219.211:443
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:219.226	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:38:45Z	status:FAILURE	latency:828.894	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:1089.577	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:1140.575	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:38:45Z	status:HEALTHY	latency:1359.987	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:43:45Z	status:HEALTHY	latency:10.909	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46866	target_addr:172.64.147.104:443
time:2026-09-29T16:43:45Z	status:UNKNOWN	latency:35.959	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:43:45Z	status:HEALTHY	latency:153.863	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39074	target_addr:104.21.86.125:443
time:2026-09-29T16:43:45Z	status:HEALTHY	latency:176.344	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54142	target_addr:104.21.26.208:443
time:2026-09-29T16:43:45Z	status:HEALTHY	latency:189.359	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58712	target_addr:172.67.219.211:443
time:2026-09-29T16:43:45Z	status:HEALTHY	latency:263.098	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:43:45Z	status:FAILURE	latency:642.251	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:43:45Z	status:HEALTHY	latency:1171.747	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:43:45Z	status:FAILURE	latency:10626.464	target:https://go3-cn.blog/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-09-29T16:43:45Z	status:FAILURE	latency:11151.887	target:https://go3-cn.xyz/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-09-29T16:48:45Z	status:UNKNOWN	latency:8.825	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:31.498	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35492	target_addr:104.18.40.152:443
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:164.658	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57232	target_addr:104.21.86.125:443
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:180.707	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58972	target_addr:172.67.219.211:443
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:203.726	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39450	target_addr:104.21.26.208:443
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:310.282	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:689.546	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:48:45Z	status:FAILURE	latency:733.409	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:972.637	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:48:45Z	status:HEALTHY	latency:1096.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:53:45Z	status:UNKNOWN	latency:8.921	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:9.950	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41404	target_addr:104.18.40.152:443
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:148.779	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52018	target_addr:172.67.219.211:443
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:173.720	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46714	target_addr:104.21.26.208:443
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:175.165	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52004	target_addr:172.67.219.211:443
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:196.209	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:53:45Z	status:FAILURE	latency:618.041	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:1042.936	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:1066.433	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:53:45Z	status:HEALTHY	latency:1169.631	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:58:45Z	status:UNKNOWN	latency:8.210	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:11.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36574	target_addr:172.64.147.104:443
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:156.959	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34438	target_addr:104.21.86.125:443
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:160.215	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54102	target_addr:172.67.219.211:443
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:161.923	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35654	target_addr:172.67.168.140:443
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:245.443	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:58:45Z	status:FAILURE	latency:754.498	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:992.215	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:1103.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T16:58:45Z	status:HEALTHY	latency:1114.309	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:03:45Z	status:UNKNOWN	latency:8.594	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:17.609	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53266	target_addr:172.64.147.104:443
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:157.590	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51448	target_addr:172.67.168.140:443
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:162.572	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45034	target_addr:172.67.219.211:443
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:166.925	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45048	target_addr:172.67.219.211:443
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:331.146	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:03:45Z	status:FAILURE	latency:410.545	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:1112.951	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:1114.703	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:03:45Z	status:HEALTHY	latency:2110.596	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:08:45Z	status:UNKNOWN	latency:5.990	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:27.570	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37832	target_addr:104.18.40.152:443
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:164.606	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49910	target_addr:172.67.219.211:443
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:168.653	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39194	target_addr:104.21.26.208:443
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:183.019	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56756	target_addr:104.21.86.125:443
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:186.317	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:08:45Z	status:FAILURE	latency:435.505	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:1200.987	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:1923.146	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:08:45Z	status:HEALTHY	latency:6348.798	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:13:45Z	status:UNKNOWN	latency:7.676	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:9.246	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41578	target_addr:104.18.40.152:443
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:155.318	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59888	target_addr:104.21.86.125:443
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:160.721	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35084	target_addr:172.67.219.211:443
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:173.570	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51216	target_addr:104.21.26.208:443
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:228.099	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:13:45Z	status:FAILURE	latency:669.791	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:979.073	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:1004.115	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:13:45Z	status:HEALTHY	latency:1010.177	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:18:45Z	status:UNKNOWN	latency:13.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:28.876	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35862	target_addr:172.64.147.104:443
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:77.330	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53792	target_addr:104.21.86.125:443
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:182.266	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40848	target_addr:104.21.26.208:443
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:245.850	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:18:45Z	status:FAILURE	latency:520.631	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:1198.375	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53802	target_addr:104.21.86.125:443
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:1438.802	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:2137.134	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:18:45Z	status:HEALTHY	latency:3354.857	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:23:45Z	status:UNKNOWN	latency:8.855	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:13.259	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56820	target_addr:104.18.40.152:443
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:168.476	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59676	target_addr:172.67.219.211:443
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:177.555	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59668	target_addr:172.67.219.211:443
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:224.741	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:256.446	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51872	target_addr:104.21.26.208:443
time:2026-09-29T17:23:45Z	status:FAILURE	latency:634.155	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:726.465	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:1031.857	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:23:45Z	status:HEALTHY	latency:1082.513	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:9.701	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37532	target_addr:104.18.40.152:443
time:2026-09-29T17:28:45Z	status:UNKNOWN	latency:36.928	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:72.317	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50094	target_addr:104.21.26.208:443
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:173.692	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57088	target_addr:104.21.86.125:443
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:194.606	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:583.946	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38614	target_addr:172.67.219.211:443
time:2026-09-29T17:28:45Z	status:FAILURE	latency:976.873	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:1128.261	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:1590.608	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:28:45Z	status:HEALTHY	latency:3610.568	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:33:45Z	status:UNKNOWN	latency:7.694	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:11.929	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59520	target_addr:104.18.40.152:443
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:292.690	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:699.369	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:776.444	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:1467.557	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35894	target_addr:172.67.219.211:443
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:1658.286	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44472	target_addr:104.21.26.208:443
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:1670.935	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54352	target_addr:104.21.86.125:443
time:2026-09-29T17:33:45Z	status:HEALTHY	latency:2230.040	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:33:45Z	status:FAILURE	latency:8567.364	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:38:45Z	status:UNKNOWN	latency:10.013	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:13.052	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50184	target_addr:172.64.147.104:443
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:214.446	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:38:45Z	status:FAILURE	latency:502.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:528.051	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59780	target_addr:104.21.86.125:443
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:603.205	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40320	target_addr:172.67.168.140:443
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:612.295	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60316	target_addr:172.67.219.211:443
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:2087.271	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:5948.526	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:38:45Z	status:HEALTHY	latency:6557.067	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:43:45Z	status:UNKNOWN	latency:8.253	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:10.879	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48022	target_addr:104.18.40.152:443
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:72.658	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53728	target_addr:104.21.86.125:443
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:81.513	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34988	target_addr:172.67.168.140:443
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:162.719	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53730	target_addr:104.21.86.125:443
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:205.300	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:43:45Z	status:FAILURE	latency:639.129	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:824.995	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:1196.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:43:45Z	status:HEALTHY	latency:1300.340	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:48:45Z	status:UNKNOWN	latency:6.915	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:10.921	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55530	target_addr:172.64.147.104:443
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:162.861	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51636	target_addr:104.21.86.125:443
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:164.050	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51922	target_addr:104.21.26.208:443
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:177.270	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51620	target_addr:104.21.86.125:443
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:234.800	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:48:45Z	status:FAILURE	latency:392.326	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:709.750	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:1040.380	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:48:45Z	status:HEALTHY	latency:1191.735	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:13.428	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56750	target_addr:172.64.147.104:443
time:2026-09-29T17:53:45Z	status:UNKNOWN	latency:17.151	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:159.452	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41774	target_addr:104.21.86.125:443
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:159.693	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57450	target_addr:104.21.26.208:443
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:170.268	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41782	target_addr:104.21.86.125:443
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:235.162	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:53:45Z	status:FAILURE	latency:428.275	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:748.128	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:1148.291	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:53:45Z	status:HEALTHY	latency:1240.478	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:58:45Z	status:UNKNOWN	latency:7.032	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:10.615	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48586	target_addr:172.64.147.104:443
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:72.535	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60310	target_addr:172.67.219.211:443
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:77.377	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40160	target_addr:104.21.86.125:443
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:175.590	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41212	target_addr:172.67.168.140:443
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:257.422	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:58:45Z	status:FAILURE	latency:642.656	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:1163.771	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:1178.845	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T17:58:45Z	status:HEALTHY	latency:1186.416	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:03:45Z	status:UNKNOWN	latency:8.392	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:15.132	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51674	target_addr:104.18.40.152:443
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:20.917	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54860	target_addr:104.21.86.125:443
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:74.519	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53100	target_addr:172.67.219.211:443
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:174.364	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57338	target_addr:172.67.168.140:443
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:272.078	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:03:45Z	status:FAILURE	latency:632.917	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:1052.127	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:1055.890	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:03:45Z	status:HEALTHY	latency:1074.497	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:08:45Z	status:UNKNOWN	latency:5.979	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:9.589	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44466	target_addr:104.18.40.152:443
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:70.899	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50560	target_addr:172.67.219.211:443
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:167.306	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57858	target_addr:104.21.86.125:443
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:175.136	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42108	target_addr:104.21.26.208:443
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:260.017	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:499.434	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:08:45Z	status:FAILURE	latency:665.085	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:813.958	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:08:45Z	status:HEALTHY	latency:1068.432	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:13:45Z	status:UNKNOWN	latency:8.516	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:11.310	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57688	target_addr:104.18.40.152:443
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:160.258	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50844	target_addr:172.67.219.211:443
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:161.277	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40284	target_addr:104.21.26.208:443
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:174.862	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50834	target_addr:172.67.219.211:443
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:239.114	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:13:45Z	status:FAILURE	latency:676.577	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:751.729	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:1048.175	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:13:45Z	status:HEALTHY	latency:1135.932	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:18:45Z	status:UNKNOWN	latency:6.509	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:13.483	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35526	target_addr:104.18.40.152:443
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:157.902	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46526	target_addr:172.67.168.140:443
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:180.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41724	target_addr:172.67.219.211:443
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:229.540	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:18:45Z	status:FAILURE	latency:465.839	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:755.437	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:813.220	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:1125.374	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:18:45Z	status:HEALTHY	latency:1171.914	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41732	target_addr:172.67.219.211:443
time:2026-09-29T18:23:45Z	status:UNKNOWN	latency:8.301	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:11.479	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42126	target_addr:172.64.147.104:443
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:79.177	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38996	target_addr:104.21.26.208:443
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:164.720	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34850	target_addr:172.67.219.211:443
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:223.965	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:405.923	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55690	target_addr:104.21.86.125:443
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:584.066	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:23:45Z	status:FAILURE	latency:644.855	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:752.428	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:23:45Z	status:HEALTHY	latency:1142.841	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:28:45Z	status:UNKNOWN	latency:6.731	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:9.236	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37208	target_addr:172.64.147.104:443
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:155.279	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40938	target_addr:104.21.86.125:443
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:158.532	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40922	target_addr:104.21.86.125:443
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:176.412	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49952	target_addr:104.21.26.208:443
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:209.287	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:28:45Z	status:FAILURE	latency:635.145	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:1136.680	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:1141.596	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:28:45Z	status:HEALTHY	latency:6196.369	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:33:45Z	status:UNKNOWN	latency:12.066	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:14.320	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38592	target_addr:104.18.40.152:443
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:71.244	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55802	target_addr:104.21.86.125:443
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:161.025	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50562	target_addr:104.21.26.208:443
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:175.165	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50444	target_addr:172.67.219.211:443
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:239.443	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:33:45Z	status:FAILURE	latency:686.746	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:1152.055	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:1202.393	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:33:45Z	status:HEALTHY	latency:1500.311	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:38:45Z	status:UNKNOWN	latency:7.510	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:16.142	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40788	target_addr:104.18.40.152:443
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:156.946	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51734	target_addr:104.21.86.125:443
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:179.169	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57064	target_addr:172.67.219.211:443
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:179.485	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42196	target_addr:104.21.26.208:443
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:241.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:38:45Z	status:FAILURE	latency:654.173	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:1165.281	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:1171.319	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:38:45Z	status:HEALTHY	latency:2771.269	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:43:45Z	status:UNKNOWN	latency:6.733	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:9.876	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52454	target_addr:104.18.40.152:443
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:77.856	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41608	target_addr:172.67.219.211:443
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:155.435	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59744	target_addr:104.21.86.125:443
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:162.166	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58872	target_addr:172.67.168.140:443
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:186.432	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:553.744	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:43:45Z	status:FAILURE	latency:709.643	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:1191.527	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:43:45Z	status:HEALTHY	latency:1217.437	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:48:45Z	status:UNKNOWN	latency:6.790	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:11.490	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38420	target_addr:172.64.147.104:443
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:165.472	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40590	target_addr:104.21.86.125:443
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:167.710	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35236	target_addr:104.21.26.208:443
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:175.502	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45608	target_addr:172.67.219.211:443
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:225.342	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:1060.394	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:1082.119	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:48:45Z	status:HEALTHY	latency:1380.692	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:48:45Z	status:FAILURE	latency:1819.847	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:53:45Z	status:UNKNOWN	latency:9.548	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:14.030	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48122	target_addr:172.64.147.104:443
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:80.322	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50470	target_addr:172.67.219.211:443
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:169.680	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51350	target_addr:172.67.168.140:443
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:169.675	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50466	target_addr:172.67.219.211:443
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:217.172	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:53:45Z	status:FAILURE	latency:678.241	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:972.790	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:1137.515	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:53:45Z	status:HEALTHY	latency:1233.000	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:58:45Z	status:UNKNOWN	latency:7.294	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:13.606	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45542	target_addr:104.18.40.152:443
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:85.749	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46734	target_addr:104.21.86.125:443
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:164.163	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46728	target_addr:104.21.86.125:443
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:177.540	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37878	target_addr:104.21.26.208:443
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:371.360	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:58:45Z	status:FAILURE	latency:528.657	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:1210.316	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:1324.600	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T18:58:45Z	status:HEALTHY	latency:1616.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:12.845	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58254	target_addr:104.18.40.152:443
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:74.677	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32960	target_addr:172.67.168.140:443
time:2026-09-29T19:03:45Z	status:UNKNOWN	latency:146.398	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:157.322	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39478	target_addr:172.67.219.211:443
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:159.116	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39490	target_addr:172.67.219.211:443
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:295.426	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:03:45Z	status:FAILURE	latency:641.227	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:1085.911	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:1418.628	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:03:45Z	status:HEALTHY	latency:4915.905	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:12.031	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33402	target_addr:172.64.147.104:443
time:2026-09-29T19:08:45Z	status:UNKNOWN	latency:37.132	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:82.003	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36672	target_addr:172.67.219.211:443
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:161.790	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40452	target_addr:104.21.26.208:443
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:170.381	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52488	target_addr:104.21.86.125:443
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:205.747	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:08:45Z	status:FAILURE	latency:215.038	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:692.718	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:1020.231	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:08:45Z	status:HEALTHY	latency:1040.698	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:13:45Z	status:UNKNOWN	latency:6.873	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:12.381	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43300	target_addr:172.64.147.104:443
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:73.115	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51768	target_addr:172.67.168.140:443
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:170.351	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42648	target_addr:104.21.86.125:443
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:175.407	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33914	target_addr:172.67.219.211:443
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:299.837	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:13:45Z	status:FAILURE	latency:480.253	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:741.755	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:812.218	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:13:45Z	status:HEALTHY	latency:1628.836	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:23.008	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51286	target_addr:172.67.219.211:443
time:2026-09-29T19:18:45Z	status:UNKNOWN	latency:33.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:78.920	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51302	target_addr:172.67.219.211:443
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:257.024	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36500	target_addr:172.67.168.140:443
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:345.841	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32778	target_addr:172.64.147.104:443
time:2026-09-29T19:18:45Z	status:FAILURE	latency:433.856	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:1117.197	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:1585.399	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:1906.869	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:18:45Z	status:HEALTHY	latency:1995.960	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:23:45Z	status:UNKNOWN	latency:104.638	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:135.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57922	target_addr:104.18.40.152:443
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:157.169	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48366	target_addr:172.67.219.211:443
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:159.773	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36630	target_addr:172.67.168.140:443
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:160.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46984	target_addr:104.21.86.125:443
time:2026-09-29T19:23:45Z	status:FAILURE	latency:538.144	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:658.272	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:779.091	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:841.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:23:45Z	status:HEALTHY	latency:1075.668	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:28:45Z	status:UNKNOWN	latency:10.422	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:80.632	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45154	target_addr:172.67.219.211:443
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:113.176	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56900	target_addr:104.18.40.152:443
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:181.457	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47792	target_addr:172.67.168.140:443
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:293.733	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54022	target_addr:104.21.86.125:443
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:328.099	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:28:45Z	status:FAILURE	latency:572.022	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:1433.177	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:1924.901	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:28:45Z	status:HEALTHY	latency:6192.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:10.898	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43002	target_addr:172.64.147.104:443
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:182.760	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36984	target_addr:104.21.86.125:443
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:199.990	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58326	target_addr:172.67.168.140:443
time:2026-09-29T19:33:45Z	status:UNKNOWN	latency:252.444	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:339.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:408.801	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33858	target_addr:172.67.219.211:443
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:456.429	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:33:45Z	status:FAILURE	latency:491.533	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:774.234	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:33:45Z	status:HEALTHY	latency:1179.321	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:38:45Z	status:UNKNOWN	latency:7.189	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:16.192	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34216	target_addr:104.18.40.152:443
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:70.361	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48020	target_addr:104.21.86.125:443
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:81.508	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48030	target_addr:104.21.86.125:443
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:175.458	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44072	target_addr:104.21.26.208:443
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:204.304	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:1133.887	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:1145.722	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:38:45Z	status:HEALTHY	latency:1592.126	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:38:45Z	status:FAILURE	latency:4036.275	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:43:45Z	status:UNKNOWN	latency:8.304	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:10.301	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41856	target_addr:172.64.147.104:443
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:75.642	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52050	target_addr:172.67.168.140:443
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:78.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58206	target_addr:172.67.219.211:443
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:85.991	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58210	target_addr:172.67.219.211:443
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:138.484	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:43:45Z	status:FAILURE	latency:506.897	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:1030.416	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:1122.025	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:43:45Z	status:HEALTHY	latency:1139.583	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:48:45Z	status:UNKNOWN	latency:6.862	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:75.890	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57560	target_addr:104.21.86.125:443
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:110.649	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52144	target_addr:172.64.147.104:443
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:159.528	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57546	target_addr:104.21.86.125:443
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:170.911	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57636	target_addr:172.67.168.140:443
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:322.279	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:48:45Z	status:FAILURE	latency:577.780	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:716.491	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:1184.333	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:48:45Z	status:HEALTHY	latency:6113.311	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:53:45Z	status:UNKNOWN	latency:7.423	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:12.769	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42170	target_addr:104.18.40.152:443
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:154.440	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57878	target_addr:104.21.86.125:443
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:176.395	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56278	target_addr:104.21.26.208:443
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:179.292	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57880	target_addr:104.21.86.125:443
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:231.320	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:53:45Z	status:FAILURE	latency:399.074	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:797.192	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:1103.070	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:53:45Z	status:HEALTHY	latency:1427.807	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:58:45Z	status:UNKNOWN	latency:7.735	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:21.915	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40468	target_addr:172.64.147.104:443
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:153.428	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38646	target_addr:104.21.26.208:443
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:154.890	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35906	target_addr:104.21.86.125:443
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:161.407	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35902	target_addr:104.21.86.125:443
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:228.126	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:58:45Z	status:FAILURE	latency:352.942	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:1087.374	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:1108.929	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T19:58:45Z	status:HEALTHY	latency:1127.891	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:03:45Z	status:UNKNOWN	latency:8.004	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:10.638	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37430	target_addr:172.64.147.104:443
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:155.384	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49460	target_addr:104.21.86.125:443
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:157.667	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60794	target_addr:104.21.26.208:443
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:166.787	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49462	target_addr:104.21.86.125:443
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:197.100	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:03:45Z	status:FAILURE	latency:357.224	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:757.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:1069.296	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:03:45Z	status:HEALTHY	latency:1085.042	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:08:45Z	status:UNKNOWN	latency:8.404	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:12.774	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45888	target_addr:172.64.147.104:443
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:77.283	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46854	target_addr:104.21.26.208:443
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:79.630	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43736	target_addr:172.67.219.211:443
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:177.281	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41140	target_addr:104.21.86.125:443
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:196.701	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:836.742	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:1079.058	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:08:45Z	status:HEALTHY	latency:1110.243	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:08:45Z	status:FAILURE	latency:4877.189	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:32.054	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42104	target_addr:104.18.40.152:443
time:2026-09-29T20:13:45Z	status:UNKNOWN	latency:56.854	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:159.041	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44026	target_addr:172.67.219.211:443
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:160.873	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35974	target_addr:104.21.26.208:443
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:162.869	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44032	target_addr:172.67.219.211:443
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:198.028	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:13:45Z	status:FAILURE	latency:656.820	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:780.988	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:1043.017	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:13:45Z	status:HEALTHY	latency:1324.472	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:18:45Z	status:UNKNOWN	latency:7.444	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:15.368	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51370	target_addr:104.18.40.152:443
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:152.825	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41310	target_addr:172.67.219.211:443
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:159.504	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41306	target_addr:172.67.219.211:443
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:165.213	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57010	target_addr:104.21.26.208:443
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:237.571	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:18:45Z	status:FAILURE	latency:628.000	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:762.137	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:966.045	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:18:45Z	status:HEALTHY	latency:1074.491	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:23:46Z	status:UNKNOWN	latency:7.376	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:11.377	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41172	target_addr:172.64.147.104:443
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:72.983	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44444	target_addr:104.21.86.125:443
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:156.752	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53564	target_addr:172.67.168.140:443
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:167.177	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44450	target_addr:104.21.86.125:443
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:258.225	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:23:46Z	status:FAILURE	latency:622.445	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:1086.199	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:1135.103	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:23:46Z	status:HEALTHY	latency:1406.078	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:9.774	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32784	target_addr:104.18.40.152:443
time:2026-09-29T20:28:46Z	status:UNKNOWN	latency:34.340	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:73.632	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41696	target_addr:172.67.219.211:443
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:156.998	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51808	target_addr:172.67.168.140:443
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:175.051	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41684	target_addr:172.67.219.211:443
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:188.536	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:28:46Z	status:FAILURE	latency:410.273	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:1243.317	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:1328.724	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:28:46Z	status:HEALTHY	latency:1396.270	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:33:46Z	status:UNKNOWN	latency:8.375	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:14.240	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53158	target_addr:172.64.147.104:443
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:75.185	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40480	target_addr:172.67.219.211:443
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:167.909	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42952	target_addr:104.21.86.125:443
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:176.070	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55196	target_addr:104.21.26.208:443
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:250.854	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:33:46Z	status:FAILURE	latency:420.582	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:859.627	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:1031.339	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:33:46Z	status:HEALTHY	latency:1180.442	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:38:46Z	status:UNKNOWN	latency:8.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:14.209	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51856	target_addr:172.64.147.104:443
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:31.016	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33900	target_addr:104.21.86.125:443
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:69.300	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57202	target_addr:104.21.26.208:443
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:83.577	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50966	target_addr:172.67.219.211:443
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:243.376	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:38:46Z	status:FAILURE	latency:407.960	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:854.342	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:1003.799	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:38:46Z	status:HEALTHY	latency:1142.939	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:43:46Z	status:UNKNOWN	latency:8.295	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:17.052	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37398	target_addr:104.18.40.152:443
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:21.345	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50256	target_addr:104.21.86.125:443
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:158.514	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59394	target_addr:104.21.26.208:443
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:164.614	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46836	target_addr:172.67.219.211:443
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:284.044	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:43:46Z	status:FAILURE	latency:656.584	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:687.882	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:700.857	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:43:46Z	status:HEALTHY	latency:1387.662	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:48:46Z	status:UNKNOWN	latency:8.575	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:17.446	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37838	target_addr:104.18.40.152:443
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:155.002	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43898	target_addr:172.67.168.140:443
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:155.802	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56958	target_addr:104.21.86.125:443
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:160.869	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55960	target_addr:172.67.219.211:443
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:238.988	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:48:46Z	status:FAILURE	latency:415.409	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:739.404	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:1141.226	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:48:46Z	status:HEALTHY	latency:1181.215	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:10.294	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52710	target_addr:172.64.147.104:443
time:2026-09-29T20:53:46Z	status:UNKNOWN	latency:56.577	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:175.906	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58144	target_addr:172.67.219.211:443
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:176.834	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58148	target_addr:172.67.219.211:443
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:177.304	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56862	target_addr:172.67.168.140:443
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:201.286	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:53:46Z	status:FAILURE	latency:733.747	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:1117.578	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:1120.091	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:53:46Z	status:HEALTHY	latency:1446.380	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:58:46Z	status:UNKNOWN	latency:7.916	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:13.505	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42590	target_addr:172.64.147.104:443
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:18.419	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60976	target_addr:172.67.219.211:443
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:74.188	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51184	target_addr:104.21.26.208:443
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:168.079	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45072	target_addr:104.21.86.125:443
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:211.840	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:58:46Z	status:FAILURE	latency:527.212	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:744.117	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:1093.727	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T20:58:46Z	status:HEALTHY	latency:1492.312	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:03:46Z	status:UNKNOWN	latency:8.186	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:13.729	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43546	target_addr:172.64.147.104:443
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:75.683	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48848	target_addr:172.67.219.211:443
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:155.566	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48860	target_addr:172.67.219.211:443
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:157.004	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42704	target_addr:104.21.26.208:443
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:214.670	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:312.266	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:322.342	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:03:46Z	status:FAILURE	latency:654.681	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:03:46Z	status:HEALTHY	latency:674.265	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:14.875	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40150	target_addr:172.64.147.104:443
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:73.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58924	target_addr:104.21.26.208:443
time:2026-09-29T21:08:46Z	status:UNKNOWN	latency:154.062	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:155.369	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38108	target_addr:172.67.219.211:443
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:175.306	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38102	target_addr:172.67.219.211:443
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:214.619	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:298.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:08:46Z	status:FAILURE	latency:637.226	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:669.147	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:08:46Z	status:HEALTHY	latency:1339.998	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:13:46Z	status:UNKNOWN	latency:6.748	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:12.373	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33654	target_addr:104.18.40.152:443
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:19.791	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48298	target_addr:172.67.168.140:443
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:152.030	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44032	target_addr:104.21.86.125:443
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:167.215	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55458	target_addr:172.67.219.211:443
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:211.674	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:13:46Z	status:FAILURE	latency:235.585	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:656.950	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:706.470	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:13:46Z	status:HEALTHY	latency:1258.281	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:18:46Z	status:UNKNOWN	latency:7.159	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:18.425	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46002	target_addr:104.18.40.152:443
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:73.332	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39950	target_addr:104.21.86.125:443
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:156.438	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52252	target_addr:172.67.219.211:443
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:160.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33050	target_addr:104.21.26.208:443
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:270.626	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:18:46Z	status:FAILURE	latency:481.477	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:634.531	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:670.436	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:18:46Z	status:HEALTHY	latency:4270.316	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:13.510	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57952	target_addr:104.18.40.152:443
time:2026-09-29T21:23:46Z	status:UNKNOWN	latency:36.058	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:71.810	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51954	target_addr:172.67.219.211:443
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:163.821	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58114	target_addr:172.67.168.140:443
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:176.391	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51938	target_addr:172.67.219.211:443
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:320.563	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:365.570	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:23:46Z	status:FAILURE	latency:432.339	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:691.634	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:23:46Z	status:HEALTHY	latency:984.252	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:28:46Z	status:UNKNOWN	latency:8.411	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:12.732	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38712	target_addr:104.18.40.152:443
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:78.510	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43440	target_addr:172.67.219.211:443
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:159.133	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41250	target_addr:104.21.86.125:443
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:164.828	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48884	target_addr:104.21.26.208:443
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:253.441	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:645.916	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:28:46Z	status:FAILURE	latency:698.615	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:708.988	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:28:46Z	status:HEALTHY	latency:2625.031	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:33:46Z	status:UNKNOWN	latency:7.726	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:15.304	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54878	target_addr:104.18.40.152:443
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:160.988	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37336	target_addr:172.67.219.211:443
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:162.515	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37592	target_addr:104.21.86.125:443
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:175.517	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59252	target_addr:104.21.26.208:443
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:193.197	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:645.334	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:647.895	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:33:46Z	status:FAILURE	latency:651.834	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:33:46Z	status:HEALTHY	latency:667.379	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:38:46Z	status:UNKNOWN	latency:7.891	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:14.448	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42138	target_addr:104.18.40.152:443
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:150.704	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40460	target_addr:104.21.86.125:443
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:162.103	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56266	target_addr:104.21.26.208:443
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:176.589	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40470	target_addr:104.21.86.125:443
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:208.418	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:306.479	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:343.308	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:38:46Z	status:FAILURE	latency:587.471	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:38:46Z	status:HEALTHY	latency:681.684	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:14.228	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58836	target_addr:172.64.147.104:443
time:2026-09-29T21:43:46Z	status:UNKNOWN	latency:15.585	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:23.633	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60888	target_addr:172.67.219.211:443
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:160.499	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45670	target_addr:172.67.168.140:443
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:161.733	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57910	target_addr:104.21.86.125:443
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:356.924	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:365.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:43:46Z	status:FAILURE	latency:404.338	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:649.937	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:43:46Z	status:HEALTHY	latency:5356.566	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:48:46Z	status:UNKNOWN	latency:7.719	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:15.676	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46288	target_addr:172.64.147.104:443
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:88.778	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:91.568	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:127.169	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:161.517	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51224	target_addr:104.21.86.125:443
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:164.821	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41790	target_addr:104.21.26.208:443
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:174.985	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51228	target_addr:104.21.86.125:443
time:2026-09-29T21:48:46Z	status:FAILURE	latency:279.100	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:48:46Z	status:HEALTHY	latency:440.324	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:53:46Z	status:UNKNOWN	latency:6.631	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:12.036	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45842	target_addr:172.64.147.104:443
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:157.682	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47436	target_addr:172.67.219.211:443
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:158.485	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51522	target_addr:104.21.86.125:443
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:172.819	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50060	target_addr:104.21.26.208:443
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:227.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:333.153	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:645.198	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:53:46Z	status:FAILURE	latency:668.937	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:53:46Z	status:HEALTHY	latency:955.474	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:58:46Z	status:UNKNOWN	latency:8.019	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:13.248	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51702	target_addr:172.64.147.104:443
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:78.095	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59066	target_addr:104.21.86.125:443
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:132.618	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:176.042	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59064	target_addr:104.21.86.125:443
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:177.759	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54522	target_addr:172.67.168.140:443
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:252.108	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:58:46Z	status:FAILURE	latency:667.970	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:688.581	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T21:58:46Z	status:HEALTHY	latency:970.034	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:03:46Z	status:UNKNOWN	latency:7.819	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:12.977	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55700	target_addr:104.18.40.152:443
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:154.663	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54584	target_addr:104.21.86.125:443
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:156.032	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43390	target_addr:172.67.168.140:443
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:180.009	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42006	target_addr:172.67.219.211:443
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:218.899	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:332.731	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:351.310	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:03:46Z	status:FAILURE	latency:468.571	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:03:46Z	status:HEALTHY	latency:653.393	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:08:46Z	status:UNKNOWN	latency:7.118	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:11.061	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34348	target_addr:172.64.147.104:443
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:17.494	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60876	target_addr:172.67.219.211:443
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:21.522	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60890	target_addr:172.67.219.211:443
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:127.353	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:160.464	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60180	target_addr:104.21.26.208:443
time:2026-09-29T22:08:46Z	status:FAILURE	latency:525.549	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:757.770	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:1034.317	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:08:46Z	status:HEALTHY	latency:1396.743	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:13:46Z	status:UNKNOWN	latency:7.508	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:11.699	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45864	target_addr:104.18.40.152:443
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:25.093	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34132	target_addr:172.67.219.211:443
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:25.169	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51590	target_addr:104.21.26.208:443
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:167.856	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34134	target_addr:172.67.219.211:443
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:272.605	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:638.170	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:13:46Z	status:FAILURE	latency:686.262	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:1134.063	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:13:46Z	status:HEALTHY	latency:1470.412	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:18:46Z	status:UNKNOWN	latency:7.447	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:11.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45980	target_addr:104.18.40.152:443
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:20.339	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37364	target_addr:104.21.86.125:443
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:38.067	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45050	target_addr:104.21.26.208:443
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:177.265	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37372	target_addr:104.21.86.125:443
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:230.543	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:18:46Z	status:FAILURE	latency:463.421	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:555.847	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:787.074	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:18:46Z	status:HEALTHY	latency:1092.789	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:23:46Z	status:UNKNOWN	latency:7.337	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:16.980	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33046	target_addr:172.64.147.104:443
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:39.541	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40026	target_addr:104.21.86.125:443
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:164.312	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43410	target_addr:172.67.219.211:443
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:169.182	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43336	target_addr:172.67.168.140:443
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:250.927	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:514.582	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:23:46Z	status:FAILURE	latency:622.071	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:1030.061	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:23:46Z	status:HEALTHY	latency:1085.166	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:28:46Z	status:UNKNOWN	latency:7.876	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:13.082	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59034	target_addr:104.18.40.152:443
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:156.915	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53562	target_addr:172.67.219.211:443
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:164.770	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52712	target_addr:172.67.168.140:443
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:180.950	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53570	target_addr:172.67.219.211:443
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:209.857	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:28:46Z	status:FAILURE	latency:222.649	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:650.315	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:917.920	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:28:46Z	status:HEALTHY	latency:1047.786	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:33:46Z	status:UNKNOWN	latency:7.767	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:10.957	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54388	target_addr:104.18.40.152:443
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:161.756	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47662	target_addr:172.67.219.211:443
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:162.612	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59416	target_addr:104.21.26.208:443
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:163.447	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37922	target_addr:104.21.86.125:443
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:225.918	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:33:46Z	status:FAILURE	latency:479.249	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:939.316	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:1091.361	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:33:46Z	status:HEALTHY	latency:1138.518	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:38:46Z	status:UNKNOWN	latency:7.404	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:10.384	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54666	target_addr:172.64.147.104:443
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:20.066	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43826	target_addr:104.21.86.125:443
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:154.604	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43812	target_addr:104.21.86.125:443
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:168.243	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56656	target_addr:104.21.26.208:443
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:326.956	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:38:46Z	status:FAILURE	latency:655.811	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:1333.620	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:1359.442	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:38:46Z	status:HEALTHY	latency:1559.979	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:43:46Z	status:UNKNOWN	latency:7.386	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:15.194	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49978	target_addr:104.18.40.152:443
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:153.412	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36874	target_addr:104.21.26.208:443
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:169.906	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36702	target_addr:172.67.219.211:443
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:189.725	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52442	target_addr:104.21.86.125:443
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:209.875	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:526.885	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:43:46Z	status:FAILURE	latency:711.601	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:1086.326	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:43:46Z	status:HEALTHY	latency:1464.782	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:48:46Z	status:UNKNOWN	latency:7.041	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:9.767	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40290	target_addr:104.18.40.152:443
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:20.491	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47280	target_addr:104.21.26.208:443
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:27.536	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44946	target_addr:172.67.219.211:443
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:159.302	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44936	target_addr:172.67.219.211:443
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:249.340	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:48:46Z	status:FAILURE	latency:661.756	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:1108.613	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:1424.464	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:48:46Z	status:HEALTHY	latency:1497.240	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:53:46Z	status:UNKNOWN	latency:8.806	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:10.743	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51246	target_addr:104.18.40.152:443
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:86.504	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36674	target_addr:104.21.26.208:443
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:171.459	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41032	target_addr:172.67.219.211:443
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:173.512	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41020	target_addr:172.67.219.211:443
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:210.305	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:53:46Z	status:FAILURE	latency:649.721	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:1079.672	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:1125.519	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:53:46Z	status:HEALTHY	latency:1423.733	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:58:46Z	status:UNKNOWN	latency:9.745	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:13.062	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41396	target_addr:172.64.147.104:443
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:40.809	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54872	target_addr:104.21.26.208:443
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:158.838	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59286	target_addr:104.21.86.125:443
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:170.770	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59300	target_addr:104.21.86.125:443
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:237.568	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:58:46Z	status:FAILURE	latency:424.216	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:576.829	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:1145.047	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T22:58:46Z	status:HEALTHY	latency:1203.613	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:10.971	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42134	target_addr:172.64.147.104:443
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:19.599	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44990	target_addr:104.21.86.125:443
time:2026-09-29T23:03:46Z	status:UNKNOWN	latency:57.024	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:161.041	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45236	target_addr:172.67.219.211:443
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:174.950	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60214	target_addr:172.67.168.140:443
time:2026-09-29T23:03:46Z	status:FAILURE	latency:655.033	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:721.540	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:1008.298	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:1030.695	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:03:46Z	status:HEALTHY	latency:1259.237	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:08:46Z	status:UNKNOWN	latency:7.868	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:10.279	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41480	target_addr:172.64.147.104:443
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:155.219	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38882	target_addr:172.67.219.211:443
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:164.203	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57626	target_addr:104.21.26.208:443
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:213.402	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:353.549	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:615.403	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:632.085	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38898	target_addr:172.67.219.211:443
time:2026-09-29T23:08:46Z	status:HEALTHY	latency:647.013	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:08:46Z	status:FAILURE	latency:812.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:13:46Z	status:UNKNOWN	latency:8.180	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:13.835	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52026	target_addr:104.18.40.152:443
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:22.884	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43642	target_addr:172.67.219.211:443
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:76.962	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:85.015	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33496	target_addr:104.21.26.208:443
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:161.006	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43636	target_addr:172.67.219.211:443
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:218.328	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:643.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:13:46Z	status:HEALTHY	latency:677.002	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:13:46Z	status:FAILURE	latency:758.895	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:18:46Z	status:UNKNOWN	latency:7.939	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:13.378	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51336	target_addr:172.64.147.104:443
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:22.873	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42302	target_addr:104.21.26.208:443
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:87.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44780	target_addr:104.21.86.125:443
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:167.436	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44778	target_addr:104.21.86.125:443
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:240.235	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:338.653	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:18:46Z	status:FAILURE	latency:440.970	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:650.069	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:18:46Z	status:HEALTHY	latency:651.770	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:23:46Z	status:UNKNOWN	latency:7.230	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:13.944	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36126	target_addr:104.18.40.152:443
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:85.898	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33726	target_addr:104.21.86.125:443
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:92.772	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42764	target_addr:172.67.219.211:443
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:166.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41692	target_addr:172.67.168.140:443
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:210.817	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:618.375	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:662.653	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:23:46Z	status:FAILURE	latency:691.221	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:23:46Z	status:HEALTHY	latency:715.433	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:19.012	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57992	target_addr:172.64.147.104:443
time:2026-09-29T23:28:46Z	status:UNKNOWN	latency:57.605	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:82.624	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55626	target_addr:172.67.219.211:443
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:95.182	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59904	target_addr:104.21.26.208:443
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:158.525	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55618	target_addr:172.67.219.211:443
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:203.378	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:28:46Z	status:FAILURE	latency:629.854	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:1052.483	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:1053.957	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:28:46Z	status:HEALTHY	latency:1060.794	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:33:46Z	status:UNKNOWN	latency:7.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:12.935	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55074	target_addr:104.18.40.152:443
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:23.167	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41272	target_addr:104.21.86.125:443
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:162.770	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37592	target_addr:172.67.168.140:443
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:164.562	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54356	target_addr:172.67.219.211:443
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:308.995	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:443.696	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:33:46Z	status:FAILURE	latency:635.628	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:1020.467	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:33:46Z	status:HEALTHY	latency:1032.363	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:38:46Z	status:UNKNOWN	latency:6.744	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:11.682	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44126	target_addr:172.64.147.104:443
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:19.597	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56842	target_addr:104.21.86.125:443
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:153.134	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41840	target_addr:172.67.168.140:443
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:160.918	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56838	target_addr:104.21.86.125:443
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:218.421	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:527.032	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:38:46Z	status:FAILURE	latency:714.474	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:1152.886	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:38:46Z	status:HEALTHY	latency:1474.756	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:43:46Z	status:UNKNOWN	latency:7.308	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:13.511	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46384	target_addr:172.64.147.104:443
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:154.143	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57654	target_addr:104.21.26.208:443
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:158.065	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49780	target_addr:172.67.219.211:443
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:171.264	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49788	target_addr:172.67.219.211:443
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:287.869	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:43:46Z	status:FAILURE	latency:665.828	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:1070.855	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:1125.005	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:43:46Z	status:HEALTHY	latency:1132.921	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:48:46Z	status:UNKNOWN	latency:9.757	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:13.026	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35550	target_addr:104.18.40.152:443
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:17.645	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35328	target_addr:172.67.219.211:443
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:86.579	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36450	target_addr:104.21.26.208:443
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:86.906	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32880	target_addr:104.21.86.125:443
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:126.583	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:215.219	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:338.101	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:48:46Z	status:FAILURE	latency:516.366	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:48:46Z	status:HEALTHY	latency:621.960	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:53:46Z	status:UNKNOWN	latency:6.544	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:11.359	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54098	target_addr:172.64.147.104:443
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:79.687	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:166.727	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50590	target_addr:104.21.86.125:443
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:172.378	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52478	target_addr:172.67.219.211:443
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:176.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40954	target_addr:104.21.26.208:443
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:206.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:53:46Z	status:FAILURE	latency:639.494	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:640.224	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:53:46Z	status:HEALTHY	latency:714.456	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:58:46Z	status:UNKNOWN	latency:7.285	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:18.808	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55130	target_addr:104.21.86.125:443
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:19.743	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39826	target_addr:104.18.40.152:443
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:81.141	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51504	target_addr:104.21.26.208:443
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:157.180	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55578	target_addr:172.67.219.211:443
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:199.407	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:531.885	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:58:46Z	status:FAILURE	latency:657.891	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:1082.738	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-29T23:58:46Z	status:HEALTHY	latency:1414.288	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:03:46Z	status:UNKNOWN	latency:7.723	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:12.075	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45058	target_addr:104.18.40.152:443
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:20.568	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45578	target_addr:104.21.86.125:443
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:155.725	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50284	target_addr:172.67.168.140:443
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:164.827	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35764	target_addr:172.67.219.211:443
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:247.197	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:03:46Z	status:FAILURE	latency:754.399	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:896.553	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:1075.000	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:03:46Z	status:HEALTHY	latency:1076.489	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:08:46Z	status:UNKNOWN	latency:5.421	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:11.063	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59658	target_addr:104.18.40.152:443
time:2026-09-30T00:08:46Z	status:FAILURE	latency:52.660	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:81.509	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60820	target_addr:104.21.86.125:443
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:161.274	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60816	target_addr:104.21.86.125:443
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:176.927	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40954	target_addr:104.21.26.208:443
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:346.995	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:471.307	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:527.837	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:08:46Z	status:HEALTHY	latency:1076.842	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:13:46Z	status:UNKNOWN	latency:7.742	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:11.219	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53786	target_addr:104.18.40.152:443
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:17.861	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42272	target_addr:104.21.86.125:443
time:2026-09-30T00:13:46Z	status:FAILURE	latency:50.846	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:90.340	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37906	target_addr:172.67.219.211:443
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:153.116	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37206	target_addr:172.67.168.140:443
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:244.545	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:1141.317	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:1208.389	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:13:46Z	status:HEALTHY	latency:1611.705	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:18:46Z	status:UNKNOWN	latency:8.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:14.934	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42614	target_addr:104.18.40.152:443
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:175.454	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53074	target_addr:104.21.26.208:443
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:177.227	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34748	target_addr:104.21.86.125:443
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:179.923	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50312	target_addr:172.67.219.211:443
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:302.381	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:462.493	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:18:46Z	status:FAILURE	latency:661.865	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:1025.661	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:18:46Z	status:HEALTHY	latency:1311.998	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:23:46Z	status:UNKNOWN	latency:7.952	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:12.804	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34180	target_addr:172.64.147.104:443
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:76.148	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42784	target_addr:172.67.219.211:443
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:91.530	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51650	target_addr:104.21.26.208:443
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:164.012	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55726	target_addr:104.21.86.125:443
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:216.511	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:23:46Z	status:FAILURE	latency:624.960	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:878.112	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:1136.129	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:23:46Z	status:HEALTHY	latency:1567.885	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:28:46Z	status:UNKNOWN	latency:6.213	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:11.535	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37910	target_addr:104.18.40.152:443
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:86.064	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47744	target_addr:172.67.219.211:443
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:152.412	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41956	target_addr:104.21.86.125:443
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:159.819	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56598	target_addr:104.21.26.208:443
time:2026-09-30T00:28:46Z	status:FAILURE	latency:218.214	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:245.867	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:531.942	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:1006.599	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:28:46Z	status:HEALTHY	latency:1136.698	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:33:46Z	status:UNKNOWN	latency:7.653	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:10.969	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53542	target_addr:172.64.147.104:443
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:76.303	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37224	target_addr:104.21.86.125:443
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:90.603	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37236	target_addr:104.21.86.125:443
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:177.741	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45826	target_addr:172.67.168.140:443
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:261.471	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:33:46Z	status:FAILURE	latency:635.503	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:840.929	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:1174.125	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:33:46Z	status:HEALTHY	latency:1431.521	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:38:47Z	status:UNKNOWN	latency:6.560	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:10.882	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43606	target_addr:104.18.40.152:443
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:159.659	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49024	target_addr:172.67.168.140:443
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:161.181	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57846	target_addr:104.21.86.125:443
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:168.512	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57858	target_addr:104.21.86.125:443
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:262.596	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:38:47Z	status:FAILURE	latency:367.978	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:549.577	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:1128.246	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:38:47Z	status:HEALTHY	latency:1158.243	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:10.252	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50862	target_addr:104.18.40.152:443
time:2026-09-30T00:43:47Z	status:UNKNOWN	latency:34.976	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:36.444	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33534	target_addr:104.21.86.125:443
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:175.049	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33546	target_addr:104.21.86.125:443
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:176.769	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49206	target_addr:172.67.168.140:443
time:2026-09-30T00:43:47Z	status:FAILURE	latency:436.599	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:479.843	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:769.842	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:1070.900	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:43:47Z	status:HEALTHY	latency:1216.972	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:11.295	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53610	target_addr:172.64.147.104:443
time:2026-09-30T00:48:47Z	status:UNKNOWN	latency:34.254	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:48:47Z	status:FAILURE	latency:62.344	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:173.006	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52320	target_addr:172.67.168.140:443
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:174.622	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59798	target_addr:104.21.86.125:443
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:178.076	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59808	target_addr:104.21.86.125:443
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:194.183	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:590.786	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:1099.122	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:48:47Z	status:HEALTHY	latency:1101.441	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:53:47Z	status:UNKNOWN	latency:7.938	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:14.466	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38112	target_addr:104.18.40.152:443
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:20.633	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34216	target_addr:172.67.168.140:443
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:22.083	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52720	target_addr:104.21.86.125:443
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:173.026	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52712	target_addr:104.21.86.125:443
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:219.713	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:410.811	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:499.552	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:53:47Z	status:HEALTHY	latency:512.102	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:53:47Z	status:FAILURE	latency:692.084	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:9.444	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56658	target_addr:172.64.147.104:443
time:2026-09-30T00:58:47Z	status:UNKNOWN	latency:18.018	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:169.056	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58972	target_addr:172.67.219.211:443
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:170.441	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59320	target_addr:104.21.26.208:443
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:175.416	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35048	target_addr:104.21.86.125:443
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:215.319	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:458.489	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:58:47Z	status:FAILURE	latency:673.902	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:1049.723	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T00:58:47Z	status:HEALTHY	latency:1348.076	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:03:47Z	status:UNKNOWN	latency:8.971	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:15.797	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38136	target_addr:104.18.40.152:443
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:87.597	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47094	target_addr:104.21.86.125:443
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:154.657	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47084	target_addr:104.21.86.125:443
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:159.078	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58116	target_addr:172.67.168.140:443
time:2026-09-30T01:03:47Z	status:FAILURE	latency:236.553	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:237.669	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:735.921	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:1006.839	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:03:47Z	status:HEALTHY	latency:6111.003	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:08:47Z	status:UNKNOWN	latency:7.538	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:9.728	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32904	target_addr:172.64.147.104:443
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:17.450	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40218	target_addr:172.67.219.211:443
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:80.741	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60102	target_addr:104.21.86.125:443
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:163.933	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32818	target_addr:172.67.168.140:443
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:224.142	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:08:47Z	status:FAILURE	latency:272.205	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:1026.382	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:1139.787	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:08:47Z	status:HEALTHY	latency:2928.173	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:13:47Z	status:UNKNOWN	latency:8.752	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:21.698	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42640	target_addr:172.64.147.104:443
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:159.280	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41648	target_addr:172.67.219.211:443
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:170.550	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34268	target_addr:104.21.86.125:443
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:174.801	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44096	target_addr:104.21.26.208:443
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:239.887	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:13:47Z	status:FAILURE	latency:403.294	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:1062.039	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:1641.104	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:13:47Z	status:HEALTHY	latency:2179.813	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:18:47Z	status:UNKNOWN	latency:8.018	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:17.524	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36636	target_addr:172.64.147.104:443
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:19.314	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39074	target_addr:172.67.168.140:443
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:75.986	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53666	target_addr:172.67.219.211:443
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:81.806	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33216	target_addr:104.21.86.125:443
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:229.522	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:18:47Z	status:FAILURE	latency:652.594	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:1131.221	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:1131.357	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:18:47Z	status:HEALTHY	latency:1178.220	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:23:47Z	status:UNKNOWN	latency:7.775	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:24.957	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45094	target_addr:104.18.40.152:443
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:155.420	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35906	target_addr:104.21.86.125:443
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:162.324	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46670	target_addr:172.67.168.140:443
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:177.231	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41918	target_addr:172.67.219.211:443
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:239.582	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:491.419	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:23:47Z	status:FAILURE	latency:693.287	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:1004.765	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:23:47Z	status:HEALTHY	latency:1035.896	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:11.399	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52042	target_addr:172.64.147.104:443
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:35.456	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42354	target_addr:172.67.168.140:443
time:2026-09-30T01:28:47Z	status:UNKNOWN	latency:38.367	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:156.107	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39914	target_addr:104.21.86.125:443
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:170.914	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39928	target_addr:104.21.86.125:443
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:255.465	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:585.439	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:28:47Z	status:FAILURE	latency:663.826	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:784.980	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:28:47Z	status:HEALTHY	latency:1201.403	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:33:47Z	status:UNKNOWN	latency:8.300	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:12.312	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56638	target_addr:172.64.147.104:443
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:22.570	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34392	target_addr:172.67.219.211:443
time:2026-09-30T01:33:47Z	status:FAILURE	latency:47.922	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:155.764	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34960	target_addr:104.21.86.125:443
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:168.653	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51514	target_addr:172.67.168.140:443
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:255.624	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:787.311	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:1147.859	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:33:47Z	status:HEALTHY	latency:1460.659	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:17.140	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50622	target_addr:172.64.147.104:443
time:2026-09-30T01:38:47Z	status:UNKNOWN	latency:56.675	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:84.512	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42556	target_addr:172.67.168.140:443
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:186.422	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50364	target_addr:104.21.86.125:443
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:235.339	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:38:47Z	status:FAILURE	latency:670.734	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:911.034	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:1114.540	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:1521.130	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57986	target_addr:172.67.219.211:443
time:2026-09-30T01:38:47Z	status:HEALTHY	latency:5205.722	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:43:47Z	status:UNKNOWN	latency:10.046	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:14.165	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57398	target_addr:104.18.40.152:443
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:87.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:156.057	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48924	target_addr:172.67.219.211:443
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:177.845	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34984	target_addr:172.67.168.140:443
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:182.633	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38958	target_addr:104.21.86.125:443
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:255.612	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:307.763	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:43:47Z	status:FAILURE	latency:516.077	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:43:47Z	status:HEALTHY	latency:682.463	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:13.218	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44894	target_addr:172.64.147.104:443
time:2026-09-30T01:48:47Z	status:UNKNOWN	latency:34.667	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:154.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51858	target_addr:104.21.26.208:443
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:158.526	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37184	target_addr:172.67.219.211:443
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:165.533	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49700	target_addr:104.21.86.125:443
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:220.741	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:624.240	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:627.386	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:48:47Z	status:FAILURE	latency:644.088	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:48:47Z	status:HEALTHY	latency:708.034	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:53:47Z	status:UNKNOWN	latency:6.986	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:10.571	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41024	target_addr:104.18.40.152:443
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:80.081	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:151.060	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57564	target_addr:172.67.219.211:443
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:160.215	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60312	target_addr:172.67.168.140:443
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:177.332	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53264	target_addr:104.21.86.125:443
time:2026-09-30T01:53:47Z	status:FAILURE	latency:190.746	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:220.697	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:1179.280	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:53:47Z	status:HEALTHY	latency:3990.907	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:58:47Z	status:UNKNOWN	latency:7.532	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:11.224	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42584	target_addr:172.64.147.104:443
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:79.113	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60598	target_addr:172.67.219.211:443
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:157.517	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35478	target_addr:104.21.26.208:443
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:177.678	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60600	target_addr:172.67.219.211:443
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:223.948	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:58:47Z	status:FAILURE	latency:662.244	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:1015.691	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:1077.608	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T01:58:47Z	status:HEALTHY	latency:1118.763	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:03:47Z	status:UNKNOWN	latency:6.506	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:16.111	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54926	target_addr:172.64.147.104:443
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:159.399	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52226	target_addr:104.21.86.125:443
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:163.097	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35642	target_addr:172.67.219.211:443
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:163.489	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49160	target_addr:172.67.168.140:443
time:2026-09-30T02:03:47Z	status:FAILURE	latency:243.764	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:278.373	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:768.033	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:819.365	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:03:47Z	status:HEALTHY	latency:1138.090	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:08:47Z	status:UNKNOWN	latency:7.426	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:10.158	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51194	target_addr:104.18.40.152:443
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:158.719	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41894	target_addr:104.21.86.125:443
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:163.023	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60402	target_addr:172.67.219.211:443
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:180.573	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41808	target_addr:104.21.26.208:443
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:279.671	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:08:47Z	status:FAILURE	latency:513.357	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:1084.742	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:1111.091	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:08:47Z	status:HEALTHY	latency:1113.557	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:13:47Z	status:UNKNOWN	latency:9.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:11.882	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53072	target_addr:172.64.147.104:443
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:159.372	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32812	target_addr:172.67.168.140:443
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:156.189	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56414	target_addr:104.21.86.125:443
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:163.005	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56428	target_addr:104.21.86.125:443
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:329.607	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:449.892	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:476.371	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:13:47Z	status:FAILURE	latency:666.460	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:13:47Z	status:HEALTHY	latency:1109.381	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:14.241	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44392	target_addr:172.64.147.104:443
time:2026-09-30T02:18:47Z	status:UNKNOWN	latency:36.402	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:164.399	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60038	target_addr:104.21.86.125:443
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:164.137	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43500	target_addr:172.67.219.211:443
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:183.367	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50422	target_addr:172.67.168.140:443
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:309.963	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:18:47Z	status:FAILURE	latency:461.121	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:482.341	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:688.420	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:18:47Z	status:HEALTHY	latency:1042.579	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:23:47Z	status:UNKNOWN	latency:7.441	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:11.860	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34378	target_addr:104.18.40.152:443
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:18.836	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39186	target_addr:172.67.168.140:443
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:67.135	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56586	target_addr:172.67.219.211:443
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:157.543	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56594	target_addr:172.67.219.211:443
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:251.633	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:23:47Z	status:FAILURE	latency:692.501	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:1050.840	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:1085.512	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:23:47Z	status:HEALTHY	latency:1134.125	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:15.916	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41218	target_addr:172.64.147.104:443
time:2026-09-30T02:28:47Z	status:UNKNOWN	latency:55.882	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:69.637	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43938	target_addr:172.67.219.211:443
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:156.940	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36050	target_addr:104.21.26.208:443
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:173.128	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:174.610	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45282	target_addr:104.21.86.125:443
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:535.062	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:28:47Z	status:FAILURE	latency:664.769	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:703.853	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:28:47Z	status:HEALTHY	latency:1082.033	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:33:47Z	status:UNKNOWN	latency:9.113	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:14.269	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52102	target_addr:172.64.147.104:443
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:81.300	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55668	target_addr:172.67.219.211:443
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:156.075	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51680	target_addr:104.21.86.125:443
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:174.726	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40962	target_addr:172.67.168.140:443
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:305.068	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:33:47Z	status:FAILURE	latency:768.910	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:1143.699	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:1168.946	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:33:47Z	status:HEALTHY	latency:1173.294	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:12.327	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34000	target_addr:172.64.147.104:443
time:2026-09-30T02:38:47Z	status:UNKNOWN	latency:34.862	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:70.836	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42642	target_addr:104.21.26.208:443
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:168.576	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60706	target_addr:104.21.86.125:443
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:171.882	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60296	target_addr:172.67.219.211:443
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:311.820	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:38:47Z	status:FAILURE	latency:398.577	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:676.360	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:1671.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:38:47Z	status:HEALTHY	latency:2105.101	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:43:47Z	status:UNKNOWN	latency:6.552	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:11.891	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35800	target_addr:104.18.40.152:443
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:18.673	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35980	target_addr:172.67.168.140:443
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:18.769	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46266	target_addr:172.67.219.211:443
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:46.023	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46256	target_addr:172.67.219.211:443
time:2026-09-30T02:43:47Z	status:FAILURE	latency:210.127	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:237.848	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:448.093	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:694.977	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:43:47Z	status:HEALTHY	latency:1068.470	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:12.948	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58844	target_addr:172.64.147.104:443
time:2026-09-30T02:48:47Z	status:UNKNOWN	latency:58.002	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:72.955	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54654	target_addr:172.67.219.211:443
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:80.406	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54402	target_addr:104.21.86.125:443
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:168.151	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40280	target_addr:104.21.26.208:443
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:259.091	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:532.820	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:48:47Z	status:FAILURE	latency:643.241	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:1045.546	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:48:47Z	status:HEALTHY	latency:1331.203	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:53:47Z	status:UNKNOWN	latency:8.502	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:14.291	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33250	target_addr:172.64.147.104:443
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:68.918	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44066	target_addr:172.67.219.211:443
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:71.422	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59342	target_addr:104.21.26.208:443
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:166.085	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44074	target_addr:172.67.219.211:443
time:2026-09-30T02:53:47Z	status:FAILURE	latency:221.685	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:247.446	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:475.928	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:492.172	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:53:47Z	status:HEALTHY	latency:719.952	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:12.095	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38648	target_addr:172.64.147.104:443
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:20.901	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36800	target_addr:172.67.219.211:443
time:2026-09-30T02:58:47Z	status:UNKNOWN	latency:37.899	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:71.626	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45028	target_addr:104.21.86.125:443
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:172.595	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40580	target_addr:104.21.26.208:443
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:234.293	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:58:47Z	status:FAILURE	latency:385.323	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:961.874	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:1097.461	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T02:58:47Z	status:HEALTHY	latency:1142.805	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:13.445	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59946	target_addr:104.18.40.152:443
time:2026-09-30T03:03:47Z	status:UNKNOWN	latency:35.846	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:39.623	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49222	target_addr:104.21.26.208:443
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:75.279	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45670	target_addr:104.21.86.125:443
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:77.088	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45666	target_addr:104.21.86.125:443
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:251.255	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:03:47Z	status:FAILURE	latency:414.449	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:576.985	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:736.666	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:03:47Z	status:HEALTHY	latency:1086.423	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:08:47Z	status:UNKNOWN	latency:12.428	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:13.569	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51928	target_addr:172.64.147.104:443
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:19.951	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57844	target_addr:172.67.168.140:443
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:161.269	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53948	target_addr:104.21.86.125:443
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:205.965	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53956	target_addr:104.21.86.125:443
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:264.357	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:08:47Z	status:FAILURE	latency:638.992	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:1044.777	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:1063.801	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:08:47Z	status:HEALTHY	latency:1119.845	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:9.537	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55234	target_addr:172.64.147.104:443
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:18.550	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37670	target_addr:172.67.219.211:443
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:21.322	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37682	target_addr:172.67.219.211:443
time:2026-09-30T03:13:47Z	status:UNKNOWN	latency:68.174	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:159.761	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57192	target_addr:104.21.26.208:443
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:419.192	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:13:47Z	status:FAILURE	latency:497.314	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:527.019	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:691.448	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:13:47Z	status:HEALTHY	latency:1268.085	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:18:47Z	status:UNKNOWN	latency:8.664	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:14.317	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54448	target_addr:104.18.40.152:443
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:20.408	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39480	target_addr:172.67.219.211:443
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:160.320	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57192	target_addr:104.21.26.208:443
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:162.146	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39488	target_addr:172.67.219.211:443
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:258.531	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:469.407	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:479.571	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:18:47Z	status:FAILURE	latency:643.537	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:18:47Z	status:HEALTHY	latency:869.292	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:23:47Z	status:UNKNOWN	latency:9.271	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:11.997	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32994	target_addr:104.18.40.152:443
time:2026-09-30T03:23:47Z	status:FAILURE	latency:50.697	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:74.614	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48322	target_addr:172.67.219.211:443
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:79.376	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50162	target_addr:104.21.86.125:443
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:82.528	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60368	target_addr:104.21.26.208:443
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:247.387	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:1084.508	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:1213.523	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:23:47Z	status:HEALTHY	latency:1446.032	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:12.968	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58206	target_addr:104.18.40.152:443
time:2026-09-30T03:28:47Z	status:UNKNOWN	latency:55.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:77.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52298	target_addr:172.67.168.140:443
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:162.544	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36728	target_addr:172.67.219.211:443
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:170.294	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37880	target_addr:104.21.86.125:443
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:243.127	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:28:47Z	status:FAILURE	latency:707.502	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:723.285	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:723.981	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:28:47Z	status:HEALTHY	latency:1088.088	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:33:47Z	status:UNKNOWN	latency:7.259	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:9.728	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34356	target_addr:172.64.147.104:443
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:19.967	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37488	target_addr:104.21.26.208:443
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:20.327	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55770	target_addr:172.67.219.211:443
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:160.034	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55784	target_addr:172.67.219.211:443
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:275.767	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:708.204	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:33:47Z	status:FAILURE	latency:710.414	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:710.915	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:33:47Z	status:HEALTHY	latency:1072.518	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:26.753	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44176	target_addr:172.67.168.140:443
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:27.346	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49194	target_addr:172.64.147.104:443
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:28.071	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54486	target_addr:172.67.219.211:443
time:2026-09-30T03:38:47Z	status:UNKNOWN	latency:56.962	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:172.154	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54482	target_addr:172.67.219.211:443
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:286.360	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:480.589	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:38:47Z	status:FAILURE	latency:569.974	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:693.136	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:38:47Z	status:HEALTHY	latency:1113.420	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:43:47Z	status:UNKNOWN	latency:5.803	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:14.918	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53522	target_addr:172.64.147.104:443
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:68.626	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42192	target_addr:104.21.86.125:443
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:165.205	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51094	target_addr:172.67.168.140:443
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:173.265	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54402	target_addr:172.67.219.211:443
time:2026-09-30T03:43:47Z	status:FAILURE	latency:242.489	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:269.040	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:492.325	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:574.008	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:43:47Z	status:HEALTHY	latency:746.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:48:47Z	status:UNKNOWN	latency:8.052	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:17.467	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52168	target_addr:172.64.147.104:443
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:67.811	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35410	target_addr:104.21.86.125:443
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:76.404	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39602	target_addr:172.67.219.211:443
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:162.711	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55764	target_addr:172.67.168.140:443
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:265.867	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:455.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:48:47Z	status:FAILURE	latency:460.817	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:656.717	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:48:47Z	status:HEALTHY	latency:1385.092	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:13.370	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37552	target_addr:172.64.147.104:443
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:47.791	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47780	target_addr:172.67.219.211:443
time:2026-09-30T03:53:47Z	status:UNKNOWN	latency:56.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:171.210	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53428	target_addr:104.21.86.125:443
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:172.386	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49674	target_addr:172.67.168.140:443
time:2026-09-30T03:53:47Z	status:FAILURE	latency:234.151	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:241.072	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:517.779	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:795.648	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:53:47Z	status:HEALTHY	latency:1081.875	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:58:47Z	status:UNKNOWN	latency:10.749	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:23.601	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60988	target_addr:104.21.86.125:443
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:26.106	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58886	target_addr:104.18.40.152:443
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:41.500	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60998	target_addr:104.21.86.125:443
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:68.477	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51428	target_addr:172.67.168.140:443
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:302.581	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:58:47Z	status:FAILURE	latency:374.887	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:458.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:1087.967	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T03:58:47Z	status:HEALTHY	latency:1321.308	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:03:48Z	status:UNKNOWN	latency:9.177	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:13.336	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37488	target_addr:172.64.147.104:443
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:93.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52604	target_addr:172.67.219.211:443
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:166.250	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52588	target_addr:172.67.219.211:443
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:168.281	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37712	target_addr:172.67.168.140:443
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:297.231	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:03:48Z	status:FAILURE	latency:448.847	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:569.822	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:1081.942	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:03:48Z	status:HEALTHY	latency:1277.708	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:08:48Z	status:UNKNOWN	latency:12.807	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:14.570	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39684	target_addr:104.18.40.152:443
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:72.044	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56068	target_addr:104.21.26.208:443
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:73.923	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52746	target_addr:104.21.86.125:443
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:153.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45956	target_addr:172.67.219.211:443
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:281.890	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:556.183	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:08:48Z	status:FAILURE	latency:655.195	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:853.844	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:08:48Z	status:HEALTHY	latency:855.449	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:13:48Z	status:UNKNOWN	latency:58.610	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:151.310	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43412	target_addr:104.21.26.208:443
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:152.467	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46782	target_addr:172.67.219.211:443
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:218.671	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38918	target_addr:104.21.86.125:443
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:359.051	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:417.734	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36068	target_addr:172.64.147.104:443
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:1062.491	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:1186.755	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:13:48Z	status:FAILURE	latency:1245.652	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:13:48Z	status:HEALTHY	latency:1275.104	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:18:48Z	status:UNKNOWN	latency:8.907	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:18.648	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57048	target_addr:172.64.147.104:443
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:131.749	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:186.663	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55468	target_addr:104.21.86.125:443
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:207.173	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49108	target_addr:104.21.26.208:443
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:211.229	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41892	target_addr:172.67.219.211:443
time:2026-09-30T04:18:48Z	status:FAILURE	latency:591.655	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:716.927	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:988.554	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:18:48Z	status:HEALTHY	latency:1739.348	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:23:48Z	status:UNKNOWN	latency:9.671	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:13.259	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56806	target_addr:104.18.40.152:443
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:19.580	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43712	target_addr:104.21.86.125:443
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:89.813	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:124.471	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:163.479	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59006	target_addr:172.67.168.140:443
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:163.519	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38998	target_addr:172.67.219.211:443
time:2026-09-30T04:23:48Z	status:FAILURE	latency:196.486	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:271.820	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:23:48Z	status:HEALTHY	latency:315.922	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:28:48Z	status:UNKNOWN	latency:8.508	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:12.185	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58362	target_addr:104.18.40.152:443
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:24.163	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34422	target_addr:104.21.86.125:443
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:38.404	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33486	target_addr:104.21.26.208:443
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:84.629	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34420	target_addr:104.21.86.125:443
time:2026-09-30T04:28:48Z	status:FAILURE	latency:176.576	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:426.917	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:1089.030	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:1163.818	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:28:48Z	status:HEALTHY	latency:1499.449	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:33:48Z	status:UNKNOWN	latency:7.744	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:8.979	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34716	target_addr:104.18.40.152:443
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:20.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56544	target_addr:104.21.26.208:443
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:20.571	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59532	target_addr:172.67.219.211:443
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:170.955	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59526	target_addr:172.67.219.211:443
time:2026-09-30T04:33:48Z	status:FAILURE	latency:227.183	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:234.108	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:790.711	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:1108.619	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:33:48Z	status:HEALTHY	latency:1190.727	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:38:48Z	status:UNKNOWN	latency:9.592	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:13.722	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59732	target_addr:172.64.147.104:443
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:21.826	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37398	target_addr:104.21.86.125:443
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:168.192	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46162	target_addr:104.21.26.208:443
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:174.592	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45992	target_addr:172.67.219.211:443
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:209.832	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:38:48Z	status:FAILURE	latency:366.314	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:527.384	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:1044.617	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:38:48Z	status:HEALTHY	latency:1052.055	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:43:48Z	status:UNKNOWN	latency:12.741	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:19.172	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36992	target_addr:172.64.147.104:443
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:79.800	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44902	target_addr:104.21.26.208:443
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:154.703	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43640	target_addr:172.67.219.211:443
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:159.804	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43652	target_addr:172.67.219.211:443
time:2026-09-30T04:43:48Z	status:FAILURE	latency:236.813	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:272.646	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:561.144	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:571.391	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:43:48Z	status:HEALTHY	latency:574.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:48:48Z	status:UNKNOWN	latency:6.914	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:11.673	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34018	target_addr:172.64.147.104:443
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:161.897	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36730	target_addr:172.67.219.211:443
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:164.911	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59280	target_addr:104.21.86.125:443
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:166.866	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33392	target_addr:172.67.168.140:443
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:252.063	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:48:48Z	status:FAILURE	latency:401.458	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:987.342	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:1027.403	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:48:48Z	status:HEALTHY	latency:1047.958	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:53:48Z	status:UNKNOWN	latency:10.239	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:40.898	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40492	target_addr:172.67.168.140:443
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:48.704	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50284	target_addr:172.64.147.104:443
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:76.791	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58324	target_addr:104.21.86.125:443
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:165.796	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58322	target_addr:104.21.86.125:443
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:267.976	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:53:48Z	status:FAILURE	latency:288.309	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:1092.589	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:1123.079	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:53:48Z	status:HEALTHY	latency:1289.899	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:58:48Z	status:UNKNOWN	latency:12.919	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:17.121	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50896	target_addr:104.18.40.152:443
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:76.998	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52366	target_addr:104.21.86.125:443
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:94.120	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56742	target_addr:172.67.168.140:443
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:168.128	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52376	target_addr:104.21.86.125:443
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:265.950	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:58:48Z	status:FAILURE	latency:552.011	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:780.467	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:821.612	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T04:58:48Z	status:HEALTHY	latency:1042.148	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:03:48Z	status:UNKNOWN	latency:7.704	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:11.614	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33650	target_addr:172.64.147.104:443
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:18.931	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45612	target_addr:104.21.86.125:443
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:22.777	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45624	target_addr:104.21.86.125:443
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:26.833	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51126	target_addr:172.67.168.140:443
time:2026-09-30T05:03:48Z	status:FAILURE	latency:170.223	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:236.521	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:576.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:743.027	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:03:48Z	status:HEALTHY	latency:1099.998	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:08:48Z	status:UNKNOWN	latency:7.367	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:8.921	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48320	target_addr:104.18.40.152:443
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:18.749	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36996	target_addr:172.67.168.140:443
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:70.414	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34042	target_addr:172.67.219.211:443
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:166.134	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34050	target_addr:172.67.219.211:443
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:280.590	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:08:48Z	status:FAILURE	latency:669.127	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:1096.117	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:1108.866	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:08:48Z	status:HEALTHY	latency:1198.282	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:13:48Z	status:UNKNOWN	latency:7.382	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:14.369	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57564	target_addr:172.64.147.104:443
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:19.841	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33226	target_addr:172.67.219.211:443
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:81.325	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34790	target_addr:172.67.168.140:443
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:157.338	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55326	target_addr:104.21.86.125:443
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:283.217	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:13:48Z	status:FAILURE	latency:383.954	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:715.743	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:830.084	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:13:48Z	status:HEALTHY	latency:1122.272	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:18:48Z	status:UNKNOWN	latency:9.526	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:13.765	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37978	target_addr:172.64.147.104:443
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:38.452	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45508	target_addr:172.67.219.211:443
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:79.677	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56376	target_addr:104.21.26.208:443
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:168.682	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45514	target_addr:172.67.219.211:443
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:385.815	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:18:48Z	status:FAILURE	latency:399.745	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:518.447	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:766.565	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:18:48Z	status:HEALTHY	latency:808.676	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:23:48Z	status:UNKNOWN	latency:7.599	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:10.260	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60492	target_addr:172.64.147.104:443
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:18.293	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47526	target_addr:172.67.168.140:443
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:19.249	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50122	target_addr:172.67.219.211:443
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:20.636	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40868	target_addr:104.21.86.125:443
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:258.052	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:566.045	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:573.207	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:23:48Z	status:FAILURE	latency:668.706	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:23:48Z	status:HEALTHY	latency:1197.830	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:28:48Z	status:UNKNOWN	latency:11.334	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:12.541	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39376	target_addr:104.18.40.152:443
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:21.405	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51492	target_addr:172.67.219.211:443
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:69.287	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37484	target_addr:104.21.86.125:443
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:77.079	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33996	target_addr:104.21.26.208:443
time:2026-09-30T05:28:48Z	status:FAILURE	latency:305.146	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:330.649	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:498.340	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:848.702	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:28:48Z	status:HEALTHY	latency:1098.039	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:8.838	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47060	target_addr:172.64.147.104:443
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:21.747	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39580	target_addr:172.67.219.211:443
time:2026-09-30T05:33:48Z	status:UNKNOWN	latency:54.951	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:71.001	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35542	target_addr:104.21.26.208:443
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:78.488	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48320	target_addr:104.21.86.125:443
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:272.517	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:33:48Z	status:FAILURE	latency:468.858	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:611.631	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:1164.054	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:33:48Z	status:HEALTHY	latency:1695.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:38:48Z	status:UNKNOWN	latency:8.460	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:11.653	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44414	target_addr:104.18.40.152:443
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:21.871	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40866	target_addr:104.21.26.208:443
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:78.724	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46764	target_addr:172.67.219.211:443
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:155.571	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46750	target_addr:172.67.219.211:443
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:279.958	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:38:48Z	status:FAILURE	latency:371.550	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:801.509	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:1136.325	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:38:48Z	status:HEALTHY	latency:1576.818	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:43:48Z	status:UNKNOWN	latency:6.568	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:11.881	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49392	target_addr:104.18.40.152:443
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:21.852	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49942	target_addr:172.67.168.140:443
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:168.056	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60628	target_addr:104.21.86.125:443
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:170.366	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33098	target_addr:172.67.219.211:443
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:239.757	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:43:48Z	status:FAILURE	latency:629.131	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:984.268	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:996.403	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:43:48Z	status:HEALTHY	latency:1762.883	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:10.822	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50366	target_addr:104.18.40.152:443
time:2026-09-30T05:48:48Z	status:UNKNOWN	latency:15.000	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:25.453	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55942	target_addr:172.67.168.140:443
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:72.180	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46298	target_addr:104.21.86.125:443
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:162.358	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46296	target_addr:104.21.86.125:443
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:204.132	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:759.809	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:48:48Z	status:FAILURE	latency:779.474	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:810.249	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:48:48Z	status:HEALTHY	latency:1083.490	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:53:48Z	status:UNKNOWN	latency:7.108	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:12.232	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53600	target_addr:104.18.40.152:443
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:38.720	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54128	target_addr:104.21.26.208:443
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:51.177	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49344	target_addr:172.67.219.211:443
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:92.566	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59642	target_addr:104.21.86.125:443
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:230.855	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:542.499	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:53:48Z	status:FAILURE	latency:659.814	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:713.925	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:53:48Z	status:HEALTHY	latency:1036.675	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:22.181	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34034	target_addr:172.64.147.104:443
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:68.183	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55620	target_addr:104.21.26.208:443
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:69.663	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44798	target_addr:104.21.86.125:443
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:171.547	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40902	target_addr:172.67.219.211:443
time:2026-09-30T05:58:48Z	status:FAILURE	latency:221.848	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:238.022	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:58:48Z	status:UNKNOWN	latency:409.742	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:777.973	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:803.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T05:58:48Z	status:HEALTHY	latency:1116.929	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:12.870	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49690	target_addr:172.64.147.104:443
time:2026-09-30T06:03:48Z	status:UNKNOWN	latency:56.890	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:71.619	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36116	target_addr:104.21.86.125:443
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:73.956	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59822	target_addr:172.67.168.140:443
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:164.493	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36120	target_addr:104.21.86.125:443
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:275.545	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:03:48Z	status:FAILURE	latency:384.068	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:770.711	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:770.832	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:03:48Z	status:HEALTHY	latency:1112.033	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:08:48Z	status:UNKNOWN	latency:8.007	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:12.169	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60148	target_addr:104.18.40.152:443
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:86.118	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40838	target_addr:104.21.86.125:443
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:163.485	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42194	target_addr:172.67.219.211:443
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:172.862	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51820	target_addr:172.67.168.140:443
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:207.300	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:08:48Z	status:FAILURE	latency:367.587	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:606.030	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:682.765	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:08:48Z	status:HEALTHY	latency:932.631	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:13:48Z	status:UNKNOWN	latency:8.148	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:10.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46114	target_addr:172.64.147.104:443
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:20.230	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51994	target_addr:172.67.168.140:443
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:71.913	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55170	target_addr:104.21.86.125:443
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:76.374	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55184	target_addr:104.21.86.125:443
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:272.423	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:13:48Z	status:FAILURE	latency:619.548	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:732.821	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:1191.073	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:13:48Z	status:HEALTHY	latency:1416.502	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:18:48Z	status:UNKNOWN	latency:8.173	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:12.122	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36214	target_addr:104.18.40.152:443
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:18.145	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50896	target_addr:172.67.219.211:443
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:41.994	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47196	target_addr:172.67.168.140:443
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:167.757	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50900	target_addr:172.67.219.211:443
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:245.401	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:18:48Z	status:FAILURE	latency:510.403	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:803.257	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:999.333	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:18:48Z	status:HEALTHY	latency:1047.996	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:23:48Z	status:UNKNOWN	latency:8.365	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:18.095	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50148	target_addr:172.64.147.104:443
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:129.620	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50198	target_addr:172.67.219.211:443
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:169.619	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38356	target_addr:104.21.86.125:443
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:224.610	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58060	target_addr:104.21.26.208:443
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:330.839	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:23:48Z	status:FAILURE	latency:392.691	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:545.859	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:1110.886	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:23:48Z	status:HEALTHY	latency:1182.527	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:28:48Z	status:UNKNOWN	latency:8.528	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:10.019	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33856	target_addr:104.18.40.152:443
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:36.725	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41470	target_addr:172.67.219.211:443
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:81.403	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41480	target_addr:172.67.219.211:443
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:82.022	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:90.856	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:175.376	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47552	target_addr:172.67.168.140:443
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:297.729	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:28:48Z	status:HEALTHY	latency:332.064	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:28:48Z	status:FAILURE	latency:725.872	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:33:48Z	status:UNKNOWN	latency:8.757	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:11.599	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37858	target_addr:104.18.40.152:443
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:18.675	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58870	target_addr:172.67.168.140:443
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:19.894	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56458	target_addr:172.67.219.211:443
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:73.879	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46826	target_addr:104.21.86.125:443
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:82.693	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:83.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:221.323	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:33:48Z	status:FAILURE	latency:374.772	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:33:48Z	status:HEALTHY	latency:674.644	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:16.097	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37474	target_addr:104.18.40.152:443
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:55.233	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55294	target_addr:104.21.86.125:443
time:2026-09-30T06:38:48Z	status:UNKNOWN	latency:57.015	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:163.943	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51254	target_addr:172.67.168.140:443
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:167.917	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55292	target_addr:104.21.86.125:443
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:207.075	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:529.712	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:38:48Z	status:FAILURE	latency:608.410	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:1030.950	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:38:48Z	status:HEALTHY	latency:1315.895	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:14.879	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55014	target_addr:172.64.147.104:443
time:2026-09-30T06:43:48Z	status:UNKNOWN	latency:18.621	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:37.910	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47896	target_addr:172.67.168.140:443
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:72.602	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33668	target_addr:172.67.219.211:443
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:150.180	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43004	target_addr:104.21.86.125:443
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:361.326	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:43:48Z	status:FAILURE	latency:367.882	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:417.455	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:520.374	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:43:48Z	status:HEALTHY	latency:812.942	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:48:48Z	status:UNKNOWN	latency:7.317	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:14.554	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53182	target_addr:172.64.147.104:443
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:30.668	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59576	target_addr:172.67.219.211:443
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:77.261	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56066	target_addr:172.67.168.140:443
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:182.261	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33752	target_addr:104.21.86.125:443
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:218.844	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:48:48Z	status:FAILURE	latency:368.817	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:593.667	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:618.437	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:48:48Z	status:HEALTHY	latency:744.869	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:53:48Z	status:UNKNOWN	latency:7.253	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:10.652	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48950	target_addr:172.64.147.104:443
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:35.684	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50212	target_addr:172.67.168.140:443
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:70.591	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55516	target_addr:172.67.219.211:443
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:71.349	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50724	target_addr:104.21.86.125:443
time:2026-09-30T06:53:48Z	status:FAILURE	latency:229.420	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:241.917	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:459.649	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:1675.552	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:53:48Z	status:HEALTHY	latency:2038.463	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:58:48Z	status:UNKNOWN	latency:7.178	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:8.945	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51894	target_addr:104.18.40.152:443
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:42.704	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58306	target_addr:172.67.219.211:443
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:71.986	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55046	target_addr:172.67.168.140:443
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:154.252	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58302	target_addr:172.67.219.211:443
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:257.581	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:514.008	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:616.438	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T06:58:48Z	status:FAILURE	latency:689.742	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T06:58:48Z	status:HEALTHY	latency:918.691	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:11.474	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47346	target_addr:172.64.147.104:443
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:18.646	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58274	target_addr:104.21.86.125:443
time:2026-09-30T07:03:48Z	status:UNKNOWN	latency:34.861	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:77.813	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37866	target_addr:172.67.219.211:443
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:174.641	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35282	target_addr:172.67.168.140:443
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:335.508	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:03:48Z	status:FAILURE	latency:493.672	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:580.600	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:654.851	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:03:48Z	status:HEALTHY	latency:773.244	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:08:48Z	status:UNKNOWN	latency:6.613	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:12.904	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60310	target_addr:172.64.147.104:443
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:41.176	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33534	target_addr:172.67.219.211:443
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:48.430	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33540	target_addr:172.67.219.211:443
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:117.857	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:161.923	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40554	target_addr:172.67.168.140:443
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:328.004	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:482.856	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:08:48Z	status:FAILURE	latency:753.783	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:08:48Z	status:HEALTHY	latency:1225.492	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:13:48Z	status:UNKNOWN	latency:12.557	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:15.368	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46964	target_addr:172.64.147.104:443
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:24.211	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49784	target_addr:172.67.219.211:443
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:158.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47964	target_addr:104.21.26.208:443
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:163.308	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34130	target_addr:104.21.86.125:443
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:231.458	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:521.143	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:537.958	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:13:48Z	status:FAILURE	latency:677.481	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:13:48Z	status:HEALTHY	latency:964.526	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:12.954	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51432	target_addr:104.18.40.152:443
time:2026-09-30T07:18:48Z	status:UNKNOWN	latency:37.407	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:71.060	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47342	target_addr:104.21.86.125:443
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:105.036	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45626	target_addr:172.67.168.140:443
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:147.939	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33100	target_addr:172.67.219.211:443
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:249.383	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:601.957	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:714.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:18:48Z	status:HEALTHY	latency:1004.909	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:18:48Z	status:FAILURE	latency:1577.719	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:23:48Z	status:UNKNOWN	latency:6.312	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:13.575	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49388	target_addr:104.18.40.152:443
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:168.763	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44934	target_addr:172.67.168.140:443
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:168.393	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48380	target_addr:104.21.86.125:443
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:177.013	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34214	target_addr:172.67.219.211:443
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:267.934	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:499.634	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:563.451	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:23:48Z	status:FAILURE	latency:1429.333	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:23:48Z	status:HEALTHY	latency:1601.726	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:28:48Z	status:UNKNOWN	latency:9.493	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:9.663	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41634	target_addr:104.18.40.152:443
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:19.398	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49104	target_addr:104.21.86.125:443
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:70.068	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55506	target_addr:172.67.219.211:443
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:159.250	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56324	target_addr:172.67.168.140:443
time:2026-09-30T07:28:48Z	status:FAILURE	latency:210.443	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:364.898	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:756.111	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:789.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:28:48Z	status:HEALTHY	latency:1022.498	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:11.588	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47262	target_addr:104.18.40.152:443
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:12.875	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55558	target_addr:104.21.26.208:443
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:18.040	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38856	target_addr:104.21.86.125:443
time:2026-09-30T07:33:48Z	status:UNKNOWN	latency:59.273	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:162.337	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59592	target_addr:172.67.219.211:443
time:2026-09-30T07:33:48Z	status:FAILURE	latency:199.891	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:387.297	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:489.720	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:1023.349	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:33:48Z	status:HEALTHY	latency:1123.774	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:14.116	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53572	target_addr:172.67.168.140:443
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:14.223	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35834	target_addr:172.67.219.211:443
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:15.615	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54012	target_addr:172.64.147.104:443
time:2026-09-30T07:38:49Z	status:UNKNOWN	latency:15.700	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:24.464	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35850	target_addr:172.67.219.211:443
time:2026-09-30T07:38:49Z	status:FAILURE	latency:189.231	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:226.406	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:520.291	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:689.814	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:38:49Z	status:HEALTHY	latency:788.349	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:43:49Z	status:UNKNOWN	latency:10.488	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:14.858	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37818	target_addr:172.64.147.104:443
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:66.363	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44650	target_addr:104.21.86.125:443
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:66.919	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44652	target_addr:104.21.86.125:443
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:198.916	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:703.808	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:709.305	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:762.337	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:43:49Z	status:HEALTHY	latency:1124.923	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38748	target_addr:104.21.26.208:443
time:2026-09-30T07:43:49Z	status:FAILURE	latency:1380.893	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:48:49Z	status:UNKNOWN	latency:7.590	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:13.361	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60474	target_addr:172.64.147.104:443
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:67.851	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56314	target_addr:172.67.219.211:443
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:68.302	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55598	target_addr:172.67.168.140:443
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:78.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56320	target_addr:172.67.219.211:443
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:234.878	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:48:49Z	status:FAILURE	latency:402.561	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:626.045	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:635.207	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:48:49Z	status:HEALTHY	latency:677.472	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:14.522	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33706	target_addr:104.18.40.152:443
time:2026-09-30T07:53:49Z	status:UNKNOWN	latency:38.544	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:67.238	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52310	target_addr:172.67.219.211:443
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:70.334	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35954	target_addr:104.21.86.125:443
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:75.175	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43404	target_addr:104.21.26.208:443
time:2026-09-30T07:53:49Z	status:FAILURE	latency:203.512	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:239.912	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:729.337	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:733.726	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:53:49Z	status:HEALTHY	latency:736.262	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:9.493	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50378	target_addr:104.18.40.152:443
time:2026-09-30T07:58:49Z	status:UNKNOWN	latency:12.970	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:60.605	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49654	target_addr:172.67.219.211:443
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:60.449	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39252	target_addr:172.67.168.140:443
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:67.893	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49668	target_addr:172.67.219.211:443
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:275.323	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:58:49Z	status:FAILURE	latency:342.804	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:712.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:748.103	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T07:58:49Z	status:HEALTHY	latency:929.968	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:03:49Z	status:UNKNOWN	latency:8.632	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:10.519	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33966	target_addr:104.18.40.152:443
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:68.236	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53848	target_addr:172.67.168.140:443
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:68.118	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47412	target_addr:172.67.219.211:443
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:68.246	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52210	target_addr:104.21.86.125:443
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:195.392	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:03:49Z	status:FAILURE	latency:340.281	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:640.220	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:651.201	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:03:49Z	status:HEALTHY	latency:858.262	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:08:49Z	status:UNKNOWN	latency:7.795	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:12.629	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47726	target_addr:104.18.40.152:443
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:68.007	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56068	target_addr:172.67.219.211:443
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:68.130	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46508	target_addr:104.21.26.208:443
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:77.123	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56074	target_addr:172.67.219.211:443
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:201.671	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:08:49Z	status:FAILURE	latency:325.824	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:937.510	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:982.537	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:08:49Z	status:HEALTHY	latency:1043.069	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:13:49Z	status:UNKNOWN	latency:7.459	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:13.560	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50572	target_addr:104.18.40.152:443
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:68.123	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57540	target_addr:104.21.86.125:443
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:70.821	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54564	target_addr:172.67.219.211:443
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:121.035	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60970	target_addr:104.21.26.208:443
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:235.485	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:13:49Z	status:FAILURE	latency:495.203	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:724.910	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:741.099	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:13:49Z	status:HEALTHY	latency:1137.514	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:18:49Z	status:UNKNOWN	latency:7.312	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:66.685	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37144	target_addr:104.21.86.125:443
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:66.950	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39344	target_addr:172.67.219.211:443
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:70.631	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45276	target_addr:172.64.147.104:443
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:74.061	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42314	target_addr:104.21.26.208:443
time:2026-09-30T08:18:49Z	status:FAILURE	latency:194.707	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:348.861	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:630.953	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:649.547	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:18:49Z	status:HEALTHY	latency:983.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:23:49Z	status:UNKNOWN	latency:8.493	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:13.720	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59676	target_addr:104.18.40.152:443
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:65.577	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42766	target_addr:172.67.168.140:443
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:68.147	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43404	target_addr:104.21.86.125:443
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:84.950	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43412	target_addr:104.21.86.125:443
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:281.841	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:23:49Z	status:FAILURE	latency:408.542	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:705.674	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:712.828	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:23:49Z	status:HEALTHY	latency:1870.176	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:10.323	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48474	target_addr:172.64.147.104:443
time:2026-09-30T08:28:49Z	status:UNKNOWN	latency:10.675	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:69.664	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59362	target_addr:172.67.219.211:443
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:70.342	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36054	target_addr:104.21.86.125:443
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:73.568	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33634	target_addr:104.21.26.208:443
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:216.350	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:699.919	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:736.354	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:28:49Z	status:HEALTHY	latency:761.199	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:28:49Z	status:FAILURE	latency:1318.617	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:33:49Z	status:UNKNOWN	latency:10.716	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:14.353	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48490	target_addr:104.18.40.152:443
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:68.522	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34328	target_addr:172.67.168.140:443
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:68.799	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52598	target_addr:104.21.86.125:443
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:85.386	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56530	target_addr:172.67.219.211:443
time:2026-09-30T08:33:49Z	status:FAILURE	latency:193.872	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:199.352	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:638.177	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:713.357	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:33:49Z	status:HEALTHY	latency:724.554	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:38:49Z	status:UNKNOWN	latency:7.646	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:10.695	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60980	target_addr:104.18.40.152:443
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:68.521	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33450	target_addr:104.21.86.125:443
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:69.225	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55804	target_addr:104.21.26.208:443
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:76.709	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33464	target_addr:104.21.86.125:443
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:203.331	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:38:49Z	status:FAILURE	latency:384.704	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:696.798	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:708.590	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:38:49Z	status:HEALTHY	latency:712.471	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:43:49Z	status:UNKNOWN	latency:7.956	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:12.200	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41044	target_addr:172.64.147.104:443
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:67.218	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37564	target_addr:104.21.86.125:443
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:67.949	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54172	target_addr:172.67.219.211:443
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:68.332	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40568	target_addr:172.67.168.140:443
time:2026-09-30T08:43:49Z	status:FAILURE	latency:357.377	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:525.629	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:803.620	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:804.639	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:43:49Z	status:HEALTHY	latency:5609.944	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:48:49Z	status:UNKNOWN	latency:7.679	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:9.657	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37466	target_addr:172.64.147.104:443
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:65.849	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40544	target_addr:104.21.86.125:443
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:66.664	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45030	target_addr:104.21.26.208:443
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:70.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45228	target_addr:172.67.219.211:443
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:274.768	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:48:49Z	status:FAILURE	latency:372.578	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:635.002	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:636.480	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:48:49Z	status:HEALTHY	latency:897.692	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:53:49Z	status:UNKNOWN	latency:7.316	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:11.655	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43914	target_addr:172.64.147.104:443
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:66.447	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33760	target_addr:172.67.219.211:443
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:78.146	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55960	target_addr:172.67.168.140:443
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:81.950	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38558	target_addr:104.21.86.125:443
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:193.179	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:629.831	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:639.410	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:53:49Z	status:FAILURE	latency:1250.421	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:53:49Z	status:HEALTHY	latency:1780.340	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:58:49Z	status:UNKNOWN	latency:7.963	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:10.735	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60296	target_addr:172.64.147.104:443
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:65.813	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39812	target_addr:172.67.219.211:443
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:68.266	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39820	target_addr:172.67.219.211:443
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:78.150	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51736	target_addr:104.21.26.208:443
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:246.168	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:58:49Z	status:FAILURE	latency:358.605	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:754.946	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:896.369	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T08:58:49Z	status:HEALTHY	latency:1377.666	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:23.567	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55022	target_addr:104.18.40.152:443
time:2026-09-30T09:03:49Z	status:UNKNOWN	latency:34.338	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:69.460	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49888	target_addr:172.67.168.140:443
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:72.114	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57886	target_addr:172.67.219.211:443
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:90.564	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57896	target_addr:172.67.219.211:443
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:214.287	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:03:49Z	status:FAILURE	latency:342.815	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:768.505	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:781.509	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:03:49Z	status:HEALTHY	latency:856.402	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:08:49Z	status:UNKNOWN	latency:7.298	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:11.770	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33742	target_addr:172.64.147.104:443
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:66.830	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38818	target_addr:104.21.26.208:443
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:67.099	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53880	target_addr:104.21.86.125:443
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:100.832	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:08:49Z	status:FAILURE	latency:203.343	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:678.063	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:715.609	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:762.352	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:08:49Z	status:HEALTHY	latency:1074.272	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34892	target_addr:172.67.219.211:443
time:2026-09-30T09:13:49Z	status:UNKNOWN	latency:8.842	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:9.189	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54704	target_addr:104.18.40.152:443
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:65.089	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40820	target_addr:104.21.86.125:443
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:67.766	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36712	target_addr:104.21.26.208:443
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:76.529	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40834	target_addr:104.21.86.125:443
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:212.359	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:681.253	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:701.842	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:13:49Z	status:HEALTHY	latency:744.752	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:13:49Z	status:FAILURE	latency:2340.638	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:18:49Z	status:UNKNOWN	latency:7.315	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:10.678	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57304	target_addr:172.64.147.104:443
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:67.257	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37058	target_addr:104.21.86.125:443
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:68.291	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39732	target_addr:172.67.168.140:443
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:74.336	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49926	target_addr:172.67.219.211:443
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:185.183	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:18:49Z	status:FAILURE	latency:200.153	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:653.286	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:686.663	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:18:49Z	status:HEALTHY	latency:690.370	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:23:49Z	status:UNKNOWN	latency:9.070	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:22.018	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50656	target_addr:104.18.40.152:443
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:68.075	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48600	target_addr:104.21.26.208:443
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:67.608	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47792	target_addr:104.21.86.125:443
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:76.174	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47794	target_addr:104.21.86.125:443
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:239.049	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:23:49Z	status:FAILURE	latency:388.723	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:686.177	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:798.432	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:23:49Z	status:HEALTHY	latency:899.898	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:11.564	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50646	target_addr:172.64.147.104:443
time:2026-09-30T09:28:49Z	status:UNKNOWN	latency:15.633	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:66.105	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58964	target_addr:104.21.86.125:443
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:66.691	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43990	target_addr:172.67.219.211:443
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:78.277	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51708	target_addr:172.67.168.140:443
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:280.009	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:28:49Z	status:FAILURE	latency:339.064	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:744.667	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:748.375	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:28:49Z	status:HEALTHY	latency:749.450	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:33:49Z	status:UNKNOWN	latency:7.517	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:13.875	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43024	target_addr:104.18.40.152:443
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:66.044	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41454	target_addr:172.67.168.140:443
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:67.459	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36804	target_addr:172.67.219.211:443
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:68.441	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43020	target_addr:104.21.86.125:443
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:222.219	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:33:49Z	status:FAILURE	latency:493.160	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:968.585	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:974.747	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:33:49Z	status:HEALTHY	latency:1119.793	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:38:49Z	status:UNKNOWN	latency:10.708	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:34.931	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38488	target_addr:172.64.147.104:443
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:72.265	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33770	target_addr:172.67.168.140:443
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:96.878	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:38:49Z	status:FAILURE	latency:341.469	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:667.711	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:767.060	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:1069.103	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46186	target_addr:172.67.219.211:443
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:1083.732	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46188	target_addr:172.67.219.211:443
time:2026-09-30T09:38:49Z	status:HEALTHY	latency:1777.940	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:43:49Z	status:UNKNOWN	latency:8.214	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:14.137	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46798	target_addr:104.18.40.152:443
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:67.878	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49782	target_addr:172.67.168.140:443
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:67.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47062	target_addr:104.21.86.125:443
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:69.252	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38082	target_addr:172.67.219.211:443
time:2026-09-30T09:43:49Z	status:FAILURE	latency:194.650	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:223.974	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:1032.251	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:1074.697	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:43:49Z	status:HEALTHY	latency:1159.641	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:48:49Z	status:UNKNOWN	latency:9.626	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:30.991	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54596	target_addr:104.18.40.152:443
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:65.711	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55288	target_addr:104.21.86.125:443
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:68.682	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50486	target_addr:172.67.219.211:443
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:69.463	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45986	target_addr:104.21.26.208:443
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:222.304	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:48:49Z	status:FAILURE	latency:378.356	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:1301.801	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:1311.815	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:48:49Z	status:HEALTHY	latency:1315.118	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:53:49Z	status:UNKNOWN	latency:7.907	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:10.169	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48238	target_addr:104.18.40.152:443
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:66.551	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48310	target_addr:104.21.26.208:443
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:66.769	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50394	target_addr:172.67.219.211:443
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:67.294	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50396	target_addr:172.67.219.211:443
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:223.048	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:53:49Z	status:FAILURE	latency:368.739	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:706.617	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:707.710	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:53:49Z	status:HEALTHY	latency:708.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:58:49Z	status:UNKNOWN	latency:7.251	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:9.626	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44606	target_addr:172.64.147.104:443
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:65.492	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41264	target_addr:104.21.86.125:443
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:66.031	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43540	target_addr:172.67.219.211:443
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:66.619	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36308	target_addr:172.67.168.140:443
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:186.838	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:58:49Z	status:FAILURE	latency:193.231	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:581.187	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:650.566	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T09:58:49Z	status:HEALTHY	latency:1244.281	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:03:49Z	status:UNKNOWN	latency:6.738	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:14.206	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51184	target_addr:172.64.147.104:443
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:65.891	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43714	target_addr:172.67.219.211:443
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:70.271	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37096	target_addr:104.21.26.208:443
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:140.011	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50594	target_addr:104.21.86.125:443
time:2026-09-30T10:03:49Z	status:FAILURE	latency:326.341	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:648.766	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:699.117	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:700.201	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:03:49Z	status:HEALTHY	latency:782.053	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:08:49Z	status:UNKNOWN	latency:7.206	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:9.717	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51500	target_addr:172.64.147.104:443
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:66.782	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45426	target_addr:172.67.219.211:443
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:68.490	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45428	target_addr:172.67.219.211:443
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:73.340	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35384	target_addr:104.21.26.208:443
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:195.091	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:08:49Z	status:FAILURE	latency:427.197	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:642.477	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:645.046	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:08:49Z	status:HEALTHY	latency:704.749	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:9.939	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34294	target_addr:104.18.40.152:443
time:2026-09-30T10:13:49Z	status:UNKNOWN	latency:33.171	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:67.136	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49176	target_addr:172.67.219.211:443
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:67.444	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49168	target_addr:172.67.219.211:443
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:68.436	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55858	target_addr:104.21.26.208:443
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:180.163	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:13:49Z	status:FAILURE	latency:310.939	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:867.357	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:922.810	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:13:49Z	status:HEALTHY	latency:1015.585	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:18:49Z	status:UNKNOWN	latency:7.199	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:10.859	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57190	target_addr:172.64.147.104:443
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:65.668	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44482	target_addr:172.67.219.211:443
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:66.718	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52198	target_addr:104.21.86.125:443
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:69.909	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59328	target_addr:172.67.168.140:443
time:2026-09-30T10:18:49Z	status:FAILURE	latency:193.978	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:245.137	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:758.733	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:1036.237	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:18:49Z	status:HEALTHY	latency:1050.085	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:23:49Z	status:UNKNOWN	latency:8.265	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:10.752	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54754	target_addr:172.64.147.104:443
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:68.200	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44640	target_addr:172.67.219.211:443
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:68.498	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51982	target_addr:172.67.168.140:443
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:69.031	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47034	target_addr:104.21.86.125:443
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:214.027	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:23:49Z	status:FAILURE	latency:354.740	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:971.399	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:1043.801	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:23:49Z	status:HEALTHY	latency:1702.515	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:11.336	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43066	target_addr:104.18.40.152:443
time:2026-09-30T10:28:49Z	status:UNKNOWN	latency:36.027	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:65.965	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35956	target_addr:172.67.219.211:443
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:66.768	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35960	target_addr:172.67.219.211:443
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:67.339	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34334	target_addr:104.21.26.208:443
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:179.723	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:28:49Z	status:FAILURE	latency:315.081	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:608.519	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:615.254	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:28:49Z	status:HEALTHY	latency:632.903	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:33:49Z	status:UNKNOWN	latency:8.517	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:11.399	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41638	target_addr:104.18.40.152:443
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:66.416	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45106	target_addr:172.67.219.211:443
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:66.501	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45094	target_addr:172.67.219.211:443
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:67.050	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52992	target_addr:172.67.168.140:443
time:2026-09-30T10:33:49Z	status:FAILURE	latency:199.917	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:221.844	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:613.075	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:613.784	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:33:49Z	status:HEALTHY	latency:643.337	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:38:49Z	status:UNKNOWN	latency:6.271	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:10.397	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42336	target_addr:172.64.147.104:443
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:67.811	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45628	target_addr:172.67.168.140:443
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:67.747	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46548	target_addr:172.67.219.211:443
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:68.775	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49786	target_addr:104.21.86.125:443
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:180.339	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:38:49Z	status:FAILURE	latency:200.167	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:620.417	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:632.535	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:38:49Z	status:HEALTHY	latency:648.709	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:12.425	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56754	target_addr:104.18.40.152:443
time:2026-09-30T10:43:49Z	status:UNKNOWN	latency:35.133	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:67.037	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45814	target_addr:104.21.86.125:443
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:67.583	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37828	target_addr:104.21.26.208:443
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:68.794	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45818	target_addr:104.21.86.125:443
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:174.712	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:43:49Z	status:FAILURE	latency:205.092	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:702.013	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:712.326	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:43:49Z	status:HEALTHY	latency:1064.277	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:48:50Z	status:UNKNOWN	latency:8.456	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:9.501	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37358	target_addr:104.18.40.152:443
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:66.664	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56718	target_addr:104.21.86.125:443
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:66.697	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44836	target_addr:104.21.26.208:443
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:66.751	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56722	target_addr:104.21.86.125:443
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:201.009	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:48:50Z	status:FAILURE	latency:485.591	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:694.065	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:709.490	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:48:50Z	status:HEALTHY	latency:712.409	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:53:50Z	status:UNKNOWN	latency:7.280	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:8.962	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41684	target_addr:172.64.147.104:443
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:65.738	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32844	target_addr:104.21.26.208:443
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:68.486	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36500	target_addr:104.21.86.125:443
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:95.101	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42676	target_addr:172.67.219.211:443
time:2026-09-30T10:53:50Z	status:FAILURE	latency:192.957	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:196.534	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:581.387	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:641.895	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:53:50Z	status:HEALTHY	latency:707.008	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:58:50Z	status:UNKNOWN	latency:7.256	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:14.254	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37772	target_addr:104.18.40.152:443
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:70.454	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34812	target_addr:104.21.86.125:443
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:77.072	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38562	target_addr:104.21.26.208:443
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:78.197	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34826	target_addr:104.21.86.125:443
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:217.910	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:58:50Z	status:FAILURE	latency:478.824	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:703.389	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:917.374	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T10:58:50Z	status:HEALTHY	latency:1029.863	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:10.190	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34320	target_addr:172.64.147.104:443
time:2026-09-30T11:03:50Z	status:UNKNOWN	latency:37.153	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:66.316	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34348	target_addr:172.67.219.211:443
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:67.108	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46270	target_addr:104.21.86.125:443
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:67.427	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59204	target_addr:104.21.26.208:443
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:197.603	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:03:50Z	status:FAILURE	latency:441.423	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:851.447	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:943.150	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:03:50Z	status:HEALTHY	latency:1030.377	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:08:50Z	status:UNKNOWN	latency:8.180	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:9.763	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38842	target_addr:172.64.147.104:443
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:67.477	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60184	target_addr:104.21.26.208:443
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:67.741	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47860	target_addr:104.21.86.125:443
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:67.900	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47870	target_addr:104.21.86.125:443
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:215.830	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:08:50Z	status:FAILURE	latency:357.532	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:995.371	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:999.369	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:08:50Z	status:HEALTHY	latency:999.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:13:50Z	status:UNKNOWN	latency:7.818	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:8.621	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34454	target_addr:172.64.147.104:443
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:69.346	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45542	target_addr:172.67.219.211:443
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:75.433	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60928	target_addr:172.67.168.140:443
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:78.335	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37238	target_addr:104.21.86.125:443
time:2026-09-30T11:13:50Z	status:FAILURE	latency:192.806	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:210.327	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:918.615	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:967.131	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:13:50Z	status:HEALTHY	latency:968.644	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:18:50Z	status:UNKNOWN	latency:6.710	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:9.351	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35488	target_addr:172.64.147.104:443
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:66.090	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33258	target_addr:172.67.219.211:443
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:66.474	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48644	target_addr:104.21.26.208:443
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:66.175	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36660	target_addr:104.21.86.125:443
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:184.986	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:18:50Z	status:FAILURE	latency:403.928	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:893.850	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:939.761	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:18:50Z	status:HEALTHY	latency:975.708	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:23:50Z	status:UNKNOWN	latency:7.851	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:9.041	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58694	target_addr:172.64.147.104:443
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:65.658	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33862	target_addr:172.67.168.140:443
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:70.466	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60968	target_addr:172.67.219.211:443
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:77.213	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60980	target_addr:172.67.219.211:443
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:161.896	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:23:50Z	status:FAILURE	latency:196.027	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:683.081	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:750.251	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:23:50Z	status:HEALTHY	latency:2123.612	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:28:50Z	status:UNKNOWN	latency:7.896	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:10.022	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50372	target_addr:104.18.40.152:443
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:67.539	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35392	target_addr:104.21.26.208:443
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:68.141	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59966	target_addr:172.67.219.211:443
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:74.643	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59970	target_addr:172.67.219.211:443
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:242.815	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:28:50Z	status:FAILURE	latency:392.501	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:875.217	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:938.967	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:28:50Z	status:HEALTHY	latency:941.926	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:33:50Z	status:UNKNOWN	latency:9.410	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:10.118	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40680	target_addr:104.18.40.152:443
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:176.918	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:33:50Z	status:FAILURE	latency:466.297	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:896.457	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:903.869	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:1076.561	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57612	target_addr:172.67.168.140:443
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:1081.313	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45620	target_addr:172.67.219.211:443
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:1081.274	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33308	target_addr:104.21.86.125:443
time:2026-09-30T11:33:50Z	status:HEALTHY	latency:1881.093	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:38:50Z	status:UNKNOWN	latency:8.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:10.382	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48212	target_addr:104.18.40.152:443
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:67.665	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45188	target_addr:172.67.168.140:443
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:67.635	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57728	target_addr:104.21.86.125:443
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:67.720	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57744	target_addr:104.21.86.125:443
time:2026-09-30T11:38:50Z	status:FAILURE	latency:207.038	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:252.120	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:722.486	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:1059.981	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:38:50Z	status:HEALTHY	latency:1225.150	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:43:50Z	status:UNKNOWN	latency:7.765	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:11.011	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39558	target_addr:172.64.147.104:443
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:67.093	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58410	target_addr:104.21.86.125:443
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:67.242	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55396	target_addr:104.21.26.208:443
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:67.922	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59678	target_addr:172.67.219.211:443
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:191.665	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:43:50Z	status:FAILURE	latency:194.302	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:688.823	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:930.730	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:43:50Z	status:HEALTHY	latency:1068.978	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:48:50Z	status:UNKNOWN	latency:7.246	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:9.890	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37882	target_addr:104.18.40.152:443
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:65.629	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50746	target_addr:172.67.219.211:443
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:68.123	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43094	target_addr:172.67.168.140:443
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:68.211	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54134	target_addr:104.21.86.125:443
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:160.795	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:48:50Z	status:FAILURE	latency:192.478	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:873.551	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:917.201	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:48:50Z	status:HEALTHY	latency:5710.166	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:53:50Z	status:UNKNOWN	latency:6.959	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:9.624	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49302	target_addr:104.18.40.152:443
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:65.613	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60794	target_addr:104.21.86.125:443
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:68.827	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44772	target_addr:104.21.26.208:443
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:76.678	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55576	target_addr:172.67.219.211:443
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:200.010	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:704.065	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:777.677	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:53:50Z	status:HEALTHY	latency:1473.803	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:53:50Z	status:FAILURE	latency:5995.704	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:10.724	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40648	target_addr:104.18.40.152:443
time:2026-09-30T11:58:50Z	status:UNKNOWN	latency:16.392	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:65.345	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56286	target_addr:172.67.168.140:443
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:69.057	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55470	target_addr:172.67.219.211:443
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:75.086	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55480	target_addr:172.67.219.211:443
time:2026-09-30T11:58:50Z	status:FAILURE	latency:200.271	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:246.232	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:629.647	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:630.537	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T11:58:50Z	status:HEALTHY	latency:646.960	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:03:50Z	status:UNKNOWN	latency:8.732	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:9.500	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54794	target_addr:172.64.147.104:443
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:67.369	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38496	target_addr:104.21.86.125:443
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:67.612	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40238	target_addr:172.67.168.140:443
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:73.918	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38486	target_addr:104.21.86.125:443
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:252.009	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:03:50Z	status:FAILURE	latency:383.484	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:714.195	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:764.854	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:03:50Z	status:HEALTHY	latency:783.392	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:08:50Z	status:UNKNOWN	latency:7.429	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:9.389	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46202	target_addr:104.18.40.152:443
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:67.137	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55866	target_addr:172.67.168.140:443
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:66.745	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38844	target_addr:172.67.219.211:443
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:73.429	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42938	target_addr:104.21.86.125:443
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:181.248	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:08:50Z	status:FAILURE	latency:493.754	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:585.974	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:656.156	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:08:50Z	status:HEALTHY	latency:771.215	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:11.042	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45594	target_addr:104.18.40.152:443
time:2026-09-30T12:13:50Z	status:UNKNOWN	latency:34.173	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:65.173	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40268	target_addr:104.21.26.208:443
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:67.570	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33172	target_addr:104.21.86.125:443
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:75.627	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33188	target_addr:104.21.86.125:443
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:175.714	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:256.358	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:286.796	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:13:50Z	status:HEALTHY	latency:296.976	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:13:50Z	status:FAILURE	latency:422.944	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:10.518	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50952	target_addr:172.64.147.104:443
time:2026-09-30T12:18:50Z	status:UNKNOWN	latency:11.667	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:65.486	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47370	target_addr:104.21.86.125:443
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:69.300	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54152	target_addr:172.67.219.211:443
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:70.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43668	target_addr:172.67.168.140:443
time:2026-09-30T12:18:50Z	status:FAILURE	latency:202.957	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:255.228	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:256.468	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:273.128	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:18:50Z	status:HEALTHY	latency:283.719	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:23:50Z	status:UNKNOWN	latency:7.498	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:9.803	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51392	target_addr:104.18.40.152:443
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:66.904	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38988	target_addr:104.21.26.208:443
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:67.308	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40596	target_addr:172.67.219.211:443
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:75.976	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33354	target_addr:104.21.86.125:443
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:183.524	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:261.892	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:268.168	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:23:50Z	status:HEALTHY	latency:279.295	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:23:50Z	status:FAILURE	latency:499.015	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:28:50Z	status:UNKNOWN	latency:6.676	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:9.392	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44834	target_addr:104.18.40.152:443
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:66.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50708	target_addr:104.21.26.208:443
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:66.891	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58384	target_addr:104.21.86.125:443
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:67.010	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58394	target_addr:104.21.86.125:443
time:2026-09-30T12:28:50Z	status:FAILURE	latency:206.889	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:206.855	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:259.878	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:261.995	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:28:50Z	status:HEALTHY	latency:275.224	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:33:50Z	status:UNKNOWN	latency:8.173	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:11.498	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52332	target_addr:104.18.40.152:443
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:66.674	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44574	target_addr:172.67.219.211:443
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:67.072	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44588	target_addr:172.67.219.211:443
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:75.392	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48330	target_addr:172.67.168.140:443
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:190.057	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:264.120	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:266.760	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:33:50Z	status:HEALTHY	latency:271.736	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:33:50Z	status:FAILURE	latency:1314.646	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:38:50Z	status:UNKNOWN	latency:6.692	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:10.354	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60384	target_addr:104.18.40.152:443
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:67.332	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53222	target_addr:172.67.219.211:443
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:68.315	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56698	target_addr:104.21.86.125:443
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:75.675	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36232	target_addr:104.21.26.208:443
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:192.341	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:38:50Z	status:FAILURE	latency:197.568	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:257.305	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:271.100	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:38:50Z	status:HEALTHY	latency:280.382	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:43:50Z	status:UNKNOWN	latency:33.671	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:47.629	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44010	target_addr:172.64.147.104:443
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:66.157	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40872	target_addr:104.21.26.208:443
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:65.962	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51812	target_addr:104.21.86.125:443
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:66.494	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51820	target_addr:104.21.86.125:443
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:191.215	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:259.982	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:261.968	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:43:50Z	status:HEALTHY	latency:281.118	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:43:50Z	status:FAILURE	latency:396.664	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:48:50Z	status:UNKNOWN	latency:7.297	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:10.170	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57294	target_addr:172.64.147.104:443
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:66.555	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40552	target_addr:104.21.86.125:443
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:76.054	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34786	target_addr:172.67.219.211:443
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:79.818	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53354	target_addr:104.21.26.208:443
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:189.099	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:48:50Z	status:FAILURE	latency:199.603	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:254.960	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:265.204	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:48:50Z	status:HEALTHY	latency:956.502	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:53:50Z	status:UNKNOWN	latency:7.443	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:11.029	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57726	target_addr:172.64.147.104:443
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:68.711	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43032	target_addr:104.21.86.125:443
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:75.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43048	target_addr:104.21.86.125:443
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:76.182	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35032	target_addr:104.21.26.208:443
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:189.155	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:274.380	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:280.027	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:53:50Z	status:HEALTHY	latency:286.166	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:53:50Z	status:FAILURE	latency:340.223	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T12:58:50Z	status:UNKNOWN	latency:6.741	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:9.698	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56922	target_addr:172.64.147.104:443
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:65.635	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38724	target_addr:104.21.26.208:443
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:66.432	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40960	target_addr:104.21.86.125:443
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:67.895	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53432	target_addr:172.67.219.211:443
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:148.329	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:257.022	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:268.848	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:58:50Z	status:HEALTHY	latency:269.444	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T12:58:50Z	status:FAILURE	latency:353.328	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:03:50Z	status:UNKNOWN	latency:7.485	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:14.392	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50242	target_addr:104.18.40.152:443
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:66.060	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56240	target_addr:172.67.219.211:443
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:70.345	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34570	target_addr:104.21.26.208:443
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:75.898	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56706	target_addr:104.21.86.125:443
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:216.957	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:253.561	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:279.320	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:03:50Z	status:HEALTHY	latency:285.030	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:03:50Z	status:FAILURE	latency:511.530	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:08:50Z	status:UNKNOWN	latency:8.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:8.577	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41122	target_addr:104.18.40.152:443
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:68.648	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50460	target_addr:172.67.219.211:443
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:68.777	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60228	target_addr:104.21.26.208:443
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:68.495	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57466	target_addr:104.21.86.125:443
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:78.120	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:08:50Z	status:FAILURE	latency:204.093	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:269.306	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:282.496	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:08:50Z	status:HEALTHY	latency:407.288	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:13:50Z	status:UNKNOWN	latency:6.846	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:10.324	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50166	target_addr:104.18.40.152:443
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:66.247	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48138	target_addr:104.21.86.125:443
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:67.046	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43294	target_addr:172.67.168.140:443
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:67.452	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48154	target_addr:104.21.86.125:443
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:107.732	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:260.995	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:272.058	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:13:50Z	status:HEALTHY	latency:291.323	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:13:50Z	status:FAILURE	latency:407.057	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:18:50Z	status:UNKNOWN	latency:8.205	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:9.642	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52806	target_addr:172.64.147.104:443
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:66.828	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56262	target_addr:104.21.86.125:443
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:68.047	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57120	target_addr:104.21.26.208:443
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:74.683	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56278	target_addr:104.21.86.125:443
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:200.891	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:18:50Z	status:FAILURE	latency:200.788	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:275.752	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:279.765	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:18:50Z	status:HEALTHY	latency:548.012	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:23:50Z	status:UNKNOWN	latency:7.988	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:9.852	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51112	target_addr:104.18.40.152:443
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:66.989	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53934	target_addr:172.67.168.140:443
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:67.658	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51486	target_addr:104.21.86.125:443
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:72.056	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38898	target_addr:172.67.219.211:443
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:206.185	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:267.057	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:267.039	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:23:50Z	status:HEALTHY	latency:280.226	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:23:50Z	status:FAILURE	latency:417.692	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:28:50Z	status:UNKNOWN	latency:7.840	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:11.763	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48092	target_addr:104.18.40.152:443
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:66.697	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51344	target_addr:172.67.219.211:443
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:67.415	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51034	target_addr:104.21.86.125:443
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:67.864	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40132	target_addr:104.21.26.208:443
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:220.616	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:270.506	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:275.680	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:28:50Z	status:HEALTHY	latency:278.657	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:28:50Z	status:FAILURE	latency:517.484	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:33:50Z	status:UNKNOWN	latency:7.769	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:10.215	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55744	target_addr:172.64.147.104:443
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:65.313	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59254	target_addr:104.21.86.125:443
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:67.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40168	target_addr:104.21.26.208:443
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:75.859	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54506	target_addr:172.67.219.211:443
time:2026-09-30T13:33:50Z	status:FAILURE	latency:213.460	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:246.550	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:272.467	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:275.331	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:33:50Z	status:HEALTHY	latency:286.466	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:38:50Z	status:UNKNOWN	latency:7.992	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:10.298	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41796	target_addr:172.64.147.104:443
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:66.518	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37050	target_addr:104.21.26.208:443
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:69.083	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50396	target_addr:172.67.219.211:443
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:76.557	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38660	target_addr:104.21.86.125:443
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:215.276	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:262.439	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:278.187	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:38:50Z	status:HEALTHY	latency:289.690	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:38:50Z	status:FAILURE	latency:1318.218	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:43:50Z	status:UNKNOWN	latency:8.432	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:11.373	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49034	target_addr:104.18.40.152:443
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:66.361	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57688	target_addr:104.21.86.125:443
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:69.915	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45534	target_addr:104.21.26.208:443
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:80.301	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57686	target_addr:104.21.86.125:443
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:200.629	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:43:50Z	status:FAILURE	latency:357.271	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:766.187	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:1048.640	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:43:50Z	status:HEALTHY	latency:1249.905	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:48:50Z	status:UNKNOWN	latency:8.148	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:10.039	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55708	target_addr:104.18.40.152:443
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:68.681	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53804	target_addr:172.67.219.211:443
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:79.973	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35076	target_addr:172.67.168.140:443
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:81.271	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53798	target_addr:172.67.219.211:443
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:224.514	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:48:50Z	status:FAILURE	latency:530.203	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:635.852	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:674.239	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:48:50Z	status:HEALTHY	latency:1017.021	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:53:50Z	status:UNKNOWN	latency:7.546	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:11.284	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34860	target_addr:172.64.147.104:443
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:68.530	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43030	target_addr:104.21.86.125:443
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:80.878	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47282	target_addr:172.67.168.140:443
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:81.623	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60066	target_addr:172.67.219.211:443
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:234.463	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:53:50Z	status:FAILURE	latency:381.999	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:743.862	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:1000.655	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:53:50Z	status:HEALTHY	latency:1021.310	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:58:50Z	status:UNKNOWN	latency:7.988	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:10.772	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48452	target_addr:104.18.40.152:443
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:19.515	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44478	target_addr:172.67.219.211:443
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:19.761	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57954	target_addr:104.21.26.208:443
time:2026-09-30T13:58:50Z	status:FAILURE	latency:52.905	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:71.533	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54530	target_addr:104.21.86.125:443
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:221.863	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:1092.835	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:1141.584	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T13:58:50Z	status:HEALTHY	latency:3544.511	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:03:50Z	status:UNKNOWN	latency:8.715	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:12.888	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43080	target_addr:104.18.40.152:443
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:37.651	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36354	target_addr:104.21.26.208:443
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:77.117	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53366	target_addr:172.67.219.211:443
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:79.694	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53380	target_addr:172.67.219.211:443
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:240.034	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:03:50Z	status:FAILURE	latency:403.340	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:645.580	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:692.872	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:03:50Z	status:HEALTHY	latency:1121.321	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:08:50Z	status:UNKNOWN	latency:6.604	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:9.386	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55786	target_addr:172.64.147.104:443
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:20.127	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45966	target_addr:104.21.26.208:443
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:69.556	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46856	target_addr:172.67.219.211:443
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:72.455	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36456	target_addr:104.21.86.125:443
time:2026-09-30T14:08:50Z	status:FAILURE	latency:447.703	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:513.304	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:810.809	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:881.769	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:08:50Z	status:HEALTHY	latency:991.228	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:13:50Z	status:UNKNOWN	latency:6.230	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:9.959	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49300	target_addr:172.64.147.104:443
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:20.418	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33836	target_addr:172.67.168.140:443
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:73.243	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34204	target_addr:104.21.86.125:443
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:93.870	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34212	target_addr:104.21.86.125:443
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:193.642	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:13:50Z	status:FAILURE	latency:244.605	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:733.293	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:781.656	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:13:50Z	status:HEALTHY	latency:1689.372	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:10.373	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45424	target_addr:172.64.147.104:443
time:2026-09-30T14:18:50Z	status:UNKNOWN	latency:33.307	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:45.367	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52288	target_addr:172.67.168.140:443
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:70.331	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56214	target_addr:172.67.219.211:443
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:71.303	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:93.613	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56228	target_addr:172.67.219.211:443
time:2026-09-30T14:18:50Z	status:FAILURE	latency:286.593	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:785.230	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:792.395	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:18:50Z	status:HEALTHY	latency:1025.137	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:10.134	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55966	target_addr:104.18.40.152:443
time:2026-09-30T14:23:50Z	status:UNKNOWN	latency:36.594	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:70.520	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47392	target_addr:172.67.168.140:443
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:104.106	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47300	target_addr:172.67.219.211:443
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:205.158	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:23:50Z	status:FAILURE	latency:264.684	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:513.171	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:660.318	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:1085.164	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:23:50Z	status:HEALTHY	latency:3219.707	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47294	target_addr:172.67.219.211:443
time:2026-09-30T14:28:50Z	status:UNKNOWN	latency:9.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:12.675	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43200	target_addr:172.64.147.104:443
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:20.135	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38592	target_addr:172.67.219.211:443
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:70.082	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58190	target_addr:104.21.26.208:443
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:76.784	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:85.145	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38582	target_addr:172.67.219.211:443
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:544.430	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:761.656	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:28:50Z	status:HEALTHY	latency:1033.121	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:28:50Z	status:FAILURE	latency:1453.119	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:33:50Z	status:UNKNOWN	latency:7.664	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:10.914	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56180	target_addr:172.64.147.104:443
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:36.446	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37482	target_addr:104.21.86.125:443
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:72.899	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37476	target_addr:104.21.86.125:443
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:83.239	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33638	target_addr:104.21.26.208:443
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:206.489	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:33:50Z	status:FAILURE	latency:405.137	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:751.382	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:814.632	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:33:50Z	status:HEALTHY	latency:829.458	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:38:50Z	status:UNKNOWN	latency:7.918	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:11.080	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56690	target_addr:172.64.147.104:443
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:69.720	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60420	target_addr:172.67.219.211:443
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:69.808	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46054	target_addr:172.67.168.140:443
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:82.249	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57316	target_addr:104.21.86.125:443
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:183.459	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:38:50Z	status:FAILURE	latency:425.760	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:584.483	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:734.478	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:38:50Z	status:HEALTHY	latency:1782.542	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:43:50Z	status:UNKNOWN	latency:7.598	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:9.212	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57408	target_addr:104.18.40.152:443
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:18.511	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40976	target_addr:104.21.86.125:443
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:38.135	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40980	target_addr:104.21.86.125:443
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:79.488	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37486	target_addr:104.21.26.208:443
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:88.070	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:43:50Z	status:FAILURE	latency:370.584	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:455.567	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:480.524	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:43:50Z	status:HEALTHY	latency:667.630	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:9.257	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46162	target_addr:104.18.40.152:443
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:63.009	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33048	target_addr:172.67.219.211:443
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:73.622	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45706	target_addr:172.67.168.140:443
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:73.879	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48148	target_addr:104.21.86.125:443
time:2026-09-30T14:48:51Z	status:UNKNOWN	latency:74.605	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:181.692	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:478.712	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:685.241	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:48:51Z	status:HEALTHY	latency:720.913	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:48:51Z	status:FAILURE	latency:1542.400	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:53:51Z	status:UNKNOWN	latency:6.796	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:9.798	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39006	target_addr:172.64.147.104:443
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:61.555	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39458	target_addr:172.67.219.211:443
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:72.515	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39474	target_addr:172.67.219.211:443
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:91.500	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44960	target_addr:104.21.26.208:443
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:236.727	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:53:51Z	status:FAILURE	latency:239.493	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:768.639	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:783.092	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:53:51Z	status:HEALTHY	latency:804.311	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:13.727	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43212	target_addr:104.18.40.152:443
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:20.714	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35838	target_addr:172.67.168.140:443
time:2026-09-30T14:58:51Z	status:UNKNOWN	latency:36.941	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:87.912	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43812	target_addr:104.21.86.125:443
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:104.221	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35144	target_addr:172.67.219.211:443
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:198.438	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:58:51Z	status:FAILURE	latency:393.885	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:553.358	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:670.532	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T14:58:51Z	status:HEALTHY	latency:715.609	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:03:51Z	status:UNKNOWN	latency:8.156	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:8.449	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56118	target_addr:172.64.147.104:443
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:69.548	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50272	target_addr:104.21.86.125:443
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:80.582	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55606	target_addr:172.67.168.140:443
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:96.259	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55832	target_addr:172.67.219.211:443
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:203.618	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:03:51Z	status:FAILURE	latency:377.722	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:588.608	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:788.569	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:03:51Z	status:HEALTHY	latency:1149.627	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:08:51Z	status:UNKNOWN	latency:6.952	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:12.221	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51122	target_addr:172.64.147.104:443
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:38.224	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38466	target_addr:172.67.219.211:443
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:38.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57662	target_addr:104.21.86.125:443
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:178.669	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45392	target_addr:104.21.26.208:443
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:194.228	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:08:51Z	status:FAILURE	latency:689.964	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:1436.643	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:1756.953	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:08:51Z	status:HEALTHY	latency:2449.164	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:13:51Z	status:UNKNOWN	latency:7.730	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:12.020	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44936	target_addr:104.18.40.152:443
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:159.621	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44584	target_addr:172.67.168.140:443
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:171.537	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45980	target_addr:104.21.86.125:443
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:221.285	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:232.345	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60794	target_addr:172.67.219.211:443
time:2026-09-30T15:13:51Z	status:FAILURE	latency:659.125	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:1322.577	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:3172.361	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:13:51Z	status:HEALTHY	latency:56645.364	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:11.592	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49654	target_addr:104.18.40.152:443
time:2026-09-30T15:18:51Z	status:UNKNOWN	latency:34.587	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:169.494	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55922	target_addr:172.67.219.211:443
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:169.939	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52934	target_addr:104.21.86.125:443
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:170.073	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42728	target_addr:172.67.168.140:443
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:182.578	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:18:51Z	status:FAILURE	latency:669.794	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:1321.945	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:1877.558	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:18:51Z	status:HEALTHY	latency:2303.227	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:23:51Z	status:UNKNOWN	latency:8.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:9.140	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47902	target_addr:104.18.40.152:443
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:36.883	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48970	target_addr:104.21.86.125:443
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:200.108	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:540.266	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:1119.605	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:1256.343	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48958	target_addr:104.21.86.125:443
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:1257.456	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40348	target_addr:172.67.168.140:443
time:2026-09-30T15:23:51Z	status:FAILURE	latency:1679.131	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:23:51Z	status:HEALTHY	latency:49483.991	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:9.932	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43902	target_addr:172.64.147.104:443
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:39.234	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57406	target_addr:104.21.86.125:443
time:2026-09-30T15:28:51Z	status:UNKNOWN	latency:55.495	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:167.686	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33842	target_addr:104.21.26.208:443
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:178.689	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:189.704	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53576	target_addr:172.67.219.211:443
time:2026-09-30T15:28:51Z	status:FAILURE	latency:506.133	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:509.494	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:1080.031	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:28:51Z	status:HEALTHY	latency:1179.099	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:33:51Z	status:UNKNOWN	latency:9.349	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:10.062	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59902	target_addr:104.18.40.152:443
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:165.419	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44888	target_addr:104.21.26.208:443
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:168.855	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37090	target_addr:104.21.86.125:443
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:168.997	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53824	target_addr:172.67.219.211:443
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:354.363	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:33:51Z	status:FAILURE	latency:533.813	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:1112.006	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:3876.936	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:33:51Z	status:HEALTHY	latency:27315.293	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:38:51Z	status:UNKNOWN	latency:7.540	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:30.669	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38384	target_addr:104.18.40.152:443
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:35.488	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57654	target_addr:104.21.86.125:443
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:163.950	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55896	target_addr:172.67.219.211:443
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:200.451	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54246	target_addr:172.67.168.140:443
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:227.686	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:610.324	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:38:51Z	status:FAILURE	latency:648.417	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:1106.580	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:38:51Z	status:HEALTHY	latency:1176.459	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:43:51Z	status:UNKNOWN	latency:7.099	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:12.063	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57546	target_addr:104.18.40.152:443
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:37.247	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58092	target_addr:104.21.86.125:443
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:207.117	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58094	target_addr:104.21.86.125:443
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:228.046	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:43:51Z	status:FAILURE	latency:655.940	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:1066.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:1630.358	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48330	target_addr:172.67.168.140:443
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:3428.649	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:43:51Z	status:HEALTHY	latency:7185.538	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:48:51Z	status:UNKNOWN	latency:7.797	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:11.748	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53888	target_addr:104.18.40.152:443
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:37.421	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56578	target_addr:104.21.86.125:443
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:208.952	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:487.346	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:629.351	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56592	target_addr:104.21.86.125:443
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:1133.073	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:48:51Z	status:HEALTHY	latency:1586.726	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59492	target_addr:172.67.168.140:443
time:2026-09-30T15:48:51Z	status:FAILURE	latency:1910.257	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:48:51Z	status:FAILURE	latency:17201.839	target:https://go3-cn.xyz/	message:Get "https://go3-cn.xyz": unexpected EOF
time:2026-09-30T15:53:51Z	status:UNKNOWN	latency:7.475	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:18.904	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60368	target_addr:172.64.147.104:443
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:206.293	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:479.972	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:562.001	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59522	target_addr:104.21.86.125:443
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:564.096	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37742	target_addr:104.21.26.208:443
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:2647.996	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59512	target_addr:104.21.86.125:443
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:4059.724	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:53:51Z	status:HEALTHY	latency:10348.038	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:53:51Z	status:FAILURE	latency:10787.619	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:58:51Z	status:UNKNOWN	latency:6.882	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:11.497	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57834	target_addr:104.18.40.152:443
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:37.812	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38464	target_addr:104.21.86.125:443
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:115.948	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43926	target_addr:172.67.168.140:443
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:512.058	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:635.150	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37374	target_addr:172.67.219.211:443
time:2026-09-30T15:58:51Z	status:FAILURE	latency:668.034	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:1033.652	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:1411.253	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T15:58:51Z	status:HEALTHY	latency:1483.237	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:03:51Z	status:UNKNOWN	latency:6.173	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:9.665	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42202	target_addr:172.64.147.104:443
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:176.497	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50866	target_addr:172.67.219.211:443
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:182.448	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57540	target_addr:104.21.26.208:443
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:212.525	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:773.569	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:03:51Z	status:FAILURE	latency:844.098	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:1140.892	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:1610.706	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50852	target_addr:172.67.219.211:443
time:2026-09-30T16:03:51Z	status:HEALTHY	latency:9070.775	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:08:51Z	status:UNKNOWN	latency:7.222	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:9.676	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35800	target_addr:104.18.40.152:443
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:206.659	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:578.753	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47410	target_addr:104.21.26.208:443
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:603.303	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49334	target_addr:104.21.86.125:443
time:2026-09-30T16:08:51Z	status:FAILURE	latency:650.236	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:716.581	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:1197.670	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:08:51Z	status:HEALTHY	latency:1655.569	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49344	target_addr:104.21.86.125:443
time:2026-09-30T16:08:51Z	status:FAILURE	latency:17401.731	target:https://go3-cn.xyz/	message:Get "https://go3-cn.xyz": EOF
time:2026-09-30T16:13:51Z	status:UNKNOWN	latency:8.597	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:13:51Z	status:HEALTHY	latency:11.552	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56446	target_addr:104.18.40.152:443
time:2026-09-30T16:13:51Z	status:HEALTHY	latency:111.789	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44646	target_addr:172.67.219.211:443
time:2026-09-30T16:13:51Z	status:HEALTHY	latency:456.840	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:13:51Z	status:FAILURE	latency:522.333	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:13:51Z	status:FAILURE	latency:891.660	target:https://go3-cn.online/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-09-30T16:13:51Z	status:HEALTHY	latency:927.330	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:13:51Z	status:HEALTHY	latency:1187.989	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46770	target_addr:104.21.86.125:443
time:2026-09-30T16:13:51Z	status:HEALTHY	latency:1657.314	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40950	target_addr:104.21.26.208:443
time:2026-09-30T16:13:51Z	status:FAILURE	latency:4410.746	target:https://go3-cn.blog/	message:Get "https://go3-cn.blog": read tcp 172.17.0.2:51724->172.67.200.78:443: read: connection reset by peer
time:2026-09-30T16:18:51Z	status:UNKNOWN	latency:8.090	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:12.169	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49872	target_addr:104.18.40.152:443
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:103.965	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:128.193	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51680	target_addr:104.21.86.125:443
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:1073.857	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:1116.238	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:2653.843	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51688	target_addr:104.21.86.125:443
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:2659.261	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60472	target_addr:104.21.26.208:443
time:2026-09-30T16:18:51Z	status:HEALTHY	latency:9457.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:18:51Z	status:FAILURE	latency:11041.867	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:23:51Z	status:UNKNOWN	latency:7.614	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:10.338	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41688	target_addr:172.64.147.104:443
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:121.133	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57670	target_addr:172.67.168.140:443
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:158.679	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60358	target_addr:104.21.86.125:443
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:176.353	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41478	target_addr:172.67.219.211:443
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:211.060	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:782.101	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:23:51Z	status:FAILURE	latency:884.428	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:23:51Z	status:HEALTHY	latency:1086.086	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:23:51Z	status:FAILURE	latency:16141.944	target:https://go3-cn.blog/	message:Get "https://go3-cn.blog": unexpected EOF
time:2026-09-30T16:28:51Z	status:UNKNOWN	latency:9.700	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:14.765	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32952	target_addr:104.18.40.152:443
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:227.331	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:585.251	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47750	target_addr:104.21.86.125:443
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:1423.405	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:1440.275	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:28:51Z	status:FAILURE	latency:1637.000	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:2443.493	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:2643.865	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54920	target_addr:172.67.219.211:443
time:2026-09-30T16:28:51Z	status:HEALTHY	latency:4686.699	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52038	target_addr:104.21.26.208:443
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:8.805	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51700	target_addr:104.18.40.152:443
time:2026-09-30T16:33:51Z	status:UNKNOWN	latency:36.489	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:159.470	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54586	target_addr:172.67.219.211:443
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:161.377	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54090	target_addr:104.21.26.208:443
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:195.635	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:33:51Z	status:FAILURE	latency:501.416	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:609.337	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54584	target_addr:172.67.219.211:443
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:962.196	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:2447.829	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:33:51Z	status:HEALTHY	latency:6840.761	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:38:51Z	status:UNKNOWN	latency:7.625	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:9.030	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44174	target_addr:172.64.147.104:443
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:169.825	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41622	target_addr:172.67.219.211:443
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:208.905	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:603.524	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49646	target_addr:104.21.26.208:443
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:609.893	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41618	target_addr:172.67.219.211:443
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:771.880	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:1066.134	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:38:51Z	status:HEALTHY	latency:1290.074	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:38:51Z	status:FAILURE	latency:5667.689	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:43:51Z	status:UNKNOWN	latency:9.351	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:10.763	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50522	target_addr:104.18.40.152:443
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:163.135	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58392	target_addr:104.21.86.125:443
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:179.777	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:428.714	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58396	target_addr:104.21.86.125:443
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:1129.225	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:1425.173	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:2307.887	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40256	target_addr:172.67.168.140:443
time:2026-09-30T16:43:51Z	status:HEALTHY	latency:4358.469	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:43:51Z	status:FAILURE	latency:15338.319	target:https://www.ao3-cn.com/	message:Get "https://www.ao3-cn.com": EOF
time:2026-09-30T16:48:51Z	status:UNKNOWN	latency:7.613	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:11.376	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60562	target_addr:104.18.40.152:443
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:91.537	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53722	target_addr:104.21.86.125:443
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:163.942	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51904	target_addr:172.67.219.211:443
time:2026-09-30T16:48:51Z	status:FAILURE	latency:624.511	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:1242.331	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:2158.688	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:2215.575	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:48:51Z	status:HEALTHY	latency:2243.059	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44918	target_addr:104.21.26.208:443
time:2026-09-30T16:48:51Z	status:FAILURE	latency:15802.139	target:https://go3-cn.xyz/	message:Get "https://go3-cn.xyz": EOF
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:8.047	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54500	target_addr:172.64.147.104:443
time:2026-09-30T16:53:51Z	status:UNKNOWN	latency:35.778	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:154.401	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:165.074	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48040	target_addr:104.21.86.125:443
time:2026-09-30T16:53:51Z	status:FAILURE	latency:654.519	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:1113.072	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:1180.689	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:1612.856	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42392	target_addr:172.67.168.140:443
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:1642.069	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53126	target_addr:172.67.219.211:443
time:2026-09-30T16:53:51Z	status:HEALTHY	latency:4011.352	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:58:51Z	status:UNKNOWN	latency:7.752	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:12.065	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34326	target_addr:172.64.147.104:443
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:82.468	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52288	target_addr:172.67.168.140:443
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:166.881	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54402	target_addr:104.21.86.125:443
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:201.848	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:214.684	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54400	target_addr:104.21.86.125:443
time:2026-09-30T16:58:51Z	status:FAILURE	latency:663.692	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:6289.551	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:8845.331	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T16:58:51Z	status:HEALTHY	latency:48585.745	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:03:51Z	status:UNKNOWN	latency:8.260	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:12.909	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53804	target_addr:172.64.147.104:443
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:93.895	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34724	target_addr:104.21.26.208:443
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:162.891	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47836	target_addr:172.67.219.211:443
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:221.390	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:03:51Z	status:FAILURE	latency:688.025	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:1139.203	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:1139.307	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:1216.392	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40462	target_addr:104.21.86.125:443
time:2026-09-30T17:03:51Z	status:HEALTHY	latency:6180.456	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:10.597	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42066	target_addr:104.18.40.152:443
time:2026-09-30T17:08:51Z	status:UNKNOWN	latency:11.469	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:157.459	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41152	target_addr:104.21.86.125:443
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:165.539	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41142	target_addr:104.21.86.125:443
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:165.934	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44472	target_addr:172.67.168.140:443
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:191.321	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:08:51Z	status:FAILURE	latency:728.863	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:776.805	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:1243.264	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:08:51Z	status:HEALTHY	latency:3530.493	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:10.595	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46134	target_addr:104.18.40.152:443
time:2026-09-30T17:13:51Z	status:UNKNOWN	latency:38.400	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:160.187	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56482	target_addr:104.21.86.125:443
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:165.551	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56468	target_addr:104.21.86.125:443
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:179.252	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51160	target_addr:172.67.168.140:443
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:223.085	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:786.137	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:1444.411	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:13:51Z	status:FAILURE	latency:8449.075	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:13:51Z	status:HEALTHY	latency:35614.799	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:18:51Z	status:UNKNOWN	latency:8.305	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:11.357	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48290	target_addr:104.18.40.152:443
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:160.762	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46900	target_addr:104.21.86.125:443
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:167.868	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52662	target_addr:172.67.219.211:443
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:168.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36060	target_addr:172.67.168.140:443
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:179.403	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:18:51Z	status:FAILURE	latency:633.625	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:1191.453	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:4270.236	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:18:51Z	status:HEALTHY	latency:4847.104	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:8.551	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47486	target_addr:172.64.147.104:443
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:171.819	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55010	target_addr:104.21.86.125:443
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:219.978	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36512	target_addr:172.67.168.140:443
time:2026-09-30T17:23:51Z	status:UNKNOWN	latency:230.511	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:230.230	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43572	target_addr:172.67.219.211:443
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:239.024	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:23:51Z	status:FAILURE	latency:708.887	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:2086.699	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:2945.050	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:23:51Z	status:HEALTHY	latency:5607.034	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:28:51Z	status:UNKNOWN	latency:9.008	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:13.215	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52552	target_addr:104.18.40.152:443
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:160.938	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35942	target_addr:172.67.219.211:443
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:161.747	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35948	target_addr:172.67.219.211:443
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:183.581	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38362	target_addr:104.21.26.208:443
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:201.322	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:28:51Z	status:FAILURE	latency:643.019	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:1888.130	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:2661.392	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:28:51Z	status:HEALTHY	latency:3347.867	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:33:51Z	status:UNKNOWN	latency:8.678	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:10.551	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58260	target_addr:104.18.40.152:443
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:172.283	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51898	target_addr:104.21.86.125:443
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:186.680	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:253.442	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57492	target_addr:172.67.219.211:443
time:2026-09-30T17:33:51Z	status:FAILURE	latency:646.136	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:1036.772	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:1084.230	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:1725.532	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:33:51Z	status:HEALTHY	latency:4241.733	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44592	target_addr:104.21.26.208:443
time:2026-09-30T17:38:51Z	status:UNKNOWN	latency:9.845	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:28.921	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54134	target_addr:172.64.147.104:443
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:168.431	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60556	target_addr:104.21.26.208:443
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:170.730	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46668	target_addr:104.21.86.125:443
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:185.503	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46658	target_addr:104.21.86.125:443
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:248.645	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:38:51Z	status:FAILURE	latency:673.332	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:1051.767	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:1124.765	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:38:51Z	status:HEALTHY	latency:137962.386	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:43:51Z	status:UNKNOWN	latency:6.337	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:9.186	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57360	target_addr:104.18.40.152:443
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:167.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42398	target_addr:104.21.86.125:443
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:168.341	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43496	target_addr:172.67.168.140:443
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:183.896	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:43:51Z	status:FAILURE	latency:669.791	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:1023.905	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:1070.240	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:1227.941	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:43:51Z	status:HEALTHY	latency:1230.831	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58124	target_addr:172.67.219.211:443
time:2026-09-30T17:48:51Z	status:UNKNOWN	latency:7.025	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:11.874	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38126	target_addr:104.18.40.152:443
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:83.747	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56978	target_addr:104.21.86.125:443
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:167.116	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44388	target_addr:172.67.168.140:443
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:168.899	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33874	target_addr:172.67.219.211:443
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:200.301	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:48:51Z	status:FAILURE	latency:827.008	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:1137.784	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:1138.316	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:48:51Z	status:HEALTHY	latency:1209.054	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:53:51Z	status:UNKNOWN	latency:7.646	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:10.604	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52752	target_addr:104.18.40.152:443
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:115.118	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39820	target_addr:172.67.168.140:443
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:172.819	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40438	target_addr:104.21.86.125:443
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:176.722	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40454	target_addr:104.21.86.125:443
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:204.402	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:53:51Z	status:FAILURE	latency:650.598	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:1156.555	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:1157.962	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:53:51Z	status:HEALTHY	latency:1453.500	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:58:51Z	status:UNKNOWN	latency:8.455	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:9.524	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43182	target_addr:172.64.147.104:443
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:167.581	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40718	target_addr:172.67.219.211:443
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:168.934	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46682	target_addr:172.67.168.140:443
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:182.787	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50714	target_addr:104.21.86.125:443
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:329.627	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:58:51Z	status:FAILURE	latency:672.297	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:1061.970	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:1169.811	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T17:58:51Z	status:HEALTHY	latency:1394.173	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:11.110	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33764	target_addr:172.64.147.104:443
time:2026-09-30T18:03:51Z	status:UNKNOWN	latency:57.151	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:87.031	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42612	target_addr:172.67.219.211:443
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:120.225	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49306	target_addr:172.67.168.140:443
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:181.192	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44434	target_addr:104.21.86.125:443
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:213.819	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:03:51Z	status:FAILURE	latency:844.091	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:856.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:1139.449	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:03:51Z	status:HEALTHY	latency:1420.890	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:08:51Z	status:UNKNOWN	latency:7.891	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:11.300	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51018	target_addr:104.18.40.152:443
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:168.311	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34352	target_addr:172.67.219.211:443
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:197.146	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39140	target_addr:104.21.26.208:443
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:206.953	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50330	target_addr:104.21.86.125:443
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:244.099	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:08:51Z	status:FAILURE	latency:665.320	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:1146.232	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:1179.643	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:08:51Z	status:HEALTHY	latency:1184.909	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:13:51Z	status:UNKNOWN	latency:7.821	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:9.587	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40612	target_addr:172.64.147.104:443
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:162.646	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55190	target_addr:172.67.219.211:443
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:180.425	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42664	target_addr:172.67.168.140:443
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:190.004	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55202	target_addr:172.67.219.211:443
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:224.271	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:13:51Z	status:FAILURE	latency:519.379	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:1089.273	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:1118.968	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:13:51Z	status:HEALTHY	latency:1926.841	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:18:51Z	status:UNKNOWN	latency:8.970	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:21.047	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60008	target_addr:172.64.147.104:443
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:166.295	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41972	target_addr:172.67.219.211:443
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:170.483	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35548	target_addr:172.67.168.140:443
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:171.227	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58296	target_addr:104.21.86.125:443
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:231.394	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:18:51Z	status:FAILURE	latency:778.836	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:987.722	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:1102.568	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:18:51Z	status:HEALTHY	latency:1424.833	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:9.257	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41454	target_addr:172.64.147.104:443
time:2026-09-30T18:23:52Z	status:UNKNOWN	latency:15.786	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:85.622	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32770	target_addr:104.21.26.208:443
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:177.132	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40238	target_addr:172.67.219.211:443
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:196.138	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:198.722	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56504	target_addr:104.21.86.125:443
time:2026-09-30T18:23:52Z	status:FAILURE	latency:708.690	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:1036.486	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:1420.325	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:23:52Z	status:HEALTHY	latency:1646.876	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:28:52Z	status:UNKNOWN	latency:8.270	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:29.417	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35306	target_addr:172.64.147.104:443
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:91.209	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42668	target_addr:104.21.86.125:443
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:118.018	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33158	target_addr:172.67.168.140:443
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:170.719	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34608	target_addr:172.67.219.211:443
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:243.512	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:28:52Z	status:FAILURE	latency:756.378	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:962.087	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:1063.721	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:28:52Z	status:HEALTHY	latency:1123.561	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:33:52Z	status:UNKNOWN	latency:9.409	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:20.104	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36590	target_addr:172.64.147.104:443
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:85.303	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41690	target_addr:172.67.219.211:443
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:177.563	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36674	target_addr:172.67.168.140:443
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:186.397	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44316	target_addr:104.21.86.125:443
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:223.891	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:33:52Z	status:FAILURE	latency:671.375	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:1168.776	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:1681.984	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:33:52Z	status:HEALTHY	latency:21954.243	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:38:52Z	status:UNKNOWN	latency:21.034	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:22.143	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45628	target_addr:104.18.40.152:443
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:95.137	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57342	target_addr:104.21.86.125:443
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:170.449	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55618	target_addr:172.67.168.140:443
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:180.371	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36678	target_addr:172.67.219.211:443
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:233.344	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:38:52Z	status:FAILURE	latency:811.728	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:1138.860	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:1188.420	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:38:52Z	status:HEALTHY	latency:1210.364	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:15.467	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60496	target_addr:172.64.147.104:443
time:2026-09-30T18:43:52Z	status:UNKNOWN	latency:35.139	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:86.840	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41038	target_addr:104.21.26.208:443
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:166.023	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46424	target_addr:104.21.86.125:443
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:170.145	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58136	target_addr:172.67.219.211:443
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:533.549	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:43:52Z	status:FAILURE	latency:717.362	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:1160.989	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:1189.189	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:43:52Z	status:HEALTHY	latency:1256.157	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:48:52Z	status:UNKNOWN	latency:6.449	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:8.621	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44876	target_addr:172.64.147.104:443
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:187.590	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34172	target_addr:172.67.219.211:443
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:191.466	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35804	target_addr:172.67.168.140:443
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:191.840	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34184	target_addr:172.67.219.211:443
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:226.523	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:48:52Z	status:FAILURE	latency:697.152	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:1108.442	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:1178.650	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:48:52Z	status:HEALTHY	latency:1256.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:53:52Z	status:UNKNOWN	latency:6.531	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:9.439	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36184	target_addr:104.18.40.152:443
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:92.521	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37066	target_addr:172.67.168.140:443
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:92.721	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60662	target_addr:172.67.219.211:443
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:163.649	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54518	target_addr:104.21.86.125:443
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:210.824	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:53:52Z	status:FAILURE	latency:696.122	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:1136.119	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:3345.543	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:53:52Z	status:HEALTHY	latency:3907.318	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:58:52Z	status:UNKNOWN	latency:7.296	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:8.471	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33298	target_addr:104.18.40.152:443
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:167.009	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54178	target_addr:104.21.86.125:443
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:168.941	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47786	target_addr:104.21.26.208:443
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:172.606	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54190	target_addr:104.21.86.125:443
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:200.477	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:58:52Z	status:FAILURE	latency:498.192	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:1117.128	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:1169.239	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T18:58:52Z	status:HEALTHY	latency:1246.317	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:12.295	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41294	target_addr:172.64.147.104:443
time:2026-09-30T19:03:52Z	status:UNKNOWN	latency:34.354	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:172.388	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60098	target_addr:104.21.86.125:443
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:172.126	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59738	target_addr:104.21.26.208:443
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:182.705	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47816	target_addr:172.67.219.211:443
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:431.914	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:724.919	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:731.914	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:03:52Z	status:FAILURE	latency:744.383	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:03:52Z	status:HEALTHY	latency:1150.043	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:08:52Z	status:UNKNOWN	latency:7.589	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:12.917	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34630	target_addr:104.18.40.152:443
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:164.102	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36300	target_addr:104.21.86.125:443
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:184.286	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36310	target_addr:104.21.86.125:443
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:189.712	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51068	target_addr:172.67.168.140:443
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:221.918	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:08:52Z	status:FAILURE	latency:489.436	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:1133.820	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:1184.969	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:08:52Z	status:HEALTHY	latency:1292.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:13:52Z	status:UNKNOWN	latency:7.247	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:10.986	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59230	target_addr:172.64.147.104:443
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:161.174	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39730	target_addr:104.21.86.125:443
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:166.992	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34924	target_addr:172.67.168.140:443
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:180.930	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59986	target_addr:172.67.219.211:443
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:324.586	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:13:52Z	status:FAILURE	latency:497.285	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:1137.839	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:1147.556	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:13:52Z	status:HEALTHY	latency:5167.338	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:18:52Z	status:UNKNOWN	latency:7.879	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:8.425	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34116	target_addr:172.64.147.104:443
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:86.383	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59790	target_addr:172.67.219.211:443
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:180.744	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39292	target_addr:104.21.26.208:443
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:239.191	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:18:52Z	status:FAILURE	latency:490.824	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:943.709	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:1184.368	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59774	target_addr:172.67.219.211:443
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:1362.205	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:18:52Z	status:HEALTHY	latency:1723.691	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:23:52Z	status:UNKNOWN	latency:9.619	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:12.419	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36538	target_addr:104.18.40.152:443
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:83.518	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37612	target_addr:104.21.86.125:443
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:171.017	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58726	target_addr:172.67.219.211:443
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:172.947	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34642	target_addr:172.67.168.140:443
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:328.344	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:23:52Z	status:FAILURE	latency:651.867	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:955.786	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:1075.057	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:23:52Z	status:HEALTHY	latency:3772.238	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:28:52Z	status:UNKNOWN	latency:8.028	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:15.409	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34216	target_addr:104.18.40.152:443
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:172.646	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48022	target_addr:104.21.26.208:443
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:226.271	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:256.250	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43134	target_addr:172.67.219.211:443
time:2026-09-30T19:28:52Z	status:FAILURE	latency:496.272	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:1275.338	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43150	target_addr:172.67.219.211:443
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:3538.985	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:3876.423	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:28:52Z	status:HEALTHY	latency:7903.673	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:33:52Z	status:UNKNOWN	latency:8.131	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:17.829	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48528	target_addr:172.64.147.104:443
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:171.139	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42250	target_addr:172.67.219.211:443
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:174.463	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42248	target_addr:172.67.219.211:443
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:191.812	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48658	target_addr:172.67.168.140:443
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:217.306	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:734.129	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:1072.866	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:33:52Z	status:HEALTHY	latency:1083.308	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:33:52Z	status:FAILURE	latency:2575.946	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:38:52Z	status:UNKNOWN	latency:6.546	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:9.886	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52078	target_addr:172.64.147.104:443
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:96.473	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55904	target_addr:172.67.219.211:443
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:165.799	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45532	target_addr:172.67.168.140:443
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:207.017	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35998	target_addr:104.21.86.125:443
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:215.492	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:38:52Z	status:FAILURE	latency:695.807	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:933.352	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:1352.050	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:38:52Z	status:HEALTHY	latency:2009.646	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:43:52Z	status:UNKNOWN	latency:8.780	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:15.721	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58002	target_addr:172.64.147.104:443
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:24.734	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48824	target_addr:172.67.219.211:443
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:168.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48814	target_addr:172.67.219.211:443
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:174.208	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44774	target_addr:104.21.26.208:443
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:300.708	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:43:52Z	status:FAILURE	latency:644.677	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:1226.568	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:1515.414	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:43:52Z	status:HEALTHY	latency:1518.152	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:9.594	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35650	target_addr:172.64.147.104:443
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:30.044	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56690	target_addr:172.67.168.140:443
time:2026-09-30T19:48:52Z	status:UNKNOWN	latency:56.471	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:88.420	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56668	target_addr:104.21.86.125:443
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:170.086	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42842	target_addr:172.67.219.211:443
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:214.309	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:827.528	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:1080.824	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:48:52Z	status:FAILURE	latency:3627.930	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:48:52Z	status:HEALTHY	latency:110487.967	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:11.735	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39270	target_addr:104.18.40.152:443
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:19.835	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47234	target_addr:104.21.86.125:443
time:2026-09-30T19:53:52Z	status:UNKNOWN	latency:35.587	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:35.374	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51502	target_addr:172.67.219.211:443
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:165.878	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45898	target_addr:104.21.26.208:443
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:218.675	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:484.272	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:53:52Z	status:FAILURE	latency:811.581	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:1023.481	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:53:52Z	status:HEALTHY	latency:1041.683	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:15.202	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53788	target_addr:104.18.40.152:443
time:2026-09-30T19:58:52Z	status:UNKNOWN	latency:18.355	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:40.661	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45904	target_addr:172.67.168.140:443
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:67.287	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46194	target_addr:172.67.219.211:443
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:175.161	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46210	target_addr:172.67.219.211:443
time:2026-09-30T19:58:52Z	status:FAILURE	latency:253.325	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:264.574	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:755.095	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:891.151	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T19:58:52Z	status:HEALTHY	latency:1115.184	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:03:52Z	status:UNKNOWN	latency:8.751	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:17.820	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55950	target_addr:104.18.40.152:443
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:38.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39786	target_addr:104.21.86.125:443
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:38.866	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39778	target_addr:104.21.86.125:443
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:91.104	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51918	target_addr:104.21.26.208:443
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:248.913	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:03:52Z	status:FAILURE	latency:513.759	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:571.011	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:634.136	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:03:52Z	status:HEALTHY	latency:1191.155	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:08:52Z	status:UNKNOWN	latency:9.546	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:12.127	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57430	target_addr:104.18.40.152:443
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:40.077	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60324	target_addr:172.67.219.211:443
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:83.076	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59966	target_addr:172.67.168.140:443
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:136.765	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60336	target_addr:172.67.219.211:443
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:137.135	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:08:52Z	status:FAILURE	latency:258.579	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:409.485	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:546.007	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:08:52Z	status:HEALTHY	latency:853.871	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:13:52Z	status:UNKNOWN	latency:6.943	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:14.804	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37524	target_addr:172.64.147.104:443
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:20.660	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43986	target_addr:104.21.86.125:443
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:28.211	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36070	target_addr:172.67.168.140:443
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:160.977	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43996	target_addr:104.21.86.125:443
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:201.495	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:13:52Z	status:FAILURE	latency:388.051	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:579.408	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:762.546	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:13:52Z	status:HEALTHY	latency:1134.829	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:18:52Z	status:UNKNOWN	latency:8.132	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:11.555	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51202	target_addr:104.18.40.152:443
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:18.246	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56388	target_addr:172.67.219.211:443
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:19.376	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46414	target_addr:104.21.26.208:443
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:68.945	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56400	target_addr:172.67.219.211:443
time:2026-09-30T20:18:52Z	status:FAILURE	latency:107.668	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:238.266	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:526.643	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:564.146	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:18:52Z	status:HEALTHY	latency:1165.033	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:23:52Z	status:UNKNOWN	latency:8.234	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:10.349	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39256	target_addr:172.64.147.104:443
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:20.776	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34306	target_addr:172.67.219.211:443
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:38.308	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54016	target_addr:104.21.26.208:443
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:70.142	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34296	target_addr:172.67.219.211:443
time:2026-09-30T20:23:52Z	status:FAILURE	latency:221.803	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:224.786	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:514.711	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:804.341	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:23:52Z	status:HEALTHY	latency:817.695	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:28:52Z	status:UNKNOWN	latency:8.604	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:12.727	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45336	target_addr:172.64.147.104:443
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:27.202	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58448	target_addr:104.21.86.125:443
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:49.477	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48950	target_addr:104.21.26.208:443
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:77.753	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58458	target_addr:104.21.86.125:443
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:225.583	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:28:52Z	status:FAILURE	latency:239.001	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:542.310	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:583.562	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:28:52Z	status:HEALTHY	latency:844.886	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:33:52Z	status:UNKNOWN	latency:8.935	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:20.482	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56844	target_addr:104.21.26.208:443
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:20.470	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57202	target_addr:104.21.86.125:443
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:23.808	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50918	target_addr:172.64.147.104:443
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:35.584	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57186	target_addr:104.21.86.125:443
time:2026-09-30T20:33:52Z	status:FAILURE	latency:120.147	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:208.896	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:557.373	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:559.837	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:33:52Z	status:HEALTHY	latency:588.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:38:52Z	status:UNKNOWN	latency:8.016	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:10.937	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60958	target_addr:172.64.147.104:443
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:19.612	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51504	target_addr:172.67.168.140:443
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:21.257	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52738	target_addr:172.67.219.211:443
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:22.947	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52606	target_addr:104.21.86.125:443
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:217.612	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:38:52Z	status:FAILURE	latency:360.057	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:565.729	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:576.276	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:38:52Z	status:HEALTHY	latency:593.208	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:43:52Z	status:UNKNOWN	latency:9.146	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:12.289	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51180	target_addr:172.64.147.104:443
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:21.360	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37734	target_addr:104.21.86.125:443
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:36.827	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36048	target_addr:172.67.168.140:443
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:46.526	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42464	target_addr:172.67.219.211:443
time:2026-09-30T20:43:52Z	status:FAILURE	latency:55.950	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:231.532	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:574.565	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:604.175	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:43:52Z	status:HEALTHY	latency:1087.514	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:48:52Z	status:UNKNOWN	latency:8.527	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:10.722	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50664	target_addr:104.18.40.152:443
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:19.363	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37564	target_addr:172.67.219.211:443
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:19.511	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47068	target_addr:104.21.26.208:443
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:74.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37578	target_addr:172.67.219.211:443
time:2026-09-30T20:48:52Z	status:FAILURE	latency:209.801	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:291.155	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:545.177	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:650.978	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:48:52Z	status:HEALTHY	latency:910.407	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:8.972	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51974	target_addr:172.64.147.104:443
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:20.211	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34340	target_addr:104.21.26.208:443
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:20.571	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47072	target_addr:172.67.219.211:443
time:2026-09-30T20:53:52Z	status:UNKNOWN	latency:35.379	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:37.836	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56422	target_addr:104.21.86.125:443
time:2026-09-30T20:53:52Z	status:FAILURE	latency:258.867	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:262.640	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:478.425	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:479.603	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:53:52Z	status:HEALTHY	latency:512.293	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:58:52Z	status:UNKNOWN	latency:7.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:12.663	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46442	target_addr:104.18.40.152:443
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:20.024	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49436	target_addr:104.21.86.125:443
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:28.910	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49444	target_addr:104.21.86.125:443
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:30.581	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52588	target_addr:172.67.168.140:443
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:186.457	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:58:52Z	status:FAILURE	latency:207.935	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:523.839	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:529.533	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T20:58:52Z	status:HEALTHY	latency:598.748	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:03:52Z	status:UNKNOWN	latency:8.396	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:12.133	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41844	target_addr:172.64.147.104:443
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:26.673	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48930	target_addr:104.21.86.125:443
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:46.929	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58620	target_addr:172.67.219.211:443
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:47.382	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55416	target_addr:172.67.168.140:443
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:275.641	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:03:52Z	status:FAILURE	latency:363.689	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:587.475	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:650.892	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:03:52Z	status:HEALTHY	latency:702.992	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:08:52Z	status:UNKNOWN	latency:6.913	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:14.786	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43166	target_addr:172.64.147.104:443
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:19.182	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35648	target_addr:172.67.219.211:443
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:22.736	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35000	target_addr:104.21.86.125:443
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:39.931	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41146	target_addr:172.67.168.140:443
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:246.731	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:08:52Z	status:FAILURE	latency:247.033	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:471.865	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:527.193	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:08:52Z	status:HEALTHY	latency:5450.651	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:13:52Z	status:UNKNOWN	latency:9.037	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:12.317	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56514	target_addr:172.64.147.104:443
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:20.935	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51716	target_addr:172.67.219.211:443
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:21.250	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51222	target_addr:104.21.26.208:443
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:45.351	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51724	target_addr:172.67.219.211:443
time:2026-09-30T21:13:52Z	status:FAILURE	latency:63.875	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:222.659	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:557.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:576.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:13:52Z	status:HEALTHY	latency:943.006	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:18:52Z	status:UNKNOWN	latency:6.590	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:12.911	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45134	target_addr:104.18.40.152:443
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:18.322	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53454	target_addr:172.67.219.211:443
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:26.354	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32822	target_addr:104.21.86.125:443
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:45.680	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48450	target_addr:104.21.26.208:443
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:198.809	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:18:52Z	status:FAILURE	latency:237.686	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:878.064	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:917.190	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:18:52Z	status:HEALTHY	latency:923.713	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:11.851	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58830	target_addr:172.64.147.104:443
time:2026-09-30T21:23:52Z	status:UNKNOWN	latency:15.263	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:18.503	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50424	target_addr:104.21.86.125:443
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:20.027	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44248	target_addr:172.67.219.211:443
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:29.141	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60936	target_addr:104.21.26.208:443
time:2026-09-30T21:23:52Z	status:FAILURE	latency:259.514	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:260.801	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:466.809	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:739.637	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:23:52Z	status:HEALTHY	latency:741.410	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:28:52Z	status:UNKNOWN	latency:6.188	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:9.814	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56460	target_addr:172.64.147.104:443
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:21.019	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47038	target_addr:104.21.86.125:443
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:21.137	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60424	target_addr:104.21.26.208:443
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:21.000	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47036	target_addr:104.21.86.125:443
time:2026-09-30T21:28:52Z	status:FAILURE	latency:175.155	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:222.989	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:543.944	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:558.206	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:28:52Z	status:HEALTHY	latency:1331.477	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:33:52Z	status:UNKNOWN	latency:10.555	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:13.700	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32876	target_addr:172.64.147.104:443
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:20.461	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40744	target_addr:104.21.26.208:443
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:21.856	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36318	target_addr:172.67.219.211:443
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:31.122	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36326	target_addr:172.67.219.211:443
time:2026-09-30T21:33:52Z	status:FAILURE	latency:237.717	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:313.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:420.234	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:489.733	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:33:52Z	status:HEALTHY	latency:524.186	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:13.424	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35270	target_addr:104.18.40.152:443
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:19.404	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50194	target_addr:172.67.219.211:443
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:27.821	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42998	target_addr:172.67.168.140:443
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:34.048	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50208	target_addr:172.67.219.211:443
time:2026-09-30T21:38:52Z	status:UNKNOWN	latency:35.709	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:38:52Z	status:FAILURE	latency:60.154	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:235.640	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:597.481	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:602.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:38:52Z	status:HEALTHY	latency:756.927	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:43:52Z	status:UNKNOWN	latency:7.870	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:12.151	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43362	target_addr:104.18.40.152:443
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:19.040	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49298	target_addr:104.21.26.208:443
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:31.744	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58940	target_addr:172.67.219.211:443
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:32.822	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42170	target_addr:104.21.86.125:443
time:2026-09-30T21:43:52Z	status:FAILURE	latency:234.282	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:276.284	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:463.969	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:838.157	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:43:52Z	status:HEALTHY	latency:5440.304	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:12.499	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58942	target_addr:104.18.40.152:443
time:2026-09-30T21:48:52Z	status:UNKNOWN	latency:14.800	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:18.983	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55248	target_addr:172.67.219.211:443
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:19.785	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55260	target_addr:172.67.219.211:443
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:20.662	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41738	target_addr:104.21.26.208:443
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:219.278	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:48:52Z	status:FAILURE	latency:225.295	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:457.995	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:527.863	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:48:52Z	status:HEALTHY	latency:532.583	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:53:52Z	status:UNKNOWN	latency:7.623	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:11.922	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37922	target_addr:172.64.147.104:443
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:20.129	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50918	target_addr:172.67.168.140:443
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:25.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55082	target_addr:104.21.86.125:443
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:28.573	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55096	target_addr:104.21.86.125:443
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:213.922	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:53:52Z	status:FAILURE	latency:255.330	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:491.953	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:531.556	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:53:52Z	status:HEALTHY	latency:535.553	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:11.286	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37338	target_addr:172.64.147.104:443
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:20.069	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54174	target_addr:172.67.219.211:443
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:21.153	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36040	target_addr:104.21.26.208:443
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:20.990	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41908	target_addr:104.21.86.125:443
time:2026-09-30T21:58:52Z	status:UNKNOWN	latency:35.953	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T21:58:52Z	status:FAILURE	latency:51.739	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:205.134	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:455.318	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:522.539	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T21:58:52Z	status:HEALTHY	latency:999.264	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:03:52Z	status:UNKNOWN	latency:9.546	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:15.802	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37180	target_addr:104.18.40.152:443
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:19.570	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37158	target_addr:172.67.219.211:443
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:21.266	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54180	target_addr:104.21.86.125:443
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:22.878	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46978	target_addr:104.21.26.208:443
time:2026-09-30T22:03:52Z	status:FAILURE	latency:188.247	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:301.962	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:487.492	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:550.468	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:03:52Z	status:HEALTHY	latency:656.771	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:08:52Z	status:UNKNOWN	latency:6.000	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:13.623	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50004	target_addr:104.18.40.152:443
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:19.461	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52294	target_addr:104.21.86.125:443
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:23.521	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52298	target_addr:104.21.86.125:443
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:29.866	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59040	target_addr:172.67.168.140:443
time:2026-09-30T22:08:52Z	status:FAILURE	latency:245.027	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:251.100	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:456.372	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:615.336	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:08:52Z	status:HEALTHY	latency:922.824	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:13:52Z	status:UNKNOWN	latency:7.750	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:10.816	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43302	target_addr:104.18.40.152:443
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:19.339	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48412	target_addr:104.21.86.125:443
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:20.996	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54556	target_addr:172.67.168.140:443
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:29.791	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51634	target_addr:172.67.219.211:443
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:212.971	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:13:52Z	status:FAILURE	latency:244.929	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:460.516	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:533.624	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:13:52Z	status:HEALTHY	latency:557.203	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:18:52Z	status:UNKNOWN	latency:7.926	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:15.484	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40720	target_addr:172.64.147.104:443
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:20.440	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42234	target_addr:104.21.86.125:443
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:22.534	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59764	target_addr:172.67.168.140:443
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:29.047	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42250	target_addr:104.21.86.125:443
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:208.157	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:18:52Z	status:FAILURE	latency:212.134	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:541.599	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:542.027	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:18:52Z	status:HEALTHY	latency:1009.982	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:23:53Z	status:UNKNOWN	latency:8.504	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:11.196	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50076	target_addr:172.64.147.104:443
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:16.919	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57972	target_addr:172.67.219.211:443
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:23.660	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39110	target_addr:104.21.86.125:443
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:25.394	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52264	target_addr:104.21.26.208:443
time:2026-09-30T22:23:53Z	status:FAILURE	latency:210.008	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:446.764	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:454.209	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:455.953	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:23:53Z	status:HEALTHY	latency:1249.558	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:28:53Z	status:UNKNOWN	latency:7.800	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:12.788	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43948	target_addr:172.64.147.104:443
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:19.212	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42680	target_addr:104.21.86.125:443
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:22.736	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42692	target_addr:104.21.86.125:443
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:30.454	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49478	target_addr:104.21.26.208:443
time:2026-09-30T22:28:53Z	status:FAILURE	latency:204.622	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:222.824	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:466.127	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:486.656	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:28:53Z	status:HEALTHY	latency:538.139	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:33:53Z	status:UNKNOWN	latency:7.032	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:10.609	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36406	target_addr:104.18.40.152:443
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:18.862	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36326	target_addr:104.21.26.208:443
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:21.007	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33716	target_addr:172.67.219.211:443
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:24.197	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40246	target_addr:104.21.86.125:443
time:2026-09-30T22:33:53Z	status:FAILURE	latency:230.485	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:331.127	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:770.043	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:775.718	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:33:53Z	status:HEALTHY	latency:785.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:38:53Z	status:UNKNOWN	latency:8.409	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:11.573	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59936	target_addr:172.64.147.104:443
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:17.597	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34712	target_addr:172.67.168.140:443
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:19.229	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46612	target_addr:104.21.86.125:443
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:25.652	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46628	target_addr:104.21.86.125:443
time:2026-09-30T22:38:53Z	status:FAILURE	latency:54.766	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:232.502	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:537.138	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:539.305	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:38:53Z	status:HEALTHY	latency:588.434	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:43:53Z	status:UNKNOWN	latency:8.610	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:14.558	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33912	target_addr:172.64.147.104:443
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:18.187	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43610	target_addr:172.67.219.211:443
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:21.037	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38906	target_addr:172.67.168.140:443
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:22.157	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43618	target_addr:172.67.219.211:443
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:232.721	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:468.458	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:469.083	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:43:53Z	status:FAILURE	latency:699.962	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:43:53Z	status:HEALTHY	latency:958.491	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:48:53Z	status:UNKNOWN	latency:6.526	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:20.121	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44828	target_addr:104.21.86.125:443
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:20.635	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37738	target_addr:104.21.26.208:443
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:24.016	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54496	target_addr:172.67.219.211:443
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:33.177	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37818	target_addr:104.18.40.152:443
time:2026-09-30T22:48:53Z	status:FAILURE	latency:66.287	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:296.735	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:539.298	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:718.342	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:48:53Z	status:HEALTHY	latency:775.143	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:53:53Z	status:UNKNOWN	latency:9.000	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:11.391	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56674	target_addr:172.64.147.104:443
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:18.737	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54308	target_addr:172.67.219.211:443
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:19.892	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37978	target_addr:104.21.26.208:443
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:28.260	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54324	target_addr:172.67.219.211:443
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:250.972	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:53:53Z	status:FAILURE	latency:267.274	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:398.470	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:761.974	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:53:53Z	status:HEALTHY	latency:812.057	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:58:53Z	status:UNKNOWN	latency:8.579	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:12.976	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56810	target_addr:172.64.147.104:443
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:18.751	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38330	target_addr:104.21.86.125:443
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:20.031	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46530	target_addr:104.21.26.208:443
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:27.556	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50732	target_addr:172.67.219.211:443
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:88.925	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:94.581	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:127.428	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T22:58:53Z	status:FAILURE	latency:256.136	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T22:58:53Z	status:HEALTHY	latency:268.636	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:11.437	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58386	target_addr:172.64.147.104:443
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:20.636	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40950	target_addr:104.21.86.125:443
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:21.467	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40960	target_addr:104.21.86.125:443
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:31.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34326	target_addr:172.67.168.140:443
time:2026-09-30T23:03:53Z	status:UNKNOWN	latency:57.292	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:77.089	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:89.536	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:89.554	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:03:53Z	status:HEALTHY	latency:229.569	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:03:53Z	status:FAILURE	latency:241.527	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:08:53Z	status:UNKNOWN	latency:6.031	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:12.599	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56900	target_addr:104.18.40.152:443
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:19.294	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53510	target_addr:172.67.168.140:443
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:19.876	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47086	target_addr:104.21.86.125:443
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:22.577	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40772	target_addr:172.67.219.211:443
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:92.228	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:100.211	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:113.494	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:08:53Z	status:FAILURE	latency:219.934	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:08:53Z	status:HEALTHY	latency:232.598	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:13:53Z	status:UNKNOWN	latency:6.090	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:10.295	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35144	target_addr:104.18.40.152:443
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:21.242	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48174	target_addr:172.67.219.211:443
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:23.036	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56622	target_addr:104.21.26.208:443
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:23.737	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41704	target_addr:104.21.86.125:443
time:2026-09-30T23:13:53Z	status:FAILURE	latency:57.512	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:88.544	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:91.516	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:112.165	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:13:53Z	status:HEALTHY	latency:216.167	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:18:53Z	status:UNKNOWN	latency:7.438	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:10.483	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43862	target_addr:172.64.147.104:443
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:20.252	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60092	target_addr:172.67.219.211:443
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:21.862	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60104	target_addr:172.67.219.211:443
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:22.135	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40896	target_addr:104.21.26.208:443
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:289.131	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:18:53Z	status:FAILURE	latency:356.609	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:458.591	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:668.940	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:18:53Z	status:HEALTHY	latency:739.647	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:14.787	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34240	target_addr:104.18.40.152:443
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:17.535	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55092	target_addr:104.21.86.125:443
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:18.042	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55100	target_addr:104.21.86.125:443
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:23.338	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41224	target_addr:104.21.26.208:443
time:2026-09-30T23:23:53Z	status:UNKNOWN	latency:56.475	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:23:53Z	status:FAILURE	latency:223.414	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:263.334	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:446.370	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:454.198	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:23:53Z	status:HEALTHY	latency:458.914	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:28:53Z	status:UNKNOWN	latency:7.900	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:13.471	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59750	target_addr:104.18.40.152:443
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:18.225	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35702	target_addr:172.67.219.211:443
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:23.617	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40712	target_addr:172.67.168.140:443
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:23.696	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35714	target_addr:172.67.219.211:443
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:259.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:28:53Z	status:FAILURE	latency:267.274	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:564.474	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:570.570	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:28:53Z	status:HEALTHY	latency:584.467	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:33:53Z	status:UNKNOWN	latency:8.762	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:15.099	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52836	target_addr:104.18.40.152:443
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:18.008	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42908	target_addr:104.21.26.208:443
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:18.814	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42748	target_addr:104.21.86.125:443
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:23.269	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53318	target_addr:172.67.219.211:443
time:2026-09-30T23:33:53Z	status:FAILURE	latency:215.482	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:227.230	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:447.651	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:458.841	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:33:53Z	status:HEALTHY	latency:514.756	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:38:53Z	status:UNKNOWN	latency:7.202	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:16.609	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34818	target_addr:104.18.40.152:443
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:20.032	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42396	target_addr:172.67.219.211:443
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:20.964	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42404	target_addr:172.67.219.211:443
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:25.010	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60692	target_addr:172.67.168.140:443
time:2026-09-30T23:38:53Z	status:FAILURE	latency:208.286	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:372.048	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:788.825	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:847.979	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:38:53Z	status:HEALTHY	latency:850.921	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:43:53Z	status:UNKNOWN	latency:6.891	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:10.435	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49562	target_addr:104.18.40.152:443
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:23.380	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35038	target_addr:172.67.219.211:443
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:23.377	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39798	target_addr:104.21.26.208:443
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:24.651	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35040	target_addr:172.67.219.211:443
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:228.288	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:43:53Z	status:FAILURE	latency:291.366	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:475.191	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:571.682	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:43:53Z	status:HEALTHY	latency:786.762	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:48:53Z	status:UNKNOWN	latency:7.929	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:12.935	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57428	target_addr:172.64.147.104:443
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:19.894	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44226	target_addr:172.67.219.211:443
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:21.332	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44362	target_addr:172.67.168.140:443
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:33.430	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44230	target_addr:172.67.219.211:443
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:248.487	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:48:53Z	status:FAILURE	latency:355.783	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:724.160	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:725.458	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:48:53Z	status:HEALTHY	latency:725.908	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:53:53Z	status:UNKNOWN	latency:9.289	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:11.935	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37188	target_addr:172.64.147.104:443
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:21.807	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47194	target_addr:104.21.26.208:443
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:22.402	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46508	target_addr:104.21.86.125:443
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:25.303	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52180	target_addr:172.67.219.211:443
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:206.469	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:53:53Z	status:FAILURE	latency:249.352	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:459.124	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:742.673	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:53:53Z	status:HEALTHY	latency:839.358	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:11.262	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35982	target_addr:172.64.147.104:443
time:2026-09-30T23:58:53Z	status:UNKNOWN	latency:15.457	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:18.189	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52314	target_addr:104.21.86.125:443
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:22.610	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54488	target_addr:172.67.168.140:443
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:22.388	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52320	target_addr:104.21.86.125:443
time:2026-09-30T23:58:53Z	status:FAILURE	latency:204.711	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:236.293	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:537.833	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:587.608	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-09-30T23:58:53Z	status:HEALTHY	latency:919.581	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:16.856	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60876	target_addr:172.64.147.104:443
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:20.023	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59460	target_addr:104.21.86.125:443
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:21.782	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51162	target_addr:172.67.168.140:443
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:23.169	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59462	target_addr:104.21.86.125:443
time:2026-10-01T00:03:53Z	status:UNKNOWN	latency:34.883	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:293.461	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:03:53Z	status:FAILURE	latency:344.359	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:498.070	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:510.215	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:03:53Z	status:HEALTHY	latency:551.228	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:9.794	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60850	target_addr:172.64.147.104:443
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:18.087	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46818	target_addr:172.67.168.140:443
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:21.122	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47988	target_addr:172.67.219.211:443
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:40.895	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50364	target_addr:104.21.86.125:443
time:2026-10-01T00:08:53Z	status:UNKNOWN	latency:57.258	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:226.660	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:08:53Z	status:FAILURE	latency:228.135	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:443.914	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:458.475	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:08:53Z	status:HEALTHY	latency:769.228	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:13:53Z	status:UNKNOWN	latency:8.687	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:11.872	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58748	target_addr:104.18.40.152:443
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:19.021	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45362	target_addr:172.67.168.140:443
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:21.185	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37876	target_addr:104.21.86.125:443
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:21.539	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37472	target_addr:172.67.219.211:443
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:253.233	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:13:53Z	status:FAILURE	latency:351.932	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:446.468	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:454.859	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:13:53Z	status:HEALTHY	latency:467.750	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:18:53Z	status:UNKNOWN	latency:8.554	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:10.006	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41486	target_addr:172.64.147.104:443
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:18.858	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35202	target_addr:104.21.86.125:443
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:19.818	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35198	target_addr:104.21.86.125:443
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:24.792	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40902	target_addr:104.21.26.208:443
time:2026-10-01T00:18:53Z	status:FAILURE	latency:59.740	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:337.167	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:497.524	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:537.441	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:18:53Z	status:HEALTHY	latency:564.458	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:23:53Z	status:UNKNOWN	latency:7.604	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:10.843	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52080	target_addr:104.18.40.152:443
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:19.477	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55992	target_addr:172.67.219.211:443
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:20.188	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35552	target_addr:104.21.86.125:443
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:25.887	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51210	target_addr:104.21.26.208:443
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:76.914	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:82.135	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:94.098	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:23:53Z	status:FAILURE	latency:222.916	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:23:53Z	status:HEALTHY	latency:260.526	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:28:53Z	status:UNKNOWN	latency:7.524	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:11.624	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58764	target_addr:172.64.147.104:443
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:21.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52720	target_addr:172.67.219.211:443
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:22.010	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52716	target_addr:172.67.219.211:443
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:23.554	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51408	target_addr:172.67.168.140:443
time:2026-10-01T00:28:53Z	status:FAILURE	latency:51.633	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:82.715	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:83.496	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:108.759	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:28:53Z	status:HEALTHY	latency:291.303	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:33:53Z	status:UNKNOWN	latency:9.528	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:11.970	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53406	target_addr:104.18.40.152:443
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:21.304	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51782	target_addr:172.67.219.211:443
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:21.324	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58806	target_addr:104.21.26.208:443
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:22.083	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34052	target_addr:104.21.86.125:443
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:82.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:85.602	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:228.267	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:33:53Z	status:FAILURE	latency:244.993	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:33:53Z	status:HEALTHY	latency:259.112	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:38:53Z	status:UNKNOWN	latency:8.580	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:13.006	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47970	target_addr:104.18.40.152:443
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:20.722	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51742	target_addr:172.67.219.211:443
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:22.539	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35134	target_addr:104.21.86.125:443
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:23.906	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44010	target_addr:104.21.26.208:443
time:2026-10-01T00:38:53Z	status:FAILURE	latency:210.647	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:266.053	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:455.678	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:535.253	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:38:53Z	status:HEALTHY	latency:895.421	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:12.593	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44120	target_addr:172.64.147.104:443
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:20.383	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54318	target_addr:104.21.86.125:443
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:23.149	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46830	target_addr:104.21.26.208:443
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:34.418	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51410	target_addr:172.67.219.211:443
time:2026-10-01T00:43:53Z	status:UNKNOWN	latency:59.772	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:251.440	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:43:53Z	status:FAILURE	latency:319.501	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:557.700	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:569.505	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:43:53Z	status:HEALTHY	latency:664.985	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:48:53Z	status:UNKNOWN	latency:8.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:17.756	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39902	target_addr:172.64.147.104:443
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:20.073	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32982	target_addr:172.67.168.140:443
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:21.441	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33692	target_addr:172.67.219.211:443
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:22.546	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33706	target_addr:172.67.219.211:443
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:76.353	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:119.470	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:158.758	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:48:53Z	status:FAILURE	latency:192.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:48:53Z	status:HEALTHY	latency:360.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:53:53Z	status:UNKNOWN	latency:8.369	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:10.572	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57100	target_addr:172.64.147.104:443
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:19.662	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42078	target_addr:172.67.219.211:443
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:20.298	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39908	target_addr:104.21.86.125:443
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:31.320	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44432	target_addr:104.21.26.208:443
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:77.589	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:88.719	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:89.091	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:53:53Z	status:FAILURE	latency:215.060	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:53:53Z	status:HEALTHY	latency:246.183	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:21.609	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57192	target_addr:104.18.40.152:443
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:22.345	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40998	target_addr:172.67.219.211:443
time:2026-10-01T00:58:53Z	status:UNKNOWN	latency:72.718	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:126.523	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52464	target_addr:172.67.168.140:443
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:132.451	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41010	target_addr:172.67.219.211:443
time:2026-10-01T00:58:53Z	status:FAILURE	latency:231.915	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:247.843	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:597.715	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:772.742	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T00:58:53Z	status:HEALTHY	latency:1128.416	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:8.579	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60770	target_addr:104.18.40.152:443
time:2026-10-01T01:03:53Z	status:UNKNOWN	latency:9.968	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:20.540	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59788	target_addr:104.21.86.125:443
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:21.358	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32790	target_addr:104.21.26.208:443
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:22.918	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44068	target_addr:172.67.219.211:443
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:77.328	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:82.545	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:101.444	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:03:53Z	status:FAILURE	latency:175.916	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:03:53Z	status:HEALTHY	latency:226.984	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:08:53Z	status:UNKNOWN	latency:10.508	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:13.702	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58068	target_addr:104.18.40.152:443
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:21.378	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60594	target_addr:172.67.219.211:443
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:22.937	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43284	target_addr:104.21.86.125:443
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:24.063	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43428	target_addr:172.67.168.140:443
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:92.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:95.768	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:97.352	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:08:53Z	status:FAILURE	latency:213.478	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:08:53Z	status:HEALTHY	latency:240.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:13:53Z	status:UNKNOWN	latency:8.342	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:10.683	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57208	target_addr:172.64.147.104:443
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:18.270	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59676	target_addr:104.21.86.125:443
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:20.393	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59674	target_addr:104.21.86.125:443
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:23.384	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56118	target_addr:104.21.26.208:443
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:104.908	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:13:53Z	status:FAILURE	latency:235.146	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:477.856	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:712.991	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:13:53Z	status:HEALTHY	latency:755.897	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:18:53Z	status:UNKNOWN	latency:9.632	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:14.209	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36650	target_addr:104.18.40.152:443
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:22.982	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52024	target_addr:172.67.219.211:443
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:23.097	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33830	target_addr:172.67.168.140:443
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:23.431	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52032	target_addr:172.67.219.211:443
time:2026-10-01T01:18:53Z	status:FAILURE	latency:64.674	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:250.828	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:477.337	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:536.433	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:18:53Z	status:HEALTHY	latency:790.380	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:23:53Z	status:UNKNOWN	latency:13.890	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:19.959	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38066	target_addr:172.67.219.211:443
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:21.068	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57858	target_addr:104.21.86.125:443
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:22.020	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36834	target_addr:172.67.168.140:443
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:31.884	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52298	target_addr:104.18.40.152:443
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:245.264	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:23:53Z	status:FAILURE	latency:253.573	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:453.893	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:492.146	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:23:53Z	status:HEALTHY	latency:547.966	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:28:53Z	status:UNKNOWN	latency:5.931	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:9.903	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40142	target_addr:104.18.40.152:443
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:21.417	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37914	target_addr:104.21.86.125:443
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:22.456	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42422	target_addr:172.67.168.140:443
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:22.967	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60734	target_addr:172.67.219.211:443
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:95.230	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:98.203	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:103.404	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:28:53Z	status:FAILURE	latency:232.568	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:28:53Z	status:HEALTHY	latency:285.452	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:33:53Z	status:UNKNOWN	latency:6.766	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:16.635	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54546	target_addr:104.18.40.152:443
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:23.749	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52308	target_addr:172.67.219.211:443
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:26.166	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51076	target_addr:104.21.26.208:443
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:38.963	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52320	target_addr:172.67.219.211:443
time:2026-10-01T01:33:53Z	status:FAILURE	latency:55.738	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:76.209	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:81.485	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:110.967	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:33:53Z	status:HEALTHY	latency:1470.268	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:38:53Z	status:UNKNOWN	latency:6.807	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:12.198	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34978	target_addr:104.18.40.152:443
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:17.652	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38378	target_addr:172.67.219.211:443
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:25.597	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60050	target_addr:104.21.86.125:443
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:28.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39070	target_addr:104.21.26.208:443
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:220.656	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:38:53Z	status:FAILURE	latency:226.439	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:508.389	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:515.086	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:38:53Z	status:HEALTHY	latency:534.703	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:43:53Z	status:UNKNOWN	latency:7.458	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:10.669	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33474	target_addr:172.64.147.104:443
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:19.004	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52724	target_addr:172.67.168.140:443
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:19.172	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43500	target_addr:172.67.219.211:443
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:20.215	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52402	target_addr:104.21.86.125:443
time:2026-10-01T01:43:53Z	status:FAILURE	latency:46.349	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:302.117	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:459.243	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:934.780	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:43:53Z	status:HEALTHY	latency:943.868	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:48:53Z	status:UNKNOWN	latency:6.187	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:11.603	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52066	target_addr:104.18.40.152:443
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:18.256	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39088	target_addr:104.21.86.125:443
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:21.255	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35696	target_addr:104.21.26.208:443
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:117.486	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:198.396	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39002	target_addr:172.67.219.211:443
time:2026-10-01T01:48:53Z	status:FAILURE	latency:201.573	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:446.454	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:487.028	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:48:53Z	status:HEALTHY	latency:823.090	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:9.961	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55480	target_addr:172.64.147.104:443
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:22.057	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46152	target_addr:104.21.86.125:443
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:23.924	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34394	target_addr:172.67.168.140:443
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:23.539	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46164	target_addr:104.21.86.125:443
time:2026-10-01T01:53:53Z	status:UNKNOWN	latency:37.680	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:53:53Z	status:FAILURE	latency:54.084	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:239.883	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:542.310	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:542.898	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:53:53Z	status:HEALTHY	latency:560.616	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:58:53Z	status:UNKNOWN	latency:8.468	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:10.476	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39390	target_addr:172.64.147.104:443
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:22.167	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45072	target_addr:172.67.219.211:443
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:29.585	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45062	target_addr:172.67.219.211:443
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:29.917	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37452	target_addr:172.67.168.140:443
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:220.603	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:58:53Z	status:FAILURE	latency:254.981	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:591.124	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:607.011	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T01:58:53Z	status:HEALTHY	latency:860.614	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:03:54Z	status:UNKNOWN	latency:8.207	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:10.569	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54916	target_addr:172.64.147.104:443
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:18.353	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37324	target_addr:104.21.86.125:443
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:20.080	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56390	target_addr:104.21.26.208:443
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:23.365	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47602	target_addr:172.67.219.211:443
time:2026-10-01T02:03:54Z	status:FAILURE	latency:58.498	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:343.205	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:521.823	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:588.630	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:03:54Z	status:HEALTHY	latency:667.640	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:08:54Z	status:UNKNOWN	latency:7.645	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:12.560	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56930	target_addr:104.18.40.152:443
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:21.194	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35432	target_addr:172.67.168.140:443
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:21.802	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43776	target_addr:172.67.219.211:443
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:25.202	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51380	target_addr:104.21.86.125:443
time:2026-10-01T02:08:54Z	status:FAILURE	latency:278.526	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:292.323	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:543.498	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:803.398	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:08:54Z	status:HEALTHY	latency:820.384	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:13:54Z	status:UNKNOWN	latency:8.909	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:11.557	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60270	target_addr:172.64.147.104:443
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:21.509	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37660	target_addr:172.67.168.140:443
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:24.785	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55570	target_addr:104.21.86.125:443
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:25.877	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55562	target_addr:104.21.86.125:443
time:2026-10-01T02:13:54Z	status:FAILURE	latency:243.602	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:249.593	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:471.275	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:472.335	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:13:54Z	status:HEALTHY	latency:528.583	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:12.879	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56934	target_addr:172.64.147.104:443
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:19.541	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43330	target_addr:104.21.86.125:443
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:23.275	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38494	target_addr:172.67.219.211:443
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:39.874	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52212	target_addr:172.67.168.140:443
time:2026-10-01T02:18:54Z	status:FAILURE	latency:53.778	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:18:54Z	status:UNKNOWN	latency:57.386	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:207.099	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:574.927	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:578.636	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:18:54Z	status:HEALTHY	latency:587.216	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:13.958	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52704	target_addr:172.64.147.104:443
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:22.693	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35760	target_addr:172.67.168.140:443
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:22.872	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43652	target_addr:104.21.86.125:443
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:27.127	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40450	target_addr:172.67.219.211:443
time:2026-10-01T02:23:54Z	status:UNKNOWN	latency:32.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:274.551	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:540.014	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:549.721	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:23:54Z	status:HEALTHY	latency:678.075	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:23:54Z	status:FAILURE	latency:1235.567	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:28:54Z	status:UNKNOWN	latency:8.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:18.740	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59120	target_addr:172.67.168.140:443
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:19.549	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37958	target_addr:104.21.86.125:443
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:20.299	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56274	target_addr:104.18.40.152:443
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:34.538	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44922	target_addr:172.67.219.211:443
time:2026-10-01T02:28:54Z	status:FAILURE	latency:225.914	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:249.872	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:425.136	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:469.110	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:28:54Z	status:HEALTHY	latency:522.774	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:33:54Z	status:UNKNOWN	latency:9.614	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:10.970	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47744	target_addr:172.64.147.104:443
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:20.239	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56528	target_addr:172.67.219.211:443
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:20.643	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56512	target_addr:172.67.219.211:443
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:22.996	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45592	target_addr:104.21.26.208:443
time:2026-10-01T02:33:54Z	status:FAILURE	latency:223.553	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:269.924	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:474.948	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:514.360	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:33:54Z	status:HEALTHY	latency:561.276	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:38:54Z	status:UNKNOWN	latency:6.665	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:10.031	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51130	target_addr:172.64.147.104:443
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:22.291	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44954	target_addr:104.21.86.125:443
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:24.233	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51306	target_addr:172.67.168.140:443
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:26.009	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44962	target_addr:104.21.86.125:443
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:272.207	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:541.572	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:551.116	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:38:54Z	status:HEALTHY	latency:931.163	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:38:54Z	status:FAILURE	latency:1211.897	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:43:54Z	status:UNKNOWN	latency:7.871	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:10.500	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47484	target_addr:172.64.147.104:443
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:20.307	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52940	target_addr:104.21.26.208:443
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:20.805	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54036	target_addr:104.21.86.125:443
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:24.329	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54044	target_addr:104.21.86.125:443
time:2026-10-01T02:43:54Z	status:FAILURE	latency:57.842	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:110.791	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:497.256	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:508.685	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:43:54Z	status:HEALTHY	latency:547.391	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:48:54Z	status:UNKNOWN	latency:7.900	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:11.760	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44728	target_addr:172.64.147.104:443
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:20.599	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42594	target_addr:104.21.86.125:443
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:21.441	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42606	target_addr:104.21.86.125:443
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:21.513	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37728	target_addr:104.21.26.208:443
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:258.994	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:48:54Z	status:FAILURE	latency:322.025	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:568.394	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:851.220	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:48:54Z	status:HEALTHY	latency:903.559	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:53:54Z	status:UNKNOWN	latency:6.643	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:9.472	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40712	target_addr:172.64.147.104:443
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:17.944	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35750	target_addr:104.21.86.125:443
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:19.538	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54270	target_addr:104.21.26.208:443
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:20.620	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40374	target_addr:172.67.219.211:443
time:2026-10-01T02:53:54Z	status:FAILURE	latency:226.343	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:282.063	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:493.986	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:601.764	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:53:54Z	status:HEALTHY	latency:1645.925	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:58:54Z	status:UNKNOWN	latency:6.499	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:9.526	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43758	target_addr:104.18.40.152:443
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:20.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35104	target_addr:104.21.26.208:443
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:21.155	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33882	target_addr:104.21.86.125:443
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:21.782	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53154	target_addr:172.67.219.211:443
time:2026-10-01T02:58:54Z	status:FAILURE	latency:53.358	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:117.807	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:506.880	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:676.097	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T02:58:54Z	status:HEALTHY	latency:863.106	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:14.083	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37246	target_addr:104.18.40.152:443
time:2026-10-01T03:03:54Z	status:UNKNOWN	latency:16.506	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:23.112	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50710	target_addr:172.67.168.140:443
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:27.153	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37256	target_addr:172.67.219.211:443
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:152.554	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43998	target_addr:104.21.86.125:443
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:180.634	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:03:54Z	status:FAILURE	latency:251.829	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:470.796	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:486.420	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:03:54Z	status:HEALTHY	latency:756.668	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:08:54Z	status:UNKNOWN	latency:6.697	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:9.265	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43452	target_addr:104.18.40.152:443
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:18.350	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47604	target_addr:104.21.26.208:443
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:18.899	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37228	target_addr:172.67.219.211:443
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:20.208	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37226	target_addr:172.67.219.211:443
time:2026-10-01T03:08:54Z	status:FAILURE	latency:228.840	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:239.829	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:546.103	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:958.906	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:08:54Z	status:HEALTHY	latency:3827.299	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:13:54Z	status:UNKNOWN	latency:8.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:11.116	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44220	target_addr:104.18.40.152:443
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:20.700	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45318	target_addr:172.67.219.211:443
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:22.318	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52506	target_addr:104.21.26.208:443
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:26.621	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45332	target_addr:172.67.219.211:443
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:76.528	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:90.811	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:231.966	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:13:54Z	status:FAILURE	latency:253.370	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:13:54Z	status:HEALTHY	latency:2749.210	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:18:54Z	status:UNKNOWN	latency:7.844	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:14.332	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52044	target_addr:104.18.40.152:443
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:19.822	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56536	target_addr:104.21.86.125:443
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:19.876	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50766	target_addr:172.67.219.211:443
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:19.638	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43918	target_addr:172.67.168.140:443
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:73.137	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:87.648	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:108.271	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:18:54Z	status:FAILURE	latency:224.468	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:18:54Z	status:HEALTHY	latency:240.074	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:10.025	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39502	target_addr:172.64.147.104:443
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:19.288	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44770	target_addr:104.21.86.125:443
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:20.316	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55388	target_addr:172.67.219.211:443
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:20.924	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57356	target_addr:172.67.168.140:443
time:2026-10-01T03:23:54Z	status:UNKNOWN	latency:34.439	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:81.104	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:82.516	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:86.222	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:23:54Z	status:HEALTHY	latency:215.698	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:23:54Z	status:FAILURE	latency:238.303	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:8.888	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48770	target_addr:172.64.147.104:443
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:18.350	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33248	target_addr:104.21.86.125:443
time:2026-10-01T03:28:54Z	status:UNKNOWN	latency:20.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:21.191	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57376	target_addr:104.21.26.208:443
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:24.161	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33260	target_addr:104.21.86.125:443
time:2026-10-01T03:28:54Z	status:FAILURE	latency:231.090	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:293.164	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:543.027	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:756.459	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:28:54Z	status:HEALTHY	latency:3356.297	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:33:54Z	status:UNKNOWN	latency:6.543	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:9.424	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44702	target_addr:172.64.147.104:443
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:18.409	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52950	target_addr:104.21.86.125:443
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:31.914	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54512	target_addr:172.67.168.140:443
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:32.840	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35694	target_addr:172.67.219.211:443
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:246.651	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:33:54Z	status:FAILURE	latency:253.715	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:454.525	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:458.731	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:33:54Z	status:HEALTHY	latency:458.936	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:13.070	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43460	target_addr:172.64.147.104:443
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:19.491	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52730	target_addr:172.67.168.140:443
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:20.412	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54264	target_addr:104.21.86.125:443
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:25.141	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54276	target_addr:104.21.86.125:443
time:2026-10-01T03:38:54Z	status:UNKNOWN	latency:38.185	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:38:54Z	status:FAILURE	latency:241.875	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:260.851	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:489.398	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:563.344	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:38:54Z	status:HEALTHY	latency:826.306	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:43:54Z	status:UNKNOWN	latency:8.405	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:8.432	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45502	target_addr:104.18.40.152:443
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:19.066	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33600	target_addr:104.21.86.125:443
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:21.771	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41490	target_addr:104.21.26.208:443
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:22.278	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56478	target_addr:172.67.219.211:443
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:82.204	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:83.044	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:43:54Z	status:FAILURE	latency:206.076	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:213.804	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:43:54Z	status:HEALTHY	latency:1945.353	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:13.566	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46832	target_addr:172.64.147.104:443
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:18.436	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33248	target_addr:104.21.86.125:443
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:20.069	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33258	target_addr:104.21.86.125:443
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:20.711	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33970	target_addr:172.67.168.140:443
time:2026-10-01T03:48:54Z	status:UNKNOWN	latency:33.470	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:83.043	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:90.100	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:100.674	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:48:54Z	status:FAILURE	latency:221.240	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:48:54Z	status:HEALTHY	latency:266.701	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:53:54Z	status:UNKNOWN	latency:7.276	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:11.204	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38982	target_addr:172.64.147.104:443
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:18.101	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43670	target_addr:104.21.86.125:443
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:20.828	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60436	target_addr:104.21.26.208:443
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:22.297	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46010	target_addr:172.67.219.211:443
time:2026-10-01T03:53:54Z	status:FAILURE	latency:238.512	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:315.497	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:543.379	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:769.280	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:53:54Z	status:HEALTHY	latency:825.831	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:58:54Z	status:UNKNOWN	latency:10.587	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:18.577	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55528	target_addr:104.21.86.125:443
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:18.513	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48756	target_addr:104.18.40.152:443
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:20.421	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41504	target_addr:172.67.219.211:443
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:21.199	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36650	target_addr:172.67.168.140:443
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:255.458	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:58:54Z	status:FAILURE	latency:259.966	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:641.316	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:672.129	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T03:58:54Z	status:HEALTHY	latency:868.404	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:11.428	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60302	target_addr:172.64.147.104:443
time:2026-10-01T04:03:54Z	status:UNKNOWN	latency:18.478	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:18.087	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38410	target_addr:104.21.86.125:443
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:20.166	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53326	target_addr:172.67.168.140:443
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:21.287	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38422	target_addr:104.21.86.125:443
time:2026-10-01T04:03:54Z	status:FAILURE	latency:197.455	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:202.075	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:502.342	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:569.451	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:03:54Z	status:HEALTHY	latency:652.644	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:08:54Z	status:UNKNOWN	latency:9.055	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:20.463	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49564	target_addr:172.67.219.211:443
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:29.408	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50638	target_addr:172.64.147.104:443
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:76.987	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47608	target_addr:172.67.168.140:443
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:84.746	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34274	target_addr:104.21.86.125:443
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:261.786	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:08:54Z	status:FAILURE	latency:295.816	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:618.715	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:862.089	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:08:54Z	status:HEALTHY	latency:3015.043	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:13:54Z	status:UNKNOWN	latency:8.829	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:11.753	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42516	target_addr:172.64.147.104:443
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:19.690	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53126	target_addr:104.21.86.125:443
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:37.404	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53110	target_addr:104.21.86.125:443
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:87.848	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51284	target_addr:172.67.168.140:443
time:2026-10-01T04:13:54Z	status:FAILURE	latency:109.342	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:415.401	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:497.807	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:568.860	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:13:54Z	status:HEALTHY	latency:1533.176	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:18:54Z	status:UNKNOWN	latency:12.361	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:12.793	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50732	target_addr:104.18.40.152:443
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:19.667	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54094	target_addr:172.67.219.211:443
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:19.878	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45082	target_addr:104.21.26.208:443
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:20.859	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54106	target_addr:172.67.219.211:443
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:196.095	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:18:54Z	status:FAILURE	latency:282.224	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:533.172	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:758.770	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:18:54Z	status:HEALTHY	latency:776.038	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:23:54Z	status:UNKNOWN	latency:7.521	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:34.564	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38632	target_addr:172.67.219.211:443
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:36.489	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55930	target_addr:172.67.168.140:443
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:49.734	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43958	target_addr:172.64.147.104:443
time:2026-10-01T04:23:54Z	status:FAILURE	latency:51.958	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:77.959	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38634	target_addr:172.67.219.211:443
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:278.189	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:431.505	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:511.299	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:23:54Z	status:HEALTHY	latency:634.684	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:28:54Z	status:UNKNOWN	latency:6.252	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:17.105	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46636	target_addr:172.64.147.104:443
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:19.202	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34614	target_addr:172.67.219.211:443
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:21.538	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39402	target_addr:104.21.86.125:443
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:37.609	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47696	target_addr:104.21.26.208:443
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:261.994	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:28:54Z	status:FAILURE	latency:309.123	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:711.367	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:1007.078	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:28:54Z	status:HEALTHY	latency:1872.914	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:9.697	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36564	target_addr:172.64.147.104:443
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:16.231	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42032	target_addr:172.67.168.140:443
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:20.648	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50268	target_addr:172.67.219.211:443
time:2026-10-01T04:33:54Z	status:UNKNOWN	latency:57.499	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:33:54Z	status:FAILURE	latency:72.442	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:74.030	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:74.287	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:79.889	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:179.047	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54660	target_addr:104.21.86.125:443
time:2026-10-01T04:33:54Z	status:HEALTHY	latency:522.160	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:12.897	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37216	target_addr:172.64.147.104:443
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:18.894	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49424	target_addr:104.21.86.125:443
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:20.937	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59500	target_addr:172.67.168.140:443
time:2026-10-01T04:38:54Z	status:UNKNOWN	latency:36.669	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:36.436	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49440	target_addr:104.21.86.125:443
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:89.703	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:97.163	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:256.558	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:38:54Z	status:FAILURE	latency:268.075	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:38:54Z	status:HEALTHY	latency:1912.648	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:43:54Z	status:UNKNOWN	latency:8.797	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:19.614	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59680	target_addr:104.18.40.152:443
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:20.887	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35524	target_addr:104.21.86.125:443
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:21.919	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57302	target_addr:172.67.168.140:443
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:22.356	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35508	target_addr:104.21.86.125:443
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:258.562	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:43:54Z	status:FAILURE	latency:282.269	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:445.650	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:448.507	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:43:54Z	status:HEALTHY	latency:448.807	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:10.853	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53908	target_addr:104.18.40.152:443
time:2026-10-01T04:48:54Z	status:UNKNOWN	latency:16.259	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:18.502	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34302	target_addr:104.21.86.125:443
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:20.890	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42868	target_addr:104.21.26.208:443
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:21.995	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55582	target_addr:172.67.219.211:443
time:2026-10-01T04:48:54Z	status:FAILURE	latency:60.673	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:77.665	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:236.149	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:239.091	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:48:54Z	status:HEALTHY	latency:1262.727	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:53:54Z	status:UNKNOWN	latency:7.738	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:17.464	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38768	target_addr:104.21.86.125:443
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:18.174	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55448	target_addr:104.21.26.208:443
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:18.896	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51392	target_addr:172.67.219.211:443
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:30.190	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34016	target_addr:172.64.147.104:443
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:91.371	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:96.079	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:109.728	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:53:54Z	status:HEALTHY	latency:241.822	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:53:54Z	status:FAILURE	latency:261.254	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:9.993	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34132	target_addr:172.64.147.104:443
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:20.208	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38932	target_addr:104.21.26.208:443
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:23.156	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46724	target_addr:172.67.219.211:443
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:33.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57648	target_addr:104.21.86.125:443
time:2026-10-01T04:58:54Z	status:UNKNOWN	latency:36.785	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T04:58:54Z	status:FAILURE	latency:208.464	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:470.499	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:510.330	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:546.595	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T04:58:54Z	status:HEALTHY	latency:816.911	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:03:54Z	status:UNKNOWN	latency:8.813	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:10.147	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42094	target_addr:172.64.147.104:443
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:18.737	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47014	target_addr:104.21.26.208:443
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:19.781	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52154	target_addr:104.21.86.125:443
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:37.131	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44548	target_addr:172.67.219.211:443
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:216.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:03:54Z	status:FAILURE	latency:221.829	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:488.649	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:3631.230	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:03:54Z	status:HEALTHY	latency:3709.170	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:08:54Z	status:UNKNOWN	latency:7.089	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:10.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35454	target_addr:104.18.40.152:443
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:68.079	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38382	target_addr:172.67.219.211:443
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:256.302	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:688.117	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:1077.795	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39466	target_addr:104.21.86.125:443
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:1078.367	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38226	target_addr:104.21.26.208:443
time:2026-10-01T05:08:54Z	status:FAILURE	latency:1222.465	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:1709.791	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:08:54Z	status:HEALTHY	latency:1971.652	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:13:54Z	status:UNKNOWN	latency:7.785	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:11.499	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60530	target_addr:104.18.40.152:443
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:20.720	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52512	target_addr:172.67.168.140:443
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:37.593	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33820	target_addr:104.21.86.125:443
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:38.785	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33834	target_addr:104.21.86.125:443
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:213.776	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:13:54Z	status:FAILURE	latency:397.748	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:505.676	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:1710.821	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:13:54Z	status:HEALTHY	latency:1716.448	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:15.055	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47480	target_addr:104.18.40.152:443
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:18.727	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53264	target_addr:172.67.219.211:443
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:19.320	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48590	target_addr:104.21.86.125:443
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:20.151	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53250	target_addr:172.67.168.140:443
time:2026-10-01T05:18:54Z	status:UNKNOWN	latency:38.087	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:18:54Z	status:FAILURE	latency:53.034	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:305.799	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:429.508	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:438.964	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:18:54Z	status:HEALTHY	latency:455.273	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:23:54Z	status:UNKNOWN	latency:7.473	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:8.851	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49882	target_addr:104.18.40.152:443
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:18.230	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35678	target_addr:104.21.86.125:443
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:18.988	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35686	target_addr:104.21.86.125:443
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:21.985	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55044	target_addr:104.21.26.208:443
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:209.670	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:23:54Z	status:FAILURE	latency:229.704	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:571.310	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:574.351	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:23:54Z	status:HEALTHY	latency:1471.269	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:28:54Z	status:UNKNOWN	latency:7.106	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:16.128	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36230	target_addr:172.64.147.104:443
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:17.993	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43174	target_addr:172.67.168.140:443
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:20.065	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39750	target_addr:172.67.219.211:443
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:20.601	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39760	target_addr:172.67.219.211:443
time:2026-10-01T05:28:54Z	status:FAILURE	latency:200.964	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:257.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:463.624	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:468.254	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:28:54Z	status:HEALTHY	latency:491.564	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:33:54Z	status:UNKNOWN	latency:8.051	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:14.045	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51356	target_addr:172.64.147.104:443
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:20.727	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47968	target_addr:104.21.86.125:443
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:21.318	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47970	target_addr:104.21.86.125:443
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:23.008	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46004	target_addr:172.67.168.140:443
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:243.571	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:33:54Z	status:FAILURE	latency:270.924	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:497.229	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:521.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:33:54Z	status:HEALTHY	latency:528.815	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:38:54Z	status:UNKNOWN	latency:7.814	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:9.825	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33800	target_addr:172.64.147.104:443
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:21.366	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38962	target_addr:104.21.86.125:443
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:31.389	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38976	target_addr:104.21.86.125:443
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:34.775	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36236	target_addr:104.21.26.208:443
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:244.759	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:38:54Z	status:FAILURE	latency:266.839	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:490.965	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:554.601	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:38:54Z	status:HEALTHY	latency:583.080	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:43:54Z	status:UNKNOWN	latency:7.705	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:13.890	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46128	target_addr:172.64.147.104:443
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:17.369	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47100	target_addr:104.21.26.208:443
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:19.652	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47920	target_addr:172.67.219.211:443
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:24.541	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60456	target_addr:104.21.86.125:443
time:2026-10-01T05:43:54Z	status:FAILURE	latency:230.785	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:271.062	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:470.753	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:531.182	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:43:54Z	status:HEALTHY	latency:549.914	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:48:54Z	status:UNKNOWN	latency:7.970	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:13.867	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42642	target_addr:172.64.147.104:443
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:21.317	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48458	target_addr:172.67.168.140:443
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:21.883	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34368	target_addr:104.21.86.125:443
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:27.074	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53740	target_addr:172.67.219.211:443
time:2026-10-01T05:48:54Z	status:FAILURE	latency:76.417	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:223.732	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:423.471	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:497.685	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:48:54Z	status:HEALTHY	latency:498.385	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:9.617	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47572	target_addr:172.64.147.104:443
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:18.822	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38724	target_addr:172.67.219.211:443
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:20.273	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44708	target_addr:172.67.168.140:443
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:22.933	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56676	target_addr:104.21.86.125:443
time:2026-10-01T05:53:54Z	status:UNKNOWN	latency:39.706	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:53:54Z	status:FAILURE	latency:229.439	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:257.701	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:460.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:461.242	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:53:54Z	status:HEALTHY	latency:557.304	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:58:54Z	status:UNKNOWN	latency:18.559	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:18.239	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50476	target_addr:172.67.168.140:443
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:21.370	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51250	target_addr:104.21.86.125:443
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:21.990	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50452	target_addr:172.64.147.104:443
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:43.990	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51260	target_addr:104.21.86.125:443
time:2026-10-01T05:58:54Z	status:FAILURE	latency:214.479	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:336.450	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:528.054	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:529.131	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T05:58:54Z	status:HEALTHY	latency:768.981	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:9.129	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49922	target_addr:104.18.40.152:443
time:2026-10-01T06:03:54Z	status:UNKNOWN	latency:9.588	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:18.170	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41340	target_addr:172.67.219.211:443
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:23.442	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42610	target_addr:104.21.26.208:443
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:24.821	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42482	target_addr:104.21.86.125:443
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:250.379	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:03:54Z	status:FAILURE	latency:282.849	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:438.852	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:448.886	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:03:54Z	status:HEALTHY	latency:483.802	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:8.403	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34650	target_addr:104.18.40.152:443
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:8.822	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44756	target_addr:104.21.86.125:443
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:9.926	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38078	target_addr:172.67.219.211:443
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:20.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38922	target_addr:104.21.26.208:443
time:2026-10-01T06:08:54Z	status:UNKNOWN	latency:31.705	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:88.644	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:105.120	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:205.209	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:08:54Z	status:FAILURE	latency:225.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:08:54Z	status:HEALTHY	latency:1734.488	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:13:54Z	status:UNKNOWN	latency:8.716	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:12.923	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36656	target_addr:172.64.147.104:443
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:18.430	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51958	target_addr:172.67.219.211:443
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:21.744	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51974	target_addr:172.67.219.211:443
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:33.103	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33590	target_addr:104.21.26.208:443
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:90.890	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:95.732	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:102.888	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:13:54Z	status:FAILURE	latency:169.279	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:13:54Z	status:HEALTHY	latency:219.061	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:18:54Z	status:UNKNOWN	latency:7.221	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:9.705	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39418	target_addr:172.67.168.140:443
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:12.219	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45208	target_addr:172.67.219.211:443
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:13.162	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38206	target_addr:172.64.147.104:443
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:18.955	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45200	target_addr:172.67.219.211:443
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:203.405	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:18:54Z	status:FAILURE	latency:215.854	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:524.756	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:545.751	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:18:54Z	status:HEALTHY	latency:571.739	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:10.389	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51872	target_addr:172.64.147.104:443
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:18.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43604	target_addr:104.21.26.208:443
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:20.756	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41244	target_addr:172.67.219.211:443
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:20.314	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41258	target_addr:172.67.219.211:443
time:2026-10-01T06:23:55Z	status:UNKNOWN	latency:20.870	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:219.914	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:23:55Z	status:FAILURE	latency:237.669	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:539.094	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:554.308	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:23:55Z	status:HEALTHY	latency:1620.241	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:10.408	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53748	target_addr:172.64.147.104:443
time:2026-10-01T06:28:55Z	status:UNKNOWN	latency:19.742	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:21.913	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39752	target_addr:104.21.26.208:443
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:24.171	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52330	target_addr:172.67.219.211:443
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:25.506	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47744	target_addr:104.21.86.125:443
time:2026-10-01T06:28:55Z	status:FAILURE	latency:228.975	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:229.611	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:541.047	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:545.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:28:55Z	status:HEALTHY	latency:556.076	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:33:55Z	status:UNKNOWN	latency:9.304	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:14.184	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58924	target_addr:104.21.26.208:443
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:20.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46686	target_addr:104.21.86.125:443
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:23.134	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40230	target_addr:104.18.40.152:443
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:28.234	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54354	target_addr:172.67.219.211:443
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:226.616	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:33:55Z	status:FAILURE	latency:229.137	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:550.346	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:569.846	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:33:55Z	status:HEALTHY	latency:605.730	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:38:55Z	status:UNKNOWN	latency:6.841	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:19.471	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37650	target_addr:104.21.86.125:443
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:19.552	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47866	target_addr:104.18.40.152:443
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:21.134	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33312	target_addr:172.67.219.211:443
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:44.119	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42508	target_addr:172.67.168.140:443
time:2026-10-01T06:38:55Z	status:FAILURE	latency:233.933	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:290.203	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:526.214	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:558.671	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:38:55Z	status:HEALTHY	latency:581.496	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:43:55Z	status:UNKNOWN	latency:7.956	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:11.974	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55828	target_addr:172.64.147.104:443
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:17.661	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46966	target_addr:172.67.168.140:443
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:24.681	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59882	target_addr:172.67.219.211:443
time:2026-10-01T06:43:55Z	status:FAILURE	latency:24.878	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:33.887	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59892	target_addr:172.67.219.211:443
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:238.167	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:506.421	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:579.754	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:43:55Z	status:HEALTHY	latency:1752.194	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:48:55Z	status:UNKNOWN	latency:10.700	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:10.658	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43086	target_addr:104.18.40.152:443
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:10.898	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39510	target_addr:104.21.86.125:443
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:14.897	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55180	target_addr:104.21.26.208:443
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:30.918	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39522	target_addr:104.21.86.125:443
time:2026-10-01T06:48:55Z	status:FAILURE	latency:196.994	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:255.998	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:498.922	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:541.546	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:48:55Z	status:HEALTHY	latency:543.890	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:53:55Z	status:UNKNOWN	latency:6.869	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:12.860	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44862	target_addr:172.64.147.104:443
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:20.106	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47952	target_addr:104.21.26.208:443
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:20.655	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35972	target_addr:104.21.86.125:443
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:23.064	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43700	target_addr:172.67.219.211:443
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:227.944	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:53:55Z	status:FAILURE	latency:239.905	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:402.176	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:466.659	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:53:55Z	status:HEALTHY	latency:507.540	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:7.548	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45708	target_addr:104.18.40.152:443
time:2026-10-01T06:58:55Z	status:UNKNOWN	latency:8.409	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:20.242	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54176	target_addr:104.21.86.125:443
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:21.285	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49810	target_addr:104.21.26.208:443
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:21.552	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43374	target_addr:172.67.219.211:443
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:221.988	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:58:55Z	status:FAILURE	latency:381.898	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:490.684	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:507.544	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T06:58:55Z	status:HEALTHY	latency:567.042	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:12.047	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52968	target_addr:172.64.147.104:443
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:19.433	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57464	target_addr:172.67.168.140:443
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:21.683	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46078	target_addr:172.67.219.211:443
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:30.423	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46074	target_addr:172.67.219.211:443
time:2026-10-01T07:03:55Z	status:FAILURE	latency:32.778	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:03:55Z	status:UNKNOWN	latency:34.971	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:84.871	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:122.365	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:226.076	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:03:55Z	status:HEALTHY	latency:406.716	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:08:55Z	status:UNKNOWN	latency:6.512	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:9.883	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54436	target_addr:172.67.219.211:443
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:12.255	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43466	target_addr:104.18.40.152:443
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:20.505	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56522	target_addr:172.67.168.140:443
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:23.989	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54440	target_addr:172.67.219.211:443
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:60.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:62.093	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:115.048	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:08:55Z	status:FAILURE	latency:226.467	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:08:55Z	status:HEALTHY	latency:227.949	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:13:55Z	status:UNKNOWN	latency:7.744	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:9.722	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43430	target_addr:104.18.40.152:443
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:13.844	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38712	target_addr:104.21.86.125:443
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:20.801	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44398	target_addr:104.21.26.208:443
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:22.078	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34386	target_addr:172.67.219.211:443
time:2026-10-01T07:13:55Z	status:FAILURE	latency:190.476	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:231.260	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:549.081	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:555.028	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:13:55Z	status:HEALTHY	latency:556.626	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:18:55Z	status:UNKNOWN	latency:7.898	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:9.740	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54378	target_addr:104.18.40.152:443
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:10.625	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60342	target_addr:104.21.26.208:443
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:11.810	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44756	target_addr:172.67.219.211:443
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:17.389	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44766	target_addr:172.67.219.211:443
time:2026-10-01T07:18:55Z	status:FAILURE	latency:185.674	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:226.278	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:529.589	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:534.057	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:18:55Z	status:HEALTHY	latency:535.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:23:55Z	status:UNKNOWN	latency:7.416	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:9.404	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54850	target_addr:172.64.147.104:443
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:9.400	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34050	target_addr:104.21.86.125:443
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:16.460	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34058	target_addr:104.21.86.125:443
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:19.379	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60412	target_addr:104.21.26.208:443
time:2026-10-01T07:23:55Z	status:FAILURE	latency:35.784	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:202.738	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:446.139	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:448.883	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:23:55Z	status:HEALTHY	latency:697.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:28:55Z	status:UNKNOWN	latency:15.504	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:15.493	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43908	target_addr:172.67.168.140:443
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:19.432	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44728	target_addr:104.21.86.125:443
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:33.340	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44734	target_addr:104.21.86.125:443
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:35.025	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50082	target_addr:172.64.147.104:443
time:2026-10-01T07:28:55Z	status:FAILURE	latency:204.626	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:222.611	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:521.981	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:557.914	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:28:55Z	status:HEALTHY	latency:1474.373	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:33:55Z	status:UNKNOWN	latency:7.873	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:12.211	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53626	target_addr:172.64.147.104:443
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:12.706	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48360	target_addr:104.21.26.208:443
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:21.761	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43422	target_addr:172.67.219.211:443
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:21.799	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45310	target_addr:104.21.86.125:443
time:2026-10-01T07:33:55Z	status:FAILURE	latency:29.740	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:59.028	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:72.249	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:203.690	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:33:55Z	status:HEALTHY	latency:1495.494	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:38:55Z	status:UNKNOWN	latency:6.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:8.533	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34314	target_addr:104.18.40.152:443
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:12.949	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47854	target_addr:172.67.219.211:443
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:20.600	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46860	target_addr:104.21.26.208:443
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:20.907	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47860	target_addr:172.67.219.211:443
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:77.568	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:80.118	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:38:55Z	status:FAILURE	latency:218.501	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:225.826	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:38:55Z	status:HEALTHY	latency:1089.235	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:43:55Z	status:UNKNOWN	latency:8.397	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:12.418	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36930	target_addr:172.67.219.211:443
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:23.436	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42352	target_addr:104.18.40.152:443
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:25.499	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38834	target_addr:104.21.26.208:443
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:46.341	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36940	target_addr:172.67.219.211:443
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:202.230	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:544.852	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:43:55Z	status:FAILURE	latency:635.249	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:738.825	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:43:55Z	status:HEALTHY	latency:744.321	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:48:55Z	status:UNKNOWN	latency:7.644	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:11.493	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49362	target_addr:172.67.219.211:443
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:12.312	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44660	target_addr:104.18.40.152:443
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:35.122	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34304	target_addr:104.21.86.125:443
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:58.440	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49690	target_addr:172.67.168.140:443
time:2026-10-01T07:48:55Z	status:FAILURE	latency:235.565	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:358.903	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:439.625	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:760.092	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:48:55Z	status:HEALTHY	latency:2822.800	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:53:55Z	status:UNKNOWN	latency:9.116	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:9.167	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45528	target_addr:172.64.147.104:443
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:11.619	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48648	target_addr:104.21.86.125:443
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:25.696	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51502	target_addr:172.67.219.211:443
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:26.372	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40816	target_addr:104.21.26.208:443
time:2026-10-01T07:53:55Z	status:FAILURE	latency:47.196	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:208.787	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:444.696	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:559.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:53:55Z	status:HEALTHY	latency:700.436	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:11.642	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43264	target_addr:172.67.219.211:443
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:12.252	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59474	target_addr:104.18.40.152:443
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:18.821	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43262	target_addr:172.67.219.211:443
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:20.830	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39894	target_addr:172.67.168.140:443
time:2026-10-01T07:58:55Z	status:UNKNOWN	latency:33.246	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:197.922	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:58:55Z	status:FAILURE	latency:418.065	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:449.708	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:451.726	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T07:58:55Z	status:HEALTHY	latency:462.612	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:03:55Z	status:UNKNOWN	latency:6.960	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:11.860	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53932	target_addr:104.18.40.152:443
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:14.365	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39958	target_addr:172.67.219.211:443
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:18.760	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40526	target_addr:104.21.26.208:443
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:21.505	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39960	target_addr:172.67.219.211:443
time:2026-10-01T08:03:55Z	status:FAILURE	latency:35.545	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:325.654	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:430.841	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:439.909	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:03:55Z	status:HEALTHY	latency:732.660	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:08:55Z	status:UNKNOWN	latency:8.279	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:11.280	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56720	target_addr:172.64.147.104:443
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:11.094	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40634	target_addr:104.21.86.125:443
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:13.209	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37226	target_addr:172.67.219.211:443
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:19.106	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52930	target_addr:104.21.26.208:443
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:188.450	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:08:55Z	status:FAILURE	latency:225.629	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:450.206	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:457.247	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:08:55Z	status:HEALTHY	latency:464.118	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:13:55Z	status:UNKNOWN	latency:8.976	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:9.776	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46004	target_addr:104.18.40.152:443
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:19.696	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37350	target_addr:104.21.26.208:443
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:21.275	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36098	target_addr:104.21.86.125:443
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:39.974	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36112	target_addr:104.21.86.125:443
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:62.384	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:73.572	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:13:55Z	status:FAILURE	latency:204.314	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:240.899	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:13:55Z	status:HEALTHY	latency:2400.108	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:18:55Z	status:UNKNOWN	latency:8.226	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:11.271	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50500	target_addr:104.21.86.125:443
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:11.691	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47430	target_addr:172.64.147.104:443
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:12.432	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52640	target_addr:104.21.26.208:443
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:54.962	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50502	target_addr:104.21.86.125:443
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:65.652	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:68.127	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:137.332	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:18:55Z	status:HEALTHY	latency:260.036	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:18:55Z	status:FAILURE	latency:332.804	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:23:55Z	status:UNKNOWN	latency:7.245	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:10.239	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41844	target_addr:104.18.40.152:443
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:9.910	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60162	target_addr:172.67.219.211:443
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:11.237	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60174	target_addr:172.67.219.211:443
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:20.040	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48660	target_addr:104.21.26.208:443
time:2026-10-01T08:23:55Z	status:FAILURE	latency:50.453	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:297.317	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:442.947	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:459.277	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:23:55Z	status:HEALTHY	latency:563.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:14.685	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37342	target_addr:104.18.40.152:443
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:17.006	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54370	target_addr:172.67.219.211:443
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:19.602	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54374	target_addr:172.67.219.211:443
time:2026-10-01T08:28:55Z	status:UNKNOWN	latency:36.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:45.234	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57072	target_addr:172.67.168.140:443
time:2026-10-01T08:28:55Z	status:FAILURE	latency:205.391	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:224.381	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:536.450	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:541.352	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:28:55Z	status:HEALTHY	latency:775.148	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:25.782	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50242	target_addr:104.21.86.125:443
time:2026-10-01T08:33:55Z	status:UNKNOWN	latency:30.664	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:31.504	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45982	target_addr:172.67.219.211:443
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:33.941	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47724	target_addr:104.21.26.208:443
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:54.930	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38644	target_addr:172.64.147.104:443
time:2026-10-01T08:33:55Z	status:FAILURE	latency:178.588	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:309.167	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:479.531	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:481.598	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:33:55Z	status:HEALTHY	latency:492.846	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:38:55Z	status:UNKNOWN	latency:7.857	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:9.666	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33876	target_addr:104.21.86.125:443
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:11.460	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55046	target_addr:104.18.40.152:443
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:12.523	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44724	target_addr:172.67.219.211:443
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:14.230	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38614	target_addr:172.67.168.140:443
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:314.442	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:38:55Z	status:FAILURE	latency:336.962	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:415.164	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:465.668	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:38:55Z	status:HEALTHY	latency:483.645	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:43:55Z	status:UNKNOWN	latency:7.503	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:10.136	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48086	target_addr:172.67.168.140:443
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:10.718	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45960	target_addr:172.67.219.211:443
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:12.444	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45966	target_addr:172.67.219.211:443
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:20.446	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56176	target_addr:172.64.147.104:443
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:63.249	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:72.082	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:72.964	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:43:55Z	status:HEALTHY	latency:214.531	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:43:55Z	status:FAILURE	latency:236.199	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:48:55Z	status:UNKNOWN	latency:9.561	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:14.207	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55160	target_addr:104.18.40.152:443
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:14.434	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53060	target_addr:172.67.168.140:443
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:15.864	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46534	target_addr:104.21.86.125:443
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:16.738	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57768	target_addr:172.67.219.211:443
time:2026-10-01T08:48:55Z	status:FAILURE	latency:27.862	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:65.644	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:81.558	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:92.529	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:48:55Z	status:HEALTHY	latency:254.149	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:8.993	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59646	target_addr:172.64.147.104:443
time:2026-10-01T08:53:55Z	status:UNKNOWN	latency:9.307	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:10.915	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48744	target_addr:104.21.26.208:443
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:19.217	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44532	target_addr:172.67.219.211:443
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:28.517	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44540	target_addr:172.67.219.211:443
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:57.242	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:65.351	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:102.930	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:53:55Z	status:FAILURE	latency:206.349	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:53:55Z	status:HEALTHY	latency:214.469	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:58:55Z	status:UNKNOWN	latency:7.678	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:10.430	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37406	target_addr:104.18.40.152:443
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:17.889	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35438	target_addr:172.67.219.211:443
time:2026-10-01T08:58:55Z	status:FAILURE	latency:26.113	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:29.289	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33804	target_addr:104.21.26.208:443
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:36.025	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35440	target_addr:172.67.219.211:443
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:57.604	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:74.027	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:81.703	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T08:58:55Z	status:HEALTHY	latency:223.709	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:03:55Z	status:UNKNOWN	latency:7.954	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:10.289	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58826	target_addr:104.18.40.152:443
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:11.447	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47438	target_addr:104.21.86.125:443
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:11.778	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47530	target_addr:172.67.219.211:443
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:16.088	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59190	target_addr:172.67.168.140:443
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:59.747	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:78.696	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:103.567	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:03:55Z	status:FAILURE	latency:188.866	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:03:55Z	status:HEALTHY	latency:344.268	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:08:55Z	status:UNKNOWN	latency:7.573	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:10.638	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47978	target_addr:104.21.86.125:443
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:12.684	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47990	target_addr:104.21.86.125:443
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:14.232	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36528	target_addr:172.64.147.104:443
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:15.352	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55604	target_addr:172.67.168.140:443
time:2026-10-01T09:08:55Z	status:FAILURE	latency:27.552	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:57.940	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:58.658	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:123.093	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:08:55Z	status:HEALTHY	latency:198.202	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:13:55Z	status:UNKNOWN	latency:8.124	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:12.554	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40044	target_addr:104.21.26.208:443
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:12.967	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38504	target_addr:104.18.40.152:443
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:15.246	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46154	target_addr:104.21.86.125:443
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:17.033	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46164	target_addr:104.21.86.125:443
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:64.190	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:64.584	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:71.651	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:13:55Z	status:HEALTHY	latency:200.601	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:13:55Z	status:FAILURE	latency:210.488	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:10.381	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56474	target_addr:172.67.219.211:443
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:12.579	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56484	target_addr:172.67.219.211:443
time:2026-10-01T09:18:55Z	status:UNKNOWN	latency:15.659	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:19.629	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53186	target_addr:104.21.26.208:443
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:23.873	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59916	target_addr:104.18.40.152:443
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:64.653	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:91.675	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:96.836	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:18:55Z	status:HEALTHY	latency:198.644	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:18:55Z	status:FAILURE	latency:235.648	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:23:55Z	status:UNKNOWN	latency:8.700	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:11.349	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50296	target_addr:172.67.168.140:443
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:20.253	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54328	target_addr:104.18.40.152:443
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:25.538	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52040	target_addr:104.21.86.125:443
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:40.809	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46606	target_addr:172.67.219.211:443
time:2026-10-01T09:23:55Z	status:FAILURE	latency:197.862	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:198.096	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:525.416	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:572.067	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:23:55Z	status:HEALTHY	latency:775.265	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:28:55Z	status:UNKNOWN	latency:7.015	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:8.427	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45966	target_addr:172.67.219.211:443
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:10.121	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33578	target_addr:172.64.147.104:443
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:12.411	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38464	target_addr:104.21.86.125:443
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:15.712	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47848	target_addr:172.67.168.140:443
time:2026-10-01T09:28:55Z	status:FAILURE	latency:241.097	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:244.630	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:1273.859	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:1508.833	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:28:55Z	status:HEALTHY	latency:1711.432	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:33:55Z	status:UNKNOWN	latency:8.903	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:9.419	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45972	target_addr:172.64.147.104:443
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:10.673	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39766	target_addr:104.21.86.125:443
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:11.777	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59876	target_addr:172.67.219.211:443
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:15.054	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54172	target_addr:104.21.26.208:443
time:2026-10-01T09:33:55Z	status:FAILURE	latency:205.383	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:213.051	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:437.066	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:518.544	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:33:55Z	status:HEALTHY	latency:753.245	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:38:55Z	status:UNKNOWN	latency:8.645	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:11.831	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39370	target_addr:172.64.147.104:443
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:11.500	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56400	target_addr:172.67.219.211:443
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:11.474	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34578	target_addr:172.67.168.140:443
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:12.131	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56398	target_addr:172.67.219.211:443
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:61.318	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:69.303	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:109.678	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:38:55Z	status:FAILURE	latency:193.431	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:38:55Z	status:HEALTHY	latency:246.311	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:9.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54474	target_addr:104.21.86.125:443
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:10.496	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37332	target_addr:104.18.40.152:443
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:12.139	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48568	target_addr:104.21.26.208:443
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:12.212	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41838	target_addr:172.67.219.211:443
time:2026-10-01T09:43:56Z	status:UNKNOWN	latency:14.060	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:43:56Z	status:FAILURE	latency:30.226	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:62.958	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:64.979	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:245.590	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:43:56Z	status:HEALTHY	latency:3480.078	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:11.791	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38838	target_addr:172.67.168.140:443
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:11.911	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36780	target_addr:172.67.219.211:443
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:12.569	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40324	target_addr:172.64.147.104:443
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:11.896	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49144	target_addr:104.21.86.125:443
time:2026-10-01T09:48:56Z	status:UNKNOWN	latency:58.979	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:231.105	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:48:56Z	status:FAILURE	latency:333.464	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:479.416	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:506.951	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:48:56Z	status:HEALTHY	latency:795.405	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:53:56Z	status:UNKNOWN	latency:7.556	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:10.926	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51360	target_addr:172.67.219.211:443
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:10.927	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35096	target_addr:172.64.147.104:443
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:11.929	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59242	target_addr:104.21.86.125:443
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:53.559	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:57.870	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43378	target_addr:104.21.26.208:443
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:61.308	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:65.093	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:53:56Z	status:FAILURE	latency:208.755	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:53:56Z	status:HEALTHY	latency:222.072	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:58:56Z	status:UNKNOWN	latency:7.531	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:9.480	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38474	target_addr:104.18.40.152:443
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:9.909	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37916	target_addr:104.21.26.208:443
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:15.080	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58048	target_addr:172.67.219.211:443
time:2026-10-01T09:58:56Z	status:FAILURE	latency:32.226	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:40.705	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60468	target_addr:104.21.86.125:443
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:55.540	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:58.703	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:64.483	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T09:58:56Z	status:HEALTHY	latency:254.080	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:9.575	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43152	target_addr:104.21.86.125:443
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:10.819	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46156	target_addr:172.67.168.140:443
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:11.564	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43154	target_addr:104.21.86.125:443
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:11.563	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60562	target_addr:104.18.40.152:443
time:2026-10-01T10:03:56Z	status:UNKNOWN	latency:38.821	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:03:56Z	status:FAILURE	latency:169.751	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:219.340	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:552.649	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:557.324	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:03:56Z	status:HEALTHY	latency:592.086	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:08:56Z	status:UNKNOWN	latency:9.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:10.328	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52928	target_addr:172.67.219.211:443
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:10.772	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42922	target_addr:104.18.40.152:443
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:12.340	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36840	target_addr:104.21.26.208:443
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:14.523	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52938	target_addr:172.67.219.211:443
time:2026-10-01T10:08:56Z	status:FAILURE	latency:34.473	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:243.530	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:448.974	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:479.964	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:08:56Z	status:HEALTHY	latency:494.830	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:13:56Z	status:UNKNOWN	latency:8.844	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:10.728	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51814	target_addr:104.21.86.125:443
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:10.785	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37404	target_addr:172.64.147.104:443
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:11.082	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59912	target_addr:172.67.168.140:443
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:14.609	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52362	target_addr:172.67.219.211:443
time:2026-10-01T10:13:56Z	status:FAILURE	latency:209.114	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:227.034	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:416.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:418.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:13:56Z	status:HEALTHY	latency:506.989	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:18:56Z	status:UNKNOWN	latency:8.086	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:8.586	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41974	target_addr:172.67.219.211:443
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:10.955	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34582	target_addr:172.64.147.104:443
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:13.417	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41988	target_addr:172.67.219.211:443
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:14.276	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35156	target_addr:104.21.26.208:443
time:2026-10-01T10:18:56Z	status:FAILURE	latency:41.532	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:213.196	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:392.726	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:439.281	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:18:56Z	status:HEALTHY	latency:457.575	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:10.984	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57330	target_addr:104.21.26.208:443
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:11.051	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39578	target_addr:104.18.40.152:443
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:11.040	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56692	target_addr:172.67.219.211:443
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:14.064	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39544	target_addr:104.21.86.125:443
time:2026-10-01T10:23:56Z	status:UNKNOWN	latency:56.763	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:59.701	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:64.248	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:71.144	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:23:56Z	status:FAILURE	latency:189.957	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:23:56Z	status:HEALTHY	latency:205.548	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:28:56Z	status:UNKNOWN	latency:8.007	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:10.403	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59318	target_addr:104.18.40.152:443
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:10.260	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43048	target_addr:172.67.219.211:443
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:10.448	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43050	target_addr:172.67.219.211:443
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:11.046	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59770	target_addr:104.21.26.208:443
time:2026-10-01T10:28:56Z	status:FAILURE	latency:45.899	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:56.831	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:57.665	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:61.413	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:28:56Z	status:HEALTHY	latency:223.873	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:33:56Z	status:UNKNOWN	latency:7.546	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:10.759	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39928	target_addr:104.21.86.125:443
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:11.259	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42540	target_addr:104.21.26.208:443
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:19.213	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47718	target_addr:104.18.40.152:443
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:22.534	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39934	target_addr:104.21.86.125:443
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:68.916	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:84.629	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:85.080	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:33:56Z	status:FAILURE	latency:142.809	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:33:56Z	status:HEALTHY	latency:230.315	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:11.604	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50482	target_addr:172.64.147.104:443
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:11.526	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41504	target_addr:104.21.86.125:443
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:14.662	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37980	target_addr:172.67.168.140:443
time:2026-10-01T10:38:56Z	status:FAILURE	latency:31.025	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:30.884	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41508	target_addr:104.21.86.125:443
time:2026-10-01T10:38:56Z	status:UNKNOWN	latency:38.198	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:214.740	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:449.580	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:552.713	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:38:56Z	status:HEALTHY	latency:761.279	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:43:56Z	status:UNKNOWN	latency:7.740	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:10.762	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54862	target_addr:104.18.40.152:443
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:11.193	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55760	target_addr:104.21.86.125:443
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:11.459	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45972	target_addr:172.67.219.211:443
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:29.735	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57590	target_addr:104.21.26.208:443
time:2026-10-01T10:43:56Z	status:FAILURE	latency:179.179	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:277.124	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:537.825	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:543.986	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:43:56Z	status:HEALTHY	latency:544.526	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:48:56Z	status:UNKNOWN	latency:8.738	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:11.078	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39658	target_addr:104.21.86.125:443
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:11.158	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58638	target_addr:172.67.168.140:443
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:11.934	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56868	target_addr:172.64.147.104:443
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:13.605	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39664	target_addr:104.21.86.125:443
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:54.402	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:57.037	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:92.448	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:48:56Z	status:HEALTHY	latency:220.461	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:48:56Z	status:FAILURE	latency:235.447	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:10.492	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53890	target_addr:104.21.86.125:443
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:13.881	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50560	target_addr:172.64.147.104:443
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:33.939	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53898	target_addr:104.21.86.125:443
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:38.959	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35292	target_addr:172.67.168.140:443
time:2026-10-01T10:53:56Z	status:UNKNOWN	latency:56.453	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:58.146	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:100.677	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:125.437	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:53:56Z	status:FAILURE	latency:201.905	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:53:56Z	status:HEALTHY	latency:497.384	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:58:56Z	status:UNKNOWN	latency:8.559	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:9.582	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53580	target_addr:104.21.26.208:443
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:10.643	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55394	target_addr:172.64.147.104:443
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:11.996	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56684	target_addr:172.67.219.211:443
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:13.543	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56682	target_addr:172.67.219.211:443
time:2026-10-01T10:58:56Z	status:FAILURE	latency:198.359	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:260.529	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:504.706	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:507.023	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T10:58:56Z	status:HEALTHY	latency:508.539	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:03:56Z	status:UNKNOWN	latency:7.321	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:9.605	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51918	target_addr:104.21.86.125:443
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:11.389	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46268	target_addr:104.18.40.152:443
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:11.054	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51932	target_addr:104.21.86.125:443
time:2026-10-01T11:03:56Z	status:FAILURE	latency:27.433	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:59.250	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59530	target_addr:172.67.168.140:443
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:268.374	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:426.179	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:429.209	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:03:56Z	status:HEALTHY	latency:439.585	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:9.127	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42364	target_addr:104.21.86.125:443
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:9.692	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51402	target_addr:172.67.219.211:443
time:2026-10-01T11:08:56Z	status:UNKNOWN	latency:14.550	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:21.930	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47476	target_addr:172.67.168.140:443
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:49.766	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39990	target_addr:172.64.147.104:443
time:2026-10-01T11:08:56Z	status:FAILURE	latency:192.601	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:194.237	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:526.270	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:556.527	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:08:56Z	status:HEALTHY	latency:567.064	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:10.145	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59056	target_addr:172.67.219.211:443
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:22.787	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57304	target_addr:104.21.26.208:443
time:2026-10-01T11:13:56Z	status:UNKNOWN	latency:25.012	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:13:56Z	status:FAILURE	latency:28.859	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:32.331	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43016	target_addr:172.64.147.104:443
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:61.984	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:86.327	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:106.793	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:119.289	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59062	target_addr:172.67.219.211:443
time:2026-10-01T11:13:56Z	status:HEALTHY	latency:398.793	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:18:56Z	status:UNKNOWN	latency:7.352	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:9.723	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43276	target_addr:104.21.86.125:443
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:9.645	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42516	target_addr:172.67.219.211:443
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:11.196	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48546	target_addr:172.64.147.104:443
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:14.278	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60676	target_addr:104.21.26.208:443
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:58.575	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:68.989	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:69.637	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:18:56Z	status:FAILURE	latency:228.368	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:18:56Z	status:HEALTHY	latency:322.630	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:23:56Z	status:UNKNOWN	latency:9.155	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:10.826	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59394	target_addr:104.18.40.152:443
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:10.904	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47644	target_addr:104.21.26.208:443
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:11.788	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56986	target_addr:172.67.219.211:443
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:11.833	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56982	target_addr:172.67.219.211:443
time:2026-10-01T11:23:56Z	status:FAILURE	latency:39.211	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:60.412	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:61.371	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:351.106	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:23:56Z	status:HEALTHY	latency:480.107	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:28:56Z	status:UNKNOWN	latency:7.320	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:10.423	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45264	target_addr:172.64.147.104:443
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:14.872	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50958	target_addr:104.21.86.125:443
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:19.000	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41902	target_addr:172.67.219.211:443
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:21.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42316	target_addr:104.21.26.208:443
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:56.681	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:73.810	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:131.311	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:28:56Z	status:FAILURE	latency:210.950	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:28:56Z	status:HEALTHY	latency:214.959	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:9.496	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45654	target_addr:104.21.86.125:443
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:11.111	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45660	target_addr:104.21.86.125:443
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:11.901	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54158	target_addr:172.64.147.104:443
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:13.250	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56658	target_addr:172.67.168.140:443
time:2026-10-01T11:33:56Z	status:FAILURE	latency:29.556	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:33:56Z	status:UNKNOWN	latency:36.088	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:56.323	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:62.920	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:217.962	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:33:56Z	status:HEALTHY	latency:1581.110	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:38:56Z	status:UNKNOWN	latency:6.619	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:10.291	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37508	target_addr:172.67.168.140:443
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:10.385	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44808	target_addr:104.21.86.125:443
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:11.949	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44820	target_addr:104.21.86.125:443
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:17.569	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56620	target_addr:172.64.147.104:443
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:49.939	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:53.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:70.848	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:38:56Z	status:HEALTHY	latency:189.006	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:38:56Z	status:FAILURE	latency:189.437	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:43:56Z	status:UNKNOWN	latency:7.490	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:9.926	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46580	target_addr:104.18.40.152:443
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:10.626	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50202	target_addr:172.67.168.140:443
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:10.456	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43526	target_addr:104.21.86.125:443
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:17.837	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43542	target_addr:104.21.86.125:443
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:59.142	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:59.759	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:94.113	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:43:56Z	status:FAILURE	latency:181.201	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:43:56Z	status:HEALTHY	latency:241.004	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:9.221	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44738	target_addr:172.67.168.140:443
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:10.909	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34800	target_addr:172.67.219.211:443
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:11.034	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35672	target_addr:104.21.86.125:443
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:22.638	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51366	target_addr:172.64.147.104:443
time:2026-10-01T11:48:56Z	status:UNKNOWN	latency:27.344	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:57.072	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:62.964	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:105.970	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:48:56Z	status:FAILURE	latency:184.881	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:48:56Z	status:HEALTHY	latency:675.918	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:53:56Z	status:UNKNOWN	latency:9.209	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:9.807	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33960	target_addr:104.21.86.125:443
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:11.754	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36920	target_addr:104.21.26.208:443
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:20.543	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45514	target_addr:104.18.40.152:443
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:25.052	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48846	target_addr:172.67.219.211:443
time:2026-10-01T11:53:56Z	status:FAILURE	latency:35.520	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:64.611	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:66.700	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:169.108	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:53:56Z	status:HEALTHY	latency:514.510	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:58:56Z	status:UNKNOWN	latency:8.492	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:10.624	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58028	target_addr:172.67.168.140:443
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:10.964	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47882	target_addr:104.21.86.125:443
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:20.218	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47884	target_addr:104.21.86.125:443
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:59.043	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:62.753	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:65.415	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:124.978	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54814	target_addr:172.64.147.104:443
time:2026-10-01T11:58:56Z	status:FAILURE	latency:187.439	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T11:58:56Z	status:HEALTHY	latency:196.293	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:10.796	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56086	target_addr:104.21.86.125:443
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:12.980	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56652	target_addr:104.18.40.152:443
time:2026-10-01T12:03:56Z	status:UNKNOWN	latency:18.865	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:18.547	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56074	target_addr:104.21.86.125:443
time:2026-10-01T12:03:56Z	status:FAILURE	latency:28.451	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:30.175	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41416	target_addr:172.67.168.140:443
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:75.458	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:91.776	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:234.696	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:03:56Z	status:HEALTHY	latency:310.389	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:9.891	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38202	target_addr:104.21.26.208:443
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:10.158	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52104	target_addr:172.67.219.211:443
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:11.620	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42576	target_addr:172.64.147.104:443
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:51.992	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:57.702	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:08:56Z	status:UNKNOWN	latency:59.107	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:73.379	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:08:56Z	status:FAILURE	latency:210.802	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:214.821	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47086	target_addr:104.21.86.125:443
time:2026-10-01T12:08:56Z	status:HEALTHY	latency:219.123	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:13:56Z	status:UNKNOWN	latency:7.453	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:9.057	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43132	target_addr:104.21.86.125:443
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:9.740	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43134	target_addr:104.21.86.125:443
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:10.863	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50302	target_addr:104.18.40.152:443
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:15.893	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56708	target_addr:172.67.168.140:443
time:2026-10-01T12:13:56Z	status:FAILURE	latency:25.760	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:48.024	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:59.379	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:74.152	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:13:56Z	status:HEALTHY	latency:246.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:9.405	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49368	target_addr:104.21.26.208:443
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:10.475	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36336	target_addr:104.18.40.152:443
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:11.512	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41928	target_addr:104.21.86.125:443
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:11.606	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41938	target_addr:104.21.86.125:443
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:48.456	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:54.762	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:18:56Z	status:UNKNOWN	latency:56.842	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:192.848	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:18:56Z	status:HEALTHY	latency:207.572	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:18:56Z	status:FAILURE	latency:236.865	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:12.514	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55912	target_addr:104.18.40.152:443
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:12.391	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53060	target_addr:104.21.26.208:443
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:12.070	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51840	target_addr:104.21.86.125:443
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:12.554	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47864	target_addr:172.67.219.211:443
time:2026-10-01T12:23:56Z	status:FAILURE	latency:27.913	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:23:56Z	status:UNKNOWN	latency:34.671	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:59.126	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:61.305	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:207.414	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:23:56Z	status:HEALTHY	latency:274.668	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:28:56Z	status:UNKNOWN	latency:8.070	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:9.609	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33096	target_addr:172.67.219.211:443
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:11.703	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37084	target_addr:172.64.147.104:443
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:14.043	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49056	target_addr:172.67.168.140:443
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:13.674	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33104	target_addr:172.67.219.211:443
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:58.680	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:62.385	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:82.474	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:28:56Z	status:FAILURE	latency:177.801	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:28:56Z	status:HEALTHY	latency:281.222	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:33:56Z	status:UNKNOWN	latency:8.555	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:10.562	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46702	target_addr:104.21.26.208:443
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:11.353	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41326	target_addr:172.67.219.211:443
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:13.438	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50802	target_addr:104.18.40.152:443
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:24.084	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38906	target_addr:104.21.86.125:443
time:2026-10-01T12:33:56Z	status:FAILURE	latency:28.673	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:53.283	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:64.001	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:160.708	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:33:56Z	status:HEALTHY	latency:229.289	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:38:56Z	status:UNKNOWN	latency:7.249	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:10.122	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52824	target_addr:104.21.26.208:443
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:13.428	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40364	target_addr:104.21.86.125:443
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:13.106	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49432	target_addr:172.67.219.211:443
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:13.541	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38106	target_addr:104.18.40.152:443
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:58.173	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:70.145	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:81.476	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:38:56Z	status:FAILURE	latency:211.723	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:38:56Z	status:HEALTHY	latency:218.009	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:10.320	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48976	target_addr:104.21.86.125:443
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:11.426	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39714	target_addr:104.18.40.152:443
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:12.625	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34342	target_addr:172.67.168.140:443
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:20.512	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48992	target_addr:104.21.86.125:443
time:2026-10-01T12:43:56Z	status:FAILURE	latency:37.705	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:43:56Z	status:UNKNOWN	latency:47.954	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:61.228	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:62.256	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:102.956	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:43:56Z	status:HEALTHY	latency:260.738	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:48:56Z	status:UNKNOWN	latency:11.773	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:13.041	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36662	target_addr:104.21.86.125:443
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:19.843	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43298	target_addr:104.21.26.208:443
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:20.206	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46390	target_addr:172.64.147.104:443
time:2026-10-01T12:48:56Z	status:FAILURE	latency:23.944	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:27.691	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36670	target_addr:104.21.86.125:443
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:60.358	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:69.267	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:102.734	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:48:56Z	status:HEALTHY	latency:2372.278	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:53:56Z	status:UNKNOWN	latency:9.980	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:14.765	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43546	target_addr:172.67.219.211:443
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:14.850	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60556	target_addr:104.21.86.125:443
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:15.320	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54218	target_addr:104.18.40.152:443
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:14.919	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56782	target_addr:172.67.168.140:443
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:248.539	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:53:56Z	status:FAILURE	latency:332.893	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:431.343	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:456.464	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:53:56Z	status:HEALTHY	latency:751.516	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:58:56Z	status:UNKNOWN	latency:9.449	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:12.039	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53278	target_addr:104.21.86.125:443
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:12.708	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40708	target_addr:172.67.219.211:443
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:12.586	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38532	target_addr:104.18.40.152:443
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:12.796	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48662	target_addr:172.67.168.140:443
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:203.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:58:56Z	status:FAILURE	latency:218.767	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:477.071	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:486.326	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T12:58:56Z	status:HEALTHY	latency:913.089	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:03:56Z	status:UNKNOWN	latency:7.842	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:9.327	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56136	target_addr:172.64.147.104:443
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:10.820	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57750	target_addr:172.67.219.211:443
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:11.879	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45698	target_addr:172.67.168.140:443
time:2026-10-01T13:03:56Z	status:FAILURE	latency:25.693	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:53.435	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58490	target_addr:104.21.86.125:443
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:82.684	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:94.147	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:235.477	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:03:56Z	status:HEALTHY	latency:724.834	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:08:56Z	status:UNKNOWN	latency:7.595	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:9.210	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41330	target_addr:172.64.147.104:443
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:11.037	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56228	target_addr:104.21.86.125:443
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:11.994	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48240	target_addr:172.67.219.211:443
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:12.981	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52050	target_addr:172.67.168.140:443
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:62.386	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:66.157	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:82.169	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:08:56Z	status:FAILURE	latency:220.243	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:08:56Z	status:HEALTHY	latency:534.982	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:13:56Z	status:UNKNOWN	latency:7.752	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:10.676	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54080	target_addr:104.21.86.125:443
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:14.053	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44838	target_addr:104.18.40.152:443
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:13.834	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50620	target_addr:104.21.26.208:443
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:53.334	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:62.770	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:62.817	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:85.682	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54094	target_addr:104.21.86.125:443
time:2026-10-01T13:13:56Z	status:FAILURE	latency:176.423	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:13:56Z	status:HEALTHY	latency:232.492	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:18:56Z	status:UNKNOWN	latency:8.231	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:10.032	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55830	target_addr:172.67.219.211:443
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:10.562	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42810	target_addr:104.21.86.125:443
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:13.443	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57762	target_addr:104.18.40.152:443
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:13.437	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36180	target_addr:104.21.26.208:443
time:2026-10-01T13:18:56Z	status:FAILURE	latency:28.125	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:59.506	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:63.816	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:101.498	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:18:56Z	status:HEALTHY	latency:340.101	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:23:56Z	status:UNKNOWN	latency:6.723	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:10.800	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43036	target_addr:104.18.40.152:443
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:12.404	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51046	target_addr:172.67.219.211:443
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:20.337	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35804	target_addr:172.67.168.140:443
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:20.267	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45892	target_addr:104.21.86.125:443
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:51.320	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:72.744	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:74.092	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:23:56Z	status:FAILURE	latency:335.327	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:23:56Z	status:HEALTHY	latency:550.042	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:9.666	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44504	target_addr:172.67.168.140:443
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:10.469	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60108	target_addr:172.64.147.104:443
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:12.160	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46390	target_addr:172.67.219.211:443
time:2026-10-01T13:28:56Z	status:UNKNOWN	latency:15.301	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:20.953	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48886	target_addr:104.21.86.125:443
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:52.043	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:74.886	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:77.190	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:28:56Z	status:FAILURE	latency:215.159	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:28:56Z	status:HEALTHY	latency:259.106	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:33:56Z	status:UNKNOWN	latency:6.146	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:10.632	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42986	target_addr:104.21.86.125:443
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:10.436	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42996	target_addr:104.21.86.125:443
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:13.305	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46960	target_addr:172.64.147.104:443
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:20.648	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51120	target_addr:104.21.26.208:443
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:59.885	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:73.019	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:74.417	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:33:56Z	status:FAILURE	latency:159.491	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:33:56Z	status:HEALTHY	latency:265.694	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:38:56Z	status:UNKNOWN	latency:7.896	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:12.304	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52686	target_addr:104.21.86.125:443
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:17.815	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40532	target_addr:104.18.40.152:443
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:18.090	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52700	target_addr:104.21.86.125:443
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:19.415	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52298	target_addr:172.67.168.140:443
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:69.261	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:70.783	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:127.635	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:38:56Z	status:HEALTHY	latency:160.191	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:38:56Z	status:FAILURE	latency:255.688	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:43:56Z	status:UNKNOWN	latency:7.640	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:10.844	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58272	target_addr:172.64.147.104:443
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:11.838	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50710	target_addr:172.67.219.211:443
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:13.750	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50720	target_addr:172.67.219.211:443
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:18.960	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52850	target_addr:104.21.26.208:443
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:47.953	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:75.866	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:80.981	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:43:56Z	status:HEALTHY	latency:183.392	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:43:56Z	status:FAILURE	latency:189.386	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:10.494	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51388	target_addr:172.64.147.104:443
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:11.809	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43048	target_addr:104.21.86.125:443
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:11.967	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40600	target_addr:172.67.219.211:443
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:18.787	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58148	target_addr:104.21.26.208:443
time:2026-10-01T13:48:57Z	status:UNKNOWN	latency:34.495	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:61.302	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:67.905	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:117.470	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:48:57Z	status:FAILURE	latency:222.808	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:48:57Z	status:HEALTHY	latency:225.538	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:53:57Z	status:UNKNOWN	latency:8.074	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:11.462	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47512	target_addr:104.18.40.152:443
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:22.017	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35222	target_addr:172.67.219.211:443
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:22.790	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48066	target_addr:172.67.168.140:443
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:22.942	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43980	target_addr:104.21.86.125:443
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:70.244	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:71.986	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:75.833	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:53:57Z	status:FAILURE	latency:172.238	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:53:57Z	status:HEALTHY	latency:308.514	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:58:57Z	status:UNKNOWN	latency:6.435	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:9.711	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40840	target_addr:104.21.26.208:443
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:12.511	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44956	target_addr:104.18.40.152:443
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:19.800	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51724	target_addr:172.67.219.211:443
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:23.783	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37082	target_addr:104.21.86.125:443
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:57.526	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:65.601	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:66.510	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T13:58:57Z	status:FAILURE	latency:201.175	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T13:58:57Z	status:HEALTHY	latency:222.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:03:57Z	status:UNKNOWN	latency:8.878	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:9.422	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57322	target_addr:172.64.147.104:443
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:16.678	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43652	target_addr:172.67.219.211:443
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:20.499	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44288	target_addr:104.21.26.208:443
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:30.099	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43656	target_addr:172.67.219.211:443
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:66.842	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:68.132	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:81.443	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:03:57Z	status:HEALTHY	latency:206.844	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:03:57Z	status:FAILURE	latency:249.547	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:13.374	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37302	target_addr:172.64.147.104:443
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:20.305	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49816	target_addr:172.67.168.140:443
time:2026-10-01T14:08:57Z	status:UNKNOWN	latency:24.796	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:28.660	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45624	target_addr:172.67.219.211:443
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:37.624	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45628	target_addr:172.67.219.211:443
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:68.272	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:76.399	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:98.583	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:08:57Z	status:FAILURE	latency:207.332	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:08:57Z	status:HEALTHY	latency:253.581	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:13:57Z	status:UNKNOWN	latency:13.597	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:17.577	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54012	target_addr:104.21.26.208:443
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:21.356	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47900	target_addr:104.21.86.125:443
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:21.642	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47914	target_addr:104.21.86.125:443
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:46.787	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47338	target_addr:104.18.40.152:443
time:2026-10-01T14:13:57Z	status:FAILURE	latency:228.077	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:556.870	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:575.170	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:599.425	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:13:57Z	status:HEALTHY	latency:637.724	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:18:57Z	status:UNKNOWN	latency:6.749	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:10.884	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54634	target_addr:172.64.147.104:443
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:10.553	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32798	target_addr:172.67.219.211:443
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:11.558	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47080	target_addr:104.21.26.208:443
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:27.168	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46954	target_addr:104.21.86.125:443
time:2026-10-01T14:18:57Z	status:FAILURE	latency:231.553	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:273.693	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:435.039	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:438.626	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:18:57Z	status:HEALTHY	latency:456.465	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:23:57Z	status:UNKNOWN	latency:6.078	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:7.559	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36648	target_addr:172.67.219.211:443
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:8.121	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48262	target_addr:172.67.168.140:443
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:10.627	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39834	target_addr:104.18.40.152:443
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:11.740	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43332	target_addr:104.21.86.125:443
time:2026-10-01T14:23:57Z	status:FAILURE	latency:170.135	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:241.865	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:516.480	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:522.153	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:23:57Z	status:HEALTHY	latency:537.376	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:9.772	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33956	target_addr:172.67.219.211:443
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:10.488	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56042	target_addr:104.18.40.152:443
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:11.587	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56608	target_addr:104.21.86.125:443
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:11.631	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47540	target_addr:172.67.168.140:443
time:2026-10-01T14:28:57Z	status:UNKNOWN	latency:34.883	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:28:57Z	status:FAILURE	latency:145.552	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:233.742	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:433.786	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:447.809	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:28:57Z	status:HEALTHY	latency:451.558	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:10.971	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53252	target_addr:172.67.219.211:443
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:12.991	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44058	target_addr:104.18.40.152:443
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:17.483	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51068	target_addr:104.21.26.208:443
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:20.262	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38896	target_addr:104.21.86.125:443
time:2026-10-01T14:33:57Z	status:UNKNOWN	latency:56.643	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:95.306	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:33:57Z	status:FAILURE	latency:222.423	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:385.841	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:484.954	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:33:57Z	status:HEALTHY	latency:509.769	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:10.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45256	target_addr:172.67.219.211:443
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:11.897	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42056	target_addr:104.21.86.125:443
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:12.861	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51368	target_addr:172.67.168.140:443
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:28.236	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33500	target_addr:104.18.40.152:443
time:2026-10-01T14:38:57Z	status:UNKNOWN	latency:32.441	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:62.254	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:64.995	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:83.561	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:38:57Z	status:FAILURE	latency:223.111	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:38:57Z	status:HEALTHY	latency:249.826	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:11.173	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41162	target_addr:172.67.219.211:443
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:12.630	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53566	target_addr:172.67.168.140:443
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:22.157	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41172	target_addr:172.67.219.211:443
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:85.065	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:85.183	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:122.849	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:138.172	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:43:57Z	status:HEALTHY	latency:224.143	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39510	target_addr:172.64.147.104:443
time:2026-10-01T14:43:57Z	status:UNKNOWN	latency:243.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:43:57Z	status:FAILURE	latency:259.036	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:48:57Z	status:UNKNOWN	latency:7.020	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:14.752	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46330	target_addr:104.18.40.152:443
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:18.056	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38526	target_addr:104.21.86.125:443
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:22.188	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55390	target_addr:104.21.26.208:443
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:21.985	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38516	target_addr:104.21.86.125:443
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:62.295	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:48:57Z	status:FAILURE	latency:64.405	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:67.570	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:68.024	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:48:57Z	status:HEALTHY	latency:216.517	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:53:57Z	status:UNKNOWN	latency:7.578	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:8.971	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51834	target_addr:172.67.219.211:443
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:11.127	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55356	target_addr:104.18.40.152:443
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:18.406	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55504	target_addr:104.21.86.125:443
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:18.376	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54492	target_addr:104.21.26.208:443
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:59.400	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:65.385	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:82.531	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:53:57Z	status:HEALTHY	latency:118.107	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:53:57Z	status:FAILURE	latency:233.683	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:58:57Z	status:UNKNOWN	latency:7.570	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:16.831	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46272	target_addr:172.67.219.211:443
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:16.466	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47478	target_addr:104.21.26.208:443
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:18.539	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46288	target_addr:172.67.219.211:443
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:33.766	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48622	target_addr:172.64.147.104:443
time:2026-10-01T14:58:57Z	status:FAILURE	latency:44.998	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:71.650	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:73.542	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:83.058	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T14:58:57Z	status:HEALTHY	latency:234.951	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:03:57Z	status:UNKNOWN	latency:10.190	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:12.070	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58998	target_addr:104.18.40.152:443
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:11.931	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57594	target_addr:172.67.219.211:443
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:12.096	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58332	target_addr:104.21.86.125:443
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:12.563	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60188	target_addr:104.21.26.208:443
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:62.377	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:66.703	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:74.855	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:03:57Z	status:HEALTHY	latency:116.269	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:03:57Z	status:FAILURE	latency:212.113	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:12.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60946	target_addr:104.21.26.208:443
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:12.096	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35132	target_addr:104.21.86.125:443
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:16.160	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45396	target_addr:104.18.40.152:443
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:16.206	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42090	target_addr:172.67.219.211:443
time:2026-10-01T15:08:57Z	status:UNKNOWN	latency:16.597	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:58.687	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:74.799	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:82.771	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:08:57Z	status:HEALTHY	latency:234.703	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:08:57Z	status:FAILURE	latency:248.851	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:13:57Z	status:UNKNOWN	latency:6.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:8.997	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49456	target_addr:172.67.219.211:443
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:12.339	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35916	target_addr:104.18.40.152:443
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:14.246	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50676	target_addr:172.67.168.140:443
time:2026-10-01T15:13:57Z	status:FAILURE	latency:209.129	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:236.235	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:483.455	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:545.879	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:559.906	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:13:57Z	status:HEALTHY	latency:1080.925	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45134	target_addr:104.21.86.125:443
time:2026-10-01T15:18:57Z	status:UNKNOWN	latency:6.535	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:13.280	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50208	target_addr:104.21.26.208:443
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:12.916	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49212	target_addr:172.67.219.211:443
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:13.657	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40382	target_addr:104.21.86.125:443
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:29.666	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55400	target_addr:104.18.40.152:443
time:2026-10-01T15:18:57Z	status:FAILURE	latency:178.106	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:304.543	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:540.987	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:595.678	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:18:57Z	status:HEALTHY	latency:599.172	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:9.734	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34664	target_addr:172.67.219.211:443
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:9.933	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34624	target_addr:104.18.40.152:443
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:10.298	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43640	target_addr:172.67.168.140:443
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:16.442	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48546	target_addr:104.21.86.125:443
time:2026-10-01T15:23:57Z	status:FAILURE	latency:30.871	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:23:57Z	status:UNKNOWN	latency:31.806	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:235.679	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:453.769	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:544.187	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:23:57Z	status:HEALTHY	latency:579.887	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:28:57Z	status:UNKNOWN	latency:8.393	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:11.018	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39308	target_addr:104.18.40.152:443
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:10.719	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55574	target_addr:104.21.26.208:443
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:10.963	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46536	target_addr:104.21.86.125:443
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:13.397	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46544	target_addr:104.21.86.125:443
time:2026-10-01T15:28:57Z	status:FAILURE	latency:216.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:221.984	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:428.788	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:438.557	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:28:57Z	status:HEALTHY	latency:750.972	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:33:57Z	status:UNKNOWN	latency:8.084	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:8.877	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40740	target_addr:104.18.40.152:443
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:10.191	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33982	target_addr:104.21.26.208:443
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:10.738	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50934	target_addr:104.21.86.125:443
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:11.380	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50948	target_addr:104.21.86.125:443
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:180.753	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:33:57Z	status:FAILURE	latency:204.735	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:438.080	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:438.542	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:33:57Z	status:HEALTHY	latency:442.075	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:38:57Z	status:UNKNOWN	latency:8.224	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:10.497	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38308	target_addr:104.21.86.125:443
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:11.595	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38954	target_addr:104.18.40.152:443
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:27.451	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55020	target_addr:172.67.168.140:443
time:2026-10-01T15:38:57Z	status:FAILURE	latency:31.610	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:36.815	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35392	target_addr:172.67.219.211:443
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:222.020	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:481.813	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:495.046	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:38:57Z	status:HEALTHY	latency:535.974	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:8.220	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35240	target_addr:172.67.219.211:443
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:8.702	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35254	target_addr:172.67.219.211:443
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:10.248	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36682	target_addr:104.18.40.152:443
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:10.041	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54488	target_addr:104.21.26.208:443
time:2026-10-01T15:43:57Z	status:UNKNOWN	latency:26.483	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:43:57Z	status:FAILURE	latency:187.401	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:228.794	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:393.677	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:450.864	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:43:57Z	status:HEALTHY	latency:463.486	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:48:57Z	status:UNKNOWN	latency:7.615	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:9.245	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53670	target_addr:104.21.26.208:443
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:10.389	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46604	target_addr:172.64.147.104:443
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:11.240	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59900	target_addr:172.67.219.211:443
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:13.034	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38588	target_addr:104.21.86.125:443
time:2026-10-01T15:48:57Z	status:FAILURE	latency:30.756	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:272.150	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:436.567	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:448.369	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:48:57Z	status:HEALTHY	latency:466.680	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:12.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53632	target_addr:172.64.147.104:443
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:12.447	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41988	target_addr:104.21.86.125:443
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:12.131	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40112	target_addr:172.67.219.211:443
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:14.308	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54070	target_addr:104.21.26.208:443
time:2026-10-01T15:53:57Z	status:UNKNOWN	latency:34.175	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:246.258	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:53:57Z	status:FAILURE	latency:274.197	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:523.019	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:536.248	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:53:57Z	status:HEALTHY	latency:548.251	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:58:57Z	status:UNKNOWN	latency:7.537	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:8.602	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54548	target_addr:104.18.40.152:443
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:9.462	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39436	target_addr:104.21.86.125:443
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:13.421	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39378	target_addr:104.21.26.208:443
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:70.059	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42426	target_addr:172.67.219.211:443
time:2026-10-01T15:58:57Z	status:FAILURE	latency:348.511	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:390.236	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:479.767	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:493.170	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T15:58:57Z	status:HEALTHY	latency:543.095	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:03:57Z	status:UNKNOWN	latency:7.242	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:11.152	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39108	target_addr:104.21.86.125:443
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:12.725	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39116	target_addr:104.21.86.125:443
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:14.194	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48986	target_addr:172.64.147.104:443
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:13.792	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35720	target_addr:104.21.26.208:443
time:2026-10-01T16:03:57Z	status:FAILURE	latency:180.324	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:301.018	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:490.957	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:706.175	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:03:57Z	status:HEALTHY	latency:742.579	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:08:57Z	status:UNKNOWN	latency:6.883	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:9.948	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43160	target_addr:104.18.40.152:443
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:11.294	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49196	target_addr:172.67.219.211:443
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:12.771	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58748	target_addr:172.67.168.140:443
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:15.873	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42856	target_addr:104.21.86.125:443
time:2026-10-01T16:08:57Z	status:FAILURE	latency:150.309	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:300.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:465.512	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:488.965	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:08:57Z	status:HEALTHY	latency:651.092	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:13:57Z	status:UNKNOWN	latency:10.613	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:13.690	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40082	target_addr:172.67.168.140:443
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:14.144	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43792	target_addr:104.18.40.152:443
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:13.878	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58102	target_addr:104.21.86.125:443
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:22.770	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38630	target_addr:172.67.219.211:443
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:195.843	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:13:57Z	status:FAILURE	latency:374.008	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:439.388	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:465.100	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:13:57Z	status:HEALTHY	latency:739.232	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:18:57Z	status:UNKNOWN	latency:8.464	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:11.264	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41086	target_addr:104.21.86.125:443
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:13.206	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43794	target_addr:172.67.219.211:443
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:22.469	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38378	target_addr:104.21.26.208:443
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:55.979	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51288	target_addr:172.64.147.104:443
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:286.021	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:18:57Z	status:FAILURE	latency:367.325	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:536.816	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:565.060	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:18:57Z	status:HEALTHY	latency:756.329	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:8.516	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56822	target_addr:104.18.40.152:443
time:2026-10-01T16:23:57Z	status:UNKNOWN	latency:8.690	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:20.081	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55600	target_addr:104.21.86.125:443
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:31.967	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55604	target_addr:104.21.86.125:443
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:50.857	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48872	target_addr:172.67.168.140:443
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:207.944	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:23:57Z	status:FAILURE	latency:279.681	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:493.728	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:542.060	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:23:57Z	status:HEALTHY	latency:643.044	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:28:57Z	status:UNKNOWN	latency:8.180	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:12.680	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35330	target_addr:172.67.168.140:443
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:13.766	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60228	target_addr:172.64.147.104:443
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:20.207	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60060	target_addr:172.67.219.211:443
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:66.658	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46466	target_addr:104.21.86.125:443
time:2026-10-01T16:28:57Z	status:FAILURE	latency:210.017	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:228.046	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:575.912	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:884.387	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:28:57Z	status:HEALTHY	latency:1115.681	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:12.289	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53402	target_addr:104.18.40.152:443
time:2026-10-01T16:33:57Z	status:UNKNOWN	latency:12.729	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:13.284	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58378	target_addr:104.21.86.125:443
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:22.344	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43628	target_addr:172.67.168.140:443
time:2026-10-01T16:33:57Z	status:FAILURE	latency:25.869	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:71.498	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59392	target_addr:172.67.219.211:443
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:224.411	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:471.039	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:494.189	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:33:57Z	status:HEALTHY	latency:1794.860	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:38:57Z	status:UNKNOWN	latency:7.189	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:10.384	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57474	target_addr:104.21.26.208:443
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:10.818	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41856	target_addr:172.67.219.211:443
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:12.472	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49208	target_addr:104.18.40.152:443
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:21.044	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42460	target_addr:104.21.86.125:443
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:131.228	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:38:57Z	status:FAILURE	latency:222.712	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:445.526	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:448.892	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:38:57Z	status:HEALTHY	latency:808.608	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:43:57Z	status:UNKNOWN	latency:6.873	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:11.663	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36026	target_addr:172.67.219.211:443
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:12.529	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60102	target_addr:172.67.168.140:443
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:15.048	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36028	target_addr:172.67.219.211:443
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:15.981	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49080	target_addr:172.64.147.104:443
time:2026-10-01T16:43:57Z	status:FAILURE	latency:210.797	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:228.773	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:525.325	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:527.496	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:43:57Z	status:HEALTHY	latency:589.677	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:48:57Z	status:UNKNOWN	latency:5.661	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:10.490	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56188	target_addr:172.67.219.211:443
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:12.663	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36872	target_addr:104.18.40.152:443
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:12.777	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56198	target_addr:172.67.219.211:443
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:13.139	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53868	target_addr:104.21.26.208:443
time:2026-10-01T16:48:57Z	status:FAILURE	latency:253.116	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:282.354	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:495.158	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:499.223	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:48:57Z	status:HEALTHY	latency:552.234	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:11.139	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49538	target_addr:104.21.86.125:443
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:11.949	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58310	target_addr:104.21.26.208:443
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:12.153	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48934	target_addr:104.18.40.152:443
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:18.602	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49528	target_addr:104.21.86.125:443
time:2026-10-01T16:53:57Z	status:UNKNOWN	latency:57.501	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:140.093	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:53:57Z	status:FAILURE	latency:284.465	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:514.260	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:518.799	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:53:57Z	status:HEALTHY	latency:563.061	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:58:57Z	status:UNKNOWN	latency:6.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:9.107	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43598	target_addr:172.64.147.104:443
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:9.957	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54282	target_addr:104.21.86.125:443
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:35.212	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47390	target_addr:172.67.219.211:443
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:39.433	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53462	target_addr:104.21.26.208:443
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:207.111	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:58:57Z	status:FAILURE	latency:233.793	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:540.635	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:543.840	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T16:58:57Z	status:HEALTHY	latency:800.383	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:03:57Z	status:UNKNOWN	latency:9.218	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:10.180	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59360	target_addr:172.64.147.104:443
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:11.242	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57504	target_addr:172.67.219.211:443
time:2026-10-01T17:03:57Z	status:FAILURE	latency:36.004	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:56.450	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:82.809	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57508	target_addr:172.67.219.211:443
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:90.644	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:166.895	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54010	target_addr:172.67.168.140:443
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:328.044	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:03:57Z	status:HEALTHY	latency:333.984	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:08:57Z	status:UNKNOWN	latency:5.696	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:7.190	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38862	target_addr:104.18.40.152:443
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:9.994	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46054	target_addr:172.67.168.140:443
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:62.496	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:85.567	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37018	target_addr:172.67.219.211:443
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:162.109	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37012	target_addr:172.67.219.211:443
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:249.284	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:268.432	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:08:57Z	status:FAILURE	latency:336.943	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:08:57Z	status:HEALTHY	latency:650.535	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:13:57Z	status:UNKNOWN	latency:8.387	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:9.561	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60814	target_addr:104.21.86.125:443
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:10.493	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47000	target_addr:104.18.40.152:443
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:13.917	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49618	target_addr:104.21.26.208:443
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:60.432	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:60.770	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:64.810	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:65.870	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58240	target_addr:172.67.219.211:443
time:2026-10-01T17:13:57Z	status:HEALTHY	latency:217.690	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:13:57Z	status:FAILURE	latency:359.007	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:18:57Z	status:UNKNOWN	latency:6.534	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:9.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44506	target_addr:172.67.168.140:443
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:10.320	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51082	target_addr:172.67.219.211:443
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:12.349	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39674	target_addr:172.64.147.104:443
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:61.854	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:65.614	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51088	target_addr:172.67.219.211:443
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:134.581	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:160.811	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:18:57Z	status:FAILURE	latency:204.107	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:18:57Z	status:HEALTHY	latency:223.402	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:23:58Z	status:UNKNOWN	latency:6.776	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:9.767	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54254	target_addr:172.64.147.104:443
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:10.395	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38556	target_addr:172.67.219.211:443
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:15.122	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38572	target_addr:172.67.219.211:443
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:53.207	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:63.245	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:65.797	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49946	target_addr:104.21.26.208:443
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:71.669	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:23:58Z	status:FAILURE	latency:234.176	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:23:58Z	status:HEALTHY	latency:234.184	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:28:58Z	status:UNKNOWN	latency:8.226	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:10.047	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57040	target_addr:104.21.26.208:443
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:11.040	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46960	target_addr:104.21.86.125:443
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:20.139	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36680	target_addr:172.67.219.211:443
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:38.760	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53198	target_addr:172.64.147.104:443
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:79.021	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:81.668	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:229.774	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:28:58Z	status:FAILURE	latency:235.191	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:28:58Z	status:HEALTHY	latency:259.084	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:9.583	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35900	target_addr:104.21.86.125:443
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:12.021	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40784	target_addr:104.21.26.208:443
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:19.146	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46066	target_addr:172.67.219.211:443
time:2026-10-01T17:33:58Z	status:UNKNOWN	latency:33.200	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:57.290	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:63.145	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50980	target_addr:104.18.40.152:443
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:89.657	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:94.734	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:33:58Z	status:FAILURE	latency:217.541	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:33:58Z	status:HEALTHY	latency:296.135	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:38:58Z	status:UNKNOWN	latency:9.127	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:12.258	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34308	target_addr:104.18.40.152:443
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:11.933	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36728	target_addr:104.21.26.208:443
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:12.023	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49716	target_addr:104.21.86.125:443
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:22.867	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49724	target_addr:104.21.86.125:443
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:60.921	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:88.317	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:90.386	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:38:58Z	status:FAILURE	latency:228.949	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:38:58Z	status:HEALTHY	latency:254.709	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:43:58Z	status:UNKNOWN	latency:8.333	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:10.925	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43934	target_addr:172.64.147.104:443
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:12.170	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52774	target_addr:104.21.26.208:443
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:18.956	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35506	target_addr:172.67.219.211:443
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:27.234	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49056	target_addr:104.21.86.125:443
time:2026-10-01T17:43:58Z	status:FAILURE	latency:36.944	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:55.505	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:59.836	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:70.273	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:43:58Z	status:HEALTHY	latency:241.033	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:48:58Z	status:UNKNOWN	latency:7.312	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:9.480	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52968	target_addr:104.21.26.208:443
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:9.593	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38224	target_addr:172.67.219.211:443
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:11.145	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32974	target_addr:172.64.147.104:443
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:12.411	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59426	target_addr:104.21.86.125:443
time:2026-10-01T17:48:58Z	status:FAILURE	latency:220.597	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:235.197	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:424.874	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:589.930	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:48:58Z	status:HEALTHY	latency:833.977	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:12.459	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40638	target_addr:104.21.86.125:443
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:12.443	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57112	target_addr:172.64.147.104:443
time:2026-10-01T17:53:58Z	status:UNKNOWN	latency:20.633	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:25.486	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57618	target_addr:104.21.26.208:443
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:32.570	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40644	target_addr:104.21.86.125:443
time:2026-10-01T17:53:58Z	status:FAILURE	latency:59.310	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:251.503	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:451.736	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:470.989	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:53:58Z	status:HEALTHY	latency:734.843	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:8.893	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55486	target_addr:104.18.40.152:443
time:2026-10-01T17:58:58Z	status:UNKNOWN	latency:8.969	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:13.416	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37804	target_addr:104.21.86.125:443
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:13.788	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59098	target_addr:172.67.168.140:443
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:14.041	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37816	target_addr:104.21.86.125:443
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:233.280	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:58:58Z	status:FAILURE	latency:236.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:528.917	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:529.164	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T17:58:58Z	status:HEALTHY	latency:560.893	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:03:58Z	status:UNKNOWN	latency:8.715	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:11.132	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44858	target_addr:172.64.147.104:443
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:11.392	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39424	target_addr:172.67.168.140:443
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:13.364	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39982	target_addr:172.67.219.211:443
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:19.780	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39980	target_addr:172.67.219.211:443
time:2026-10-01T18:03:58Z	status:FAILURE	latency:31.240	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:229.766	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:451.046	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:453.775	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:03:58Z	status:HEALTHY	latency:469.306	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:08:58Z	status:UNKNOWN	latency:6.182	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:9.462	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56092	target_addr:172.67.219.211:443
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:11.176	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59152	target_addr:104.21.26.208:443
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:21.699	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59178	target_addr:172.64.147.104:443
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:30.292	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57186	target_addr:104.21.86.125:443
time:2026-10-01T18:08:58Z	status:FAILURE	latency:30.287	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:138.391	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:480.264	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:479.970	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:08:58Z	status:HEALTHY	latency:582.334	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:13:58Z	status:UNKNOWN	latency:7.568	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:10.524	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33104	target_addr:172.67.168.140:443
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:11.681	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58842	target_addr:104.21.86.125:443
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:12.157	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58848	target_addr:104.21.86.125:443
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:31.680	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52188	target_addr:172.64.147.104:443
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:203.311	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:13:58Z	status:FAILURE	latency:205.501	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:432.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:457.542	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:13:58Z	status:HEALTHY	latency:459.107	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:18:58Z	status:UNKNOWN	latency:7.212	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:8.202	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52996	target_addr:104.18.40.152:443
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:10.130	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47850	target_addr:172.67.219.211:443
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:11.902	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52812	target_addr:104.21.86.125:443
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:11.805	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33630	target_addr:104.21.26.208:443
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:257.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:18:58Z	status:FAILURE	latency:326.327	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:450.473	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:460.182	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:18:58Z	status:HEALTHY	latency:462.546	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:23:58Z	status:UNKNOWN	latency:7.865	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:8.454	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58436	target_addr:104.18.40.152:443
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:9.289	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33484	target_addr:172.67.219.211:443
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:11.730	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56778	target_addr:172.67.168.140:443
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:12.422	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48106	target_addr:104.21.86.125:443
time:2026-10-01T18:23:58Z	status:FAILURE	latency:29.306	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:61.040	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:72.309	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:77.632	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:23:58Z	status:HEALTHY	latency:195.532	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:28:58Z	status:UNKNOWN	latency:8.807	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:9.568	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49706	target_addr:104.21.26.208:443
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:11.307	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49346	target_addr:172.67.219.211:443
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:12.787	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50852	target_addr:104.18.40.152:443
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:13.491	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43478	target_addr:104.21.86.125:443
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:57.622	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:73.196	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:74.145	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:28:58Z	status:FAILURE	latency:183.169	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:28:58Z	status:HEALTHY	latency:184.050	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:33:58Z	status:UNKNOWN	latency:7.689	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:10.141	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36506	target_addr:172.67.219.211:443
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:11.986	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36508	target_addr:172.67.219.211:443
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:13.653	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37048	target_addr:172.64.147.104:443
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:14.812	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44902	target_addr:172.67.168.140:443
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:57.450	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:64.629	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:71.411	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:33:58Z	status:FAILURE	latency:209.994	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:33:58Z	status:HEALTHY	latency:216.378	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:10.918	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47574	target_addr:104.21.26.208:443
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:11.124	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40208	target_addr:172.67.219.211:443
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:11.427	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59476	target_addr:172.64.147.104:443
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:12.165	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52548	target_addr:104.21.86.125:443
time:2026-10-01T18:38:58Z	status:FAILURE	latency:29.066	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:38:58Z	status:UNKNOWN	latency:56.501	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:60.032	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:64.989	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:81.822	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:38:58Z	status:HEALTHY	latency:279.237	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:9.117	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35134	target_addr:104.21.26.208:443
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:9.582	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58356	target_addr:104.18.40.152:443
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:11.116	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44296	target_addr:104.21.86.125:443
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:11.929	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44304	target_addr:104.21.86.125:443
time:2026-10-01T18:43:58Z	status:UNKNOWN	latency:29.837	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:77.894	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:78.286	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:86.017	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:43:58Z	status:HEALTHY	latency:209.738	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:43:58Z	status:FAILURE	latency:219.692	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:48:58Z	status:UNKNOWN	latency:7.532	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:9.249	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49584	target_addr:172.67.219.211:443
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:9.803	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53492	target_addr:104.18.40.152:443
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:10.789	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48530	target_addr:172.67.168.140:443
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:18.209	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41006	target_addr:104.21.86.125:443
time:2026-10-01T18:48:58Z	status:FAILURE	latency:30.182	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:54.464	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:59.345	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:102.161	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:48:58Z	status:HEALTHY	latency:330.018	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:9.701	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57446	target_addr:172.64.147.104:443
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:12.952	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40372	target_addr:104.21.86.125:443
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:12.674	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48276	target_addr:172.67.168.140:443
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:12.822	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56936	target_addr:172.67.219.211:443
time:2026-10-01T18:53:58Z	status:UNKNOWN	latency:14.967	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:52.242	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:60.508	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:77.113	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:53:58Z	status:HEALTHY	latency:193.143	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:53:58Z	status:FAILURE	latency:219.413	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:58:58Z	status:UNKNOWN	latency:6.645	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:9.645	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54582	target_addr:172.67.168.140:443
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:10.113	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54722	target_addr:172.67.219.211:443
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:11.484	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54736	target_addr:172.67.219.211:443
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:12.458	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37580	target_addr:104.18.40.152:443
time:2026-10-01T18:58:58Z	status:FAILURE	latency:174.611	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:242.951	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:719.979	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:745.184	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T18:58:58Z	status:HEALTHY	latency:746.966	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:03:58Z	status:UNKNOWN	latency:6.160	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:9.383	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54766	target_addr:172.64.147.104:443
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:11.533	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56440	target_addr:172.67.168.140:443
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:12.049	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55016	target_addr:104.21.86.125:443
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:12.548	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34990	target_addr:172.67.219.211:443
time:2026-10-01T19:03:58Z	status:FAILURE	latency:30.160	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:59.600	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:67.816	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:93.660	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:03:58Z	status:HEALTHY	latency:270.685	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:08:58Z	status:UNKNOWN	latency:7.846	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:10.680	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43948	target_addr:104.21.86.125:443
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:10.961	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60698	target_addr:172.67.168.140:443
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:12.441	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33346	target_addr:172.64.147.104:443
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:28.225	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56698	target_addr:172.67.219.211:443
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:54.883	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:71.166	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:85.013	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:08:58Z	status:FAILURE	latency:197.362	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:08:58Z	status:HEALTHY	latency:221.236	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:13:58Z	status:UNKNOWN	latency:7.159	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:10.208	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55120	target_addr:104.21.86.125:443
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:11.715	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41272	target_addr:172.64.147.104:443
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:17.699	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55126	target_addr:104.21.86.125:443
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:19.312	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42916	target_addr:172.67.168.140:443
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:63.194	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:66.272	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:68.350	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:13:58Z	status:FAILURE	latency:220.997	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:13:58Z	status:HEALTHY	latency:269.233	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:9.489	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53838	target_addr:172.67.219.211:443
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:11.509	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38690	target_addr:104.21.26.208:443
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:11.216	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53850	target_addr:172.67.219.211:443
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:16.410	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42428	target_addr:104.18.40.152:443
time:2026-10-01T19:18:58Z	status:UNKNOWN	latency:57.538	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:58.464	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:61.841	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:76.618	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:18:58Z	status:HEALTHY	latency:215.200	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:18:58Z	status:FAILURE	latency:225.004	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:23:58Z	status:UNKNOWN	latency:8.048	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:10.965	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36688	target_addr:172.67.219.211:443
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:11.289	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36686	target_addr:172.67.219.211:443
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:11.833	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50694	target_addr:172.64.147.104:443
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:14.280	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56080	target_addr:104.21.26.208:443
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:59.536	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:61.086	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:69.009	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:23:58Z	status:FAILURE	latency:178.434	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:23:58Z	status:HEALTHY	latency:243.030	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:28:58Z	status:UNKNOWN	latency:6.331	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:9.765	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47404	target_addr:104.21.86.125:443
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:12.831	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43074	target_addr:172.64.147.104:443
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:12.540	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44976	target_addr:172.67.168.140:443
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:12.591	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47420	target_addr:104.21.86.125:443
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:57.660	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:60.784	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:75.725	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:28:58Z	status:FAILURE	latency:208.077	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:28:58Z	status:HEALTHY	latency:218.796	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:33:58Z	status:UNKNOWN	latency:6.519	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:9.744	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47732	target_addr:172.64.147.104:443
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:10.387	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56052	target_addr:104.21.26.208:443
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:11.264	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59366	target_addr:104.21.86.125:443
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:11.686	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59368	target_addr:104.21.86.125:443
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:58.170	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:74.185	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:98.130	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:33:58Z	status:FAILURE	latency:192.073	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:33:58Z	status:HEALTHY	latency:214.586	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:38:58Z	status:UNKNOWN	latency:8.106	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:12.740	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46008	target_addr:172.67.168.140:443
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:12.764	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51658	target_addr:104.18.40.152:443
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:12.354	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41628	target_addr:172.67.219.211:443
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:12.734	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41630	target_addr:172.67.219.211:443
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:58.761	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:67.679	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:68.958	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:38:58Z	status:HEALTHY	latency:100.944	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:38:58Z	status:FAILURE	latency:228.943	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:43:58Z	status:UNKNOWN	latency:7.234	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:10.251	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35588	target_addr:104.21.86.125:443
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:10.757	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53918	target_addr:172.64.147.104:443
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:11.537	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56600	target_addr:172.67.168.140:443
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:15.168	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35604	target_addr:104.21.86.125:443
time:2026-10-01T19:43:58Z	status:FAILURE	latency:224.218	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:224.640	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:529.423	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:724.208	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:43:58Z	status:HEALTHY	latency:843.930	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:48:58Z	status:UNKNOWN	latency:8.289	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:8.734	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40100	target_addr:172.64.147.104:443
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:9.634	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53902	target_addr:104.21.26.208:443
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:11.439	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50706	target_addr:172.67.219.211:443
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:11.091	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34946	target_addr:104.21.86.125:443
time:2026-10-01T19:48:58Z	status:FAILURE	latency:204.392	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:207.448	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:469.873	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:474.338	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:48:58Z	status:HEALTHY	latency:783.586	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:53:58Z	status:UNKNOWN	latency:9.066	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:9.867	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33038	target_addr:172.67.219.211:443
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:10.385	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47508	target_addr:104.18.40.152:443
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:10.148	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33048	target_addr:172.67.219.211:443
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:10.629	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60166	target_addr:104.21.26.208:443
time:2026-10-01T19:53:58Z	status:FAILURE	latency:25.901	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:268.087	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:777.748	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:815.192	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:53:58Z	status:HEALTHY	latency:827.335	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:58:59Z	status:UNKNOWN	latency:8.518	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:11.236	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40554	target_addr:172.67.219.211:443
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:12.523	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58062	target_addr:172.64.147.104:443
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:13.136	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58292	target_addr:104.21.86.125:443
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:14.623	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40026	target_addr:104.21.26.208:443
time:2026-10-01T19:58:59Z	status:FAILURE	latency:182.536	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:238.527	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:427.999	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:430.569	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T19:58:59Z	status:HEALTHY	latency:459.356	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:9.736	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47126	target_addr:172.67.219.211:443
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:11.991	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32960	target_addr:104.21.26.208:443
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:12.463	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46764	target_addr:104.18.40.152:443
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:23.381	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52308	target_addr:104.21.86.125:443
time:2026-10-01T20:03:59Z	status:UNKNOWN	latency:36.944	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:55.997	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:61.408	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:88.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:03:59Z	status:HEALTHY	latency:96.179	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:03:59Z	status:FAILURE	latency:199.556	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:08:59Z	status:UNKNOWN	latency:7.846	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:9.976	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47262	target_addr:172.64.147.104:443
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:10.655	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57290	target_addr:104.21.86.125:443
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:10.969	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57852	target_addr:104.21.26.208:443
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:12.029	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46130	target_addr:172.67.219.211:443
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:59.037	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:63.808	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:69.166	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:08:59Z	status:HEALTHY	latency:176.807	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:08:59Z	status:FAILURE	latency:193.975	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:13:59Z	status:UNKNOWN	latency:7.444	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:10.626	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49006	target_addr:104.18.40.152:443
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:10.822	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38066	target_addr:104.21.26.208:443
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:11.632	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33624	target_addr:172.67.219.211:443
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:23.229	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43074	target_addr:104.21.86.125:443
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:62.542	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:65.058	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:66.560	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:13:59Z	status:FAILURE	latency:183.561	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:13:59Z	status:HEALTHY	latency:217.288	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:18:59Z	status:UNKNOWN	latency:7.841	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:8.726	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39416	target_addr:104.18.40.152:443
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:9.658	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38250	target_addr:172.67.219.211:443
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:11.108	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38256	target_addr:172.67.219.211:443
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:23.594	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42488	target_addr:104.21.26.208:443
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:57.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:59.921	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:95.987	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:18:59Z	status:HEALTHY	latency:197.578	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:18:59Z	status:FAILURE	latency:221.207	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:23:59Z	status:UNKNOWN	latency:7.682	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:12.274	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37628	target_addr:172.67.219.211:443
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:13.057	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33190	target_addr:104.21.86.125:443
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:13.524	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56082	target_addr:104.18.40.152:443
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:13.444	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35842	target_addr:104.21.26.208:443
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:57.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:63.067	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:64.676	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:23:59Z	status:FAILURE	latency:200.324	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:23:59Z	status:HEALTHY	latency:229.668	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:28:59Z	status:UNKNOWN	latency:7.240	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:9.226	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47940	target_addr:104.21.86.125:443
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:11.385	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41344	target_addr:104.18.40.152:443
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:12.561	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57796	target_addr:172.67.168.140:443
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:20.941	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49228	target_addr:172.67.219.211:443
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:60.408	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:65.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:124.726	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:28:59Z	status:FAILURE	latency:169.601	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:28:59Z	status:HEALTHY	latency:425.625	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:33:59Z	status:UNKNOWN	latency:7.395	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:9.368	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36354	target_addr:104.18.40.152:443
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:10.121	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53514	target_addr:172.67.219.211:443
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:10.804	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60730	target_addr:104.21.26.208:443
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:10.817	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50174	target_addr:104.21.86.125:443
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:61.094	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:65.786	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:76.017	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:33:59Z	status:FAILURE	latency:194.524	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:33:59Z	status:HEALTHY	latency:208.070	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:38:59Z	status:UNKNOWN	latency:7.924	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:10.692	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53108	target_addr:172.67.219.211:443
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:11.104	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35876	target_addr:172.67.168.140:443
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:12.010	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36818	target_addr:172.64.147.104:443
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:15.660	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54586	target_addr:104.21.86.125:443
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:60.685	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:75.990	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:134.184	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:38:59Z	status:FAILURE	latency:207.325	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:38:59Z	status:HEALTHY	latency:243.948	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:8.716	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45374	target_addr:172.64.147.104:443
time:2026-10-01T20:43:59Z	status:UNKNOWN	latency:9.329	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:8.952	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43810	target_addr:104.21.86.125:443
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:10.872	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56792	target_addr:172.67.219.211:443
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:20.146	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41758	target_addr:172.67.168.140:443
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:53.873	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:58.832	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:85.114	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:43:59Z	status:FAILURE	latency:171.515	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:43:59Z	status:HEALTHY	latency:253.426	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:48:59Z	status:UNKNOWN	latency:6.190	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:11.867	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52320	target_addr:172.67.219.211:443
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:12.697	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45304	target_addr:104.21.26.208:443
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:13.548	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52334	target_addr:172.67.219.211:443
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:17.601	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37832	target_addr:172.64.147.104:443
time:2026-10-01T20:48:59Z	status:FAILURE	latency:27.286	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:57.435	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:61.670	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:72.567	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:48:59Z	status:HEALTHY	latency:205.977	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:10.168	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43500	target_addr:172.67.168.140:443
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:10.446	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59770	target_addr:172.64.147.104:443
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:11.239	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49984	target_addr:172.67.219.211:443
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:13.306	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49998	target_addr:172.67.219.211:443
time:2026-10-01T20:53:59Z	status:UNKNOWN	latency:19.223	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:57.658	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:59.673	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:60.123	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:53:59Z	status:FAILURE	latency:225.833	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:53:59Z	status:HEALTHY	latency:228.324	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:11.237	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39214	target_addr:104.18.40.152:443
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:11.086	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58942	target_addr:172.67.219.211:443
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:11.590	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35382	target_addr:104.21.86.125:443
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:12.171	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48018	target_addr:172.67.168.140:443
time:2026-10-01T20:58:59Z	status:UNKNOWN	latency:32.972	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:59.869	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:60.941	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:62.886	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T20:58:59Z	status:FAILURE	latency:196.572	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T20:58:59Z	status:HEALTHY	latency:218.160	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:03:59Z	status:UNKNOWN	latency:9.860	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:12.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46294	target_addr:104.21.86.125:443
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:13.000	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59824	target_addr:172.67.168.140:443
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:13.308	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56830	target_addr:172.67.219.211:443
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:15.324	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49008	target_addr:104.18.40.152:443
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:61.543	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:61.658	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:69.114	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:03:59Z	status:FAILURE	latency:202.188	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:03:59Z	status:HEALTHY	latency:221.151	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:08:59Z	status:UNKNOWN	latency:7.013	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:8.811	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37528	target_addr:172.64.147.104:443
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:10.682	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59542	target_addr:172.67.219.211:443
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:10.974	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36846	target_addr:104.21.86.125:443
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:11.354	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49776	target_addr:104.21.26.208:443
time:2026-10-01T21:08:59Z	status:FAILURE	latency:39.240	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:53.711	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:55.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:66.004	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:08:59Z	status:HEALTHY	latency:195.018	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:13:59Z	status:UNKNOWN	latency:7.424	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:9.197	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52208	target_addr:104.21.26.208:443
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:10.600	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42028	target_addr:104.21.86.125:443
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:10.597	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52696	target_addr:104.18.40.152:443
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:13.113	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42042	target_addr:104.21.86.125:443
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:54.679	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:55.622	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:66.729	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:13:59Z	status:FAILURE	latency:207.513	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:13:59Z	status:HEALTHY	latency:253.889	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:18:59Z	status:UNKNOWN	latency:6.692	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:8.989	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58980	target_addr:104.18.40.152:443
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:9.950	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47848	target_addr:104.21.26.208:443
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:10.026	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54176	target_addr:104.21.86.125:443
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:10.586	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46032	target_addr:172.67.219.211:443
time:2026-10-01T21:18:59Z	status:FAILURE	latency:22.481	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:56.150	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:59.630	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:59.591	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:18:59Z	status:HEALTHY	latency:247.584	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:10.599	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36332	target_addr:172.67.168.140:443
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:10.833	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53370	target_addr:172.67.219.211:443
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:11.768	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41960	target_addr:104.21.86.125:443
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:21.843	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34474	target_addr:172.64.147.104:443
time:2026-10-01T21:23:59Z	status:UNKNOWN	latency:22.858	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:50.813	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:59.617	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:83.076	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:23:59Z	status:FAILURE	latency:183.520	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:23:59Z	status:HEALTHY	latency:234.337	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:9.639	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44210	target_addr:104.18.40.152:443
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:11.536	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37930	target_addr:104.21.86.125:443
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:11.672	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54646	target_addr:172.67.168.140:443
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:12.358	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37942	target_addr:104.21.86.125:443
time:2026-10-01T21:28:59Z	status:FAILURE	latency:23.670	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:28:59Z	status:UNKNOWN	latency:56.019	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:60.807	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:61.614	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:79.460	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:28:59Z	status:HEALTHY	latency:269.564	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:33:59Z	status:UNKNOWN	latency:7.693	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:9.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35546	target_addr:172.67.168.140:443
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:10.428	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47740	target_addr:172.67.219.211:443
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:11.627	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34014	target_addr:104.21.86.125:443
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:12.383	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56678	target_addr:104.18.40.152:443
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:67.708	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:67.570	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:67.876	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:33:59Z	status:FAILURE	latency:206.679	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:33:59Z	status:HEALTHY	latency:318.989	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:38:59Z	status:UNKNOWN	latency:8.690	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:12.538	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50510	target_addr:172.64.147.104:443
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:12.402	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47602	target_addr:104.21.86.125:443
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:12.335	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48794	target_addr:172.67.219.211:443
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:12.774	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41974	target_addr:104.21.26.208:443
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:55.218	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:57.612	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:61.408	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:38:59Z	status:FAILURE	latency:205.257	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:38:59Z	status:HEALTHY	latency:231.423	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:11.616	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54962	target_addr:104.21.86.125:443
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:12.233	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40664	target_addr:104.18.40.152:443
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:12.339	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54966	target_addr:104.21.86.125:443
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:12.634	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45710	target_addr:172.67.168.140:443
time:2026-10-01T21:43:59Z	status:UNKNOWN	latency:13.493	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:57.016	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:68.397	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:84.700	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:43:59Z	status:HEALTHY	latency:193.916	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:43:59Z	status:FAILURE	latency:202.409	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:12.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59196	target_addr:172.67.219.211:443
time:2026-10-01T21:48:59Z	status:UNKNOWN	latency:13.375	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:21.917	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49088	target_addr:104.18.40.152:443
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:44.292	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51880	target_addr:104.21.26.208:443
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:61.894	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:81.919	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:83.479	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:132.668	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59202	target_addr:172.67.219.211:443
time:2026-10-01T21:48:59Z	status:FAILURE	latency:183.928	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:48:59Z	status:HEALTHY	latency:204.755	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:53:59Z	status:UNKNOWN	latency:6.475	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:11.137	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52254	target_addr:172.67.219.211:443
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:11.557	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59322	target_addr:104.21.26.208:443
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:11.996	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56088	target_addr:172.64.147.104:443
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:13.754	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52268	target_addr:172.67.219.211:443
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:67.007	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:74.509	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:84.923	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:53:59Z	status:FAILURE	latency:209.632	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:53:59Z	status:HEALTHY	latency:247.677	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:58:59Z	status:UNKNOWN	latency:6.107	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:8.778	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39532	target_addr:172.67.219.211:443
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:12.931	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49554	target_addr:172.64.147.104:443
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:23.976	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41096	target_addr:104.21.86.125:443
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:29.388	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47184	target_addr:104.21.26.208:443
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:59.957	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:68.955	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:77.867	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T21:58:59Z	status:FAILURE	latency:256.096	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T21:58:59Z	status:HEALTHY	latency:445.429	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:03:59Z	status:UNKNOWN	latency:7.567	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:10.578	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52436	target_addr:172.67.219.211:443
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:11.181	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60018	target_addr:104.18.40.152:443
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:10.851	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46320	target_addr:104.21.86.125:443
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:11.777	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55856	target_addr:172.67.168.140:443
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:55.250	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:78.064	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:80.618	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:03:59Z	status:FAILURE	latency:144.662	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:03:59Z	status:HEALTHY	latency:237.456	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:10.719	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43624	target_addr:172.67.168.140:443
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:11.294	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60214	target_addr:104.21.86.125:443
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:11.641	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60220	target_addr:104.21.86.125:443
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:15.908	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51734	target_addr:104.18.40.152:443
time:2026-10-01T22:08:59Z	status:FAILURE	latency:27.808	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:08:59Z	status:UNKNOWN	latency:55.082	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:60.670	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:63.058	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:86.975	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:08:59Z	status:HEALTHY	latency:215.626	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:9.276	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42708	target_addr:104.21.86.125:443
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:9.940	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43336	target_addr:172.67.168.140:443
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:10.946	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42402	target_addr:172.67.219.211:443
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:14.021	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42052	target_addr:172.64.147.104:443
time:2026-10-01T22:13:59Z	status:UNKNOWN	latency:15.396	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:62.674	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:68.734	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:85.266	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:13:59Z	status:HEALTHY	latency:209.092	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:13:59Z	status:FAILURE	latency:227.596	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:18:59Z	status:UNKNOWN	latency:7.977	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:9.850	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54416	target_addr:172.67.168.140:443
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:10.404	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60186	target_addr:104.18.40.152:443
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:13.519	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50846	target_addr:172.67.219.211:443
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:23.520	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50862	target_addr:172.67.219.211:443
time:2026-10-01T22:18:59Z	status:FAILURE	latency:24.987	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:56.766	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:85.884	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:101.685	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:18:59Z	status:HEALTHY	latency:174.575	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:23:59Z	status:UNKNOWN	latency:6.816	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:8.888	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52682	target_addr:104.18.40.152:443
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:10.624	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48810	target_addr:172.67.168.140:443
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:12.100	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38078	target_addr:104.21.86.125:443
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:21.196	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38092	target_addr:104.21.86.125:443
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:57.310	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:58.918	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:59.309	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:23:59Z	status:FAILURE	latency:212.719	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:23:59Z	status:HEALTHY	latency:277.160	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:28:59Z	status:UNKNOWN	latency:8.574	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:11.783	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52360	target_addr:172.67.219.211:443
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:13.281	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50054	target_addr:172.67.168.140:443
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:13.766	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41262	target_addr:104.21.86.125:443
time:2026-10-01T22:28:59Z	status:FAILURE	latency:41.151	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:51.862	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58354	target_addr:104.18.40.152:443
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:55.361	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:57.813	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:58.370	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:28:59Z	status:HEALTHY	latency:266.652	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:33:59Z	status:UNKNOWN	latency:74.278	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:137.940	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44804	target_addr:104.21.26.208:443
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:139.598	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37526	target_addr:104.21.86.125:443
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:140.731	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37540	target_addr:104.21.86.125:443
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:143.713	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47114	target_addr:104.18.40.152:443
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:320.593	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:339.532	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:342.156	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:33:59Z	status:FAILURE	latency:515.097	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:33:59Z	status:HEALTHY	latency:705.634	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:38:59Z	status:UNKNOWN	latency:7.751	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:10.087	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47196	target_addr:104.21.26.208:443
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:9.786	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55766	target_addr:104.21.86.125:443
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:12.389	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58956	target_addr:104.18.40.152:443
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:12.524	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55772	target_addr:104.21.86.125:443
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:55.810	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:67.702	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:85.462	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:38:59Z	status:HEALTHY	latency:213.763	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:38:59Z	status:FAILURE	latency:265.603	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:43:59Z	status:UNKNOWN	latency:8.675	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:12.609	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60178	target_addr:172.67.219.211:443
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:13.033	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39404	target_addr:104.21.26.208:443
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:13.151	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42234	target_addr:104.18.40.152:443
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:12.983	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60162	target_addr:172.67.219.211:443
time:2026-10-01T22:43:59Z	status:FAILURE	latency:28.206	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:58.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:70.223	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:80.225	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:43:59Z	status:HEALTHY	latency:178.568	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:10.365	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55908	target_addr:104.21.86.125:443
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:11.113	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46500	target_addr:104.21.26.208:443
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:13.415	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60836	target_addr:172.67.219.211:443
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:29.666	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55888	target_addr:172.64.147.104:443
time:2026-10-01T22:48:59Z	status:UNKNOWN	latency:33.305	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:67.954	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:69.237	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:75.475	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:48:59Z	status:HEALTHY	latency:195.892	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:48:59Z	status:FAILURE	latency:215.504	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:10.236	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39256	target_addr:104.21.26.208:443
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:10.393	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49582	target_addr:172.67.219.211:443
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:12.274	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46886	target_addr:104.21.86.125:443
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:16.356	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43064	target_addr:104.18.40.152:443
time:2026-10-01T22:53:59Z	status:UNKNOWN	latency:16.523	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:56.936	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:57.643	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:65.708	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:53:59Z	status:FAILURE	latency:229.857	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:53:59Z	status:HEALTHY	latency:1056.061	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:58:59Z	status:UNKNOWN	latency:7.232	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:9.954	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45234	target_addr:172.67.219.211:443
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:11.028	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43676	target_addr:104.18.40.152:443
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:11.485	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52346	target_addr:172.67.168.140:443
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:12.894	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38406	target_addr:104.21.86.125:443
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:61.336	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:70.365	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:211.756	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T22:58:59Z	status:FAILURE	latency:227.193	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T22:58:59Z	status:HEALTHY	latency:274.887	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:17.819	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51382	target_addr:172.67.168.140:443
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:18.416	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59532	target_addr:104.18.40.152:443
time:2026-10-01T23:03:59Z	status:UNKNOWN	latency:22.335	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:26.196	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40610	target_addr:104.21.86.125:443
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:60.944	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:62.896	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:66.649	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:03:59Z	status:FAILURE	latency:225.817	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:265.945	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36144	target_addr:172.67.219.211:443
time:2026-10-01T23:03:59Z	status:HEALTHY	latency:491.419	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:08:59Z	status:UNKNOWN	latency:6.979	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:11.322	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47294	target_addr:104.21.26.208:443
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:11.036	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51460	target_addr:104.18.40.152:443
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:11.144	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44368	target_addr:172.67.219.211:443
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:20.676	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53356	target_addr:104.21.86.125:443
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:70.852	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:73.592	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:85.841	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:08:59Z	status:FAILURE	latency:204.711	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:08:59Z	status:HEALTHY	latency:216.728	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:13:59Z	status:UNKNOWN	latency:7.344	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:9.161	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47208	target_addr:172.67.219.211:443
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:10.132	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47498	target_addr:172.64.147.104:443
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:10.650	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37866	target_addr:104.21.26.208:443
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:12.119	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47210	target_addr:172.67.219.211:443
time:2026-10-01T23:13:59Z	status:FAILURE	latency:29.197	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:56.428	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:56.770	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:67.450	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:13:59Z	status:HEALTHY	latency:265.051	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:18:59Z	status:UNKNOWN	latency:8.335	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:9.538	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44958	target_addr:172.67.219.211:443
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:11.110	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53204	target_addr:104.21.26.208:443
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:12.885	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41618	target_addr:104.18.40.152:443
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:19.782	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49846	target_addr:104.21.86.125:443
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:59.152	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:60.574	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:64.992	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:18:59Z	status:FAILURE	latency:209.607	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:18:59Z	status:HEALTHY	latency:244.748	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:23:59Z	status:UNKNOWN	latency:8.640	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:11.493	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52524	target_addr:172.64.147.104:443
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:12.033	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40316	target_addr:172.67.168.140:443
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:12.640	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38470	target_addr:104.21.86.125:443
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:16.027	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57746	target_addr:172.67.219.211:443
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:56.329	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:60.160	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:62.746	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:23:59Z	status:FAILURE	latency:208.568	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:23:59Z	status:HEALTHY	latency:252.401	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:10.328	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49598	target_addr:104.18.40.152:443
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:11.372	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41710	target_addr:172.67.219.211:443
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:11.679	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55804	target_addr:104.21.26.208:443
time:2026-10-01T23:28:59Z	status:UNKNOWN	latency:18.500	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:27.421	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41718	target_addr:172.67.219.211:443
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:53.512	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:54.967	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:75.326	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:28:59Z	status:FAILURE	latency:183.098	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:28:59Z	status:HEALTHY	latency:228.789	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:8.121	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37970	target_addr:104.18.40.152:443
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:9.255	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47076	target_addr:172.67.168.140:443
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:10.119	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49708	target_addr:172.67.219.211:443
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:10.571	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39616	target_addr:104.21.86.125:443
time:2026-10-01T23:33:59Z	status:FAILURE	latency:22.687	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:33:59Z	status:UNKNOWN	latency:71.253	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:211.806	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:433.774	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:438.545	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:33:59Z	status:HEALTHY	latency:502.844	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:38:59Z	status:UNKNOWN	latency:8.468	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:11.748	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47252	target_addr:172.67.168.140:443
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:11.800	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53042	target_addr:104.21.86.125:443
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:12.534	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53048	target_addr:104.21.86.125:443
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:14.426	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50654	target_addr:104.18.40.152:443
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:225.259	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:38:59Z	status:FAILURE	latency:227.636	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:688.024	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:734.550	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:38:59Z	status:HEALTHY	latency:783.044	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:43:59Z	status:UNKNOWN	latency:7.091	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:10.563	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46824	target_addr:104.18.40.152:443
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:10.364	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52290	target_addr:172.67.168.140:443
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:11.570	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39428	target_addr:172.67.219.211:443
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:12.994	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45376	target_addr:104.21.86.125:443
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:196.075	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:43:59Z	status:FAILURE	latency:321.021	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:525.722	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:724.452	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:43:59Z	status:HEALTHY	latency:736.723	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:48:59Z	status:UNKNOWN	latency:6.542	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:11.096	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35170	target_addr:172.64.147.104:443
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:10.800	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35984	target_addr:172.67.219.211:443
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:35.706	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52986	target_addr:104.21.26.208:443
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:39.266	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36172	target_addr:104.21.86.125:443
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:57.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:63.589	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:88.123	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:48:59Z	status:FAILURE	latency:201.283	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:48:59Z	status:HEALTHY	latency:232.329	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:53:59Z	status:UNKNOWN	latency:7.087	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:9.906	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60680	target_addr:172.67.168.140:443
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:12.696	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52646	target_addr:172.67.219.211:443
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:13.659	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52660	target_addr:172.67.219.211:443
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:14.613	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57268	target_addr:104.18.40.152:443
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:57.245	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:60.094	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:67.446	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:53:59Z	status:FAILURE	latency:209.286	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-01T23:53:59Z	status:HEALTHY	latency:292.756	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:58:59Z	status:UNKNOWN	latency:7.909	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:10.780	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43212	target_addr:172.64.147.104:443
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:11.978	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59996	target_addr:104.21.26.208:443
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:12.111	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42134	target_addr:104.21.86.125:443
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:12.487	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56380	target_addr:172.67.219.211:443
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:64.235	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:66.298	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:67.844	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:58:59Z	status:HEALTHY	latency:117.050	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-01T23:58:59Z	status:FAILURE	latency:202.634	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:03:59Z	status:UNKNOWN	latency:9.724	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:12.115	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41044	target_addr:104.21.86.125:443
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:12.694	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41052	target_addr:104.21.86.125:443
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:15.186	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37574	target_addr:172.64.147.104:443
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:28.304	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41350	target_addr:172.67.168.140:443
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:55.638	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:63.202	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:88.775	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:03:59Z	status:FAILURE	latency:228.331	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:03:59Z	status:HEALTHY	latency:1574.731	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:08:59Z	status:UNKNOWN	latency:8.086	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:9.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37896	target_addr:104.21.86.125:443
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:11.814	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46128	target_addr:172.67.219.211:443
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:13.079	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50960	target_addr:104.21.26.208:443
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:30.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40996	target_addr:104.18.40.152:443
time:2026-10-02T00:08:59Z	status:FAILURE	latency:42.283	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:61.125	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:68.367	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:69.984	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:08:59Z	status:HEALTHY	latency:229.621	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:10.744	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35106	target_addr:172.64.147.104:443
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:11.946	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50346	target_addr:172.67.219.211:443
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:12.897	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50556	target_addr:104.21.86.125:443
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:12.926	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55936	target_addr:104.21.26.208:443
time:2026-10-02T00:13:59Z	status:UNKNOWN	latency:32.146	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:13:59Z	status:FAILURE	latency:33.726	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:61.337	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:61.547	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:64.915	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:13:59Z	status:HEALTHY	latency:665.381	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:18:59Z	status:UNKNOWN	latency:8.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:10.160	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51020	target_addr:104.21.86.125:443
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:10.409	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45290	target_addr:104.18.40.152:443
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:10.607	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51140	target_addr:172.67.168.140:443
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:12.057	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51036	target_addr:104.21.86.125:443
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:64.524	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:69.342	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:18:59Z	status:FAILURE	latency:195.973	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:312.214	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:18:59Z	status:HEALTHY	latency:848.883	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:23:59Z	status:UNKNOWN	latency:7.014	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:8.508	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42186	target_addr:104.18.40.152:443
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:9.840	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60636	target_addr:104.21.26.208:443
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:10.795	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:172.67.219.211:443
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:11.702	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33750	target_addr:172.67.219.211:443
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:54.997	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:57.070	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:60.485	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:23:59Z	status:FAILURE	latency:211.198	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:23:59Z	status:HEALTHY	latency:213.658	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:28:59Z	status:UNKNOWN	latency:8.042	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:8.885	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59852	target_addr:104.21.26.208:443
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:8.873	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45696	target_addr:172.64.147.104:443
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:10.367	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55562	target_addr:104.21.86.125:443
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:11.054	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55572	target_addr:104.21.86.125:443
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:63.344	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:69.286	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:93.201	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:28:59Z	status:HEALTHY	latency:199.504	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:28:59Z	status:FAILURE	latency:254.190	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:11.617	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33166	target_addr:172.64.147.104:443
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:11.158	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59542	target_addr:104.21.86.125:443
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:12.880	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53988	target_addr:172.67.219.211:443
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:31.286	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33708	target_addr:172.67.168.140:443
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:54.387	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:33:59Z	status:UNKNOWN	latency:58.217	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:61.519	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:77.398	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:33:59Z	status:FAILURE	latency:200.990	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:33:59Z	status:HEALTHY	latency:270.483	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:39:00Z	status:UNKNOWN	latency:8.458	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:10.466	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46816	target_addr:172.67.219.211:443
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:11.747	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40786	target_addr:104.21.26.208:443
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:11.626	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37984	target_addr:172.64.147.104:443
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:12.895	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46828	target_addr:172.67.219.211:443
time:2026-10-02T00:39:00Z	status:FAILURE	latency:26.085	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:57.078	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:83.570	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:201.294	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:39:00Z	status:HEALTHY	latency:253.582	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:44:00Z	status:UNKNOWN	latency:7.134	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:10.668	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35126	target_addr:172.67.168.140:443
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:14.904	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53048	target_addr:104.21.86.125:443
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:17.019	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53060	target_addr:104.21.86.125:443
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:20.608	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51186	target_addr:172.64.147.104:443
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:60.418	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:64.171	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:72.037	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:44:00Z	status:FAILURE	latency:193.813	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:44:00Z	status:HEALTHY	latency:220.449	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:49:00Z	status:UNKNOWN	latency:7.620	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:9.840	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45212	target_addr:172.67.168.140:443
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:11.023	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42490	target_addr:172.64.147.104:443
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:12.126	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32944	target_addr:104.21.86.125:443
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:14.386	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41274	target_addr:172.67.219.211:443
time:2026-10-02T00:49:00Z	status:FAILURE	latency:213.688	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:264.692	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:441.963	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:449.279	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:49:00Z	status:HEALTHY	latency:859.559	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:54:00Z	status:UNKNOWN	latency:7.738	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:9.799	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40706	target_addr:172.67.219.211:443
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:11.073	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51452	target_addr:104.21.86.125:443
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:11.823	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35736	target_addr:104.18.40.152:443
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:12.043	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43342	target_addr:172.67.168.140:443
time:2026-10-02T00:54:00Z	status:FAILURE	latency:24.805	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:225.365	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:899.677	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:1080.347	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:54:00Z	status:HEALTHY	latency:1753.534	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:59:00Z	status:UNKNOWN	latency:8.169	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:11.545	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44206	target_addr:172.67.168.140:443
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:13.427	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42758	target_addr:104.18.40.152:443
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:13.427	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51028	target_addr:172.67.219.211:443
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:15.171	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51032	target_addr:172.67.219.211:443
time:2026-10-02T00:59:00Z	status:FAILURE	latency:192.354	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:251.409	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:440.158	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:462.064	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T00:59:00Z	status:HEALTHY	latency:669.293	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:04:00Z	status:UNKNOWN	latency:11.698	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:16.001	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34822	target_addr:172.67.168.140:443
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:15.974	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49442	target_addr:104.21.86.125:443
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:31.645	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33298	target_addr:172.64.147.104:443
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:56.130	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49446	target_addr:104.21.86.125:443
time:2026-10-02T01:04:00Z	status:FAILURE	latency:246.169	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:248.961	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:445.702	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:446.736	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:04:00Z	status:HEALTHY	latency:450.270	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:8.692	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51004	target_addr:104.21.86.125:443
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:10.835	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54230	target_addr:172.67.219.211:443
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:11.098	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54728	target_addr:172.67.168.140:443
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:13.244	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37944	target_addr:104.18.40.152:443
time:2026-10-02T01:09:00Z	status:UNKNOWN	latency:34.825	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:09:00Z	status:FAILURE	latency:181.556	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:228.667	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:511.939	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:815.460	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:09:00Z	status:HEALTHY	latency:953.449	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:11.262	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35764	target_addr:172.64.147.104:443
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:11.500	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46708	target_addr:104.21.86.125:443
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:11.403	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60738	target_addr:104.21.26.208:443
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:11.504	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46706	target_addr:104.21.86.125:443
time:2026-10-02T01:14:00Z	status:UNKNOWN	latency:57.104	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:14:00Z	status:FAILURE	latency:213.534	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:254.398	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:456.946	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:481.146	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:14:00Z	status:HEALTHY	latency:496.662	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:19:00Z	status:UNKNOWN	latency:8.452	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:12.461	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53132	target_addr:172.64.147.104:443
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:13.344	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43562	target_addr:104.21.86.125:443
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:15.943	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45244	target_addr:104.21.26.208:443
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:24.645	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51604	target_addr:172.67.219.211:443
time:2026-10-02T01:19:00Z	status:FAILURE	latency:29.928	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:254.555	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:483.365	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:517.005	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:19:00Z	status:HEALTHY	latency:833.369	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:24:00Z	status:UNKNOWN	latency:8.501	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:10.071	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50906	target_addr:172.67.219.211:443
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:12.617	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53804	target_addr:104.18.40.152:443
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:12.211	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38516	target_addr:104.21.86.125:443
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:12.377	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54556	target_addr:104.21.26.208:443
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:62.096	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:63.443	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:73.510	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:24:00Z	status:HEALTHY	latency:210.444	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:24:00Z	status:FAILURE	latency:258.471	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:29:00Z	status:UNKNOWN	latency:9.473	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:9.778	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46498	target_addr:172.67.168.140:443
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:10.664	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46282	target_addr:172.67.219.211:443
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:10.844	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40104	target_addr:104.21.86.125:443
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:11.761	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38318	target_addr:172.64.147.104:443
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:64.069	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:83.006	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:83.830	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:29:00Z	status:FAILURE	latency:192.658	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:29:00Z	status:HEALTHY	latency:264.442	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:13.843	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44432	target_addr:172.67.219.211:443
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:13.361	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44434	target_addr:172.67.219.211:443
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:15.575	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51944	target_addr:172.64.147.104:443
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:26.637	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51746	target_addr:172.67.168.140:443
time:2026-10-02T01:34:00Z	status:UNKNOWN	latency:36.170	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:226.145	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:34:00Z	status:FAILURE	latency:229.316	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:624.444	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:814.610	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:34:00Z	status:HEALTHY	latency:1709.857	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:39:00Z	status:UNKNOWN	latency:8.892	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:12.639	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34184	target_addr:104.18.40.152:443
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:12.649	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58574	target_addr:172.67.219.211:443
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:13.493	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59438	target_addr:172.67.168.140:443
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:16.408	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58584	target_addr:172.67.219.211:443
time:2026-10-02T01:39:00Z	status:FAILURE	latency:27.943	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:277.122	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:463.868	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:464.768	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:39:00Z	status:HEALTHY	latency:468.561	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:44:00Z	status:UNKNOWN	latency:7.169	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:8.867	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35312	target_addr:172.64.147.104:443
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:10.905	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35170	target_addr:172.67.219.211:443
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:11.608	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44702	target_addr:104.21.26.208:443
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:14.127	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40932	target_addr:104.21.86.125:443
time:2026-10-02T01:44:00Z	status:FAILURE	latency:24.154	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:261.798	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:557.487	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:715.777	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:44:00Z	status:HEALTHY	latency:799.899	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:49:00Z	status:UNKNOWN	latency:8.680	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:8.909	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48862	target_addr:172.67.219.211:443
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:9.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42400	target_addr:104.18.40.152:443
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:16.056	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39458	target_addr:104.21.26.208:443
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:55.782	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48870	target_addr:172.67.219.211:443
time:2026-10-02T01:49:00Z	status:FAILURE	latency:183.914	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:320.237	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:436.603	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:440.352	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:49:00Z	status:HEALTHY	latency:468.906	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:54:00Z	status:UNKNOWN	latency:9.045	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:11.634	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59308	target_addr:172.64.147.104:443
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:11.651	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48720	target_addr:104.21.86.125:443
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:13.663	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38852	target_addr:172.67.219.211:443
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:16.903	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42022	target_addr:172.67.168.140:443
time:2026-10-02T01:54:00Z	status:FAILURE	latency:226.100	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:238.844	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:424.081	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:445.985	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:54:00Z	status:HEALTHY	latency:459.844	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:59:00Z	status:UNKNOWN	latency:6.810	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:9.982	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41170	target_addr:104.21.86.125:443
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:10.978	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44066	target_addr:104.21.26.208:443
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:11.068	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56734	target_addr:172.67.219.211:443
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:12.574	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57808	target_addr:172.64.147.104:443
time:2026-10-02T01:59:00Z	status:FAILURE	latency:198.452	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:214.065	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:486.571	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:487.366	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T01:59:00Z	status:HEALTHY	latency:517.640	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:04:00Z	status:UNKNOWN	latency:8.442	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:11.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59142	target_addr:172.67.168.140:443
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:12.061	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49734	target_addr:172.64.147.104:443
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:12.364	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47458	target_addr:172.67.219.211:443
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:13.372	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47466	target_addr:172.67.219.211:443
time:2026-10-02T02:04:00Z	status:FAILURE	latency:222.760	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:269.940	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:482.779	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:581.808	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:04:00Z	status:HEALTHY	latency:714.439	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:9.206	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41088	target_addr:172.67.219.211:443
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:10.539	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50910	target_addr:172.67.168.140:443
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:15.757	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35836	target_addr:172.64.147.104:443
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:32.575	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41094	target_addr:172.67.219.211:443
time:2026-10-02T02:09:00Z	status:UNKNOWN	latency:32.874	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:09:00Z	status:FAILURE	latency:176.036	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:279.860	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:481.614	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:527.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:09:00Z	status:HEALTHY	latency:541.128	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:12.607	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36608	target_addr:104.18.40.152:443
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:12.967	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41554	target_addr:104.21.26.208:443
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:12.778	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40278	target_addr:104.21.86.125:443
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:16.886	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40288	target_addr:104.21.86.125:443
time:2026-10-02T02:14:00Z	status:UNKNOWN	latency:56.716	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:14:00Z	status:FAILURE	latency:190.367	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:243.512	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:486.623	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:496.095	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:14:00Z	status:HEALTHY	latency:760.101	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:19:00Z	status:UNKNOWN	latency:9.087	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:11.754	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49262	target_addr:104.21.86.125:443
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:13.154	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41600	target_addr:172.67.219.211:443
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:13.736	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45860	target_addr:172.64.147.104:443
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:13.571	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35186	target_addr:104.21.26.208:443
time:2026-10-02T02:19:00Z	status:FAILURE	latency:42.048	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:61.130	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:79.293	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:149.419	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:19:00Z	status:HEALTHY	latency:322.889	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:24:00Z	status:UNKNOWN	latency:8.260	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:12.038	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52800	target_addr:172.67.219.211:443
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:12.373	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38234	target_addr:104.21.86.125:443
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:12.540	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56732	target_addr:104.21.26.208:443
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:14.254	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47710	target_addr:172.64.147.104:443
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:68.679	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:69.797	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:74.315	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:24:00Z	status:FAILURE	latency:198.061	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:24:00Z	status:HEALTHY	latency:320.477	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:29:00Z	status:UNKNOWN	latency:7.247	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:8.210	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42616	target_addr:104.18.40.152:443
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:9.610	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57044	target_addr:104.21.86.125:443
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:11.916	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58550	target_addr:172.67.219.211:443
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:12.086	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58452	target_addr:172.67.168.140:443
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:56.484	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:63.653	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:70.614	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:29:00Z	status:FAILURE	latency:197.308	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:29:00Z	status:HEALTHY	latency:199.052	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:34:00Z	status:UNKNOWN	latency:7.048	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:11.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56898	target_addr:172.67.168.140:443
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:12.813	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44070	target_addr:104.21.86.125:443
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:14.971	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54134	target_addr:172.64.147.104:443
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:24.601	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36462	target_addr:172.67.219.211:443
time:2026-10-02T02:34:00Z	status:FAILURE	latency:47.991	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:216.535	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:477.176	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:495.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:34:00Z	status:HEALTHY	latency:651.753	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:10.262	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50152	target_addr:104.18.40.152:443
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:10.758	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34710	target_addr:172.67.219.211:443
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:11.280	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48704	target_addr:172.67.168.140:443
time:2026-10-02T02:39:00Z	status:UNKNOWN	latency:16.625	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:21.995	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34694	target_addr:172.67.219.211:443
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:123.881	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:39:00Z	status:FAILURE	latency:202.852	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:456.679	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:506.797	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:39:00Z	status:HEALTHY	latency:528.162	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:44:00Z	status:UNKNOWN	latency:6.437	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:9.752	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36654	target_addr:172.64.147.104:443
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:10.817	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45048	target_addr:172.67.219.211:443
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:11.785	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45050	target_addr:172.67.219.211:443
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:20.966	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55800	target_addr:172.67.168.140:443
time:2026-10-02T02:44:00Z	status:FAILURE	latency:194.090	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:244.196	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:557.655	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:565.501	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:44:00Z	status:HEALTHY	latency:576.910	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:49:00Z	status:UNKNOWN	latency:7.367	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:9.836	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38920	target_addr:172.67.168.140:443
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:10.623	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52326	target_addr:172.64.147.104:443
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:11.446	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38676	target_addr:104.21.86.125:443
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:12.275	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38686	target_addr:104.21.86.125:443
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:194.865	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:49:00Z	status:FAILURE	latency:225.855	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:459.451	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:510.178	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:49:00Z	status:HEALTHY	latency:533.299	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:54:00Z	status:UNKNOWN	latency:8.848	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:12.069	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42298	target_addr:104.18.40.152:443
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:12.597	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37226	target_addr:104.21.86.125:443
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:19.485	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37228	target_addr:104.21.86.125:443
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:21.585	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53102	target_addr:104.21.26.208:443
time:2026-10-02T02:54:00Z	status:FAILURE	latency:190.850	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:232.234	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:529.412	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:532.789	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:54:00Z	status:HEALTHY	latency:546.150	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:59:00Z	status:UNKNOWN	latency:10.421	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:10.649	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52448	target_addr:172.64.147.104:443
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:11.010	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34832	target_addr:172.67.219.211:443
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:13.275	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34838	target_addr:172.67.219.211:443
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:14.219	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46366	target_addr:172.67.168.140:443
time:2026-10-02T02:59:00Z	status:FAILURE	latency:25.854	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:237.345	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:465.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:764.559	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T02:59:00Z	status:HEALTHY	latency:772.902	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:04:00Z	status:UNKNOWN	latency:7.780	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:10.247	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43546	target_addr:172.67.168.140:443
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:11.064	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51456	target_addr:104.21.86.125:443
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:11.299	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51466	target_addr:104.21.86.125:443
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:43.137	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35796	target_addr:104.18.40.152:443
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:253.486	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:04:00Z	status:FAILURE	latency:342.844	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:437.390	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:491.827	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:04:00Z	status:HEALTHY	latency:531.683	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:09:00Z	status:UNKNOWN	latency:8.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:14.392	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56858	target_addr:172.64.147.104:443
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:14.281	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60278	target_addr:104.21.86.125:443
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:14.231	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60272	target_addr:104.21.86.125:443
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:15.709	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39178	target_addr:172.67.168.140:443
time:2026-10-02T03:09:00Z	status:FAILURE	latency:32.305	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:270.809	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:437.584	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:441.706	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:09:00Z	status:HEALTHY	latency:453.546	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:14:00Z	status:UNKNOWN	latency:9.074	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:9.814	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57362	target_addr:104.21.86.125:443
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:11.579	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40276	target_addr:172.67.168.140:443
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:11.560	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52134	target_addr:172.67.219.211:443
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:15.244	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53420	target_addr:104.18.40.152:443
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:289.877	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:14:00Z	status:FAILURE	latency:351.296	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:488.643	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:516.966	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:14:00Z	status:HEALTHY	latency:541.042	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:19:00Z	status:UNKNOWN	latency:7.648	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:11.818	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39334	target_addr:172.67.219.211:443
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:13.337	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42948	target_addr:104.18.40.152:443
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:13.299	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39348	target_addr:172.67.219.211:443
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:21.138	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41052	target_addr:104.21.26.208:443
time:2026-10-02T03:19:00Z	status:FAILURE	latency:198.417	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:244.241	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:500.985	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:532.070	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:19:00Z	status:HEALTHY	latency:699.458	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:10.683	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48718	target_addr:104.21.26.208:443
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:11.506	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32952	target_addr:104.21.86.125:443
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:11.858	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45340	target_addr:172.67.219.211:443
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:13.680	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55866	target_addr:172.64.147.104:443
time:2026-10-02T03:24:00Z	status:UNKNOWN	latency:38.640	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:24:00Z	status:FAILURE	latency:205.690	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:270.049	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:436.538	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:441.729	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:24:00Z	status:HEALTHY	latency:1448.904	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:29:00Z	status:UNKNOWN	latency:6.903	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:11.791	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38262	target_addr:172.67.168.140:443
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:12.255	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41292	target_addr:172.67.219.211:443
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:12.740	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36422	target_addr:104.18.40.152:443
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:15.490	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41302	target_addr:172.67.219.211:443
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:256.428	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:29:00Z	status:FAILURE	latency:353.290	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:455.700	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:458.243	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:29:00Z	status:HEALTHY	latency:909.851	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:34:00Z	status:UNKNOWN	latency:8.674	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:11.980	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42850	target_addr:104.21.86.125:443
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:13.009	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58394	target_addr:172.67.219.211:443
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:15.561	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56618	target_addr:104.18.40.152:443
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:22.330	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48612	target_addr:104.21.26.208:443
time:2026-10-02T03:34:00Z	status:FAILURE	latency:35.157	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:110.854	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:448.473	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:686.176	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:34:00Z	status:HEALTHY	latency:745.504	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:39:00Z	status:UNKNOWN	latency:8.970	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:12.994	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48222	target_addr:172.67.219.211:443
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:13.632	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48198	target_addr:172.64.147.104:443
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:14.905	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52060	target_addr:172.67.168.140:443
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:19.246	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48226	target_addr:172.67.219.211:443
time:2026-10-02T03:39:00Z	status:FAILURE	latency:171.938	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:222.956	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:582.592	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:799.127	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:39:00Z	status:HEALTHY	latency:852.771	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:44:01Z	status:UNKNOWN	latency:9.888	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:12.629	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49580	target_addr:172.64.147.104:443
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:12.658	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46174	target_addr:172.67.219.211:443
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:13.169	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46188	target_addr:172.67.219.211:443
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:21.525	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33658	target_addr:172.67.168.140:443
time:2026-10-02T03:44:01Z	status:FAILURE	latency:184.240	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:247.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:431.796	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:441.989	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:44:01Z	status:HEALTHY	latency:462.603	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:49:01Z	status:UNKNOWN	latency:7.617	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:11.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58106	target_addr:172.67.168.140:443
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:12.027	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36456	target_addr:104.21.86.125:443
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:13.284	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36472	target_addr:104.21.86.125:443
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:16.038	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46328	target_addr:172.64.147.104:443
time:2026-10-02T03:49:01Z	status:FAILURE	latency:204.697	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:256.060	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:432.340	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:457.320	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:49:01Z	status:HEALTHY	latency:646.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:54:01Z	status:UNKNOWN	latency:6.744	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:9.447	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51456	target_addr:172.67.168.140:443
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:11.963	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36662	target_addr:172.64.147.104:443
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:11.654	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48270	target_addr:104.21.86.125:443
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:18.566	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47672	target_addr:172.67.219.211:443
time:2026-10-02T03:54:01Z	status:FAILURE	latency:207.866	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:231.549	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:418.679	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:488.119	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:54:01Z	status:HEALTHY	latency:752.624	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:59:01Z	status:UNKNOWN	latency:6.630	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:12.106	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52334	target_addr:172.67.219.211:443
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:11.919	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52350	target_addr:172.67.219.211:443
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:14.945	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32904	target_addr:104.21.26.208:443
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:15.070	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46676	target_addr:172.64.147.104:443
time:2026-10-02T03:59:01Z	status:FAILURE	latency:217.792	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:262.839	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:520.315	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:534.142	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T03:59:01Z	status:HEALTHY	latency:818.194	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:12.844	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39304	target_addr:172.67.219.211:443
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:14.599	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54986	target_addr:104.18.40.152:443
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:16.387	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39308	target_addr:172.67.219.211:443
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:17.617	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45402	target_addr:104.21.26.208:443
time:2026-10-02T04:04:01Z	status:UNKNOWN	latency:68.155	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:04:01Z	status:FAILURE	latency:143.375	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:469.776	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:534.566	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:537.358	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:04:01Z	status:HEALTHY	latency:542.229	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:09:01Z	status:UNKNOWN	latency:8.984	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:10.134	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33010	target_addr:104.21.86.125:443
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:15.142	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33014	target_addr:104.21.86.125:443
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:21.831	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51612	target_addr:104.21.26.208:443
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:27.897	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52928	target_addr:104.18.40.152:443
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:223.009	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:09:01Z	status:FAILURE	latency:227.877	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:465.012	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:512.052	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:09:01Z	status:HEALTHY	latency:820.167	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:14:01Z	status:UNKNOWN	latency:7.910	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:10.252	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50100	target_addr:172.67.219.211:443
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:12.342	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48792	target_addr:104.21.86.125:443
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:13.129	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55554	target_addr:104.21.26.208:443
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:14.043	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48952	target_addr:172.64.147.104:443
time:2026-10-02T04:14:01Z	status:FAILURE	latency:196.260	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:251.056	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:430.362	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:436.401	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:14:01Z	status:HEALTHY	latency:456.715	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:19:01Z	status:UNKNOWN	latency:9.823	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:13.347	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51356	target_addr:172.67.219.211:443
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:13.788	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51344	target_addr:172.67.219.211:443
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:17.948	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42782	target_addr:104.21.26.208:443
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:24.104	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42816	target_addr:104.18.40.152:443
time:2026-10-02T04:19:01Z	status:FAILURE	latency:36.089	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:301.987	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:501.776	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:520.799	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:19:01Z	status:HEALTHY	latency:543.103	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:24:01Z	status:UNKNOWN	latency:9.022	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:10.231	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37328	target_addr:104.21.86.125:443
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:10.677	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53760	target_addr:104.18.40.152:443
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:11.225	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53186	target_addr:104.21.26.208:443
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:26.655	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37020	target_addr:172.67.219.211:443
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:105.291	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:24:01Z	status:FAILURE	latency:230.959	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:525.152	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:525.129	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:24:01Z	status:HEALTHY	latency:540.710	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:29:01Z	status:UNKNOWN	latency:8.559	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:10.804	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47848	target_addr:172.64.147.104:443
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:11.958	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46872	target_addr:172.67.168.140:443
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:11.669	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40496	target_addr:104.21.86.125:443
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:12.012	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41962	target_addr:172.67.219.211:443
time:2026-10-02T04:29:01Z	status:FAILURE	latency:212.565	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:231.038	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:424.495	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:431.448	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:29:01Z	status:HEALTHY	latency:437.748	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:11.371	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43664	target_addr:172.67.219.211:443
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:13.085	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43666	target_addr:172.67.219.211:443
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:25.910	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36874	target_addr:172.64.147.104:443
time:2026-10-02T04:34:01Z	status:UNKNOWN	latency:31.739	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:37.258	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60606	target_addr:104.21.26.208:443
time:2026-10-02T04:34:01Z	status:FAILURE	latency:220.595	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:301.608	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:457.899	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:501.471	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:34:01Z	status:HEALTHY	latency:503.920	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:39:01Z	status:UNKNOWN	latency:8.808	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:11.002	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55752	target_addr:172.67.168.140:443
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:11.047	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33032	target_addr:172.67.219.211:443
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:11.736	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33042	target_addr:172.67.219.211:443
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:12.958	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55364	target_addr:172.64.147.104:443
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:55.481	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:64.834	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:68.894	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:39:01Z	status:FAILURE	latency:187.413	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:39:01Z	status:HEALTHY	latency:265.534	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:44:01Z	status:UNKNOWN	latency:7.874	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:10.000	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36864	target_addr:104.21.26.208:443
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:9.848	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37360	target_addr:104.21.86.125:443
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:11.114	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43430	target_addr:104.18.40.152:443
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:11.810	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60992	target_addr:172.67.219.211:443
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:52.271	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:62.784	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:65.840	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:44:01Z	status:FAILURE	latency:193.469	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:44:01Z	status:HEALTHY	latency:232.909	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:49:01Z	status:UNKNOWN	latency:7.396	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:8.734	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44580	target_addr:172.67.219.211:443
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:11.114	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36184	target_addr:104.18.40.152:443
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:11.195	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50192	target_addr:172.67.168.140:443
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:11.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52618	target_addr:104.21.86.125:443
time:2026-10-02T04:49:01Z	status:FAILURE	latency:26.409	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:261.497	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:419.142	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:454.182	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:49:01Z	status:HEALTHY	latency:671.546	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:54:01Z	status:UNKNOWN	latency:7.711	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:11.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60528	target_addr:104.18.40.152:443
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:11.372	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43178	target_addr:104.21.86.125:443
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:11.192	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50978	target_addr:172.67.219.211:443
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:11.420	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50856	target_addr:172.67.168.140:443
time:2026-10-02T04:54:01Z	status:FAILURE	latency:183.413	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:217.819	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:421.969	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:582.832	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:54:01Z	status:HEALTHY	latency:613.313	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:59:01Z	status:UNKNOWN	latency:12.265	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:11.894	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56694	target_addr:104.21.86.125:443
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:12.121	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56706	target_addr:104.21.86.125:443
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:12.730	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45524	target_addr:172.64.147.104:443
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:13.006	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43638	target_addr:104.21.26.208:443
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:64.075	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:79.285	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:84.806	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T04:59:01Z	status:FAILURE	latency:205.750	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T04:59:01Z	status:HEALTHY	latency:264.288	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:11.047	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44330	target_addr:172.64.147.104:443
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:11.149	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55412	target_addr:104.21.26.208:443
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:11.732	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46192	target_addr:172.67.219.211:443
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:15.410	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46200	target_addr:172.67.219.211:443
time:2026-10-02T05:04:01Z	status:FAILURE	latency:26.750	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:04:01Z	status:UNKNOWN	latency:58.586	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:61.600	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:62.987	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:76.062	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:04:01Z	status:HEALTHY	latency:254.834	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:09:01Z	status:UNKNOWN	latency:7.995	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:11.088	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60862	target_addr:104.21.86.125:443
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:13.484	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38080	target_addr:172.64.147.104:443
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:14.829	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34126	target_addr:172.67.219.211:443
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:73.210	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43576	target_addr:172.67.168.140:443
time:2026-10-02T05:09:01Z	status:FAILURE	latency:206.257	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:220.436	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:737.897	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:873.535	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:09:01Z	status:HEALTHY	latency:878.184	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:14:01Z	status:UNKNOWN	latency:8.132	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:12.135	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48342	target_addr:104.21.86.125:443
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:12.515	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41782	target_addr:172.64.147.104:443
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:12.457	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60402	target_addr:172.67.219.211:443
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:21.629	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56412	target_addr:104.21.26.208:443
time:2026-10-02T05:14:01Z	status:FAILURE	latency:32.314	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:275.118	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:797.381	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:800.049	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:14:01Z	status:HEALTHY	latency:806.524	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:19:01Z	status:UNKNOWN	latency:6.985	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:9.343	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53310	target_addr:104.21.86.125:443
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:11.955	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47668	target_addr:172.64.147.104:443
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:17.616	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45444	target_addr:172.67.219.211:443
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:22.277	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49818	target_addr:172.67.168.140:443
time:2026-10-02T05:19:01Z	status:FAILURE	latency:196.933	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:236.308	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:809.952	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:818.377	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:19:01Z	status:HEALTHY	latency:834.571	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:24:01Z	status:UNKNOWN	latency:5.806	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:9.355	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51040	target_addr:172.67.168.140:443
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:9.500	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48512	target_addr:104.18.40.152:443
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:10.830	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43704	target_addr:104.21.86.125:443
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:13.824	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48338	target_addr:172.67.219.211:443
time:2026-10-02T05:24:01Z	status:FAILURE	latency:224.192	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:289.893	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:443.693	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:496.071	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:24:01Z	status:HEALTHY	latency:511.504	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:29:01Z	status:UNKNOWN	latency:8.140	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:9.509	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50990	target_addr:172.64.147.104:443
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:11.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40184	target_addr:172.67.168.140:443
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:11.326	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41778	target_addr:104.21.86.125:443
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:14.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41790	target_addr:104.21.86.125:443
time:2026-10-02T05:29:01Z	status:FAILURE	latency:200.836	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:207.247	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:493.322	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:493.490	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:29:01Z	status:HEALTHY	latency:497.641	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:34:01Z	status:UNKNOWN	latency:8.399	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:12.484	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59168	target_addr:172.67.219.211:443
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:12.415	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34298	target_addr:172.67.168.140:443
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:13.385	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35884	target_addr:104.21.86.125:443
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:13.959	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45930	target_addr:104.18.40.152:443
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:217.200	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:34:01Z	status:FAILURE	latency:231.498	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:438.313	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:489.026	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:34:01Z	status:HEALTHY	latency:772.379	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:39:01Z	status:UNKNOWN	latency:7.462	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:11.311	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36460	target_addr:104.18.40.152:443
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:12.126	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56028	target_addr:172.67.219.211:443
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:18.771	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49908	target_addr:104.21.86.125:443
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:28.581	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54122	target_addr:104.21.26.208:443
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:61.072	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:98.358	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:121.508	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:39:01Z	status:FAILURE	latency:230.073	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:39:01Z	status:HEALTHY	latency:323.469	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:44:01Z	status:UNKNOWN	latency:6.858	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:9.631	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34894	target_addr:104.21.86.125:443
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:10.632	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36316	target_addr:104.21.26.208:443
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:10.876	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46182	target_addr:172.64.147.104:443
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:10.614	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54972	target_addr:172.67.219.211:443
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:62.832	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:76.349	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:79.289	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:44:01Z	status:FAILURE	latency:228.786	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:44:01Z	status:HEALTHY	latency:586.904	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:49:01Z	status:UNKNOWN	latency:9.980	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:12.496	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55128	target_addr:104.18.40.152:443
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:13.746	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46038	target_addr:172.67.219.211:443
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:13.698	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46048	target_addr:172.67.219.211:443
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:19.318	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48400	target_addr:172.67.168.140:443
time:2026-10-02T05:49:01Z	status:FAILURE	latency:204.161	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:258.558	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:434.376	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:504.039	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:49:01Z	status:HEALTHY	latency:541.758	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:54:01Z	status:UNKNOWN	latency:7.814	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:10.070	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40664	target_addr:104.21.26.208:443
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:11.618	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39498	target_addr:104.21.86.125:443
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:19.342	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39502	target_addr:104.21.86.125:443
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:28.443	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40988	target_addr:172.64.147.104:443
time:2026-10-02T05:54:01Z	status:FAILURE	latency:201.091	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:226.306	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:610.621	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:754.966	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:54:01Z	status:HEALTHY	latency:760.107	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:59:01Z	status:UNKNOWN	latency:6.116	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:8.533	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58896	target_addr:104.18.40.152:443
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:12.402	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44130	target_addr:104.21.86.125:443
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:15.443	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42126	target_addr:172.67.219.211:443
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:21.522	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39340	target_addr:104.21.26.208:443
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:56.381	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:75.936	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:84.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T05:59:01Z	status:FAILURE	latency:229.556	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T05:59:01Z	status:HEALTHY	latency:268.289	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:04:01Z	status:UNKNOWN	latency:7.469	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:10.470	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48990	target_addr:172.64.147.104:443
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:10.624	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54224	target_addr:104.21.86.125:443
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:10.555	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57074	target_addr:172.67.219.211:443
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:12.268	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49564	target_addr:104.21.26.208:443
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:54.672	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:57.665	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:62.102	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:04:01Z	status:FAILURE	latency:199.589	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:04:01Z	status:HEALTHY	latency:204.321	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:09:01Z	status:UNKNOWN	latency:7.682	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:11.402	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34616	target_addr:172.64.147.104:443
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:11.074	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51242	target_addr:104.21.86.125:443
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:11.183	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49932	target_addr:104.21.26.208:443
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:21.451	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51258	target_addr:104.21.86.125:443
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:208.938	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:09:01Z	status:FAILURE	latency:324.551	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:412.460	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:493.847	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:09:01Z	status:HEALTHY	latency:510.545	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:14:01Z	status:UNKNOWN	latency:8.178	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:11.693	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60240	target_addr:104.21.86.125:443
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:13.123	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45862	target_addr:172.64.147.104:443
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:16.077	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60246	target_addr:104.21.86.125:443
time:2026-10-02T06:14:01Z	status:FAILURE	latency:197.994	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:311.027	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55244	target_addr:104.21.26.208:443
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:801.645	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:878.711	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:967.344	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:14:01Z	status:HEALTHY	latency:5189.110	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:19:01Z	status:UNKNOWN	latency:9.601	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:9.637	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33140	target_addr:172.64.147.104:443
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:11.438	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46990	target_addr:104.21.86.125:443
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:11.869	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46098	target_addr:172.67.219.211:443
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:13.116	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49322	target_addr:104.21.26.208:443
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:66.158	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:66.119	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:75.800	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:19:01Z	status:FAILURE	latency:255.434	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:19:01Z	status:HEALTHY	latency:729.474	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:24:01Z	status:UNKNOWN	latency:9.108	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:10.957	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40474	target_addr:172.64.147.104:443
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:11.340	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42864	target_addr:172.67.168.140:443
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:11.620	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53252	target_addr:172.67.219.211:443
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:11.912	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60400	target_addr:104.21.86.125:443
time:2026-10-02T06:24:01Z	status:FAILURE	latency:43.181	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:62.693	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:68.942	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:85.957	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:24:01Z	status:HEALTHY	latency:255.602	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:29:01Z	status:UNKNOWN	latency:9.105	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:11.918	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54036	target_addr:104.21.86.125:443
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:12.301	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41792	target_addr:104.18.40.152:443
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:11.771	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37700	target_addr:104.21.26.208:443
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:12.246	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54052	target_addr:104.21.86.125:443
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:55.717	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:59.063	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:193.156	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:29:01Z	status:FAILURE	latency:221.603	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:29:01Z	status:HEALTHY	latency:236.952	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:9.487	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54448	target_addr:172.64.147.104:443
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:11.202	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56018	target_addr:172.67.219.211:443
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:11.175	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56032	target_addr:172.67.219.211:443
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:13.314	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54200	target_addr:172.67.168.140:443
time:2026-10-02T06:34:01Z	status:FAILURE	latency:24.007	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:51.091	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:64.866	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:34:01Z	status:UNKNOWN	latency:76.839	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:133.154	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:34:01Z	status:HEALTHY	latency:225.450	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:39:01Z	status:UNKNOWN	latency:8.825	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:9.117	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57000	target_addr:172.64.147.104:443
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:9.825	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48522	target_addr:104.21.86.125:443
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:10.663	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48520	target_addr:104.21.86.125:443
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:13.521	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49872	target_addr:172.67.168.140:443
time:2026-10-02T06:39:01Z	status:FAILURE	latency:225.834	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:297.544	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:693.057	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:698.363	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:39:01Z	status:HEALTHY	latency:745.496	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:44:01Z	status:UNKNOWN	latency:8.411	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:10.882	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44774	target_addr:172.64.147.104:443
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:12.289	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59148	target_addr:172.67.219.211:443
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:12.136	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57558	target_addr:172.67.168.140:443
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:12.232	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59164	target_addr:172.67.219.211:443
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:73.176	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:78.879	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:44:01Z	status:FAILURE	latency:204.124	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:326.576	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:44:01Z	status:HEALTHY	latency:406.861	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:49:01Z	status:UNKNOWN	latency:7.279	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:10.673	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52738	target_addr:104.18.40.152:443
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:11.759	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54118	target_addr:172.67.219.211:443
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:12.647	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54128	target_addr:172.67.219.211:443
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:16.481	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41144	target_addr:172.67.168.140:443
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:55.312	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:56.861	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:49:01Z	status:FAILURE	latency:208.438	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:463.205	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:49:01Z	status:HEALTHY	latency:1068.376	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:10.268	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58850	target_addr:104.21.86.125:443
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:12.318	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49218	target_addr:104.18.40.152:443
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:13.953	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57822	target_addr:172.67.219.211:443
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:17.208	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41392	target_addr:172.67.168.140:443
time:2026-10-02T06:54:01Z	status:UNKNOWN	latency:33.033	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:136.123	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:54:01Z	status:FAILURE	latency:182.427	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:563.919	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:1481.129	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:54:01Z	status:HEALTHY	latency:1583.325	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:10.403	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57782	target_addr:172.67.219.211:443
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:10.743	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48466	target_addr:172.67.168.140:443
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:11.243	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54390	target_addr:104.21.86.125:443
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:27.488	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55408	target_addr:104.18.40.152:443
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:64.280	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:81.394	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:59:01Z	status:UNKNOWN	latency:179.986	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T06:59:01Z	status:FAILURE	latency:234.607	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:658.271	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T06:59:01Z	status:HEALTHY	latency:1052.164	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:04:01Z	status:UNKNOWN	latency:7.480	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:8.987	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49104	target_addr:104.21.86.125:443
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:20.229	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50774	target_addr:172.64.147.104:443
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:19.886	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33228	target_addr:104.21.26.208:443
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:20.736	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49120	target_addr:104.21.86.125:443
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:52.327	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:56.001	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:59.179	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:04:01Z	status:FAILURE	latency:210.203	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:04:01Z	status:HEALTHY	latency:215.139	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:09:01Z	status:UNKNOWN	latency:7.753	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:10.251	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52052	target_addr:104.21.86.125:443
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:11.009	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34396	target_addr:172.67.168.140:443
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:11.881	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52502	target_addr:104.18.40.152:443
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:11.879	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52066	target_addr:104.21.86.125:443
time:2026-10-02T07:09:01Z	status:FAILURE	latency:28.135	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:214.391	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:444.623	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:469.960	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:09:01Z	status:HEALTHY	latency:501.389	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:14:01Z	status:UNKNOWN	latency:7.821	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:12.801	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51720	target_addr:104.21.26.208:443
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:15.455	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46938	target_addr:172.64.147.104:443
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:25.477	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47658	target_addr:172.67.219.211:443
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:27.569	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42680	target_addr:104.21.86.125:443
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:63.994	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:69.746	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:100.662	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:14:01Z	status:FAILURE	latency:237.826	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:14:01Z	status:HEALTHY	latency:271.955	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:19:01Z	status:UNKNOWN	latency:8.508	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:11.104	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57900	target_addr:104.18.40.152:443
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:11.450	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45726	target_addr:172.67.219.211:443
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:11.617	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50540	target_addr:104.21.86.125:443
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:16.222	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36338	target_addr:172.67.168.140:443
time:2026-10-02T07:19:01Z	status:FAILURE	latency:52.635	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:59.894	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:62.728	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:69.447	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:19:01Z	status:HEALTHY	latency:317.797	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:24:02Z	status:UNKNOWN	latency:7.920	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:7.915	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35832	target_addr:172.67.219.211:443
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:9.057	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48942	target_addr:172.67.168.140:443
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:9.474	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46616	target_addr:172.64.147.104:443
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:11.040	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39950	target_addr:104.21.86.125:443
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:57.034	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:66.492	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:82.173	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:24:02Z	status:FAILURE	latency:219.878	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:24:02Z	status:HEALTHY	latency:262.053	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:29:02Z	status:UNKNOWN	latency:7.726	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:10.331	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56840	target_addr:172.67.219.211:443
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:10.955	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37344	target_addr:172.67.168.140:443
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:11.080	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56852	target_addr:172.67.219.211:443
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:12.226	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38270	target_addr:104.18.40.152:443
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:54.343	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:29:02Z	status:FAILURE	latency:71.715	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:72.388	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:189.887	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:29:02Z	status:HEALTHY	latency:1011.294	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:7.894	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36368	target_addr:104.18.40.152:443
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:9.547	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60598	target_addr:172.67.219.211:443
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:10.354	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55652	target_addr:172.67.168.140:443
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:13.714	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60604	target_addr:172.67.219.211:443
time:2026-10-02T07:34:02Z	status:FAILURE	latency:26.097	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:52.464	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:34:02Z	status:UNKNOWN	latency:56.254	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:66.541	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:96.074	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:34:02Z	status:HEALTHY	latency:203.709	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:39:02Z	status:UNKNOWN	latency:10.160	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:11.525	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37208	target_addr:172.67.168.140:443
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:12.114	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33916	target_addr:104.18.40.152:443
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:11.419	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46034	target_addr:104.21.86.125:443
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:13.436	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34786	target_addr:172.67.219.211:443
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:57.377	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:69.202	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:71.418	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:39:02Z	status:FAILURE	latency:344.443	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:39:02Z	status:HEALTHY	latency:1333.027	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:44:02Z	status:UNKNOWN	latency:8.118	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:10.946	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38192	target_addr:172.64.147.104:443
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:11.924	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45798	target_addr:104.21.26.208:443
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:13.198	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46828	target_addr:104.21.86.125:443
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:31.574	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46826	target_addr:104.21.86.125:443
time:2026-10-02T07:44:02Z	status:FAILURE	latency:235.222	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:238.779	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:518.375	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:518.509	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:44:02Z	status:HEALTHY	latency:823.146	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:9.210	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46588	target_addr:172.67.168.140:443
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:9.852	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53674	target_addr:172.67.219.211:443
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:11.558	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33316	target_addr:172.64.147.104:443
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:12.173	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53686	target_addr:172.67.219.211:443
time:2026-10-02T07:49:02Z	status:UNKNOWN	latency:56.292	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:189.966	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:49:02Z	status:FAILURE	latency:210.163	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:443.489	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:443.845	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:49:02Z	status:HEALTHY	latency:470.547	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:9.078	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55600	target_addr:172.67.219.211:443
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:10.855	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51004	target_addr:172.64.147.104:443
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:11.042	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55928	target_addr:104.21.26.208:443
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:10.655	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46158	target_addr:104.21.86.125:443
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:52.864	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:60.505	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:54:02Z	status:UNKNOWN	latency:71.082	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:75.528	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:54:02Z	status:FAILURE	latency:212.158	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:54:02Z	status:HEALTHY	latency:396.006	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:59:02Z	status:UNKNOWN	latency:8.192	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:9.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32946	target_addr:104.21.26.208:443
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:11.167	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51072	target_addr:172.67.219.211:443
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:12.716	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33494	target_addr:172.64.147.104:443
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:16.356	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54242	target_addr:104.21.86.125:443
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:49.917	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:58.461	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:59:02Z	status:FAILURE	latency:211.533	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:341.581	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T07:59:02Z	status:HEALTHY	latency:374.335	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:04:02Z	status:UNKNOWN	latency:7.301	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:10.407	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42312	target_addr:172.67.168.140:443
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:10.245	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52992	target_addr:172.67.219.211:443
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:16.158	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52994	target_addr:172.67.219.211:443
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:34.886	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60142	target_addr:172.64.147.104:443
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:53.039	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:68.120	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:77.524	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:04:02Z	status:HEALTHY	latency:215.115	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:04:02Z	status:FAILURE	latency:219.530	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:09:02Z	status:UNKNOWN	latency:8.231	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:9.423	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36310	target_addr:104.18.40.152:443
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:11.467	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35230	target_addr:172.67.219.211:443
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:11.893	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35236	target_addr:172.67.219.211:443
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:12.097	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47150	target_addr:172.67.168.140:443
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:54.511	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:55.848	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:58.301	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:09:02Z	status:FAILURE	latency:176.738	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:09:02Z	status:HEALTHY	latency:256.860	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:14:02Z	status:UNKNOWN	latency:9.289	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:11.621	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40032	target_addr:104.18.40.152:443
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:11.263	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37644	target_addr:172.67.219.211:443
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:11.906	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37660	target_addr:172.67.219.211:443
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:13.201	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46478	target_addr:172.67.168.140:443
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:58.403	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:66.092	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:213.863	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:14:02Z	status:FAILURE	latency:229.305	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:14:02Z	status:HEALTHY	latency:429.363	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:19:02Z	status:UNKNOWN	latency:7.008	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:9.267	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58152	target_addr:104.21.26.208:443
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:10.306	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42232	target_addr:172.67.219.211:443
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:10.715	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55302	target_addr:172.64.147.104:443
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:10.814	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42220	target_addr:172.67.219.211:443
time:2026-10-02T08:19:02Z	status:FAILURE	latency:28.895	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:50.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:60.844	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:82.003	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:19:02Z	status:HEALTHY	latency:238.382	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:24:02Z	status:UNKNOWN	latency:6.322	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:10.214	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47628	target_addr:104.18.40.152:443
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:9.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44694	target_addr:172.67.168.140:443
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:10.547	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43588	target_addr:172.67.219.211:443
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:11.947	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58440	target_addr:104.21.86.125:443
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:51.793	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:54.005	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:66.622	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:24:02Z	status:HEALTHY	latency:96.516	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:24:02Z	status:FAILURE	latency:196.940	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:29:02Z	status:UNKNOWN	latency:7.383	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:9.749	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43502	target_addr:172.64.147.104:443
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:11.254	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56908	target_addr:172.67.168.140:443
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:11.981	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43920	target_addr:104.21.86.125:443
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:24.046	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43936	target_addr:104.21.86.125:443
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:55.133	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:57.977	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:75.706	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:29:02Z	status:HEALTHY	latency:186.062	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:29:02Z	status:FAILURE	latency:188.712	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:34:02Z	status:UNKNOWN	latency:6.936	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:11.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53572	target_addr:172.67.168.140:443
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:11.518	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52220	target_addr:172.67.219.211:443
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:11.806	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52230	target_addr:172.67.219.211:443
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:19.818	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53900	target_addr:104.18.40.152:443
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:60.530	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:68.320	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:71.359	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:34:02Z	status:HEALTHY	latency:208.094	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:34:02Z	status:FAILURE	latency:228.394	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:39:02Z	status:UNKNOWN	latency:9.211	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:12.555	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38702	target_addr:172.67.168.140:443
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:13.164	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37442	target_addr:172.64.147.104:443
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:12.878	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47110	target_addr:104.21.86.125:443
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:12.709	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47096	target_addr:104.21.86.125:443
time:2026-10-02T08:39:02Z	status:FAILURE	latency:31.701	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:279.816	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:653.146	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:737.456	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:39:02Z	status:HEALTHY	latency:1570.461	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:44:02Z	status:UNKNOWN	latency:8.092	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:10.805	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56372	target_addr:172.64.147.104:443
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:12.308	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41284	target_addr:104.21.86.125:443
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:12.485	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52744	target_addr:172.67.219.211:443
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:12.706	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52776	target_addr:104.21.26.208:443
time:2026-10-02T08:44:02Z	status:FAILURE	latency:222.854	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:270.199	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:575.631	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:1149.266	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:44:02Z	status:HEALTHY	latency:1497.942	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:12.484	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46406	target_addr:172.67.219.211:443
time:2026-10-02T08:49:02Z	status:UNKNOWN	latency:19.696	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:25.937	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34886	target_addr:172.67.168.140:443
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:32.456	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46414	target_addr:172.67.219.211:443
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:32.563	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54502	target_addr:104.18.40.152:443
time:2026-10-02T08:49:02Z	status:FAILURE	latency:183.713	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:306.460	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:433.091	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:708.160	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:49:02Z	status:HEALTHY	latency:718.480	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:54:02Z	status:UNKNOWN	latency:8.461	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:11.898	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54346	target_addr:104.18.40.152:443
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:11.826	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57634	target_addr:172.67.219.211:443
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:11.773	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38934	target_addr:104.21.26.208:443
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:13.052	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58586	target_addr:104.21.86.125:443
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:515.681	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:825.035	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:845.835	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:54:02Z	status:FAILURE	latency:5189.891	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:54:02Z	status:HEALTHY	latency:5232.488	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:9.602	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35450	target_addr:172.64.147.104:443
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:10.513	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40580	target_addr:172.67.219.211:443
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:11.832	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44654	target_addr:172.67.168.140:443
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:14.787	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36584	target_addr:104.21.86.125:443
time:2026-10-02T08:59:02Z	status:UNKNOWN	latency:18.581	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:54.356	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:55.346	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:59.536	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T08:59:02Z	status:FAILURE	latency:213.042	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T08:59:02Z	status:HEALTHY	latency:252.994	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:04:02Z	status:UNKNOWN	latency:7.493	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:9.265	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34616	target_addr:104.18.40.152:443
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:9.177	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57278	target_addr:172.67.219.211:443
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:10.331	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40420	target_addr:104.21.26.208:443
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:19.300	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57288	target_addr:172.67.219.211:443
time:2026-10-02T09:04:02Z	status:FAILURE	latency:37.655	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:54.201	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:65.209	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:68.208	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:04:02Z	status:HEALTHY	latency:219.681	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:09:02Z	status:UNKNOWN	latency:6.959	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:9.738	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47858	target_addr:104.18.40.152:443
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:9.833	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43730	target_addr:104.21.86.125:443
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:9.934	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53590	target_addr:172.67.168.140:443
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:11.296	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33452	target_addr:172.67.219.211:443
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:55.673	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:76.048	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:83.982	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:09:02Z	status:HEALTHY	latency:93.504	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:09:02Z	status:FAILURE	latency:249.179	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:14:02Z	status:UNKNOWN	latency:8.191	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:11.194	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51408	target_addr:104.18.40.152:443
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:10.654	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37966	target_addr:104.21.86.125:443
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:10.836	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37954	target_addr:104.21.86.125:443
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:21.178	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39234	target_addr:172.67.168.140:443
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:70.669	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:70.960	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:196.598	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:14:02Z	status:FAILURE	latency:206.995	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:14:02Z	status:HEALTHY	latency:526.600	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:9.853	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34970	target_addr:172.67.168.140:443
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:10.220	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60526	target_addr:172.67.219.211:443
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:10.742	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38648	target_addr:104.21.86.125:443
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:11.818	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47384	target_addr:104.18.40.152:443
time:2026-10-02T09:19:02Z	status:UNKNOWN	latency:34.811	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:56.326	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:56.924	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:80.727	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:19:02Z	status:FAILURE	latency:194.775	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:19:02Z	status:HEALTHY	latency:256.676	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:9.977	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52666	target_addr:172.67.168.140:443
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:10.142	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35630	target_addr:104.18.40.152:443
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:10.804	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42756	target_addr:172.67.219.211:443
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:10.923	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42758	target_addr:172.67.219.211:443
time:2026-10-02T09:24:02Z	status:FAILURE	latency:23.506	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:24:02Z	status:UNKNOWN	latency:38.093	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:53.990	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:68.588	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:75.295	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:24:02Z	status:HEALTHY	latency:194.003	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:29:02Z	status:UNKNOWN	latency:7.108	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:9.226	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59722	target_addr:172.64.147.104:443
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:10.027	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50716	target_addr:172.67.219.211:443
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:12.931	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49152	target_addr:104.21.86.125:443
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:16.329	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50596	target_addr:104.21.26.208:443
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:64.525	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:69.468	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:101.374	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:29:02Z	status:FAILURE	latency:201.390	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:29:02Z	status:HEALTHY	latency:224.738	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:34:02Z	status:UNKNOWN	latency:7.928	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:10.009	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34360	target_addr:172.64.147.104:443
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:12.784	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32900	target_addr:172.67.219.211:443
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:15.512	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32914	target_addr:172.67.219.211:443
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:27.160	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41574	target_addr:172.67.168.140:443
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:50.581	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:62.633	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:71.643	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:34:02Z	status:FAILURE	latency:216.775	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:34:02Z	status:HEALTHY	latency:257.260	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:39:02Z	status:UNKNOWN	latency:8.298	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:10.527	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59920	target_addr:104.21.86.125:443
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:11.153	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39490	target_addr:104.18.40.152:443
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:10.693	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37658	target_addr:104.21.26.208:443
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:23.667	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59926	target_addr:104.21.86.125:443
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:55.776	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:58.047	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:62.927	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:39:02Z	status:HEALTHY	latency:212.370	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:39:02Z	status:FAILURE	latency:221.897	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:44:02Z	status:UNKNOWN	latency:6.930	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:8.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51166	target_addr:104.18.40.152:443
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:9.852	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53090	target_addr:104.21.86.125:443
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:11.755	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33176	target_addr:172.67.168.140:443
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:15.495	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33340	target_addr:172.67.219.211:443
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:52.939	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:58.731	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:62.444	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:44:02Z	status:HEALTHY	latency:189.566	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:44:02Z	status:FAILURE	latency:205.823	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:49:02Z	status:UNKNOWN	latency:5.782	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:9.284	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48408	target_addr:104.21.26.208:443
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:11.247	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53460	target_addr:104.21.86.125:443
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:12.574	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60346	target_addr:104.18.40.152:443
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:53.053	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:54.015	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:63.460	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:100.910	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53468	target_addr:104.21.86.125:443
time:2026-10-02T09:49:02Z	status:FAILURE	latency:187.403	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:49:02Z	status:HEALTHY	latency:210.302	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:54:02Z	status:UNKNOWN	latency:8.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:10.951	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57546	target_addr:104.21.86.125:443
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:11.434	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35634	target_addr:104.18.40.152:443
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:12.697	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35450	target_addr:104.21.26.208:443
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:27.124	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57556	target_addr:104.21.86.125:443
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:56.439	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:56.225	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:60.853	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:54:02Z	status:HEALTHY	latency:179.839	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:54:02Z	status:FAILURE	latency:197.298	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:9.319	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52140	target_addr:172.64.147.104:443
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:9.423	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38902	target_addr:172.67.219.211:443
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:17.074	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38904	target_addr:172.67.219.211:443
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:16.936	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37282	target_addr:172.67.168.140:443
time:2026-10-02T09:59:02Z	status:UNKNOWN	latency:34.793	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T09:59:02Z	status:FAILURE	latency:43.924	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:61.151	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:66.842	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:78.049	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T09:59:02Z	status:HEALTHY	latency:193.271	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:04:02Z	status:UNKNOWN	latency:10.280	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:16.418	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54234	target_addr:172.67.219.211:443
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:16.536	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54382	target_addr:104.21.86.125:443
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:30.152	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46358	target_addr:104.18.40.152:443
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:63.067	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:69.469	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:69.459	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:180.707	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35324	target_addr:104.21.26.208:443
time:2026-10-02T10:04:02Z	status:HEALTHY	latency:201.366	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:04:02Z	status:FAILURE	latency:221.546	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:09:02Z	status:UNKNOWN	latency:8.524	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:9.799	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56288	target_addr:172.67.219.211:443
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:10.666	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55076	target_addr:172.64.147.104:443
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:10.850	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54506	target_addr:104.21.26.208:443
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:18.005	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56304	target_addr:172.67.219.211:443
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:55.973	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:62.223	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:09:02Z	status:FAILURE	latency:148.010	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:196.649	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:09:02Z	status:HEALTHY	latency:219.831	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:14:02Z	status:UNKNOWN	latency:7.870	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:10.003	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42376	target_addr:172.67.219.211:443
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:13.392	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39620	target_addr:172.67.168.140:443
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:17.549	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42372	target_addr:172.67.219.211:443
time:2026-10-02T10:14:02Z	status:FAILURE	latency:27.411	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:48.773	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50064	target_addr:172.64.147.104:443
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:49.778	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:56.787	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:59.884	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:14:02Z	status:HEALTHY	latency:171.248	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:19:02Z	status:UNKNOWN	latency:6.995	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:9.125	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48268	target_addr:172.67.219.211:443
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:9.263	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35382	target_addr:172.67.168.140:443
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:10.279	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44914	target_addr:172.64.147.104:443
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:10.294	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48282	target_addr:172.67.219.211:443
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:53.260	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:53.714	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:19:02Z	status:FAILURE	latency:138.384	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:209.567	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:19:02Z	status:HEALTHY	latency:1040.819	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:24:02Z	status:UNKNOWN	latency:7.689	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:11.968	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44724	target_addr:104.21.26.208:443
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:12.011	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44882	target_addr:172.67.219.211:443
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:11.772	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44892	target_addr:172.67.219.211:443
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:16.732	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60866	target_addr:172.64.147.104:443
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:54.981	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:69.955	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:128.600	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:24:02Z	status:FAILURE	latency:212.613	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:24:02Z	status:HEALTHY	latency:300.702	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:29:02Z	status:UNKNOWN	latency:6.078	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:8.477	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50246	target_addr:104.18.40.152:443
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:9.318	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38952	target_addr:104.21.86.125:443
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:9.679	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38954	target_addr:104.21.86.125:443
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:10.541	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60116	target_addr:172.67.168.140:443
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:48.419	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:53.455	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:65.938	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:29:02Z	status:FAILURE	latency:222.585	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:29:02Z	status:HEALTHY	latency:451.248	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:34:02Z	status:UNKNOWN	latency:7.203	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:10.223	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55362	target_addr:172.64.147.104:443
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:9.741	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45380	target_addr:104.21.26.208:443
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:10.243	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36274	target_addr:172.67.219.211:443
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:10.679	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57804	target_addr:104.21.86.125:443
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:61.592	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:66.404	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:71.779	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:34:02Z	status:FAILURE	latency:199.156	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:34:02Z	status:HEALTHY	latency:210.332	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:39:02Z	status:UNKNOWN	latency:8.332	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:9.490	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60602	target_addr:104.21.86.125:443
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:9.583	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60592	target_addr:104.21.86.125:443
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:10.458	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43672	target_addr:172.64.147.104:443
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:10.385	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53078	target_addr:172.67.168.140:443
time:2026-10-02T10:39:02Z	status:FAILURE	latency:29.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:51.057	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:57.071	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:67.670	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:39:02Z	status:HEALTHY	latency:113.635	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:8.058	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60446	target_addr:104.18.40.152:443
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:9.127	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44736	target_addr:172.67.219.211:443
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:9.162	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38540	target_addr:172.67.168.140:443
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:10.372	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37750	target_addr:104.21.86.125:443
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:48.622	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:44:02Z	status:UNKNOWN	latency:56.318	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:62.136	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:62.468	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:44:02Z	status:HEALTHY	latency:244.011	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:44:02Z	status:FAILURE	latency:248.008	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:10.736	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58636	target_addr:172.64.147.104:443
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:11.838	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51476	target_addr:104.21.26.208:443
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:11.581	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49492	target_addr:104.21.86.125:443
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:27.419	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47846	target_addr:172.67.219.211:443
time:2026-10-02T10:49:02Z	status:UNKNOWN	latency:33.525	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:59.821	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:66.325	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:70.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:49:02Z	status:HEALTHY	latency:212.285	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:49:02Z	status:FAILURE	latency:223.464	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:54:02Z	status:UNKNOWN	latency:8.237	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:9.502	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39982	target_addr:104.21.86.125:443
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:11.468	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48506	target_addr:104.18.40.152:443
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:12.931	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42848	target_addr:172.67.168.140:443
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:14.171	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39996	target_addr:104.21.86.125:443
time:2026-10-02T10:54:02Z	status:FAILURE	latency:31.548	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:52.713	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:69.888	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:76.069	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:54:02Z	status:HEALTHY	latency:401.244	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:10.102	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55054	target_addr:172.67.168.140:443
time:2026-10-02T10:59:02Z	status:UNKNOWN	latency:10.322	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:11.414	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58298	target_addr:172.67.219.211:443
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:12.016	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36406	target_addr:104.18.40.152:443
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:17.645	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48730	target_addr:104.21.86.125:443
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:57.974	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:62.185	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:201.253	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T10:59:02Z	status:FAILURE	latency:201.541	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T10:59:02Z	status:HEALTHY	latency:254.373	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:04:03Z	status:UNKNOWN	latency:8.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:10.954	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48592	target_addr:104.21.86.125:443
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:11.552	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46120	target_addr:104.21.26.208:443
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:12.032	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48114	target_addr:104.18.40.152:443
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:12.699	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48604	target_addr:104.21.86.125:443
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:61.720	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:82.898	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:92.353	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:04:03Z	status:HEALTHY	latency:211.023	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:04:03Z	status:FAILURE	latency:583.287	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:09:03Z	status:UNKNOWN	latency:7.334	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:9.638	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35176	target_addr:104.18.40.152:443
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:9.239	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34642	target_addr:104.21.86.125:443
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:9.129	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53978	target_addr:172.67.219.211:443
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:10.047	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38316	target_addr:104.21.26.208:443
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:49.884	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:62.287	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:76.117	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:09:03Z	status:FAILURE	latency:174.958	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:09:03Z	status:HEALTHY	latency:197.891	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:10.358	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53064	target_addr:172.67.219.211:443
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:11.234	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54110	target_addr:104.21.86.125:443
time:2026-10-02T11:14:03Z	status:UNKNOWN	latency:13.094	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:14.204	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35516	target_addr:104.18.40.152:443
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:23.440	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50122	target_addr:172.67.168.140:443
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:56.599	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:60.120	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:73.826	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:14:03Z	status:HEALTHY	latency:208.603	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:14:03Z	status:FAILURE	latency:232.959	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:19:03Z	status:UNKNOWN	latency:9.419	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:9.349	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54934	target_addr:172.67.168.140:443
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:9.312	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35446	target_addr:104.21.86.125:443
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:11.315	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35460	target_addr:104.21.86.125:443
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:13.860	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59736	target_addr:172.64.147.104:443
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:85.523	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:19:03Z	status:FAILURE	latency:204.119	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:232.125	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:603.886	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:19:03Z	status:HEALTHY	latency:624.683	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:24:03Z	status:UNKNOWN	latency:7.644	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:10.659	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35410	target_addr:104.21.26.208:443
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:10.568	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42724	target_addr:172.67.219.211:443
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:10.779	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42716	target_addr:172.67.219.211:443
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:12.395	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56502	target_addr:172.64.147.104:443
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:56.618	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:63.664	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:69.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:24:03Z	status:HEALTHY	latency:199.786	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:24:03Z	status:FAILURE	latency:214.151	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:29:03Z	status:UNKNOWN	latency:8.018	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:8.851	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57774	target_addr:172.67.168.140:443
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:9.472	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41352	target_addr:172.67.219.211:443
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:10.192	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37450	target_addr:104.18.40.152:443
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:10.478	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39936	target_addr:104.21.86.125:443
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:54.902	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:126.927	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:129.360	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:29:03Z	status:HEALTHY	latency:201.588	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:29:03Z	status:FAILURE	latency:221.025	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:34:03Z	status:UNKNOWN	latency:7.970	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:12.064	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43152	target_addr:172.67.219.211:443
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:12.165	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37946	target_addr:172.64.147.104:443
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:12.214	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50498	target_addr:104.21.26.208:443
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:12.912	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53886	target_addr:104.21.86.125:443
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:50.324	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:58.513	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:113.326	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:34:03Z	status:FAILURE	latency:166.117	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:34:03Z	status:HEALTHY	latency:206.807	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:39:03Z	status:UNKNOWN	latency:8.029	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:9.426	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37096	target_addr:172.67.168.140:443
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:10.044	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60528	target_addr:104.21.86.125:443
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:10.862	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39844	target_addr:104.18.40.152:443
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:14.904	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37352	target_addr:172.67.219.211:443
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:50.817	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:63.908	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:64.658	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:39:03Z	status:FAILURE	latency:216.093	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:39:03Z	status:HEALTHY	latency:216.363	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:44:03Z	status:UNKNOWN	latency:7.319	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:9.801	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39554	target_addr:172.64.147.104:443
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:11.275	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45984	target_addr:104.21.26.208:443
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:11.399	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60624	target_addr:104.21.86.125:443
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:19.170	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60636	target_addr:104.21.86.125:443
time:2026-10-02T11:44:03Z	status:FAILURE	latency:25.939	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:51.746	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:72.125	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:196.589	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:44:03Z	status:HEALTHY	latency:709.403	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:49:03Z	status:UNKNOWN	latency:7.511	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:9.997	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58704	target_addr:172.64.147.104:443
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:10.258	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50252	target_addr:104.21.86.125:443
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:11.045	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53468	target_addr:172.67.219.211:443
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:11.247	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55014	target_addr:104.21.26.208:443
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:52.849	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:52.909	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:52.716	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:49:03Z	status:HEALTHY	latency:185.503	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:49:03Z	status:FAILURE	latency:198.684	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:54:03Z	status:UNKNOWN	latency:6.489	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:9.390	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35124	target_addr:172.64.147.104:443
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:9.362	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41200	target_addr:104.21.86.125:443
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:10.021	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34630	target_addr:172.67.168.140:443
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:12.508	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35178	target_addr:172.67.219.211:443
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:54.171	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:57.874	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:69.352	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:54:03Z	status:HEALTHY	latency:182.639	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:54:03Z	status:FAILURE	latency:191.030	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T11:59:03Z	status:UNKNOWN	latency:7.112	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:9.281	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60550	target_addr:104.18.40.152:443
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:9.079	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37114	target_addr:172.67.219.211:443
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:12.459	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37122	target_addr:172.67.219.211:443
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:13.713	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53828	target_addr:172.67.168.140:443
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:52.054	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:53.510	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:54.238	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:59:03Z	status:HEALTHY	latency:190.826	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T11:59:03Z	status:FAILURE	latency:197.416	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:04:03Z	status:UNKNOWN	latency:8.323	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:10.110	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59010	target_addr:104.21.86.125:443
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:10.514	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59006	target_addr:104.21.86.125:443
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:12.190	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47170	target_addr:104.18.40.152:443
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:11.905	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55202	target_addr:104.21.26.208:443
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:57.029	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:58.713	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:67.335	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:04:03Z	status:HEALTHY	latency:220.208	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:04:03Z	status:FAILURE	latency:319.585	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:09:03Z	status:UNKNOWN	latency:5.844	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:7.854	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46186	target_addr:104.18.40.152:443
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:9.050	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45080	target_addr:172.67.219.211:443
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:10.049	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59068	target_addr:104.21.26.208:443
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:10.190	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45092	target_addr:172.67.219.211:443
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:52.191	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:59.966	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:71.905	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:09:03Z	status:FAILURE	latency:169.642	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:09:03Z	status:HEALTHY	latency:186.104	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:14:03Z	status:UNKNOWN	latency:7.049	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:9.417	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45878	target_addr:172.67.168.140:443
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:10.197	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52662	target_addr:104.18.40.152:443
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:10.460	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38962	target_addr:104.21.86.125:443
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:12.205	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38966	target_addr:104.21.86.125:443
time:2026-10-02T12:14:03Z	status:FAILURE	latency:22.617	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:53.774	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:101.853	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:205.308	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:14:03Z	status:HEALTHY	latency:289.036	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:19:03Z	status:UNKNOWN	latency:6.544	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:10.139	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34556	target_addr:172.67.219.211:443
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:10.153	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34566	target_addr:172.67.219.211:443
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:13.422	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40216	target_addr:172.67.168.140:443
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:19.523	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59416	target_addr:172.64.147.104:443
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:51.889	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:53.156	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:60.226	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:19:03Z	status:FAILURE	latency:228.409	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:19:03Z	status:HEALTHY	latency:522.690	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:24:03Z	status:UNKNOWN	latency:7.326	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:8.781	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58504	target_addr:172.67.219.211:443
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:8.652	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53270	target_addr:172.67.168.140:443
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:8.821	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45222	target_addr:104.21.86.125:443
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:11.973	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44578	target_addr:172.64.147.104:443
time:2026-10-02T12:24:03Z	status:FAILURE	latency:24.524	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:52.289	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:55.106	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:55.506	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:24:03Z	status:HEALTHY	latency:214.040	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:29:03Z	status:UNKNOWN	latency:7.194	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:9.948	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39074	target_addr:172.67.168.140:443
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:10.315	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52224	target_addr:104.18.40.152:443
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:11.942	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34988	target_addr:172.67.219.211:443
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:13.192	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35004	target_addr:172.67.219.211:443
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:55.924	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:57.688	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:216.459	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:29:03Z	status:HEALTHY	latency:226.466	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:29:03Z	status:FAILURE	latency:243.456	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:34:03Z	status:UNKNOWN	latency:8.523	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:11.308	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45942	target_addr:172.64.147.104:443
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:11.791	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42052	target_addr:172.67.168.140:443
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:12.307	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43442	target_addr:172.67.219.211:443
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:12.317	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43438	target_addr:172.67.219.211:443
time:2026-10-02T12:34:03Z	status:FAILURE	latency:169.857	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:215.372	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:675.028	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:747.582	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:34:03Z	status:HEALTHY	latency:749.325	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:39:03Z	status:UNKNOWN	latency:8.067	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:9.774	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45544	target_addr:104.21.86.125:443
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:11.257	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41854	target_addr:104.21.26.208:443
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:11.799	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37622	target_addr:104.18.40.152:443
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:11.511	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47854	target_addr:172.67.219.211:443
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:197.522	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:39:03Z	status:FAILURE	latency:224.095	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:523.710	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:693.853	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:39:03Z	status:HEALTHY	latency:803.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:44:03Z	status:UNKNOWN	latency:6.442	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:9.827	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50730	target_addr:104.18.40.152:443
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:10.009	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55570	target_addr:104.21.26.208:443
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:9.916	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33248	target_addr:104.21.86.125:443
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:21.416	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33262	target_addr:104.21.86.125:443
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:214.755	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:44:03Z	status:FAILURE	latency:232.183	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:431.266	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:435.772	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:44:03Z	status:HEALTHY	latency:601.805	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:49:03Z	status:UNKNOWN	latency:5.810	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:8.292	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38578	target_addr:172.67.219.211:443
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:8.455	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37200	target_addr:104.21.86.125:443
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:10.466	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37016	target_addr:172.64.147.104:443
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:11.221	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55870	target_addr:104.21.26.208:443
time:2026-10-02T12:49:03Z	status:FAILURE	latency:207.133	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:217.751	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:719.964	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:721.008	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:49:03Z	status:HEALTHY	latency:800.579	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:54:03Z	status:UNKNOWN	latency:9.009	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:9.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34872	target_addr:104.18.40.152:443
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:10.693	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41538	target_addr:172.67.219.211:443
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:23.612	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59854	target_addr:104.21.86.125:443
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:202.509	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:54:03Z	status:FAILURE	latency:210.135	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:255.145	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45724	target_addr:172.67.168.140:443
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:498.878	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:513.640	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:54:03Z	status:HEALTHY	latency:633.359	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:10.269	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53698	target_addr:172.64.147.104:443
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:10.719	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39004	target_addr:172.67.219.211:443
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:10.476	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39008	target_addr:172.67.219.211:443
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:11.262	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44118	target_addr:104.21.26.208:443
time:2026-10-02T12:59:03Z	status:UNKNOWN	latency:38.850	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T12:59:03Z	status:FAILURE	latency:180.913	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:233.809	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:501.744	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:502.702	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T12:59:03Z	status:HEALTHY	latency:524.163	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:04:03Z	status:UNKNOWN	latency:8.879	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:11.835	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47510	target_addr:104.21.86.125:443
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:11.640	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41158	target_addr:172.67.219.211:443
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:11.705	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37464	target_addr:104.21.26.208:443
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:16.510	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35226	target_addr:104.18.40.152:443
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:55.848	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:73.576	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:89.436	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:04:03Z	status:HEALTHY	latency:94.304	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:04:03Z	status:FAILURE	latency:171.589	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:09:03Z	status:UNKNOWN	latency:6.655	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:8.809	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59658	target_addr:104.18.40.152:443
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:10.047	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42604	target_addr:104.21.86.125:443
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:10.334	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49814	target_addr:104.21.26.208:443
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:12.235	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42620	target_addr:104.21.86.125:443
time:2026-10-02T13:09:03Z	status:FAILURE	latency:22.693	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:50.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:54.664	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:57.503	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:09:03Z	status:HEALTHY	latency:215.214	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:14:03Z	status:UNKNOWN	latency:6.837	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:10.428	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58718	target_addr:172.64.147.104:443
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:11.590	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42712	target_addr:172.67.168.140:443
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:11.361	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41628	target_addr:104.21.86.125:443
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:11.267	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49128	target_addr:172.67.219.211:443
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:53.263	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:53.445	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:56.290	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:14:03Z	status:HEALTHY	latency:87.653	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:14:03Z	status:FAILURE	latency:169.841	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:19:03Z	status:UNKNOWN	latency:7.214	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:9.226	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34976	target_addr:172.64.147.104:443
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:10.011	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36136	target_addr:104.21.86.125:443
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:10.590	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43242	target_addr:172.67.219.211:443
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:10.815	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37970	target_addr:104.21.26.208:443
time:2026-10-02T13:19:03Z	status:FAILURE	latency:23.484	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:60.170	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:70.066	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:270.901	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:19:03Z	status:HEALTHY	latency:378.792	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:24:03Z	status:UNKNOWN	latency:6.971	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:9.165	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38902	target_addr:172.67.168.140:443
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:9.250	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50832	target_addr:172.64.147.104:443
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:9.668	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51580	target_addr:104.21.86.125:443
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:11.153	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45384	target_addr:172.67.219.211:443
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:78.278	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:80.484	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:198.845	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:24:03Z	status:FAILURE	latency:199.281	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:24:03Z	status:HEALTHY	latency:241.121	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:29:03Z	status:UNKNOWN	latency:7.584	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:8.084	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56242	target_addr:172.67.219.211:443
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:9.587	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48994	target_addr:172.64.147.104:443
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:11.778	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47440	target_addr:172.67.168.140:443
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:17.825	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43228	target_addr:104.21.86.125:443
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:53.077	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:65.144	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:208.619	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:29:03Z	status:FAILURE	latency:211.689	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:29:03Z	status:HEALTHY	latency:378.206	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:10.067	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55134	target_addr:104.21.86.125:443
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:12.038	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40542	target_addr:104.18.40.152:443
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:11.932	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50464	target_addr:104.21.26.208:443
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:32.604	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55144	target_addr:104.21.86.125:443
time:2026-10-02T13:34:03Z	status:UNKNOWN	latency:33.712	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:76.773	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:77.530	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:90.814	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:34:03Z	status:HEALTHY	latency:210.562	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:34:03Z	status:FAILURE	latency:328.146	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:39:03Z	status:UNKNOWN	latency:7.455	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:9.940	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55146	target_addr:172.67.219.211:443
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:11.266	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54632	target_addr:172.64.147.104:443
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:10.822	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48320	target_addr:172.67.168.140:443
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:11.935	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55150	target_addr:172.67.219.211:443
time:2026-10-02T13:39:03Z	status:FAILURE	latency:43.419	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:54.668	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:57.371	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:63.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:39:03Z	status:HEALTHY	latency:193.413	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:9.908	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55686	target_addr:172.67.219.211:443
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:10.017	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55698	target_addr:172.67.219.211:443
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:10.954	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55436	target_addr:172.67.168.140:443
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:19.813	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50590	target_addr:172.64.147.104:443
time:2026-10-02T13:44:03Z	status:UNKNOWN	latency:20.289	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:53.967	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:57.836	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:78.224	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:44:03Z	status:HEALTHY	latency:206.392	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:44:03Z	status:FAILURE	latency:225.494	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:49:03Z	status:UNKNOWN	latency:6.203	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:8.317	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48964	target_addr:104.21.26.208:443
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:10.230	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56412	target_addr:104.18.40.152:443
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:12.999	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33246	target_addr:172.67.219.211:443
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:12.898	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33258	target_addr:172.67.219.211:443
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:55.098	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:74.274	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:81.515	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:49:03Z	status:FAILURE	latency:237.674	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:49:03Z	status:HEALTHY	latency:267.716	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:54:03Z	status:UNKNOWN	latency:6.327	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:8.811	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37386	target_addr:104.18.40.152:443
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:9.786	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60210	target_addr:172.67.219.211:443
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:10.497	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40670	target_addr:172.67.168.140:443
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:10.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60226	target_addr:172.67.219.211:443
time:2026-10-02T13:54:03Z	status:FAILURE	latency:39.205	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:88.949	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:132.299	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:154.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:54:03Z	status:HEALTHY	latency:173.441	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:59:03Z	status:UNKNOWN	latency:8.009	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:9.535	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49502	target_addr:104.21.26.208:443
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:10.198	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33968	target_addr:172.67.219.211:443
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:10.120	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49248	target_addr:104.18.40.152:443
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:10.553	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33976	target_addr:172.67.219.211:443
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:50.548	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:56.739	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:59.466	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:59:03Z	status:HEALTHY	latency:229.403	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T13:59:03Z	status:FAILURE	latency:231.257	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:04:03Z	status:UNKNOWN	latency:7.787	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:9.611	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46308	target_addr:104.21.26.208:443
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:11.140	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42760	target_addr:104.21.86.125:443
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:11.329	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39480	target_addr:172.67.219.211:443
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:13.052	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56042	target_addr:172.64.147.104:443
time:2026-10-02T14:04:03Z	status:FAILURE	latency:44.246	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:51.143	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:56.371	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:57.807	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:04:03Z	status:HEALTHY	latency:211.472	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:9.336	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53304	target_addr:104.21.26.208:443
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:12.448	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58740	target_addr:104.21.86.125:443
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:14.440	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46722	target_addr:172.64.147.104:443
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:20.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58754	target_addr:104.21.86.125:443
time:2026-10-02T14:09:03Z	status:FAILURE	latency:25.263	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:09:03Z	status:UNKNOWN	latency:44.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:53.064	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:55.775	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:67.016	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:09:03Z	status:HEALTHY	latency:1300.937	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:14:03Z	status:UNKNOWN	latency:6.291	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:9.231	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51190	target_addr:104.21.86.125:443
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:10.083	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50696	target_addr:172.67.168.140:443
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:10.215	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58598	target_addr:104.18.40.152:443
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:10.671	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51204	target_addr:104.21.86.125:443
time:2026-10-02T14:14:03Z	status:FAILURE	latency:29.098	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:264.821	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:481.447	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:562.921	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:14:03Z	status:HEALTHY	latency:836.876	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:19:03Z	status:UNKNOWN	latency:7.919	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:9.135	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33562	target_addr:172.67.168.140:443
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:10.046	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45764	target_addr:104.18.40.152:443
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:10.729	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58460	target_addr:104.21.86.125:443
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:11.630	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58462	target_addr:104.21.86.125:443
time:2026-10-02T14:19:03Z	status:FAILURE	latency:38.209	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:179.136	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:526.135	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:538.040	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:19:03Z	status:HEALTHY	latency:577.261	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:24:03Z	status:UNKNOWN	latency:8.523	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:11.550	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39840	target_addr:104.21.86.125:443
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:12.002	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37058	target_addr:104.18.40.152:443
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:11.920	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57084	target_addr:172.67.168.140:443
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:14.524	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48924	target_addr:172.67.219.211:443
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:100.484	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:24:03Z	status:FAILURE	latency:340.409	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:783.704	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:821.475	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:24:03Z	status:HEALTHY	latency:826.283	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:8.090	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52648	target_addr:104.21.86.125:443
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:9.334	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48178	target_addr:104.21.26.208:443
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:11.648	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33650	target_addr:172.64.147.104:443
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:12.609	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42390	target_addr:172.67.219.211:443
time:2026-10-02T14:29:04Z	status:FAILURE	latency:27.691	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:29:04Z	status:UNKNOWN	latency:35.994	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:290.183	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:518.207	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:546.668	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:29:04Z	status:HEALTHY	latency:569.301	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:12.005	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47098	target_addr:104.21.26.208:443
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:12.200	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48836	target_addr:104.18.40.152:443
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:12.463	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59298	target_addr:104.21.86.125:443
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:12.457	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59312	target_addr:104.21.86.125:443
time:2026-10-02T14:34:04Z	status:UNKNOWN	latency:38.766	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:34:04Z	status:FAILURE	latency:38.597	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:224.585	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:456.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:704.247	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:34:04Z	status:HEALTHY	latency:774.577	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:39:04Z	status:UNKNOWN	latency:7.256	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:8.154	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50942	target_addr:172.67.168.140:443
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:11.066	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59758	target_addr:104.18.40.152:443
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:10.734	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33978	target_addr:104.21.86.125:443
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:11.359	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33986	target_addr:104.21.86.125:443
time:2026-10-02T14:39:04Z	status:FAILURE	latency:184.714	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:228.951	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:451.296	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:504.918	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:39:04Z	status:HEALTHY	latency:568.525	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:44:04Z	status:UNKNOWN	latency:6.080	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:8.432	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46442	target_addr:172.64.147.104:443
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:8.552	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58958	target_addr:104.21.86.125:443
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:9.851	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41220	target_addr:172.67.168.140:443
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:10.602	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58968	target_addr:104.21.86.125:443
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:195.992	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:44:04Z	status:FAILURE	latency:238.238	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:439.748	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:2407.030	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:44:04Z	status:HEALTHY	latency:2464.397	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:12.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55538	target_addr:172.64.147.104:443
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:12.618	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48336	target_addr:104.21.26.208:443
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:12.265	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55536	target_addr:172.67.219.211:443
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:12.410	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37772	target_addr:104.21.86.125:443
time:2026-10-02T14:49:04Z	status:FAILURE	latency:35.158	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:49:04Z	status:UNKNOWN	latency:36.495	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:203.024	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:475.835	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:477.068	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:49:04Z	status:HEALTHY	latency:491.522	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:8.906	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38732	target_addr:172.67.168.140:443
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:10.197	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48296	target_addr:172.64.147.104:443
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:10.618	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59912	target_addr:104.21.86.125:443
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:10.781	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50780	target_addr:172.67.219.211:443
time:2026-10-02T14:54:04Z	status:UNKNOWN	latency:57.272	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:54:04Z	status:FAILURE	latency:207.032	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:259.906	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:457.335	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:673.306	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:54:04Z	status:HEALTHY	latency:696.241	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:11.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36410	target_addr:104.21.86.125:443
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:12.958	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55048	target_addr:104.18.40.152:443
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:18.708	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50998	target_addr:104.21.26.208:443
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:63.102	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40842	target_addr:172.67.219.211:443
time:2026-10-02T14:59:04Z	status:UNKNOWN	latency:64.117	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:207.198	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:59:04Z	status:FAILURE	latency:210.594	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:458.034	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:487.154	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T14:59:04Z	status:HEALTHY	latency:650.486	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:04:04Z	status:UNKNOWN	latency:9.904	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:10.390	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56178	target_addr:104.21.86.125:443
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:11.914	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45156	target_addr:104.18.40.152:443
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:16.050	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34078	target_addr:104.21.26.208:443
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:18.657	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55736	target_addr:172.67.219.211:443
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:264.805	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:04:04Z	status:FAILURE	latency:271.707	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:461.023	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:488.245	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:04:04Z	status:HEALTHY	latency:698.525	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:09:04Z	status:UNKNOWN	latency:7.550	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:8.333	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39596	target_addr:104.18.40.152:443
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:11.789	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42796	target_addr:172.67.219.211:443
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:11.859	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48328	target_addr:104.21.26.208:443
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:19.931	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42802	target_addr:172.67.219.211:443
time:2026-10-02T15:09:04Z	status:FAILURE	latency:203.999	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:215.979	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:571.960	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:577.343	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:09:04Z	status:HEALTHY	latency:621.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:14:04Z	status:UNKNOWN	latency:8.226	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:10.070	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41894	target_addr:172.64.147.104:443
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:11.834	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46672	target_addr:104.21.26.208:443
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:11.283	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35672	target_addr:172.67.219.211:443
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:13.994	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41538	target_addr:104.21.86.125:443
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:223.026	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:14:04Z	status:FAILURE	latency:328.626	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:459.210	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:460.472	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:14:04Z	status:HEALTHY	latency:534.586	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:19:04Z	status:UNKNOWN	latency:9.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:13.298	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45132	target_addr:104.21.26.208:443
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:13.674	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60108	target_addr:104.21.86.125:443
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:17.679	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60114	target_addr:104.21.86.125:443
time:2026-10-02T15:19:04Z	status:FAILURE	latency:343.882	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:477.674	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:478.996	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:551.939	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:2504.969	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51366	target_addr:104.18.40.152:443
time:2026-10-02T15:19:04Z	status:HEALTHY	latency:5211.434	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:24:04Z	status:UNKNOWN	latency:8.079	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:8.808	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52168	target_addr:172.67.219.211:443
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:10.119	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60776	target_addr:104.21.26.208:443
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:12.376	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52182	target_addr:172.67.219.211:443
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:12.338	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55216	target_addr:104.18.40.152:443
time:2026-10-02T15:24:04Z	status:FAILURE	latency:198.238	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:533.884	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:534.636	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:601.392	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:24:04Z	status:HEALTHY	latency:795.085	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:10.886	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53152	target_addr:172.67.219.211:443
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:11.326	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53160	target_addr:172.67.219.211:443
time:2026-10-02T15:29:04Z	status:UNKNOWN	latency:19.326	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:19.983	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33448	target_addr:172.67.168.140:443
time:2026-10-02T15:29:04Z	status:FAILURE	latency:182.663	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:299.843	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55658	target_addr:104.18.40.152:443
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:301.951	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:606.048	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:735.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:29:04Z	status:HEALTHY	latency:743.510	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:34:04Z	status:UNKNOWN	latency:8.188	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:12.073	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43504	target_addr:172.64.147.104:443
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:11.758	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41786	target_addr:172.67.219.211:443
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:12.123	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38006	target_addr:104.21.86.125:443
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:14.236	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40498	target_addr:172.67.168.140:443
time:2026-10-02T15:34:04Z	status:FAILURE	latency:26.470	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:208.731	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:454.186	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:736.577	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:34:04Z	status:HEALTHY	latency:762.584	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:39:04Z	status:UNKNOWN	latency:7.564	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:11.064	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57142	target_addr:104.21.26.208:443
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:10.560	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35378	target_addr:172.67.219.211:443
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:14.655	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36992	target_addr:104.21.86.125:443
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:27.810	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45140	target_addr:172.64.147.104:443
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:207.238	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:560.650	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:560.781	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:39:04Z	status:HEALTHY	latency:795.614	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:39:04Z	status:FAILURE	latency:1207.777	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:44:04Z	status:UNKNOWN	latency:8.950	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:10.370	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58114	target_addr:172.64.147.104:443
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:11.966	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42060	target_addr:172.67.219.211:443
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:12.357	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42062	target_addr:172.67.219.211:443
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:13.063	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37338	target_addr:104.21.26.208:443
time:2026-10-02T15:44:04Z	status:FAILURE	latency:56.016	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:211.142	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:687.239	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:693.176	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:44:04Z	status:HEALTHY	latency:1319.583	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:49:04Z	status:UNKNOWN	latency:7.154	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:10.425	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59490	target_addr:172.67.168.140:443
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:10.696	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37624	target_addr:172.64.147.104:443
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:13.381	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57872	target_addr:104.21.86.125:443
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:14.306	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54422	target_addr:172.67.219.211:443
time:2026-10-02T15:49:04Z	status:FAILURE	latency:207.663	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:255.623	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:438.883	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:453.310	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:49:04Z	status:HEALTHY	latency:690.585	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:54:04Z	status:UNKNOWN	latency:9.140	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:11.745	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36416	target_addr:172.64.147.104:443
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:11.749	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53394	target_addr:172.67.168.140:443
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:11.454	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57856	target_addr:104.21.86.125:443
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:13.103	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57866	target_addr:104.21.86.125:443
time:2026-10-02T15:54:04Z	status:FAILURE	latency:204.923	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:252.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:393.880	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:412.984	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:54:04Z	status:HEALTHY	latency:440.550	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:59:04Z	status:UNKNOWN	latency:7.653	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:9.873	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43146	target_addr:172.67.219.211:443
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:10.037	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38626	target_addr:172.67.168.140:443
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:13.582	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32854	target_addr:104.18.40.152:443
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:20.089	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53516	target_addr:104.21.86.125:443
time:2026-10-02T15:59:04Z	status:FAILURE	latency:171.652	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:243.533	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:536.715	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:543.247	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T15:59:04Z	status:HEALTHY	latency:558.377	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:04:04Z	status:UNKNOWN	latency:7.975	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:10.145	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41154	target_addr:172.67.219.211:443
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:10.392	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47526	target_addr:104.18.40.152:443
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:12.432	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41168	target_addr:172.67.219.211:443
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:12.492	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35740	target_addr:172.67.168.140:443
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:231.824	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:04:04Z	status:FAILURE	latency:245.749	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:451.422	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:467.003	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:04:04Z	status:HEALTHY	latency:580.736	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:09:04Z	status:UNKNOWN	latency:7.501	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:10.056	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42514	target_addr:104.18.40.152:443
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:10.724	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51474	target_addr:172.67.219.211:443
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:10.502	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51478	target_addr:172.67.219.211:443
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:11.062	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37730	target_addr:172.67.168.140:443
time:2026-10-02T16:09:04Z	status:FAILURE	latency:211.838	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:228.058	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:421.012	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:431.091	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:09:04Z	status:HEALTHY	latency:448.448	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:14:04Z	status:UNKNOWN	latency:6.332	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:11.739	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51666	target_addr:172.64.147.104:443
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:11.568	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51858	target_addr:172.67.219.211:443
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:11.693	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47484	target_addr:104.21.86.125:443
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:14.643	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41636	target_addr:104.21.26.208:443
time:2026-10-02T16:14:04Z	status:FAILURE	latency:28.085	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:233.211	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:448.263	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:452.351	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:14:04Z	status:HEALTHY	latency:496.899	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:19:04Z	status:UNKNOWN	latency:7.243	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:10.190	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38046	target_addr:172.64.147.104:443
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:10.650	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38934	target_addr:172.67.219.211:443
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:10.496	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38922	target_addr:172.67.219.211:443
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:11.832	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49844	target_addr:104.21.26.208:443
time:2026-10-02T16:19:04Z	status:FAILURE	latency:224.529	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:226.016	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:450.059	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:462.789	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:19:04Z	status:HEALTHY	latency:476.282	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:9.991	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38380	target_addr:172.67.168.140:443
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:10.959	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37334	target_addr:104.21.86.125:443
time:2026-10-02T16:24:04Z	status:UNKNOWN	latency:11.727	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:12.610	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37348	target_addr:104.21.86.125:443
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:13.192	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42724	target_addr:104.18.40.152:443
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:145.262	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:24:04Z	status:FAILURE	latency:185.010	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:461.941	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:546.494	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:24:04Z	status:HEALTHY	latency:631.032	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:29:04Z	status:UNKNOWN	latency:8.539	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:11.577	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33672	target_addr:172.64.147.104:443
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:12.683	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43914	target_addr:172.67.219.211:443
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:15.885	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43918	target_addr:172.67.219.211:443
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:35.809	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33342	target_addr:104.21.26.208:443
time:2026-10-02T16:29:04Z	status:FAILURE	latency:226.162	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:250.948	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:552.793	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:561.404	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:29:04Z	status:HEALTHY	latency:769.193	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:9.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46428	target_addr:172.64.147.104:443
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:12.268	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46354	target_addr:104.21.86.125:443
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:15.839	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46368	target_addr:104.21.86.125:443
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:16.719	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60090	target_addr:104.21.26.208:443
time:2026-10-02T16:34:04Z	status:UNKNOWN	latency:19.503	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:34:04Z	status:FAILURE	latency:173.458	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:295.942	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:459.566	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:472.859	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:34:04Z	status:HEALTHY	latency:498.583	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:10.076	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55850	target_addr:104.21.86.125:443
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:10.415	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45176	target_addr:172.64.147.104:443
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:10.459	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50082	target_addr:172.67.219.211:443
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:11.903	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42068	target_addr:104.21.26.208:443
time:2026-10-02T16:39:04Z	status:FAILURE	latency:26.480	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:39:04Z	status:UNKNOWN	latency:57.162	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:226.623	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:512.008	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:519.287	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:39:04Z	status:HEALTHY	latency:553.526	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:44:04Z	status:UNKNOWN	latency:7.326	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:11.173	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60454	target_addr:172.64.147.104:443
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:10.961	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56434	target_addr:104.21.26.208:443
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:11.968	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60916	target_addr:104.21.86.125:443
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:27.721	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60930	target_addr:104.21.86.125:443
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:106.709	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:44:04Z	status:FAILURE	latency:400.388	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:530.001	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:533.532	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:44:04Z	status:HEALTHY	latency:868.765	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:49:04Z	status:UNKNOWN	latency:6.314	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:8.016	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52148	target_addr:172.64.147.104:443
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:10.551	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39706	target_addr:172.67.168.140:443
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:13.688	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44150	target_addr:104.21.86.125:443
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:13.574	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44152	target_addr:104.21.86.125:443
time:2026-10-02T16:49:04Z	status:FAILURE	latency:24.470	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:146.657	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:425.243	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:454.342	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:49:04Z	status:HEALTHY	latency:748.382	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:54:04Z	status:UNKNOWN	latency:7.832	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:10.491	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50132	target_addr:172.64.147.104:443
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:11.355	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39196	target_addr:172.67.219.211:443
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:12.001	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48958	target_addr:172.67.168.140:443
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:15.287	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37376	target_addr:104.21.86.125:443
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:106.422	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:54:04Z	status:FAILURE	latency:188.180	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:753.239	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:769.389	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:54:04Z	status:HEALTHY	latency:804.883	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:59:04Z	status:UNKNOWN	latency:8.832	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:9.160	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54210	target_addr:104.18.40.152:443
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:10.160	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53238	target_addr:172.67.219.211:443
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:10.636	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45166	target_addr:104.21.26.208:443
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:11.091	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53230	target_addr:172.67.219.211:443
time:2026-10-02T16:59:04Z	status:FAILURE	latency:42.735	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:207.128	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:460.370	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:462.945	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T16:59:04Z	status:HEALTHY	latency:464.771	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:04:04Z	status:UNKNOWN	latency:7.556	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:10.210	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43224	target_addr:172.67.219.211:443
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:12.140	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60968	target_addr:172.64.147.104:443
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:11.949	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40854	target_addr:104.21.26.208:443
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:23.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43238	target_addr:172.67.219.211:443
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:56.163	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:73.168	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:97.661	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:04:04Z	status:HEALTHY	latency:220.663	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:04:04Z	status:FAILURE	latency:226.088	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:9.400	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56056	target_addr:172.67.219.211:443
time:2026-10-02T17:09:04Z	status:UNKNOWN	latency:10.553	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:10.584	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32950	target_addr:104.21.86.125:443
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:11.469	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36866	target_addr:104.21.26.208:443
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:12.057	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45620	target_addr:172.64.147.104:443
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:61.433	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:61.123	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:61.893	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:09:04Z	status:FAILURE	latency:230.488	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:09:04Z	status:HEALTHY	latency:241.070	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:14:04Z	status:UNKNOWN	latency:7.311	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:7.858	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54810	target_addr:172.64.147.104:443
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:8.459	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48298	target_addr:104.21.86.125:443
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:9.167	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48304	target_addr:104.21.86.125:443
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:9.172	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59820	target_addr:172.67.168.140:443
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:60.914	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:65.251	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:72.845	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:14:04Z	status:FAILURE	latency:232.553	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:14:04Z	status:HEALTHY	latency:243.124	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:8.619	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58054	target_addr:172.64.147.104:443
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:11.323	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46120	target_addr:172.67.168.140:443
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:11.634	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37782	target_addr:172.67.219.211:443
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:13.968	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37786	target_addr:172.67.219.211:443
time:2026-10-02T17:19:04Z	status:UNKNOWN	latency:35.386	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:65.575	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:67.927	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:77.077	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:19:04Z	status:FAILURE	latency:203.376	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:19:04Z	status:HEALTHY	latency:235.687	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:24:04Z	status:UNKNOWN	latency:7.627	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:11.748	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40186	target_addr:172.67.219.211:443
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:12.207	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33896	target_addr:104.21.86.125:443
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:12.762	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34360	target_addr:172.67.168.140:443
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:12.900	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38000	target_addr:172.64.147.104:443
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:58.735	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:66.367	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:133.643	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:24:04Z	status:HEALTHY	latency:243.096	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:24:04Z	status:FAILURE	latency:453.396	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:29:04Z	status:UNKNOWN	latency:6.716	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:8.943	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43552	target_addr:172.64.147.104:443
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:9.707	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59338	target_addr:104.21.86.125:443
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:10.305	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59340	target_addr:104.21.86.125:443
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:10.908	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48838	target_addr:104.21.26.208:443
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:62.577	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:64.533	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:86.440	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:29:04Z	status:FAILURE	latency:201.621	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:29:04Z	status:HEALTHY	latency:228.246	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:34:04Z	status:UNKNOWN	latency:7.520	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:13.078	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51298	target_addr:104.21.86.125:443
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:12.874	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40990	target_addr:104.18.40.152:443
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:13.588	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56478	target_addr:104.21.26.208:443
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:18.020	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51304	target_addr:104.21.86.125:443
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:62.236	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:62.190	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:69.008	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:34:04Z	status:FAILURE	latency:184.033	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:34:04Z	status:HEALTHY	latency:268.926	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:39:04Z	status:UNKNOWN	latency:8.549	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:12.089	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41070	target_addr:172.67.219.211:443
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:11.885	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59608	target_addr:104.21.86.125:443
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:13.684	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58178	target_addr:172.67.168.140:443
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:15.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52006	target_addr:104.18.40.152:443
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:63.617	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:68.630	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:100.409	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:39:04Z	status:FAILURE	latency:213.769	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:39:04Z	status:HEALTHY	latency:234.755	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:44:04Z	status:UNKNOWN	latency:9.763	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:12.756	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48516	target_addr:104.21.86.125:443
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:13.103	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58164	target_addr:104.21.26.208:443
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:13.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49816	target_addr:104.18.40.152:443
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:12.640	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45794	target_addr:172.67.219.211:443
time:2026-10-02T17:44:04Z	status:FAILURE	latency:32.329	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:58.413	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:67.318	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:92.040	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:44:04Z	status:HEALTHY	latency:236.827	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:8.993	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40912	target_addr:172.64.147.104:443
time:2026-10-02T17:49:04Z	status:UNKNOWN	latency:9.714	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:9.597	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58922	target_addr:172.67.219.211:443
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:10.468	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58388	target_addr:104.21.86.125:443
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:11.623	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43344	target_addr:172.67.168.140:443
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:65.637	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:71.582	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:79.346	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:49:04Z	status:FAILURE	latency:202.211	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:49:04Z	status:HEALTHY	latency:212.254	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:54:04Z	status:UNKNOWN	latency:6.924	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:9.705	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32998	target_addr:104.18.40.152:443
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:9.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52426	target_addr:104.21.26.208:443
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:10.093	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43810	target_addr:172.67.219.211:443
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:13.255	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41426	target_addr:104.21.86.125:443
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:58.575	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:61.781	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:75.244	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:54:04Z	status:FAILURE	latency:192.785	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:54:04Z	status:HEALTHY	latency:218.008	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:59:05Z	status:UNKNOWN	latency:8.167	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:11.696	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38268	target_addr:172.67.219.211:443
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:12.173	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45136	target_addr:172.64.147.104:443
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:12.604	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50030	target_addr:172.67.168.140:443
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:12.656	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34596	target_addr:104.21.86.125:443
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:55.732	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:60.855	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:79.328	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T17:59:05Z	status:FAILURE	latency:210.039	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T17:59:05Z	status:HEALTHY	latency:225.481	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:10.680	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34478	target_addr:172.67.219.211:443
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:12.457	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56016	target_addr:104.18.40.152:443
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:12.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37834	target_addr:172.67.168.140:443
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:25.191	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42992	target_addr:104.21.86.125:443
time:2026-10-02T18:04:05Z	status:UNKNOWN	latency:36.723	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:61.054	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:78.945	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:88.234	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:04:05Z	status:HEALTHY	latency:109.112	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:04:05Z	status:FAILURE	latency:201.906	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:09:05Z	status:UNKNOWN	latency:6.691	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:13.204	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60412	target_addr:104.21.26.208:443
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:12.829	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59906	target_addr:172.67.219.211:443
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:13.343	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49180	target_addr:104.18.40.152:443
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:14.623	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35352	target_addr:104.21.86.125:443
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:60.266	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:89.119	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:189.936	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:09:05Z	status:FAILURE	latency:209.800	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:09:05Z	status:HEALTHY	latency:263.709	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:14:05Z	status:UNKNOWN	latency:8.620	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:10.180	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44792	target_addr:104.21.86.125:443
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:11.981	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44796	target_addr:104.21.86.125:443
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:13.005	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43434	target_addr:172.64.147.104:443
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:15.243	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33958	target_addr:104.21.26.208:443
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:59.548	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:74.710	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:98.121	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:14:05Z	status:FAILURE	latency:179.860	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:14:05Z	status:HEALTHY	latency:463.206	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:19:05Z	status:UNKNOWN	latency:7.873	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:8.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36456	target_addr:172.64.147.104:443
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:10.836	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60506	target_addr:172.67.219.211:443
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:11.049	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53610	target_addr:104.21.86.125:443
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:13.925	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43798	target_addr:104.21.26.208:443
time:2026-10-02T18:19:05Z	status:FAILURE	latency:24.635	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:61.028	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:60.983	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:70.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:19:05Z	status:HEALTHY	latency:198.889	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:24:05Z	status:UNKNOWN	latency:8.090	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:11.968	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54138	target_addr:104.18.40.152:443
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:13.369	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44366	target_addr:172.67.219.211:443
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:13.058	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34096	target_addr:104.21.26.208:443
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:17.695	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48882	target_addr:104.21.86.125:443
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:77.335	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:82.454	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:86.233	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:24:05Z	status:FAILURE	latency:209.228	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:24:05Z	status:HEALTHY	latency:224.689	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:10.542	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51806	target_addr:172.64.147.104:443
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:12.926	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59434	target_addr:172.67.219.211:443
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:13.321	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35692	target_addr:104.21.26.208:443
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:15.400	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59448	target_addr:172.67.219.211:443
time:2026-10-02T18:29:05Z	status:FAILURE	latency:46.020	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:29:05Z	status:UNKNOWN	latency:57.235	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:60.473	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:62.435	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:65.393	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:29:05Z	status:HEALTHY	latency:276.188	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:34:05Z	status:UNKNOWN	latency:9.652	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:12.266	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46058	target_addr:104.18.40.152:443
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:12.451	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45846	target_addr:172.67.168.140:443
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:12.588	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41408	target_addr:104.21.86.125:443
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:14.734	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58414	target_addr:172.67.219.211:443
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:59.230	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:65.024	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:72.808	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:34:05Z	status:FAILURE	latency:206.319	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:34:05Z	status:HEALTHY	latency:238.515	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:39:05Z	status:UNKNOWN	latency:9.026	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:11.324	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43926	target_addr:172.67.219.211:443
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:11.732	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37560	target_addr:104.21.26.208:443
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:11.694	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40156	target_addr:104.21.86.125:443
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:14.088	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53748	target_addr:104.18.40.152:443
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:53.648	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:57.277	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:105.006	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:39:05Z	status:FAILURE	latency:149.578	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:39:05Z	status:HEALTHY	latency:208.728	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:11.023	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53436	target_addr:104.21.86.125:443
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:11.921	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53424	target_addr:104.21.86.125:443
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:11.795	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36488	target_addr:172.64.147.104:443
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:11.504	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52022	target_addr:104.21.26.208:443
time:2026-10-02T18:44:05Z	status:UNKNOWN	latency:36.665	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:60.272	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:64.471	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:76.530	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:44:05Z	status:FAILURE	latency:205.481	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:44:05Z	status:HEALTHY	latency:224.474	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:7.585	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59126	target_addr:104.18.40.152:443
time:2026-10-02T18:49:05Z	status:UNKNOWN	latency:8.093	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:10.944	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41136	target_addr:172.67.219.211:443
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:12.742	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60988	target_addr:104.21.26.208:443
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:13.269	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51582	target_addr:104.21.86.125:443
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:59.241	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:61.554	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:77.894	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:49:05Z	status:FAILURE	latency:200.855	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:49:05Z	status:HEALTHY	latency:348.688	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:54:05Z	status:UNKNOWN	latency:7.674	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:11.320	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56372	target_addr:172.64.147.104:443
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:12.010	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60288	target_addr:104.21.86.125:443
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:15.563	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50044	target_addr:172.67.168.140:443
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:16.100	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53276	target_addr:172.67.219.211:443
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:56.022	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:62.040	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:70.728	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:54:05Z	status:FAILURE	latency:236.624	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:54:05Z	status:HEALTHY	latency:253.669	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:59:05Z	status:UNKNOWN	latency:9.172	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:10.393	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37872	target_addr:104.21.86.125:443
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:11.680	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57560	target_addr:104.18.40.152:443
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:11.881	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37878	target_addr:104.21.86.125:443
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:12.297	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44466	target_addr:104.21.26.208:443
time:2026-10-02T18:59:05Z	status:FAILURE	latency:30.437	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:63.978	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:66.525	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:78.270	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T18:59:05Z	status:HEALTHY	latency:229.167	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:04:05Z	status:UNKNOWN	latency:8.726	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:12.837	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42598	target_addr:172.67.219.211:443
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:13.424	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52994	target_addr:104.18.40.152:443
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:13.124	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35306	target_addr:104.21.86.125:443
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:13.120	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59216	target_addr:104.21.26.208:443
time:2026-10-02T19:04:05Z	status:FAILURE	latency:32.845	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:58.922	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:60.884	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:60.780	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:04:05Z	status:HEALTHY	latency:217.595	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:09:05Z	status:UNKNOWN	latency:7.803	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:11.082	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51002	target_addr:172.64.147.104:443
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:11.647	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52578	target_addr:104.21.86.125:443
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:13.416	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44880	target_addr:172.67.219.211:443
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:16.991	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59862	target_addr:172.67.168.140:443
time:2026-10-02T19:09:05Z	status:FAILURE	latency:31.043	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:63.699	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:64.012	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:68.524	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:09:05Z	status:HEALTHY	latency:225.152	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:9.700	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53238	target_addr:104.21.86.125:443
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:10.348	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46294	target_addr:172.67.219.211:443
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:12.144	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36354	target_addr:104.21.26.208:443
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:18.867	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34188	target_addr:104.18.40.152:443
time:2026-10-02T19:14:05Z	status:UNKNOWN	latency:37.240	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:58.303	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:62.850	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:77.004	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:14:05Z	status:FAILURE	latency:218.194	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:14:05Z	status:HEALTHY	latency:249.284	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:19:05Z	status:UNKNOWN	latency:8.098	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:8.064	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36028	target_addr:172.64.147.104:443
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:11.076	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43616	target_addr:104.21.86.125:443
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:11.644	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38904	target_addr:104.21.26.208:443
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:12.058	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:172.67.219.211:443
time:2026-10-02T19:19:05Z	status:FAILURE	latency:34.035	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:58.464	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:93.174	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:228.587	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:19:05Z	status:HEALTHY	latency:930.784	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:24:05Z	status:UNKNOWN	latency:7.259	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:10.530	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55640	target_addr:104.18.40.152:443
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:9.897	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43928	target_addr:104.21.86.125:443
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:11.841	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41316	target_addr:172.67.168.140:443
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:11.729	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56706	target_addr:172.67.219.211:443
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:63.105	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:65.673	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:65.806	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:24:05Z	status:FAILURE	latency:189.494	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:24:05Z	status:HEALTHY	latency:294.352	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:29:05Z	status:UNKNOWN	latency:8.036	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:10.583	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42002	target_addr:104.18.40.152:443
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:11.680	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39224	target_addr:104.21.86.125:443
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:11.864	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56144	target_addr:172.67.168.140:443
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:19.918	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39238	target_addr:104.21.86.125:443
time:2026-10-02T19:29:05Z	status:FAILURE	latency:31.764	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:57.611	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:64.446	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:79.157	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:29:05Z	status:HEALTHY	latency:267.740	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:34:05Z	status:UNKNOWN	latency:6.614	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:10.137	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45734	target_addr:104.18.40.152:443
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:11.018	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40730	target_addr:104.21.26.208:443
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:11.300	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37780	target_addr:104.21.86.125:443
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:12.484	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37788	target_addr:104.21.86.125:443
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:63.010	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:68.404	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:73.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:34:05Z	status:HEALTHY	latency:218.782	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:34:05Z	status:FAILURE	latency:372.101	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:39:05Z	status:UNKNOWN	latency:8.324	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:9.794	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45350	target_addr:104.21.86.125:443
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:10.183	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45366	target_addr:104.21.86.125:443
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:11.179	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44958	target_addr:104.18.40.152:443
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:11.400	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38920	target_addr:104.21.26.208:443
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:57.838	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:63.881	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:63.970	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:39:05Z	status:FAILURE	latency:225.245	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:39:05Z	status:HEALTHY	latency:241.302	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:44:05Z	status:UNKNOWN	latency:6.204	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:9.697	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46522	target_addr:172.67.219.211:443
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:11.739	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51014	target_addr:172.64.147.104:443
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:12.437	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56528	target_addr:104.21.86.125:443
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:12.395	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58004	target_addr:172.67.168.140:443
time:2026-10-02T19:44:05Z	status:FAILURE	latency:38.273	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:68.494	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:119.045	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:279.407	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:44:05Z	status:HEALTHY	latency:511.219	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:49:05Z	status:UNKNOWN	latency:7.002	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:9.958	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36148	target_addr:104.21.26.208:443
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:9.693	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41330	target_addr:172.67.219.211:443
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:10.202	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33368	target_addr:104.21.86.125:443
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:12.674	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38116	target_addr:104.18.40.152:443
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:53.655	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:63.112	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:78.378	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:49:05Z	status:FAILURE	latency:217.586	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:49:05Z	status:HEALTHY	latency:226.135	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:54:05Z	status:UNKNOWN	latency:8.897	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:9.145	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57756	target_addr:104.21.26.208:443
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:10.502	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32874	target_addr:104.21.86.125:443
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:12.545	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44610	target_addr:172.64.147.104:443
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:14.797	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32888	target_addr:104.21.86.125:443
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:55.470	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:56.839	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:58.246	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:54:05Z	status:FAILURE	latency:222.328	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T19:54:05Z	status:HEALTHY	latency:242.350	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:8.060	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50408	target_addr:172.64.147.104:443
time:2026-10-02T19:59:05Z	status:UNKNOWN	latency:8.298	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:12.063	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52418	target_addr:104.21.86.125:443
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:13.563	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52426	target_addr:104.21.86.125:443
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:30.986	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44598	target_addr:172.67.168.140:443
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:61.596	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:74.442	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:135.975	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:59:05Z	status:HEALTHY	latency:209.295	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T19:59:05Z	status:FAILURE	latency:229.120	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:04:05Z	status:UNKNOWN	latency:9.093	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:11.600	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46980	target_addr:172.67.219.211:443
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:11.779	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53398	target_addr:104.21.86.125:443
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:11.609	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43664	target_addr:172.67.168.140:443
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:13.090	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53280	target_addr:172.64.147.104:443
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:58.581	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:61.004	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:107.701	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:04:05Z	status:FAILURE	latency:183.066	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:04:05Z	status:HEALTHY	latency:200.049	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:9.881	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43966	target_addr:172.67.219.211:443
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:11.365	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38424	target_addr:172.67.168.140:443
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:11.549	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46566	target_addr:104.18.40.152:443
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:12.400	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59066	target_addr:104.21.86.125:443
time:2026-10-02T20:09:05Z	status:FAILURE	latency:31.082	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:09:05Z	status:UNKNOWN	latency:32.375	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:64.715	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:65.090	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:79.416	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:09:05Z	status:HEALTHY	latency:216.492	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:9.836	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60802	target_addr:172.64.147.104:443
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:10.194	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43912	target_addr:104.21.86.125:443
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:11.355	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43916	target_addr:104.21.86.125:443
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:12.608	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37054	target_addr:172.67.168.140:443
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:55.010	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:14:05Z	status:UNKNOWN	latency:56.648	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:57.855	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:60.556	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:14:05Z	status:HEALTHY	latency:197.928	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:14:05Z	status:FAILURE	latency:207.108	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:19:05Z	status:UNKNOWN	latency:8.780	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:12.883	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43980	target_addr:172.67.219.211:443
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:13.368	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44134	target_addr:104.18.40.152:443
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:13.342	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43976	target_addr:172.67.219.211:443
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:30.019	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47428	target_addr:172.67.168.140:443
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:61.084	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:63.516	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:85.318	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:19:05Z	status:FAILURE	latency:199.799	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:19:05Z	status:HEALTHY	latency:202.660	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:24:05Z	status:UNKNOWN	latency:8.501	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:9.975	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51852	target_addr:172.67.168.140:443
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:11.369	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43698	target_addr:172.67.219.211:443
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:12.210	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43712	target_addr:172.67.219.211:443
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:14.727	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58004	target_addr:172.64.147.104:443
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:53.846	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:55.525	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:71.517	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:24:05Z	status:FAILURE	latency:212.978	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:24:05Z	status:HEALTHY	latency:215.806	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:29:05Z	status:UNKNOWN	latency:7.557	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:10.817	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44976	target_addr:172.67.168.140:443
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:12.790	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41442	target_addr:104.21.86.125:443
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:13.150	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49576	target_addr:172.64.147.104:443
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:14.886	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41446	target_addr:104.21.86.125:443
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:56.369	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:57.756	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:75.186	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:29:05Z	status:FAILURE	latency:187.603	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:29:05Z	status:HEALTHY	latency:219.334	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:34:05Z	status:UNKNOWN	latency:7.651	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:13.429	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59606	target_addr:172.67.168.140:443
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:14.120	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39884	target_addr:104.21.86.125:443
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:15.065	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40266	target_addr:172.67.219.211:443
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:17.669	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49630	target_addr:172.64.147.104:443
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:63.166	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:81.078	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:110.575	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:34:05Z	status:FAILURE	latency:203.317	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:34:05Z	status:HEALTHY	latency:253.468	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:39:05Z	status:UNKNOWN	latency:6.783	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:9.601	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56272	target_addr:172.67.168.140:443
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:9.925	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54794	target_addr:172.67.219.211:443
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:9.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49256	target_addr:104.18.40.152:443
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:11.176	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36952	target_addr:104.21.86.125:443
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:64.497	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:75.718	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:101.793	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:39:05Z	status:FAILURE	latency:187.723	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:39:05Z	status:HEALTHY	latency:207.274	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:44:05Z	status:UNKNOWN	latency:10.339	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:11.193	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54464	target_addr:104.18.40.152:443
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:10.933	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44772	target_addr:104.21.86.125:443
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:12.913	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54316	target_addr:172.67.219.211:443
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:13.620	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43806	target_addr:172.67.168.140:443
time:2026-10-02T20:44:05Z	status:FAILURE	latency:29.452	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:58.181	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:61.050	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:85.658	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:44:05Z	status:HEALTHY	latency:156.627	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:49:05Z	status:UNKNOWN	latency:8.977	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:9.939	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50040	target_addr:104.18.40.152:443
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:11.200	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50112	target_addr:104.21.86.125:443
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:11.215	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54456	target_addr:172.67.168.140:443
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:21.811	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33678	target_addr:172.67.219.211:443
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:60.330	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:66.271	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:82.126	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:49:05Z	status:HEALTHY	latency:208.544	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:49:05Z	status:FAILURE	latency:221.893	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:54:05Z	status:UNKNOWN	latency:7.997	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:10.040	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56010	target_addr:172.64.147.104:443
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:10.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38600	target_addr:104.21.86.125:443
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:10.988	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38602	target_addr:104.21.86.125:443
time:2026-10-02T20:54:05Z	status:FAILURE	latency:32.875	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:44.777	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42118	target_addr:104.21.26.208:443
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:64.096	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:65.441	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:71.761	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:54:05Z	status:HEALTHY	latency:459.674	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:8.446	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55934	target_addr:104.18.40.152:443
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:10.146	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54022	target_addr:172.67.168.140:443
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:10.713	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40026	target_addr:104.21.86.125:443
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:12.640	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40036	target_addr:104.21.86.125:443
time:2026-10-02T20:59:05Z	status:UNKNOWN	latency:35.649	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:61.784	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:63.394	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:59:05Z	status:FAILURE	latency:171.827	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:227.794	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T20:59:05Z	status:HEALTHY	latency:362.693	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:04:05Z	status:UNKNOWN	latency:7.336	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:12.758	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49182	target_addr:104.21.26.208:443
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:12.706	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35510	target_addr:104.18.40.152:443
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:13.575	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35840	target_addr:104.21.86.125:443
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:13.569	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40494	target_addr:172.67.219.211:443
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:57.552	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:61.035	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:64.668	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:04:05Z	status:FAILURE	latency:188.128	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:04:05Z	status:HEALTHY	latency:227.577	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:09:05Z	status:UNKNOWN	latency:7.352	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:10.626	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49736	target_addr:104.21.86.125:443
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:11.521	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49748	target_addr:104.21.86.125:443
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:13.396	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48078	target_addr:172.64.147.104:443
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:14.296	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58680	target_addr:172.67.168.140:443
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:60.401	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:64.668	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:124.618	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:09:05Z	status:FAILURE	latency:196.162	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:09:05Z	status:HEALTHY	latency:253.683	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:9.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56768	target_addr:104.18.40.152:443
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:9.085	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48998	target_addr:172.67.219.211:443
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:9.621	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47314	target_addr:104.21.26.208:443
time:2026-10-02T21:14:05Z	status:UNKNOWN	latency:26.094	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:35.353	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49010	target_addr:172.67.219.211:443
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:65.003	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:72.359	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:14:05Z	status:FAILURE	latency:217.665	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:238.684	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:14:05Z	status:HEALTHY	latency:822.460	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:19:05Z	status:UNKNOWN	latency:7.821	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:8.515	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51758	target_addr:172.67.219.211:443
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:9.731	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39312	target_addr:104.18.40.152:443
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:10.495	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51760	target_addr:172.67.219.211:443
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:11.489	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47562	target_addr:172.67.168.140:443
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:60.519	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:60.237	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:66.488	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:19:05Z	status:FAILURE	latency:222.520	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:19:05Z	status:HEALTHY	latency:230.427	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:24:05Z	status:UNKNOWN	latency:8.249	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:10.788	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52542	target_addr:172.67.168.140:443
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:12.032	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50842	target_addr:104.21.86.125:443
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:13.723	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45920	target_addr:172.67.219.211:443
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:15.081	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34298	target_addr:104.18.40.152:443
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:59.576	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:73.350	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:83.227	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:24:05Z	status:FAILURE	latency:184.478	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:24:05Z	status:HEALTHY	latency:245.647	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:29:05Z	status:UNKNOWN	latency:7.129	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:9.128	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44912	target_addr:104.18.40.152:443
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:11.243	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57680	target_addr:104.21.86.125:443
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:11.680	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48762	target_addr:104.21.26.208:443
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:16.532	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51664	target_addr:172.67.219.211:443
time:2026-10-02T21:29:05Z	status:FAILURE	latency:26.316	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:58.160	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:58.073	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:58.894	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:29:05Z	status:HEALTHY	latency:264.399	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:34:05Z	status:UNKNOWN	latency:9.855	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:10.240	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34964	target_addr:104.21.86.125:443
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:10.665	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41984	target_addr:172.67.168.140:443
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:12.262	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38044	target_addr:172.67.219.211:443
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:15.603	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59224	target_addr:104.18.40.152:443
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:217.269	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:34:05Z	status:FAILURE	latency:229.320	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:771.445	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:784.969	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:34:05Z	status:HEALTHY	latency:919.333	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:39:05Z	status:UNKNOWN	latency:9.756	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:11.183	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53122	target_addr:104.21.86.125:443
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:11.729	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53124	target_addr:104.21.86.125:443
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:12.036	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40524	target_addr:172.67.168.140:443
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:12.801	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57064	target_addr:104.18.40.152:443
time:2026-10-02T21:39:05Z	status:FAILURE	latency:148.057	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:206.139	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:459.235	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:566.784	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:39:05Z	status:HEALTHY	latency:712.261	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:44:05Z	status:UNKNOWN	latency:7.439	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:9.976	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49462	target_addr:172.67.168.140:443
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:11.824	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58360	target_addr:172.67.219.211:443
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:11.446	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46592	target_addr:172.64.147.104:443
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:12.788	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39260	target_addr:104.21.86.125:443
time:2026-10-02T21:44:05Z	status:FAILURE	latency:195.683	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:207.928	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:428.586	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:457.316	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:44:05Z	status:HEALTHY	latency:472.225	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:49:06Z	status:UNKNOWN	latency:6.657	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:9.586	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53838	target_addr:104.21.86.125:443
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:10.332	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39842	target_addr:172.67.168.140:443
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:10.683	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53852	target_addr:104.21.86.125:443
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:13.600	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56672	target_addr:104.18.40.152:443
time:2026-10-02T21:49:06Z	status:FAILURE	latency:170.059	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:259.688	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:438.401	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:447.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:49:06Z	status:HEALTHY	latency:699.943	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:54:06Z	status:UNKNOWN	latency:7.630	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:9.294	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51404	target_addr:172.64.147.104:443
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:9.569	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49554	target_addr:104.21.86.125:443
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:11.442	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56750	target_addr:172.67.168.140:443
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:12.270	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35902	target_addr:172.67.219.211:443
time:2026-10-02T21:54:06Z	status:FAILURE	latency:172.963	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:252.256	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:455.662	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:759.047	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:54:06Z	status:HEALTHY	latency:774.702	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:59:06Z	status:UNKNOWN	latency:6.753	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:9.940	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59244	target_addr:172.67.168.140:443
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:11.703	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43830	target_addr:172.64.147.104:443
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:11.900	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51212	target_addr:104.21.86.125:443
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:17.418	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51216	target_addr:104.21.86.125:443
time:2026-10-02T21:59:06Z	status:FAILURE	latency:200.088	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:229.192	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:443.759	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:452.529	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T21:59:06Z	status:HEALTHY	latency:463.213	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:04:06Z	status:UNKNOWN	latency:7.583	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:10.688	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55610	target_addr:104.18.40.152:443
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:14.866	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33612	target_addr:172.67.219.211:443
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:29.239	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33616	target_addr:172.67.219.211:443
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:32.711	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53662	target_addr:104.21.26.208:443
time:2026-10-02T22:04:06Z	status:FAILURE	latency:141.550	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:207.830	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:384.334	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:523.001	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:04:06Z	status:HEALTHY	latency:592.099	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:09:06Z	status:UNKNOWN	latency:12.141	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:11.721	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33182	target_addr:104.21.86.125:443
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:12.200	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49420	target_addr:172.64.147.104:443
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:11.890	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33170	target_addr:104.21.86.125:443
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:12.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42466	target_addr:104.21.26.208:443
time:2026-10-02T22:09:06Z	status:FAILURE	latency:146.425	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:223.933	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:419.041	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:424.816	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:09:06Z	status:HEALTHY	latency:678.866	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:10.407	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57408	target_addr:172.67.219.211:443
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:11.439	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35112	target_addr:172.64.147.104:443
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:13.318	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47544	target_addr:172.67.168.140:443
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:20.562	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57468	target_addr:104.21.86.125:443
time:2026-10-02T22:14:06Z	status:UNKNOWN	latency:55.541	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:14:06Z	status:FAILURE	latency:231.944	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:238.409	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:439.687	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:492.692	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:14:06Z	status:HEALTHY	latency:494.070	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:10.268	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33638	target_addr:104.21.26.208:443
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:10.301	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44436	target_addr:172.64.147.104:443
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:11.965	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47084	target_addr:104.21.86.125:443
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:13.744	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44656	target_addr:172.67.219.211:443
time:2026-10-02T22:19:06Z	status:UNKNOWN	latency:24.316	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:19:06Z	status:FAILURE	latency:37.681	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:210.423	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:518.602	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:754.577	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:19:06Z	status:HEALTHY	latency:872.061	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:9.810	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59730	target_addr:172.64.147.104:443
time:2026-10-02T22:24:06Z	status:UNKNOWN	latency:10.192	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:10.059	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44890	target_addr:172.67.219.211:443
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:12.919	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40712	target_addr:172.67.168.140:443
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:18.805	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44892	target_addr:172.67.219.211:443
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:222.989	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:24:06Z	status:FAILURE	latency:225.299	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:463.308	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:493.196	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:24:06Z	status:HEALTHY	latency:512.576	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:29:06Z	status:UNKNOWN	latency:7.830	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:10.080	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36406	target_addr:104.21.86.125:443
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:10.021	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35520	target_addr:172.67.168.140:443
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:16.817	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36416	target_addr:104.21.86.125:443
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:17.480	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59620	target_addr:172.64.147.104:443
time:2026-10-02T22:29:06Z	status:FAILURE	latency:175.369	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:216.576	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:449.983	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:516.155	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:29:06Z	status:HEALTHY	latency:523.741	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:34:06Z	status:UNKNOWN	latency:7.743	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:10.206	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58298	target_addr:172.67.219.211:443
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:10.659	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53092	target_addr:104.21.26.208:443
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:11.058	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60910	target_addr:172.64.147.104:443
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:21.457	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58310	target_addr:172.67.219.211:443
time:2026-10-02T22:34:06Z	status:FAILURE	latency:212.918	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:218.669	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:388.783	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:494.924	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:34:06Z	status:HEALTHY	latency:504.004	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:39:06Z	status:UNKNOWN	latency:9.438	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:12.301	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46014	target_addr:104.21.26.208:443
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:12.727	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59262	target_addr:172.64.147.104:443
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:12.386	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53144	target_addr:104.21.86.125:443
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:12.465	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33576	target_addr:172.67.219.211:443
time:2026-10-02T22:39:06Z	status:FAILURE	latency:230.060	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:232.194	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:700.427	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:736.595	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:39:06Z	status:HEALTHY	latency:825.050	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:44:06Z	status:UNKNOWN	latency:6.420	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:9.425	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59662	target_addr:104.21.86.125:443
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:10.002	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51810	target_addr:104.18.40.152:443
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:10.754	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59674	target_addr:104.21.86.125:443
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:10.768	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50308	target_addr:172.67.168.140:443
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:201.276	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:44:06Z	status:FAILURE	latency:215.240	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:417.509	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:464.016	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:44:06Z	status:HEALTHY	latency:477.251	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:49:06Z	status:UNKNOWN	latency:7.094	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:8.766	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52462	target_addr:104.18.40.152:443
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:9.615	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44770	target_addr:172.67.219.211:443
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:9.833	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45442	target_addr:172.67.168.140:443
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:11.797	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36122	target_addr:104.21.86.125:443
time:2026-10-02T22:49:06Z	status:FAILURE	latency:221.832	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:268.031	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:457.927	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:474.406	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:49:06Z	status:HEALTHY	latency:480.861	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:54:06Z	status:UNKNOWN	latency:9.228	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:9.358	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56684	target_addr:172.67.219.211:443
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:9.714	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51702	target_addr:172.67.168.140:443
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:11.029	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38098	target_addr:104.18.40.152:443
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:14.294	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56696	target_addr:172.67.219.211:443
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:130.902	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:54:06Z	status:FAILURE	latency:184.281	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:578.967	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:602.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:54:06Z	status:HEALTHY	latency:822.464	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:13.218	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37712	target_addr:172.67.219.211:443
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:13.079	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37720	target_addr:172.67.219.211:443
time:2026-10-02T22:59:06Z	status:UNKNOWN	latency:15.232	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:15.108	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59276	target_addr:172.67.168.140:443
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:15.238	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33522	target_addr:104.18.40.152:443
time:2026-10-02T22:59:06Z	status:FAILURE	latency:196.837	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:224.109	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:429.640	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:437.478	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T22:59:06Z	status:HEALTHY	latency:457.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:04:06Z	status:UNKNOWN	latency:9.935	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:10.778	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52470	target_addr:104.18.40.152:443
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:11.842	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35000	target_addr:104.21.26.208:443
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:12.516	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56778	target_addr:104.21.86.125:443
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:15.305	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35524	target_addr:172.67.219.211:443
time:2026-10-02T23:04:06Z	status:FAILURE	latency:35.727	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:67.289	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:75.625	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:83.750	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:04:06Z	status:HEALTHY	latency:290.214	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:10.716	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47762	target_addr:172.67.219.211:443
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:10.703	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47748	target_addr:172.67.219.211:443
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:12.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59518	target_addr:104.21.26.208:443
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:20.010	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40188	target_addr:104.18.40.152:443
time:2026-10-02T23:09:06Z	status:FAILURE	latency:31.861	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:09:06Z	status:UNKNOWN	latency:36.049	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:64.203	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:71.347	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:77.825	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:09:06Z	status:HEALTHY	latency:238.355	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:14:06Z	status:UNKNOWN	latency:9.953	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:10.895	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46250	target_addr:172.67.219.211:443
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:14.033	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46266	target_addr:172.67.219.211:443
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:14.726	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47068	target_addr:172.64.147.104:443
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:14.613	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34712	target_addr:104.21.26.208:443
time:2026-10-02T23:14:06Z	status:FAILURE	latency:200.183	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:242.421	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:728.503	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:731.342	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:14:06Z	status:HEALTHY	latency:740.869	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:19:06Z	status:UNKNOWN	latency:6.654	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:9.410	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34622	target_addr:172.67.219.211:443
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:10.369	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42212	target_addr:104.21.86.125:443
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:11.842	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44544	target_addr:104.18.40.152:443
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:12.008	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48228	target_addr:104.21.26.208:443
time:2026-10-02T23:19:06Z	status:FAILURE	latency:42.860	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:270.658	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:689.130	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:696.144	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:19:06Z	status:HEALTHY	latency:1430.959	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:24:06Z	status:UNKNOWN	latency:8.138	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:10.410	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44766	target_addr:104.21.26.208:443
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:12.182	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35678	target_addr:172.64.147.104:443
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:13.510	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36244	target_addr:104.21.86.125:443
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:13.755	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36254	target_addr:104.21.86.125:443
time:2026-10-02T23:24:06Z	status:FAILURE	latency:175.027	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:253.054	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:432.934	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:433.038	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:24:06Z	status:HEALTHY	latency:712.981	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:29:06Z	status:UNKNOWN	latency:7.967	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:10.337	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43430	target_addr:172.67.219.211:443
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:10.857	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57940	target_addr:104.21.26.208:443
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:12.374	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47470	target_addr:172.64.147.104:443
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:12.037	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43444	target_addr:172.67.219.211:443
time:2026-10-02T23:29:06Z	status:FAILURE	latency:205.087	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:458.874	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:534.609	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:852.094	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:29:06Z	status:HEALTHY	latency:860.630	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:34:06Z	status:UNKNOWN	latency:6.332	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:10.952	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53596	target_addr:172.67.219.211:443
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:10.996	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57312	target_addr:104.21.86.125:443
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:15.940	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44604	target_addr:104.21.26.208:443
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:21.042	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40098	target_addr:172.64.147.104:443
time:2026-10-02T23:34:06Z	status:FAILURE	latency:27.852	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:209.674	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:820.688	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:835.944	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:34:06Z	status:HEALTHY	latency:1402.247	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:39:06Z	status:UNKNOWN	latency:9.516	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:10.745	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44930	target_addr:104.21.86.125:443
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:10.718	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35842	target_addr:172.67.168.140:443
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:12.572	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52852	target_addr:172.67.219.211:443
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:13.013	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41936	target_addr:172.64.147.104:443
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:188.360	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:39:06Z	status:FAILURE	latency:210.785	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:624.629	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:626.327	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:39:06Z	status:HEALTHY	latency:745.232	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:44:06Z	status:UNKNOWN	latency:7.817	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:10.862	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41492	target_addr:104.21.26.208:443
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:11.006	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56456	target_addr:172.64.147.104:443
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:10.972	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53804	target_addr:172.67.219.211:443
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:14.499	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53808	target_addr:172.67.219.211:443
time:2026-10-02T23:44:06Z	status:FAILURE	latency:21.437	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:251.974	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:422.504	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:437.679	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:44:06Z	status:HEALTHY	latency:440.736	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:49:06Z	status:UNKNOWN	latency:8.967	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:11.122	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60180	target_addr:104.21.26.208:443
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:11.429	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53820	target_addr:172.67.219.211:443
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:11.423	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50946	target_addr:104.21.86.125:443
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:16.075	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60546	target_addr:104.18.40.152:443
time:2026-10-02T23:49:06Z	status:FAILURE	latency:197.937	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:263.279	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:844.223	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:843.719	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:49:06Z	status:HEALTHY	latency:849.938	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:54:06Z	status:UNKNOWN	latency:7.851	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:11.639	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51210	target_addr:172.64.147.104:443
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:11.464	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35978	target_addr:104.21.86.125:443
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:11.918	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35222	target_addr:104.21.26.208:443
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:12.988	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53438	target_addr:172.67.219.211:443
time:2026-10-02T23:54:06Z	status:FAILURE	latency:172.516	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:251.957	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:445.371	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:452.438	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:54:06Z	status:HEALTHY	latency:732.565	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:59:06Z	status:UNKNOWN	latency:8.095	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:10.832	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35212	target_addr:104.21.86.125:443
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:11.600	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52598	target_addr:172.67.168.140:443
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:11.840	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40938	target_addr:104.18.40.152:443
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:19.052	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35218	target_addr:104.21.86.125:443
time:2026-10-02T23:59:06Z	status:FAILURE	latency:176.547	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:216.991	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:434.947	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:445.278	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-02T23:59:06Z	status:HEALTHY	latency:450.295	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:04:06Z	status:UNKNOWN	latency:8.061	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:8.654	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41680	target_addr:104.18.40.152:443
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:9.345	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39294	target_addr:104.21.86.125:443
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:11.335	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33418	target_addr:172.67.168.140:443
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:11.904	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39298	target_addr:104.21.86.125:443
time:2026-10-03T00:04:06Z	status:FAILURE	latency:20.932	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:58.186	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:59.554	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:84.238	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:04:06Z	status:HEALTHY	latency:381.787	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:09:06Z	status:UNKNOWN	latency:7.167	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:10.326	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42510	target_addr:172.67.168.140:443
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:13.432	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38266	target_addr:172.67.219.211:443
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:16.693	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59464	target_addr:104.21.86.125:443
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:20.935	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47674	target_addr:172.64.147.104:443
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:55.270	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:64.875	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:65.739	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:09:06Z	status:FAILURE	latency:200.144	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:09:06Z	status:HEALTHY	latency:344.733	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:14:06Z	status:UNKNOWN	latency:7.831	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:9.735	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44256	target_addr:172.67.168.140:443
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:10.194	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53372	target_addr:104.18.40.152:443
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:10.182	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45522	target_addr:172.67.219.211:443
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:12.918	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49040	target_addr:104.21.86.125:443
time:2026-10-03T00:14:06Z	status:FAILURE	latency:198.013	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:206.616	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:456.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:509.819	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:14:06Z	status:HEALTHY	latency:514.687	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:19:06Z	status:UNKNOWN	latency:9.431	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:9.751	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50256	target_addr:172.64.147.104:443
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:11.729	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40218	target_addr:104.21.26.208:443
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:13.006	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57986	target_addr:104.21.86.125:443
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:13.509	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57988	target_addr:104.21.86.125:443
time:2026-10-03T00:19:06Z	status:FAILURE	latency:219.156	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:269.599	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:472.974	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:667.279	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:19:06Z	status:HEALTHY	latency:725.405	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:24:06Z	status:UNKNOWN	latency:7.826	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:14.407	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42910	target_addr:172.67.219.211:443
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:20.551	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42926	target_addr:172.67.219.211:443
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:44.181	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56520	target_addr:172.67.168.140:443
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:47.732	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53664	target_addr:172.64.147.104:443
time:2026-10-03T00:24:06Z	status:FAILURE	latency:174.894	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:325.268	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:497.348	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:751.012	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:24:06Z	status:HEALTHY	latency:779.764	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:29:06Z	status:UNKNOWN	latency:8.172	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:13.646	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57428	target_addr:104.21.26.208:443
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:13.221	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37682	target_addr:104.21.86.125:443
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:13.755	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60606	target_addr:172.64.147.104:443
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:13.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37694	target_addr:104.21.86.125:443
time:2026-10-03T00:29:06Z	status:FAILURE	latency:216.866	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:236.119	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:489.224	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:726.730	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:29:06Z	status:HEALTHY	latency:734.912	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:12.000	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60154	target_addr:172.64.147.104:443
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:18.982	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44730	target_addr:172.67.168.140:443
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:19.289	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37818	target_addr:172.67.219.211:443
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:56.483	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:34:06Z	status:UNKNOWN	latency:57.219	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:62.219	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:68.026	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37824	target_addr:172.67.219.211:443
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:72.851	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:34:06Z	status:FAILURE	latency:226.310	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:34:06Z	status:HEALTHY	latency:260.171	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:9.930	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49328	target_addr:172.67.168.140:443
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:11.198	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35888	target_addr:104.21.86.125:443
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:11.434	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36588	target_addr:172.67.219.211:443
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:11.747	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60616	target_addr:104.18.40.152:443
time:2026-10-03T00:39:06Z	status:UNKNOWN	latency:33.302	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:53.680	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:63.380	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:65.925	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:39:06Z	status:HEALTHY	latency:225.721	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:39:06Z	status:FAILURE	latency:339.380	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:44:06Z	status:UNKNOWN	latency:7.774	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:12.883	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57810	target_addr:104.21.86.125:443
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:13.076	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57794	target_addr:104.21.86.125:443
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:13.304	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48738	target_addr:172.67.168.140:443
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:16.062	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41264	target_addr:172.64.147.104:443
time:2026-10-03T00:44:06Z	status:FAILURE	latency:35.238	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:70.039	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:69.753	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:73.881	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:44:06Z	status:HEALTHY	latency:248.461	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:9.762	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59814	target_addr:172.67.219.211:443
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:9.259	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46208	target_addr:104.21.86.125:443
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:10.328	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39242	target_addr:104.21.26.208:443
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:10.796	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52516	target_addr:172.64.147.104:443
time:2026-10-03T00:49:06Z	status:FAILURE	latency:27.631	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:58.409	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:62.613	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:49:06Z	status:UNKNOWN	latency:75.086	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:137.140	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:49:06Z	status:HEALTHY	latency:270.567	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:54:06Z	status:UNKNOWN	latency:8.359	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:11.460	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45956	target_addr:104.21.86.125:443
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:12.385	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36160	target_addr:172.64.147.104:443
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:12.278	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50200	target_addr:172.67.219.211:443
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:19.229	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39748	target_addr:104.21.26.208:443
time:2026-10-03T00:54:06Z	status:FAILURE	latency:228.801	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:246.491	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:379.543	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:390.851	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:54:06Z	status:HEALTHY	latency:701.592	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:59:06Z	status:UNKNOWN	latency:10.645	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:10.724	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50698	target_addr:172.64.147.104:443
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:13.472	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54362	target_addr:172.67.219.211:443
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:13.265	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54506	target_addr:104.21.86.125:443
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:13.394	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:104.21.26.208:443
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:63.640	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:71.457	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:83.821	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T00:59:06Z	status:FAILURE	latency:235.675	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T00:59:06Z	status:HEALTHY	latency:291.795	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:8.445	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34602	target_addr:172.64.147.104:443
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:9.512	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39042	target_addr:104.21.86.125:443
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:12.950	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59492	target_addr:104.21.26.208:443
time:2026-10-03T01:04:06Z	status:FAILURE	latency:29.541	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:50.272	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:56.791	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:124.731	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:135.721	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39056	target_addr:104.21.86.125:443
time:2026-10-03T01:04:06Z	status:HEALTHY	latency:278.010	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:04:06Z	status:UNKNOWN	latency:407.071	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:9.092	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39866	target_addr:172.67.219.211:443
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:9.782	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45802	target_addr:104.21.26.208:443
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:10.100	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39874	target_addr:172.67.219.211:443
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:12.569	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59792	target_addr:104.18.40.152:443
time:2026-10-03T01:09:06Z	status:UNKNOWN	latency:17.420	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:75.289	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:84.431	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:09:06Z	status:FAILURE	latency:188.972	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:201.897	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:09:06Z	status:HEALTHY	latency:224.568	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:14:06Z	status:UNKNOWN	latency:9.767	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:11.270	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52488	target_addr:172.67.219.211:443
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:11.282	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34872	target_addr:104.21.86.125:443
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:21.637	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52294	target_addr:104.21.26.208:443
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:39.673	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37008	target_addr:104.18.40.152:443
time:2026-10-03T01:14:06Z	status:FAILURE	latency:230.932	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:303.983	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:443.455	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:489.296	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:14:06Z	status:HEALTHY	latency:496.583	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:19:06Z	status:UNKNOWN	latency:8.396	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:13.005	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54840	target_addr:104.18.40.152:443
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:13.341	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48188	target_addr:172.67.219.211:443
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:13.920	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57950	target_addr:172.67.168.140:443
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:20.292	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42652	target_addr:104.21.86.125:443
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:59.364	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:113.226	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:219.432	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:19:06Z	status:FAILURE	latency:235.141	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:19:06Z	status:HEALTHY	latency:296.711	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:24:06Z	status:UNKNOWN	latency:8.173	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:10.785	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60902	target_addr:104.21.26.208:443
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:12.028	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41754	target_addr:172.64.147.104:443
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:11.965	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58934	target_addr:104.21.86.125:443
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:12.915	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58936	target_addr:104.21.86.125:443
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:74.350	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:121.753	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:24:06Z	status:FAILURE	latency:224.986	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:248.137	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:24:06Z	status:HEALTHY	latency:985.735	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:29:06Z	status:UNKNOWN	latency:8.237	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:8.967	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46230	target_addr:104.21.86.125:443
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:10.346	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46732	target_addr:172.67.168.140:443
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:12.279	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45094	target_addr:172.64.147.104:443
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:14.401	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46236	target_addr:104.21.86.125:443
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:67.833	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:71.336	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:116.181	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:29:06Z	status:FAILURE	latency:218.044	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:29:06Z	status:HEALTHY	latency:305.619	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:34:06Z	status:UNKNOWN	latency:10.802	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:16.947	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57704	target_addr:104.18.40.152:443
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:19.374	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51100	target_addr:104.21.86.125:443
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:19.473	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51108	target_addr:104.21.86.125:443
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:57.472	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36452	target_addr:172.67.168.140:443
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:59.788	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:62.374	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:77.384	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:34:06Z	status:FAILURE	latency:218.402	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:34:06Z	status:HEALTHY	latency:288.418	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:10.067	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43378	target_addr:104.18.40.152:443
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:11.121	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45842	target_addr:104.21.26.208:443
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:13.160	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59486	target_addr:104.21.86.125:443
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:13.624	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59482	target_addr:104.21.86.125:443
time:2026-10-03T01:39:06Z	status:UNKNOWN	latency:28.113	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:65.628	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:279.687	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:280.210	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:39:06Z	status:FAILURE	latency:291.743	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:39:06Z	status:HEALTHY	latency:734.326	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:44:06Z	status:UNKNOWN	latency:7.530	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:10.296	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48158	target_addr:172.64.147.104:443
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:10.498	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60644	target_addr:172.67.219.211:443
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:11.180	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49976	target_addr:104.21.86.125:443
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:17.774	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43322	target_addr:104.21.26.208:443
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:58.408	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:64.539	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:82.361	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:44:06Z	status:FAILURE	latency:237.563	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:44:06Z	status:HEALTHY	latency:319.734	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:49:06Z	status:UNKNOWN	latency:9.014	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:12.630	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54362	target_addr:104.21.26.208:443
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:12.807	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48806	target_addr:172.64.147.104:443
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:17.350	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58436	target_addr:172.67.219.211:443
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:17.471	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49946	target_addr:104.21.86.125:443
time:2026-10-03T01:49:06Z	status:FAILURE	latency:206.640	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:447.491	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:467.138	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:516.008	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:49:06Z	status:HEALTHY	latency:1157.454	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:54:06Z	status:UNKNOWN	latency:8.012	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:12.148	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40766	target_addr:104.21.86.125:443
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:13.856	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51160	target_addr:172.67.168.140:443
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:16.393	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58484	target_addr:172.67.219.211:443
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:28.343	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53152	target_addr:172.64.147.104:443
time:2026-10-03T01:54:06Z	status:FAILURE	latency:193.090	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:374.918	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:433.946	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:434.806	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:54:06Z	status:HEALTHY	latency:469.707	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:59:06Z	status:UNKNOWN	latency:7.868	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:12.965	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58510	target_addr:172.67.168.140:443
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:12.749	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36650	target_addr:172.67.219.211:443
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:13.118	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37710	target_addr:172.64.147.104:443
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:126.934	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34060	target_addr:104.21.86.125:443
time:2026-10-03T01:59:06Z	status:FAILURE	latency:203.754	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:321.706	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:512.501	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:533.486	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T01:59:06Z	status:HEALTHY	latency:546.326	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:04:06Z	status:UNKNOWN	latency:6.578	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:10.261	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49192	target_addr:104.21.86.125:443
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:11.859	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49198	target_addr:104.21.86.125:443
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:18.553	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56186	target_addr:172.67.168.140:443
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:38.488	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38538	target_addr:104.18.40.152:443
time:2026-10-03T02:04:06Z	status:FAILURE	latency:44.310	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:257.732	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:506.208	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:536.080	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:04:06Z	status:HEALTHY	latency:562.115	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:09:06Z	status:UNKNOWN	latency:11.034	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:11.567	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53872	target_addr:104.18.40.152:443
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:11.880	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45088	target_addr:172.67.219.211:443
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:13.594	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40556	target_addr:104.21.26.208:443
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:13.589	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45104	target_addr:172.67.219.211:443
time:2026-10-03T02:09:06Z	status:FAILURE	latency:216.129	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:264.846	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:431.289	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:782.897	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:09:06Z	status:HEALTHY	latency:1097.924	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:14:07Z	status:UNKNOWN	latency:8.793	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:12.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39092	target_addr:172.67.219.211:443
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:12.870	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42370	target_addr:172.67.168.140:443
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:14.877	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54248	target_addr:104.21.86.125:443
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:16.760	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47468	target_addr:172.64.147.104:443
time:2026-10-03T02:14:07Z	status:FAILURE	latency:216.975	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:343.986	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:458.638	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:492.561	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:14:07Z	status:HEALTHY	latency:1313.989	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:19:07Z	status:UNKNOWN	latency:10.971	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:10.709	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44522	target_addr:104.21.86.125:443
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:13.363	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59166	target_addr:172.67.168.140:443
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:13.773	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44520	target_addr:104.21.86.125:443
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:20.567	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42608	target_addr:172.64.147.104:443
time:2026-10-03T02:19:07Z	status:FAILURE	latency:32.753	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:79.064	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:102.556	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:266.890	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:19:07Z	status:HEALTHY	latency:297.238	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:12.407	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54106	target_addr:172.67.219.211:443
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:12.133	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59684	target_addr:104.18.40.152:443
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:12.353	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42428	target_addr:172.67.168.140:443
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:18.810	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54118	target_addr:172.67.219.211:443
time:2026-10-03T02:24:07Z	status:UNKNOWN	latency:19.939	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:59.943	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:97.050	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:24:07Z	status:FAILURE	latency:196.231	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:251.931	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:24:07Z	status:HEALTHY	latency:265.529	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:29:07Z	status:UNKNOWN	latency:7.938	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:9.807	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60424	target_addr:172.67.219.211:443
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:10.981	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56802	target_addr:104.18.40.152:443
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:26.874	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59244	target_addr:104.21.86.125:443
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:44.769	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58340	target_addr:104.21.26.208:443
time:2026-10-03T02:29:07Z	status:FAILURE	latency:146.131	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:295.283	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:451.919	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:465.435	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:29:07Z	status:HEALTHY	latency:682.143	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:9.624	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54234	target_addr:172.64.147.104:443
time:2026-10-03T02:34:07Z	status:UNKNOWN	latency:11.093	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:13.287	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47584	target_addr:104.21.26.208:443
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:13.112	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44852	target_addr:104.21.86.125:443
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:17.455	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51118	target_addr:172.67.219.211:443
time:2026-10-03T02:34:07Z	status:FAILURE	latency:208.881	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:241.275	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:545.135	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:547.415	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:34:07Z	status:HEALTHY	latency:560.114	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:9.069	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52702	target_addr:104.18.40.152:443
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:11.246	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55650	target_addr:104.21.26.208:443
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:15.040	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60668	target_addr:104.21.86.125:443
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:18.232	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60670	target_addr:104.21.86.125:443
time:2026-10-03T02:39:07Z	status:UNKNOWN	latency:56.608	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:39:07Z	status:FAILURE	latency:181.704	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:229.734	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:376.295	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:535.948	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:39:07Z	status:HEALTHY	latency:550.256	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:44:07Z	status:UNKNOWN	latency:8.198	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:11.374	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47014	target_addr:172.64.147.104:443
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:12.052	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56594	target_addr:104.21.86.125:443
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:116.782	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46764	target_addr:172.67.168.140:443
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:122.835	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53314	target_addr:172.67.219.211:443
time:2026-10-03T02:44:07Z	status:FAILURE	latency:208.176	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:251.434	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:423.490	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:440.525	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:44:07Z	status:HEALTHY	latency:505.749	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:49:07Z	status:UNKNOWN	latency:8.571	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:12.996	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47794	target_addr:104.18.40.152:443
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:14.297	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36924	target_addr:104.21.86.125:443
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:16.253	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53302	target_addr:104.21.26.208:443
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:211.827	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:220.720	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36932	target_addr:104.21.86.125:443
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:466.565	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:468.174	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:49:07Z	status:FAILURE	latency:510.050	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:49:07Z	status:HEALTHY	latency:777.216	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:9.742	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33610	target_addr:104.21.86.125:443
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:10.348	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33624	target_addr:104.21.86.125:443
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:10.777	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55426	target_addr:172.67.168.140:443
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:12.129	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44552	target_addr:104.18.40.152:443
time:2026-10-03T02:54:07Z	status:FAILURE	latency:29.280	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:54:07Z	status:UNKNOWN	latency:57.149	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:243.307	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:447.254	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:455.302	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:54:07Z	status:HEALTHY	latency:456.460	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:59:07Z	status:UNKNOWN	latency:7.883	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:10.823	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40908	target_addr:104.18.40.152:443
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:13.964	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47592	target_addr:172.67.168.140:443
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:14.033	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59136	target_addr:104.21.86.125:443
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:17.899	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50544	target_addr:172.67.219.211:443
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:68.740	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:77.370	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:114.838	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T02:59:07Z	status:FAILURE	latency:200.232	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T02:59:07Z	status:HEALTHY	latency:220.552	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:04:07Z	status:UNKNOWN	latency:7.189	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:10.640	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33400	target_addr:104.18.40.152:443
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:10.830	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42444	target_addr:172.67.168.140:443
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:10.568	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39066	target_addr:104.21.86.125:443
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:54.340	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:62.135	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:67.167	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:04:07Z	status:FAILURE	latency:244.520	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:251.776	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:04:07Z	status:HEALTHY	latency:304.397	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39068	target_addr:104.21.86.125:443
time:2026-10-03T03:09:07Z	status:UNKNOWN	latency:10.290	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:10.936	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60188	target_addr:104.21.86.125:443
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:11.222	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60186	target_addr:104.21.86.125:443
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:11.689	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37394	target_addr:104.21.26.208:443
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:12.092	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45910	target_addr:104.18.40.152:443
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:62.557	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:62.270	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:74.912	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:09:07Z	status:HEALTHY	latency:215.839	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:09:07Z	status:FAILURE	latency:242.081	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:14:07Z	status:UNKNOWN	latency:7.700	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:10.278	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40456	target_addr:172.64.147.104:443
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:10.917	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38434	target_addr:104.21.86.125:443
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:11.438	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39932	target_addr:172.67.168.140:443
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:12.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45054	target_addr:172.67.219.211:443
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:57.971	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:66.566	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:76.206	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:14:07Z	status:FAILURE	latency:215.371	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:14:07Z	status:HEALTHY	latency:355.254	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:19:07Z	status:UNKNOWN	latency:7.321	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:11.452	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37066	target_addr:104.21.26.208:443
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:11.585	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39688	target_addr:104.21.86.125:443
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:12.105	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56360	target_addr:172.67.219.211:443
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:33.383	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33312	target_addr:172.64.147.104:443
time:2026-10-03T03:19:07Z	status:FAILURE	latency:210.967	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:229.848	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:431.645	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:435.986	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:19:07Z	status:HEALTHY	latency:1220.889	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:9.871	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38752	target_addr:172.64.147.104:443
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:10.483	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36088	target_addr:172.67.219.211:443
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:30.916	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36104	target_addr:172.67.219.211:443
time:2026-10-03T03:24:07Z	status:UNKNOWN	latency:36.868	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:229.156	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47320	target_addr:104.21.26.208:443
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:229.782	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:24:07Z	status:FAILURE	latency:230.308	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:510.961	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:513.017	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:24:07Z	status:HEALTHY	latency:573.415	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:29:07Z	status:UNKNOWN	latency:8.405	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:12.092	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37308	target_addr:104.21.86.125:443
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:12.182	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42224	target_addr:172.64.147.104:443
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:25.094	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36552	target_addr:172.67.219.211:443
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:59.563	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:61.571	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:149.227	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:29:07Z	status:FAILURE	latency:198.032	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:218.243	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:29:07Z	status:HEALTHY	latency:411.446	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37546	target_addr:172.67.168.140:443
time:2026-10-03T03:34:07Z	status:UNKNOWN	latency:7.091	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:11.651	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59674	target_addr:104.21.86.125:443
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:15.841	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41668	target_addr:172.67.219.211:443
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:25.576	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59160	target_addr:104.18.40.152:443
time:2026-10-03T03:34:07Z	status:FAILURE	latency:25.380	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:26.271	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41324	target_addr:172.67.168.140:443
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:65.714	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:71.037	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:199.163	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:34:07Z	status:HEALTHY	latency:323.793	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:39:07Z	status:UNKNOWN	latency:8.662	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:8.979	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53416	target_addr:172.67.219.211:443
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:10.560	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54546	target_addr:104.21.86.125:443
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:20.650	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49104	target_addr:172.64.147.104:443
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:38.836	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52936	target_addr:104.21.26.208:443
time:2026-10-03T03:39:07Z	status:FAILURE	latency:196.849	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:288.766	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:424.116	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:458.540	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:39:07Z	status:HEALTHY	latency:469.126	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:44:07Z	status:UNKNOWN	latency:8.268	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:9.346	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48146	target_addr:172.64.147.104:443
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:10.910	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49264	target_addr:104.21.26.208:443
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:13.978	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42434	target_addr:104.21.86.125:443
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:17.447	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39730	target_addr:172.67.219.211:443
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:119.858	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:44:07Z	status:FAILURE	latency:201.597	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:429.001	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:432.794	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:44:07Z	status:HEALTHY	latency:1854.669	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:11.023	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50760	target_addr:172.64.147.104:443
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:14.136	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47858	target_addr:172.67.219.211:443
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:19.447	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52952	target_addr:172.67.168.140:443
time:2026-10-03T03:49:07Z	status:FAILURE	latency:27.658	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:37.514	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47020	target_addr:104.21.86.125:443
time:2026-10-03T03:49:07Z	status:UNKNOWN	latency:37.940	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:62.479	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:72.488	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:244.968	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:49:07Z	status:HEALTHY	latency:763.880	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:54:07Z	status:UNKNOWN	latency:7.879	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:8.760	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38908	target_addr:172.67.168.140:443
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:10.523	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47112	target_addr:172.67.219.211:443
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:10.842	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41652	target_addr:104.21.86.125:443
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:55.986	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43020	target_addr:172.64.147.104:443
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:57.322	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:57.832	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:99.316	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:54:07Z	status:FAILURE	latency:183.486	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:54:07Z	status:HEALTHY	latency:253.870	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:11.946	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32944	target_addr:104.21.86.125:443
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:13.546	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56012	target_addr:104.18.40.152:443
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:18.541	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38212	target_addr:172.67.168.140:443
time:2026-10-03T03:59:07Z	status:FAILURE	latency:30.823	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T03:59:07Z	status:UNKNOWN	latency:34.150	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:39.789	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60668	target_addr:172.67.219.211:443
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:249.248	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:538.884	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:538.483	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T03:59:07Z	status:HEALTHY	latency:618.935	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:04:07Z	status:UNKNOWN	latency:8.934	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:9.342	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45584	target_addr:104.21.86.125:443
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:11.377	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46692	target_addr:172.67.168.140:443
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:13.846	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60254	target_addr:172.64.147.104:443
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:16.660	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42374	target_addr:172.67.219.211:443
time:2026-10-03T04:04:07Z	status:FAILURE	latency:159.468	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:241.207	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:547.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:550.733	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:04:07Z	status:HEALTHY	latency:555.694	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:09:07Z	status:UNKNOWN	latency:7.956	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:12.940	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60420	target_addr:104.18.40.152:443
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:12.639	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60866	target_addr:172.67.219.211:443
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:13.173	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36128	target_addr:172.67.168.140:443
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:38.332	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60858	target_addr:172.67.219.211:443
time:2026-10-03T04:09:07Z	status:FAILURE	latency:38.471	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:241.726	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:401.538	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:439.256	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:09:07Z	status:HEALTHY	latency:1323.101	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:14:07Z	status:UNKNOWN	latency:7.525	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:11.627	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42940	target_addr:104.21.86.125:443
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:11.879	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56660	target_addr:172.67.168.140:443
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:26.477	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60184	target_addr:172.64.147.104:443
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:33.668	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42954	target_addr:104.21.86.125:443
time:2026-10-03T04:14:07Z	status:FAILURE	latency:203.089	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:272.949	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:454.874	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:463.736	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:14:07Z	status:HEALTHY	latency:758.360	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:19:07Z	status:UNKNOWN	latency:7.701	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:10.986	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36654	target_addr:104.21.86.125:443
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:12.309	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49242	target_addr:172.67.168.140:443
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:13.258	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36668	target_addr:104.21.86.125:443
time:2026-10-03T04:19:07Z	status:FAILURE	latency:200.769	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:259.983	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39680	target_addr:172.64.147.104:443
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:263.178	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:416.363	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:440.459	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:19:07Z	status:HEALTHY	latency:1400.520	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:24:07Z	status:UNKNOWN	latency:10.395	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:11.850	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38870	target_addr:172.64.147.104:443
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:11.793	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49604	target_addr:104.21.26.208:443
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:14.915	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55788	target_addr:104.21.86.125:443
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:20.621	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55804	target_addr:104.21.86.125:443
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:243.356	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:24:07Z	status:FAILURE	latency:278.194	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:434.208	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:492.725	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:24:07Z	status:HEALTHY	latency:501.841	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:29:07Z	status:UNKNOWN	latency:7.666	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:9.610	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52460	target_addr:172.67.219.211:443
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:12.403	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34988	target_addr:172.64.147.104:443
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:19.954	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41498	target_addr:172.67.168.140:443
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:27.580	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51438	target_addr:104.21.86.125:443
time:2026-10-03T04:29:07Z	status:FAILURE	latency:226.253	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:272.250	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:414.792	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:423.757	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:29:07Z	status:HEALTHY	latency:495.734	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:34:07Z	status:UNKNOWN	latency:7.387	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:9.577	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37036	target_addr:172.67.168.140:443
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:9.886	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53538	target_addr:104.21.86.125:443
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:11.212	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53544	target_addr:104.21.86.125:443
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:12.941	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59806	target_addr:104.18.40.152:443
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:232.631	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:434.655	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:443.996	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:34:07Z	status:HEALTHY	latency:449.671	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:34:07Z	status:FAILURE	latency:522.884	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:39:07Z	status:UNKNOWN	latency:8.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:12.579	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53752	target_addr:104.21.26.208:443
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:12.201	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35378	target_addr:104.21.86.125:443
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:12.649	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35382	target_addr:104.21.86.125:443
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:14.011	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55662	target_addr:172.64.147.104:443
time:2026-10-03T04:39:07Z	status:FAILURE	latency:33.420	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:244.496	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:382.536	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:453.373	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:39:07Z	status:HEALTHY	latency:490.508	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:44:07Z	status:UNKNOWN	latency:7.574	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:8.966	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57798	target_addr:104.21.86.125:443
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:9.596	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38756	target_addr:104.18.40.152:443
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:9.647	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57806	target_addr:104.21.86.125:443
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:12.552	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37768	target_addr:172.67.168.140:443
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:226.346	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:44:07Z	status:FAILURE	latency:235.765	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:460.581	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:481.594	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:44:07Z	status:HEALTHY	latency:489.404	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:10.526	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39144	target_addr:172.67.219.211:443
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:11.960	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57150	target_addr:172.67.168.140:443
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:13.173	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40752	target_addr:104.18.40.152:443
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:16.259	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54850	target_addr:104.21.86.125:443
time:2026-10-03T04:49:07Z	status:FAILURE	latency:31.215	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:58.792	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:49:07Z	status:UNKNOWN	latency:77.647	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:140.863	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:219.525	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:49:07Z	status:HEALTHY	latency:229.393	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:54:07Z	status:UNKNOWN	latency:9.435	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:10.006	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35222	target_addr:172.67.219.211:443
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:11.900	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40578	target_addr:172.64.147.104:443
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:12.689	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53100	target_addr:172.67.168.140:443
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:18.958	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45232	target_addr:104.21.86.125:443
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:57.529	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:62.383	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:54:07Z	status:FAILURE	latency:205.688	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:246.827	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:54:07Z	status:HEALTHY	latency:2189.842	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:9.551	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33634	target_addr:172.67.219.211:443
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:10.028	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48576	target_addr:172.67.168.140:443
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:10.448	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33644	target_addr:172.67.219.211:443
time:2026-10-03T04:59:07Z	status:UNKNOWN	latency:11.932	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:14.164	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34974	target_addr:172.64.147.104:443
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:59.835	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:60.877	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:74.536	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T04:59:07Z	status:FAILURE	latency:204.056	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T04:59:07Z	status:HEALTHY	latency:230.706	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:13.211	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44750	target_addr:172.67.219.211:443
time:2026-10-03T05:04:07Z	status:UNKNOWN	latency:13.238	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:13.766	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50938	target_addr:172.67.168.140:443
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:14.322	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41762	target_addr:104.21.86.125:443
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:34.203	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35498	target_addr:104.18.40.152:443
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:62.344	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:70.728	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:73.184	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:04:07Z	status:FAILURE	latency:260.026	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:04:07Z	status:HEALTHY	latency:276.557	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:9.196	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40798	target_addr:104.21.86.125:443
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:10.729	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35524	target_addr:104.21.26.208:443
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:17.933	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40812	target_addr:104.21.86.125:443
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:29.724	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40302	target_addr:104.18.40.152:443
time:2026-10-03T05:09:07Z	status:FAILURE	latency:29.641	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:09:07Z	status:UNKNOWN	latency:36.398	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:61.492	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:71.836	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:74.968	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:09:07Z	status:HEALTHY	latency:530.049	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:9.815	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46214	target_addr:104.18.40.152:443
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:10.761	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50620	target_addr:104.21.86.125:443
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:12.607	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45764	target_addr:172.67.168.140:443
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:12.764	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41628	target_addr:172.67.219.211:443
time:2026-10-03T05:14:07Z	status:UNKNOWN	latency:39.802	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:54.477	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:56.733	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:14:07Z	status:FAILURE	latency:204.643	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:212.708	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:14:07Z	status:HEALTHY	latency:524.592	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:9.870	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57236	target_addr:172.64.147.104:443
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:10.695	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54300	target_addr:172.67.219.211:443
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:10.931	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47176	target_addr:172.67.168.140:443
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:11.788	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39266	target_addr:104.21.86.125:443
time:2026-10-03T05:19:07Z	status:FAILURE	latency:25.681	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:51.011	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:53.023	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:19:07Z	status:UNKNOWN	latency:55.527	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:68.498	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:19:07Z	status:HEALTHY	latency:216.429	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:24:07Z	status:UNKNOWN	latency:8.555	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:11.157	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54306	target_addr:172.64.147.104:443
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:13.606	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59902	target_addr:172.67.219.211:443
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:18.245	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44862	target_addr:104.21.26.208:443
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:28.200	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60690	target_addr:104.21.86.125:443
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:54.545	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:58.482	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:85.291	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:24:07Z	status:FAILURE	latency:302.660	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:24:07Z	status:HEALTHY	latency:1233.329	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:29:07Z	status:UNKNOWN	latency:9.846	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:12.985	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39604	target_addr:104.21.86.125:443
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:13.093	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51208	target_addr:104.21.26.208:443
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:13.311	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39606	target_addr:104.21.86.125:443
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:17.286	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44712	target_addr:172.64.147.104:443
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:59.107	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:80.623	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:80.993	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:29:07Z	status:FAILURE	latency:233.809	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:29:07Z	status:HEALTHY	latency:608.388	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:34:07Z	status:UNKNOWN	latency:9.094	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:11.475	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34868	target_addr:104.21.86.125:443
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:12.028	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43016	target_addr:104.21.26.208:443
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:20.079	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47026	target_addr:104.18.40.152:443
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:19.761	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34884	target_addr:104.21.86.125:443
time:2026-10-03T05:34:07Z	status:FAILURE	latency:205.546	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:224.083	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:444.893	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:455.102	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:34:07Z	status:HEALTHY	latency:634.127	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:39:07Z	status:UNKNOWN	latency:8.350	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:9.514	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39090	target_addr:172.67.168.140:443
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:12.018	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50960	target_addr:104.21.86.125:443
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:12.209	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60692	target_addr:172.64.147.104:443
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:12.523	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50968	target_addr:104.21.86.125:443
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:54.505	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:59.421	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:59.674	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:39:07Z	status:FAILURE	latency:206.756	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:39:07Z	status:HEALTHY	latency:314.310	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:9.108	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33934	target_addr:104.18.40.152:443
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:11.325	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48762	target_addr:104.21.86.125:443
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:18.350	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58860	target_addr:104.21.26.208:443
time:2026-10-03T05:44:07Z	status:FAILURE	latency:25.237	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:30.399	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48770	target_addr:104.21.86.125:443
time:2026-10-03T05:44:07Z	status:UNKNOWN	latency:56.977	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:62.238	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:71.994	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:86.282	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:44:07Z	status:HEALTHY	latency:227.236	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:49:07Z	status:UNKNOWN	latency:9.777	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:12.074	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60270	target_addr:172.67.219.211:443
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:15.449	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60278	target_addr:172.67.219.211:443
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:22.445	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49582	target_addr:104.21.26.208:443
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:44.620	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33334	target_addr:172.64.147.104:443
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:60.658	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:65.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:221.171	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:49:07Z	status:FAILURE	latency:232.037	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:49:07Z	status:HEALTHY	latency:253.596	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:11.235	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51262	target_addr:104.21.86.125:443
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:12.026	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41062	target_addr:104.18.40.152:443
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:13.439	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51250	target_addr:104.21.86.125:443
time:2026-10-03T05:54:07Z	status:FAILURE	latency:24.762	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:54:07Z	status:UNKNOWN	latency:187.893	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:203.765	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44750	target_addr:172.67.168.140:443
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:218.922	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:467.594	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:489.141	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:54:07Z	status:HEALTHY	latency:490.301	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:59:07Z	status:UNKNOWN	latency:8.481	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:11.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50020	target_addr:172.64.147.104:443
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:12.986	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41402	target_addr:104.21.86.125:443
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:16.059	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40770	target_addr:104.21.26.208:443
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:20.671	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50718	target_addr:172.67.219.211:443
time:2026-10-03T05:59:07Z	status:FAILURE	latency:29.970	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:63.965	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:71.279	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:72.480	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T05:59:07Z	status:HEALTHY	latency:346.978	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:9.535	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34588	target_addr:104.18.40.152:443
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:10.510	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43838	target_addr:104.21.26.208:443
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:12.956	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50578	target_addr:104.21.86.125:443
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:14.754	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50586	target_addr:104.21.86.125:443
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:53.554	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:04:08Z	status:UNKNOWN	latency:56.663	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:57.796	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:76.594	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:04:08Z	status:HEALTHY	latency:605.772	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:04:08Z	status:FAILURE	latency:1628.363	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:09:08Z	status:UNKNOWN	latency:7.034	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:8.888	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33468	target_addr:104.18.40.152:443
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:9.624	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35536	target_addr:172.67.219.211:443
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:10.168	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33722	target_addr:104.21.86.125:443
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:20.969	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39736	target_addr:104.21.26.208:443
time:2026-10-03T06:09:08Z	status:FAILURE	latency:25.984	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:54.581	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:56.462	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:64.923	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:09:08Z	status:HEALTHY	latency:275.635	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:14:08Z	status:UNKNOWN	latency:7.673	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:10.629	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51108	target_addr:172.67.219.211:443
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:11.578	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53890	target_addr:172.67.168.140:443
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:21.202	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51110	target_addr:172.67.219.211:443
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:24.694	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36090	target_addr:104.18.40.152:443
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:58.945	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:73.717	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:113.065	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:14:08Z	status:FAILURE	latency:201.041	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:14:08Z	status:HEALTHY	latency:253.158	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:9.426	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45040	target_addr:104.21.26.208:443
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:10.416	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47442	target_addr:104.21.86.125:443
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:15.330	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47454	target_addr:104.21.86.125:443
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:16.297	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42044	target_addr:104.18.40.152:443
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:58.707	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:64.986	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:67.622	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:19:08Z	status:FAILURE	latency:199.007	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:19:08Z	status:HEALTHY	latency:259.036	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:19:08Z	status:UNKNOWN	latency:315.771	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:24:08Z	status:UNKNOWN	latency:7.574	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:8.295	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34340	target_addr:104.18.40.152:443
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:8.778	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43566	target_addr:172.67.219.211:443
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:9.652	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43580	target_addr:172.67.219.211:443
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:11.076	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42510	target_addr:172.67.168.140:443
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:55.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:87.520	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:24:08Z	status:FAILURE	latency:236.924	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:256.819	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:24:08Z	status:HEALTHY	latency:1447.664	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:29:08Z	status:UNKNOWN	latency:11.236	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:13.164	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49774	target_addr:172.64.147.104:443
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:14.831	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33754	target_addr:104.21.86.125:443
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:19.760	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33764	target_addr:104.21.86.125:443
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:33.717	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49980	target_addr:172.67.168.140:443
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:61.496	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:65.269	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:70.206	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:29:08Z	status:FAILURE	latency:206.999	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:29:08Z	status:HEALTHY	latency:232.998	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:34:08Z	status:UNKNOWN	latency:9.568	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:10.456	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38738	target_addr:104.21.26.208:443
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:13.656	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56436	target_addr:104.21.86.125:443
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:18.293	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44718	target_addr:172.64.147.104:443
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:52.526	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:55.611	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:61.052	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:222.488	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59720	target_addr:172.67.219.211:443
time:2026-10-03T06:34:08Z	status:HEALTHY	latency:239.023	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:34:08Z	status:FAILURE	latency:341.560	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:10.442	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50986	target_addr:104.18.40.152:443
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:10.240	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52308	target_addr:172.67.219.211:443
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:11.022	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52320	target_addr:172.67.219.211:443
time:2026-10-03T06:39:08Z	status:FAILURE	latency:26.131	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:39:08Z	status:UNKNOWN	latency:34.223	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:46.978	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44932	target_addr:104.21.26.208:443
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:57.897	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:71.784	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:130.777	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:39:08Z	status:HEALTHY	latency:232.860	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:9.063	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55664	target_addr:172.67.168.140:443
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:10.548	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35628	target_addr:104.21.86.125:443
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:12.055	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52050	target_addr:172.64.147.104:443
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:12.006	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41658	target_addr:172.67.219.211:443
time:2026-10-03T06:44:08Z	status:UNKNOWN	latency:14.068	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:55.176	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:77.258	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:44:08Z	status:FAILURE	latency:200.588	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:231.455	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:44:08Z	status:HEALTHY	latency:238.027	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:49:08Z	status:UNKNOWN	latency:6.817	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:10.529	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53158	target_addr:172.64.147.104:443
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:13.487	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50006	target_addr:104.21.26.208:443
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:14.447	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51814	target_addr:172.67.219.211:443
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:25.021	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35172	target_addr:104.21.86.125:443
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:59.192	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:59.671	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:73.659	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:49:08Z	status:FAILURE	latency:208.802	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:49:08Z	status:HEALTHY	latency:231.124	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:54:08Z	status:UNKNOWN	latency:7.322	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:10.164	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53400	target_addr:172.67.219.211:443
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:10.604	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48980	target_addr:172.64.147.104:443
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:12.581	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53416	target_addr:172.67.219.211:443
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:12.965	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57226	target_addr:104.21.26.208:443
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:54.272	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:55.846	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:62.170	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:54:08Z	status:FAILURE	latency:244.920	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:54:08Z	status:HEALTHY	latency:323.784	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:59:08Z	status:UNKNOWN	latency:7.517	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:10.204	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51732	target_addr:104.21.26.208:443
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:11.229	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35190	target_addr:172.67.219.211:443
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:17.992	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47300	target_addr:104.18.40.152:443
time:2026-10-03T06:59:08Z	status:FAILURE	latency:26.608	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:51.704	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:77.735	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:238.901	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:906.891	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54642	target_addr:104.21.86.125:443
time:2026-10-03T06:59:08Z	status:HEALTHY	latency:1604.612	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:7.911	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48436	target_addr:104.21.86.125:443
time:2026-10-03T07:04:08Z	status:UNKNOWN	latency:10.542	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:10.469	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38216	target_addr:172.67.219.211:443
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:10.784	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51994	target_addr:104.21.26.208:443
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:12.568	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35902	target_addr:104.18.40.152:443
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:51.964	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:57.818	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:81.616	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:04:08Z	status:HEALTHY	latency:216.887	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:04:08Z	status:FAILURE	latency:228.527	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:9.967	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45508	target_addr:104.18.40.152:443
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:10.024	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32912	target_addr:172.67.219.211:443
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:11.064	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37806	target_addr:104.21.26.208:443
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:11.034	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40396	target_addr:104.21.86.125:443
time:2026-10-03T07:09:08Z	status:FAILURE	latency:43.037	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:09:08Z	status:UNKNOWN	latency:56.446	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:56.001	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:76.287	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:230.630	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:09:08Z	status:HEALTHY	latency:249.950	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:7.794	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52720	target_addr:172.67.168.140:443
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:10.640	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54552	target_addr:104.21.86.125:443
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:15.720	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53760	target_addr:104.18.40.152:443
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:15.682	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54554	target_addr:104.21.86.125:443
time:2026-10-03T07:14:08Z	status:UNKNOWN	latency:33.232	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:52.497	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:103.437	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:111.774	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:14:08Z	status:FAILURE	latency:198.671	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:14:08Z	status:HEALTHY	latency:243.796	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:19:08Z	status:UNKNOWN	latency:9.388	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:9.519	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50278	target_addr:172.64.147.104:443
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:12.767	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43482	target_addr:104.21.86.125:443
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:12.799	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43480	target_addr:104.21.86.125:443
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:12.813	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45246	target_addr:172.67.168.140:443
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:63.559	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:68.231	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:19:08Z	status:FAILURE	latency:199.877	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:556.932	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:19:08Z	status:HEALTHY	latency:6072.796	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:7.930	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47988	target_addr:104.18.40.152:443
time:2026-10-03T07:24:08Z	status:UNKNOWN	latency:8.340	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:9.082	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51058	target_addr:172.67.219.211:443
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:9.044	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51056	target_addr:172.67.219.211:443
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:13.964	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45140	target_addr:172.67.168.140:443
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:52.302	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:53.609	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:69.983	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:24:08Z	status:FAILURE	latency:205.754	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:24:08Z	status:HEALTHY	latency:206.019	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:29:08Z	status:UNKNOWN	latency:7.845	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:9.787	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56420	target_addr:172.67.219.211:443
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:11.286	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38138	target_addr:172.67.168.140:443
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:11.796	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53804	target_addr:172.64.147.104:443
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:34.039	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47058	target_addr:104.21.86.125:443
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:57.356	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:59.127	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:29:08Z	status:FAILURE	latency:199.664	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:308.494	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:29:08Z	status:HEALTHY	latency:632.014	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:34:08Z	status:UNKNOWN	latency:8.713	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:9.396	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45484	target_addr:104.18.40.152:443
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:11.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41380	target_addr:172.67.219.211:443
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:12.483	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56058	target_addr:104.21.86.125:443
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:14.889	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33708	target_addr:172.67.168.140:443
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:60.516	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:70.493	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:34:08Z	status:FAILURE	latency:186.407	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:238.972	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:34:08Z	status:HEALTHY	latency:310.524	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:39:08Z	status:UNKNOWN	latency:13.627	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:14.202	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47252	target_addr:172.67.219.211:443
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:13.674	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39064	target_addr:104.21.26.208:443
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:13.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47250	target_addr:172.67.219.211:443
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:14.311	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60438	target_addr:104.18.40.152:443
time:2026-10-03T07:39:08Z	status:FAILURE	latency:35.114	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:67.365	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:78.072	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:276.630	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:39:08Z	status:HEALTHY	latency:1122.926	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:8.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59624	target_addr:104.21.86.125:443
time:2026-10-03T07:44:08Z	status:UNKNOWN	latency:8.723	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:8.977	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59628	target_addr:104.21.86.125:443
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:13.771	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41060	target_addr:172.67.168.140:443
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:15.052	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32892	target_addr:104.18.40.152:443
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:56.552	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:108.571	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:206.266	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:44:08Z	status:FAILURE	latency:206.570	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:44:08Z	status:HEALTHY	latency:236.172	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:9.930	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42752	target_addr:104.18.40.152:443
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:11.299	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38202	target_addr:172.67.219.211:443
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:13.327	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56908	target_addr:104.21.26.208:443
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:23.031	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38194	target_addr:172.67.219.211:443
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:54.117	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:58.043	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:49:08Z	status:UNKNOWN	latency:58.428	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:62.127	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:49:08Z	status:FAILURE	latency:206.143	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:49:08Z	status:HEALTHY	latency:236.019	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:54:08Z	status:UNKNOWN	latency:8.231	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:9.507	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53882	target_addr:172.64.147.104:443
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:10.189	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44612	target_addr:172.67.219.211:443
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:10.040	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57042	target_addr:104.21.26.208:443
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:23.027	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44618	target_addr:172.67.219.211:443
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:51.727	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:64.298	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:69.462	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:54:08Z	status:FAILURE	latency:202.269	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:54:08Z	status:HEALTHY	latency:235.656	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:10.978	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35940	target_addr:172.64.147.104:443
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:11.119	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54090	target_addr:172.67.168.140:443
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:11.110	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47960	target_addr:104.21.86.125:443
time:2026-10-03T07:59:08Z	status:UNKNOWN	latency:20.472	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:27.526	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54436	target_addr:172.67.219.211:443
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:54.086	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:58.351	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:59:08Z	status:FAILURE	latency:234.557	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:277.549	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T07:59:08Z	status:HEALTHY	latency:537.321	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:04:08Z	status:UNKNOWN	latency:8.417	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:9.245	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48024	target_addr:172.67.168.140:443
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:9.984	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41400	target_addr:104.18.40.152:443
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:10.727	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34532	target_addr:104.21.86.125:443
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:12.540	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47928	target_addr:172.67.219.211:443
time:2026-10-03T08:04:08Z	status:FAILURE	latency:33.448	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:53.289	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:65.605	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:65.528	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:04:08Z	status:HEALTHY	latency:237.177	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:09:08Z	status:UNKNOWN	latency:7.817	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:9.509	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36520	target_addr:104.21.86.125:443
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:19.012	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51788	target_addr:104.18.40.152:443
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:23.237	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36528	target_addr:104.21.86.125:443
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:23.662	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50848	target_addr:104.21.26.208:443
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:55.399	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:72.690	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:82.135	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:09:08Z	status:HEALTHY	latency:193.329	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:09:08Z	status:FAILURE	latency:222.936	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:14:08Z	status:UNKNOWN	latency:7.573	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:10.087	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33172	target_addr:172.67.219.211:443
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:11.361	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41604	target_addr:104.18.40.152:443
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:12.191	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41084	target_addr:104.21.86.125:443
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:18.712	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52554	target_addr:104.21.26.208:443
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:52.209	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:54.910	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:55.291	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:14:08Z	status:FAILURE	latency:181.843	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:14:08Z	status:HEALTHY	latency:212.534	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:19:08Z	status:UNKNOWN	latency:7.536	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:11.852	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48378	target_addr:104.18.40.152:443
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:13.893	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39910	target_addr:104.21.86.125:443
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:17.501	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39924	target_addr:104.21.86.125:443
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:20.391	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36656	target_addr:172.67.168.140:443
time:2026-10-03T08:19:08Z	status:FAILURE	latency:26.684	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:318.500	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:429.784	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:431.271	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:19:08Z	status:HEALTHY	latency:432.959	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:24:08Z	status:UNKNOWN	latency:8.269	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:10.135	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35384	target_addr:104.21.86.125:443
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:10.100	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49494	target_addr:104.21.26.208:443
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:10.388	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35382	target_addr:104.21.86.125:443
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:11.654	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43300	target_addr:172.64.147.104:443
time:2026-10-03T08:24:08Z	status:FAILURE	latency:168.489	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:276.013	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:837.072	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:2437.979	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:24:08Z	status:HEALTHY	latency:2744.005	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:29:08Z	status:UNKNOWN	latency:7.265	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:10.225	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38118	target_addr:172.67.219.211:443
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:10.379	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38134	target_addr:172.67.219.211:443
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:11.413	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55094	target_addr:104.18.40.152:443
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:12.945	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44780	target_addr:172.67.168.140:443
time:2026-10-03T08:29:08Z	status:FAILURE	latency:35.852	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:197.904	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:441.300	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:442.284	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:29:08Z	status:HEALTHY	latency:1960.355	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:34:08Z	status:UNKNOWN	latency:5.879	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:7.902	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48350	target_addr:172.67.168.140:443
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:9.535	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42042	target_addr:172.64.147.104:443
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:10.425	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45078	target_addr:104.21.86.125:443
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:11.434	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59106	target_addr:172.67.219.211:443
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:201.362	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:34:08Z	status:FAILURE	latency:345.632	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:428.219	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:441.128	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:34:08Z	status:HEALTHY	latency:458.923	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:39:08Z	status:UNKNOWN	latency:7.225	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:9.434	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44130	target_addr:172.64.147.104:443
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:9.451	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44024	target_addr:172.67.168.140:443
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:10.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32908	target_addr:104.21.86.125:443
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:16.228	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32910	target_addr:104.21.86.125:443
time:2026-10-03T08:39:08Z	status:FAILURE	latency:207.136	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:227.940	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:510.939	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:524.131	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:39:08Z	status:HEALTHY	latency:611.487	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:44:08Z	status:UNKNOWN	latency:8.186	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:9.699	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36092	target_addr:172.67.219.211:443
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:10.225	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47042	target_addr:104.21.26.208:443
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:11.140	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36094	target_addr:172.67.219.211:443
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:12.164	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53052	target_addr:172.64.147.104:443
time:2026-10-03T08:44:08Z	status:FAILURE	latency:338.195	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:428.074	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:429.906	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:434.574	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:44:08Z	status:HEALTHY	latency:490.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:9.661	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58478	target_addr:172.64.147.104:443
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:13.529	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50268	target_addr:172.67.219.211:443
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:13.512	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60748	target_addr:104.21.86.125:443
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:13.496	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38548	target_addr:172.67.168.140:443
time:2026-10-03T08:49:08Z	status:UNKNOWN	latency:56.813	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:49:08Z	status:FAILURE	latency:155.976	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:181.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:678.945	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:686.905	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:49:08Z	status:HEALTHY	latency:808.972	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:54:08Z	status:UNKNOWN	latency:7.793	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:8.765	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58892	target_addr:172.67.219.211:443
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:9.891	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40852	target_addr:172.67.168.140:443
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:11.324	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54480	target_addr:172.64.147.104:443
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:11.091	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58906	target_addr:172.67.219.211:443
time:2026-10-03T08:54:08Z	status:FAILURE	latency:170.894	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:289.642	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:680.439	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:688.454	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:54:08Z	status:HEALTHY	latency:694.642	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:59:08Z	status:UNKNOWN	latency:5.555	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:8.012	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34516	target_addr:104.21.86.125:443
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:8.813	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35928	target_addr:172.67.219.211:443
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:10.191	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52968	target_addr:172.64.147.104:443
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:19.352	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60562	target_addr:172.67.168.140:443
time:2026-10-03T08:59:08Z	status:FAILURE	latency:182.489	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:197.179	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:407.242	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:409.480	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T08:59:08Z	status:HEALTHY	latency:520.537	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:04:08Z	status:UNKNOWN	latency:8.943	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:9.473	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48446	target_addr:104.18.40.152:443
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:9.563	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36290	target_addr:104.21.86.125:443
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:9.498	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36280	target_addr:104.21.86.125:443
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:11.439	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37666	target_addr:104.21.26.208:443
time:2026-10-03T09:04:08Z	status:FAILURE	latency:31.339	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:191.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:723.784	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:755.712	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:04:08Z	status:HEALTHY	latency:757.262	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:09:08Z	status:UNKNOWN	latency:7.671	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:9.854	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58976	target_addr:172.67.168.140:443
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:10.410	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38222	target_addr:172.64.147.104:443
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:11.504	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44244	target_addr:172.67.219.211:443
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:16.926	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34358	target_addr:104.21.86.125:443
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:80.439	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:09:08Z	status:FAILURE	latency:225.460	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:497.397	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:570.083	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:09:08Z	status:HEALTHY	latency:1381.333	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:14:08Z	status:UNKNOWN	latency:8.300	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:9.191	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55188	target_addr:104.21.86.125:443
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:11.461	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39930	target_addr:104.18.40.152:443
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:11.428	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55194	target_addr:104.21.86.125:443
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:12.758	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51762	target_addr:172.67.168.140:443
time:2026-10-03T09:14:08Z	status:FAILURE	latency:27.744	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:701.269	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:714.871	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:751.436	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:14:08Z	status:HEALTHY	latency:789.477	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:9.487	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44796	target_addr:104.18.40.152:443
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:9.560	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35286	target_addr:172.67.219.211:443
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:12.053	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46974	target_addr:104.21.26.208:443
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:14.975	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35294	target_addr:172.67.219.211:443
time:2026-10-03T09:19:08Z	status:FAILURE	latency:24.105	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:19:08Z	status:UNKNOWN	latency:36.090	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:230.581	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:794.549	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:842.554	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:19:08Z	status:HEALTHY	latency:1130.184	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:24:08Z	status:UNKNOWN	latency:6.330	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:9.040	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41872	target_addr:172.67.219.211:443
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:10.100	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38308	target_addr:104.21.86.125:443
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:9.934	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35468	target_addr:172.67.168.140:443
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:10.471	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55714	target_addr:104.18.40.152:443
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:171.029	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:24:08Z	status:FAILURE	latency:207.158	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:829.394	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:837.867	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:24:08Z	status:HEALTHY	latency:947.638	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:10.149	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56048	target_addr:172.67.219.211:443
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:12.781	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34036	target_addr:172.67.168.140:443
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:12.777	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59412	target_addr:104.21.86.125:443
time:2026-10-03T09:29:08Z	status:FAILURE	latency:22.778	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:29:08Z	status:UNKNOWN	latency:36.301	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:39.511	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36658	target_addr:172.64.147.104:443
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:209.446	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:1002.378	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:1002.221	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:29:08Z	status:HEALTHY	latency:1130.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:8.861	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40532	target_addr:172.64.147.104:443
time:2026-10-03T09:34:09Z	status:UNKNOWN	latency:9.186	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:10.797	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54400	target_addr:172.67.219.211:443
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:10.863	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53144	target_addr:172.67.168.140:443
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:12.948	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45716	target_addr:104.21.86.125:443
time:2026-10-03T09:34:09Z	status:FAILURE	latency:24.598	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:199.524	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:737.066	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:744.417	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:34:09Z	status:HEALTHY	latency:1722.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:9.476	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48252	target_addr:104.21.86.125:443
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:9.609	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39662	target_addr:104.21.26.208:443
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:9.830	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48240	target_addr:104.21.86.125:443
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:11.032	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59472	target_addr:104.18.40.152:443
time:2026-10-03T09:39:09Z	status:UNKNOWN	latency:32.345	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:39:09Z	status:FAILURE	latency:165.260	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:191.492	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:710.324	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:817.804	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:39:09Z	status:HEALTHY	latency:869.656	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:44:09Z	status:UNKNOWN	latency:6.279	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:9.377	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34050	target_addr:104.21.86.125:443
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:10.429	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49162	target_addr:172.67.168.140:443
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:10.145	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34056	target_addr:104.21.86.125:443
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:11.898	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43980	target_addr:172.64.147.104:443
time:2026-10-03T09:44:09Z	status:FAILURE	latency:22.308	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:308.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:834.420	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:857.986	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:44:09Z	status:HEALTHY	latency:864.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:9.876	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51052	target_addr:172.67.219.211:443
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:10.505	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33468	target_addr:104.21.86.125:443
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:11.391	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35358	target_addr:104.18.40.152:443
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:11.834	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37704	target_addr:104.21.26.208:443
time:2026-10-03T09:49:09Z	status:FAILURE	latency:22.352	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:49:09Z	status:UNKNOWN	latency:33.087	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:293.660	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:443.748	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:450.041	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:49:09Z	status:HEALTHY	latency:496.443	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:54:09Z	status:UNKNOWN	latency:7.947	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:10.994	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38640	target_addr:172.67.168.140:443
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:10.714	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48346	target_addr:104.21.86.125:443
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:11.577	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50388	target_addr:172.64.147.104:443
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:11.705	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48020	target_addr:172.67.219.211:443
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:182.516	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:54:09Z	status:FAILURE	latency:209.039	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:808.587	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:808.349	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:54:09Z	status:HEALTHY	latency:809.927	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:59:09Z	status:UNKNOWN	latency:7.460	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:9.388	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52286	target_addr:104.18.40.152:443
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:10.810	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48974	target_addr:104.21.86.125:443
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:11.447	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53246	target_addr:172.67.168.140:443
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:12.811	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34110	target_addr:172.67.219.211:443
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:576.947	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:653.523	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:656.007	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T09:59:09Z	status:FAILURE	latency:884.652	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T09:59:09Z	status:HEALTHY	latency:904.356	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:04:09Z	status:UNKNOWN	latency:7.238	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:11.225	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47082	target_addr:172.67.168.140:443
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:20.959	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56070	target_addr:104.21.86.125:443
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:142.562	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56074	target_addr:104.21.86.125:443
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:197.698	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:389.714	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41940	target_addr:172.64.147.104:443
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:422.210	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:432.553	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:04:09Z	status:HEALTHY	latency:551.383	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:04:09Z	status:FAILURE	latency:2997.823	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:9.992	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45664	target_addr:172.64.147.104:443
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:10.661	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51736	target_addr:172.67.168.140:443
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:10.400	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58756	target_addr:172.67.219.211:443
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:22.394	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37734	target_addr:104.21.86.125:443
time:2026-10-03T10:09:09Z	status:UNKNOWN	latency:35.507	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:203.648	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:09:09Z	status:FAILURE	latency:224.186	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:405.895	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:414.645	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:09:09Z	status:HEALTHY	latency:416.370	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:14:09Z	status:UNKNOWN	latency:8.015	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:10.600	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35078	target_addr:172.67.168.140:443
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:11.540	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60050	target_addr:104.21.86.125:443
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:11.698	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51122	target_addr:104.18.40.152:443
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:19.867	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60042	target_addr:104.21.86.125:443
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:220.476	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:14:09Z	status:FAILURE	latency:293.872	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:415.906	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:917.451	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:14:09Z	status:HEALTHY	latency:965.401	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:19:09Z	status:UNKNOWN	latency:9.283	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:13.670	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53840	target_addr:104.21.26.208:443
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:13.968	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54720	target_addr:172.67.219.211:443
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:13.773	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41996	target_addr:104.21.86.125:443
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:14.151	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47630	target_addr:172.64.147.104:443
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:209.602	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:19:09Z	status:FAILURE	latency:219.364	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:425.407	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:427.080	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:19:09Z	status:HEALTHY	latency:956.258	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:9.950	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44098	target_addr:172.64.147.104:443
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:9.700	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36416	target_addr:104.21.86.125:443
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:9.952	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51626	target_addr:172.67.219.211:443
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:10.030	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44848	target_addr:104.21.26.208:443
time:2026-10-03T10:24:09Z	status:UNKNOWN	latency:57.856	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:191.451	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:599.343	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:614.975	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:24:09Z	status:HEALTHY	latency:617.768	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:24:09Z	status:FAILURE	latency:790.241	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:29:09Z	status:UNKNOWN	latency:8.752	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:10.992	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58436	target_addr:104.21.86.125:443
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:12.112	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40180	target_addr:172.67.219.211:443
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:14.538	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46862	target_addr:172.67.168.140:443
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:215.344	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:29:09Z	status:FAILURE	latency:235.365	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:416.820	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:442.166	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:442.577	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51018	target_addr:172.64.147.104:443
time:2026-10-03T10:29:09Z	status:HEALTHY	latency:975.793	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:10.850	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51844	target_addr:104.21.86.125:443
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:11.204	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49858	target_addr:104.21.26.208:443
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:11.026	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51852	target_addr:104.21.86.125:443
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:20.878	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44238	target_addr:172.64.147.104:443
time:2026-10-03T10:34:09Z	status:UNKNOWN	latency:58.099	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:200.361	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:34:09Z	status:FAILURE	latency:216.884	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:466.544	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:485.153	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:34:09Z	status:HEALTHY	latency:878.956	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:39:09Z	status:UNKNOWN	latency:8.260	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:11.036	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59562	target_addr:104.21.86.125:443
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:11.431	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33332	target_addr:172.67.219.211:443
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:12.915	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49716	target_addr:104.21.26.208:443
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:13.629	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39990	target_addr:172.64.147.104:443
time:2026-10-03T10:39:09Z	status:FAILURE	latency:149.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:249.435	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:387.557	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:388.089	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:39:09Z	status:HEALTHY	latency:492.289	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:44:09Z	status:UNKNOWN	latency:7.136	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:9.847	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43000	target_addr:172.64.147.104:443
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:10.432	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42152	target_addr:172.67.219.211:443
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:10.521	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35696	target_addr:104.21.26.208:443
time:2026-10-03T10:44:09Z	status:FAILURE	latency:22.399	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:37.601	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42158	target_addr:172.67.219.211:443
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:221.470	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:492.968	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:503.754	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:44:09Z	status:HEALTHY	latency:546.987	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:49:09Z	status:UNKNOWN	latency:7.412	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:11.795	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53952	target_addr:104.18.40.152:443
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:12.209	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47910	target_addr:172.67.219.211:443
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:17.954	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44648	target_addr:104.21.26.208:443
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:33.223	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32848	target_addr:104.21.86.125:443
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:219.255	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:418.702	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:421.650	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:49:09Z	status:HEALTHY	latency:656.558	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:49:09Z	status:FAILURE	latency:1515.289	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:54:09Z	status:UNKNOWN	latency:8.526	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:12.112	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46532	target_addr:104.21.86.125:443
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:12.264	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39586	target_addr:104.21.26.208:443
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:15.823	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46538	target_addr:104.21.86.125:443
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:17.028	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50114	target_addr:172.64.147.104:443
time:2026-10-03T10:54:09Z	status:FAILURE	latency:27.702	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:230.141	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:437.748	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:478.077	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:54:09Z	status:HEALTHY	latency:485.621	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:8.630	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46560	target_addr:104.21.86.125:443
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:9.212	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43576	target_addr:172.64.147.104:443
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:17.236	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39752	target_addr:172.67.168.140:443
time:2026-10-03T10:59:09Z	status:UNKNOWN	latency:29.943	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:32.450	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42780	target_addr:172.67.219.211:443
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:203.812	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:436.545	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:452.565	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:59:09Z	status:HEALTHY	latency:683.203	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T10:59:09Z	status:FAILURE	latency:2167.268	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:04:09Z	status:UNKNOWN	latency:6.927	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:9.781	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36324	target_addr:104.18.40.152:443
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:10.960	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33534	target_addr:172.67.168.140:443
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:10.985	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38854	target_addr:172.67.219.211:443
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:11.510	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38862	target_addr:172.67.219.211:443
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:54.198	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:66.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:206.674	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:04:09Z	status:FAILURE	latency:245.160	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:04:09Z	status:HEALTHY	latency:391.395	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:09:09Z	status:UNKNOWN	latency:6.869	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:9.146	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55446	target_addr:172.67.219.211:443
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:10.170	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37050	target_addr:104.21.86.125:443
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:16.273	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37324	target_addr:104.21.26.208:443
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:27.552	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39590	target_addr:104.18.40.152:443
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:51.168	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:59.220	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:70.721	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:09:09Z	status:HEALTHY	latency:205.916	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:09:09Z	status:FAILURE	latency:560.207	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:14:09Z	status:UNKNOWN	latency:6.529	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:7.885	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54722	target_addr:104.18.40.152:443
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:10.344	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58100	target_addr:172.67.219.211:443
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:12.609	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37026	target_addr:104.21.86.125:443
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:19.286	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48364	target_addr:104.21.26.208:443
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:65.382	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:92.372	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:208.860	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:14:09Z	status:FAILURE	latency:227.055	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:14:09Z	status:HEALTHY	latency:272.358	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:10.165	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49798	target_addr:172.67.168.140:443
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:11.362	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35524	target_addr:172.67.219.211:443
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:17.560	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51702	target_addr:104.21.86.125:443
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:21.909	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43656	target_addr:104.18.40.152:443
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:48.451	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:60.390	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:19:09Z	status:UNKNOWN	latency:71.520	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:91.297	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:19:09Z	status:FAILURE	latency:168.250	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:19:09Z	status:HEALTHY	latency:194.460	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:24:09Z	status:UNKNOWN	latency:6.803	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:9.140	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49060	target_addr:172.67.219.211:443
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:9.434	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49072	target_addr:172.67.219.211:443
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:10.503	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59516	target_addr:104.18.40.152:443
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:17.854	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56446	target_addr:172.67.168.140:443
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:48.753	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:52.355	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:53.038	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:24:09Z	status:HEALTHY	latency:207.725	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:24:09Z	status:FAILURE	latency:258.493	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:8.488	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33712	target_addr:172.67.219.211:443
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:9.487	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59860	target_addr:104.18.40.152:443
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:9.360	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33726	target_addr:172.67.219.211:443
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:12.306	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35100	target_addr:104.21.26.208:443
time:2026-10-03T11:29:09Z	status:UNKNOWN	latency:37.643	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:49.431	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:54.511	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:68.926	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:29:09Z	status:FAILURE	latency:209.423	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:29:09Z	status:HEALTHY	latency:227.274	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:10.878	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44404	target_addr:104.21.86.125:443
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:10.868	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36424	target_addr:172.64.147.104:443
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:12.534	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33888	target_addr:104.21.26.208:443
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:12.154	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44410	target_addr:104.21.86.125:443
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:56.706	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:34:09Z	status:UNKNOWN	latency:57.478	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:62.930	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:86.256	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:34:09Z	status:FAILURE	latency:197.578	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:34:09Z	status:HEALTHY	latency:221.684	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:10.687	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47068	target_addr:104.21.26.208:443
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:16.164	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40504	target_addr:104.18.40.152:443
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:18.428	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42684	target_addr:172.67.219.211:443
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:18.479	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42686	target_addr:172.67.219.211:443
time:2026-10-03T11:39:09Z	status:UNKNOWN	latency:20.623	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:50.354	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:53.241	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:59.616	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:39:09Z	status:FAILURE	latency:240.776	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:39:09Z	status:HEALTHY	latency:275.174	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:44:09Z	status:UNKNOWN	latency:7.581	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:8.637	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34780	target_addr:104.21.86.125:443
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:11.336	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41050	target_addr:172.64.147.104:443
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:12.843	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44934	target_addr:172.67.168.140:443
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:15.816	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34784	target_addr:104.21.86.125:443
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:55.747	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:56.649	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:84.868	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:44:09Z	status:FAILURE	latency:201.634	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:44:09Z	status:HEALTHY	latency:269.593	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:49:09Z	status:UNKNOWN	latency:7.453	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:12.552	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46280	target_addr:172.67.219.211:443
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:12.723	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47028	target_addr:104.18.40.152:443
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:12.544	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45138	target_addr:104.21.26.208:443
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:16.355	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39866	target_addr:104.21.86.125:443
time:2026-10-03T11:49:09Z	status:FAILURE	latency:28.636	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:54.420	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:71.329	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:110.596	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:49:09Z	status:HEALTHY	latency:263.401	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:54:09Z	status:UNKNOWN	latency:7.024	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:10.093	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45820	target_addr:104.21.26.208:443
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:10.961	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34736	target_addr:172.64.147.104:443
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:11.620	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44218	target_addr:172.67.219.211:443
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:14.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37762	target_addr:104.21.86.125:443
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:57.314	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:58.282	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:84.478	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:54:09Z	status:HEALTHY	latency:218.676	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:54:09Z	status:FAILURE	latency:223.652	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:59:09Z	status:UNKNOWN	latency:7.936	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:9.963	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54922	target_addr:172.67.168.140:443
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:10.300	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34180	target_addr:104.21.86.125:443
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:12.970	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33992	target_addr:172.64.147.104:443
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:18.976	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41970	target_addr:172.67.219.211:443
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:61.479	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:61.563	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:205.215	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T11:59:09Z	status:FAILURE	latency:416.826	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T11:59:09Z	status:HEALTHY	latency:1746.707	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:04:09Z	status:UNKNOWN	latency:7.422	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:9.536	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49434	target_addr:104.21.86.125:443
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:10.993	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49448	target_addr:104.21.86.125:443
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:12.375	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56800	target_addr:104.21.26.208:443
time:2026-10-03T12:04:09Z	status:FAILURE	latency:21.387	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:23.862	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37368	target_addr:172.64.147.104:443
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:50.752	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:53.550	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:71.659	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:04:09Z	status:HEALTHY	latency:1346.924	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:09:09Z	status:UNKNOWN	latency:7.293	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:10.970	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36088	target_addr:104.21.86.125:443
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:11.109	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40606	target_addr:104.21.26.208:443
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:10.736	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36078	target_addr:104.21.86.125:443
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:11.217	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34150	target_addr:104.18.40.152:443
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:54.838	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:57.686	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:71.433	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:09:09Z	status:FAILURE	latency:176.610	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:09:09Z	status:HEALTHY	latency:219.873	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:10.001	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37038	target_addr:104.21.26.208:443
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:10.626	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52208	target_addr:104.18.40.152:443
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:11.016	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51426	target_addr:172.67.219.211:443
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:13.146	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51436	target_addr:172.67.219.211:443
time:2026-10-03T12:14:09Z	status:FAILURE	latency:26.691	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:14:09Z	status:UNKNOWN	latency:36.212	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:71.107	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:72.222	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:284.854	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:14:09Z	status:HEALTHY	latency:1694.339	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:9.505	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55136	target_addr:172.67.219.211:443
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:10.110	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58996	target_addr:172.64.147.104:443
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:11.307	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43758	target_addr:172.67.168.140:443
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:13.263	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43142	target_addr:104.21.86.125:443
time:2026-10-03T12:19:09Z	status:UNKNOWN	latency:32.387	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:216.536	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:19:09Z	status:FAILURE	latency:222.430	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:452.083	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:734.535	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:19:09Z	status:HEALTHY	latency:1982.060	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:8.716	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33306	target_addr:172.67.168.140:443
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:9.358	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36154	target_addr:104.18.40.152:443
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:9.461	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43468	target_addr:104.21.86.125:443
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:20.017	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43482	target_addr:104.21.86.125:443
time:2026-10-03T12:24:09Z	status:FAILURE	latency:20.861	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:24:09Z	status:UNKNOWN	latency:36.465	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:262.434	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:770.438	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:1036.974	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:24:09Z	status:HEALTHY	latency:1824.780	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:29:09Z	status:UNKNOWN	latency:8.931	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:10.250	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53460	target_addr:104.21.86.125:443
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:12.371	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59474	target_addr:104.18.40.152:443
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:12.517	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39942	target_addr:172.67.219.211:443
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:21.504	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56116	target_addr:104.21.26.208:443
time:2026-10-03T12:29:09Z	status:FAILURE	latency:185.934	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:256.038	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:427.245	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:665.094	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:29:09Z	status:HEALTHY	latency:672.967	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:34:09Z	status:UNKNOWN	latency:7.530	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:10.640	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54948	target_addr:172.64.147.104:443
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:11.595	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44674	target_addr:104.21.86.125:443
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:11.502	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38802	target_addr:172.67.219.211:443
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:16.245	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32774	target_addr:104.21.26.208:443
time:2026-10-03T12:34:09Z	status:FAILURE	latency:28.225	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:200.545	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:684.895	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:690.355	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:34:09Z	status:HEALTHY	latency:690.955	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:39:09Z	status:UNKNOWN	latency:6.274	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:9.827	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44982	target_addr:104.21.26.208:443
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:10.481	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53730	target_addr:172.67.219.211:443
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:13.182	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53742	target_addr:172.67.219.211:443
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:18.210	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51490	target_addr:104.18.40.152:443
time:2026-10-03T12:39:09Z	status:FAILURE	latency:165.648	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:246.374	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:685.428	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:703.451	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:39:09Z	status:HEALTHY	latency:1685.847	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:8.501	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35826	target_addr:172.64.147.104:443
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:9.296	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57246	target_addr:104.21.86.125:443
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:10.132	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57254	target_addr:104.21.86.125:443
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:10.098	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40232	target_addr:172.67.168.140:443
time:2026-10-03T12:44:09Z	status:FAILURE	latency:20.234	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:44:09Z	status:UNKNOWN	latency:32.528	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:194.536	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:433.942	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:441.385	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:44:09Z	status:HEALTHY	latency:446.637	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:10.575	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38764	target_addr:104.21.26.208:443
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:10.687	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45904	target_addr:104.21.86.125:443
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:28.363	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49048	target_addr:172.64.147.104:443
time:2026-10-03T12:49:10Z	status:UNKNOWN	latency:85.071	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:85.302	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45918	target_addr:104.21.86.125:443
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:206.518	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:49:10Z	status:FAILURE	latency:224.761	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:417.457	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:693.981	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:49:10Z	status:HEALTHY	latency:697.216	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:54:10Z	status:UNKNOWN	latency:6.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:10.001	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40988	target_addr:172.67.219.211:443
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:10.422	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37478	target_addr:172.67.168.140:443
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:10.957	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41228	target_addr:104.21.86.125:443
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:126.982	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53528	target_addr:172.64.147.104:443
time:2026-10-03T12:54:10Z	status:FAILURE	latency:215.758	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:249.777	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:433.868	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:436.402	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:54:10Z	status:HEALTHY	latency:713.326	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:59:10Z	status:UNKNOWN	latency:7.916	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:11.748	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44280	target_addr:172.67.168.140:443
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:11.648	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41092	target_addr:172.67.219.211:443
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:11.466	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36674	target_addr:104.21.86.125:443
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:11.841	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42532	target_addr:104.18.40.152:443
time:2026-10-03T12:59:10Z	status:FAILURE	latency:218.813	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:378.120	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:378.983	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:431.314	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T12:59:10Z	status:HEALTHY	latency:641.033	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:04:10Z	status:UNKNOWN	latency:9.135	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:9.237	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42616	target_addr:172.64.147.104:443
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:10.024	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50160	target_addr:104.21.86.125:443
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:11.011	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50176	target_addr:104.21.86.125:443
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:11.943	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58726	target_addr:104.21.26.208:443
time:2026-10-03T13:04:10Z	status:FAILURE	latency:211.697	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:213.524	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:483.717	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:650.310	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:04:10Z	status:HEALTHY	latency:719.139	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:09:10Z	status:UNKNOWN	latency:6.063	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:9.108	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46260	target_addr:172.67.219.211:443
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:9.700	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46276	target_addr:172.67.219.211:443
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:10.049	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41096	target_addr:172.64.147.104:443
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:10.730	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51824	target_addr:104.21.26.208:443
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:230.154	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:09:10Z	status:FAILURE	latency:267.103	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:423.656	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:429.832	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:09:10Z	status:HEALTHY	latency:446.544	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:14:10Z	status:UNKNOWN	latency:8.891	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:9.377	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38606	target_addr:104.21.86.125:443
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:9.869	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49398	target_addr:172.64.147.104:443
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:9.293	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57698	target_addr:172.67.219.211:443
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:10.310	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50050	target_addr:172.67.168.140:443
time:2026-10-03T13:14:10Z	status:FAILURE	latency:345.074	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:429.478	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:445.038	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:703.930	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:14:10Z	status:HEALTHY	latency:1162.383	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:19:10Z	status:UNKNOWN	latency:7.354	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:10.064	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37774	target_addr:104.21.86.125:443
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:10.601	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56662	target_addr:172.67.219.211:443
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:10.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50272	target_addr:172.67.168.140:443
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:25.448	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49898	target_addr:172.64.147.104:443
time:2026-10-03T13:19:10Z	status:FAILURE	latency:167.973	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:282.095	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:392.231	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:406.292	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:19:10Z	status:HEALTHY	latency:545.368	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:24:10Z	status:UNKNOWN	latency:7.402	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:10.325	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55918	target_addr:172.67.219.211:443
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:10.488	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41626	target_addr:104.21.26.208:443
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:11.770	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47020	target_addr:172.64.147.104:443
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:12.933	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60302	target_addr:104.21.86.125:443
time:2026-10-03T13:24:10Z	status:FAILURE	latency:27.167	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:56.708	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:56.680	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:59.486	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:24:10Z	status:HEALTHY	latency:204.050	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:29:10Z	status:UNKNOWN	latency:8.117	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:8.810	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57678	target_addr:104.21.86.125:443
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:10.241	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55066	target_addr:172.64.147.104:443
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:9.924	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51726	target_addr:172.67.219.211:443
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:10.928	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34810	target_addr:172.67.168.140:443
time:2026-10-03T13:29:10Z	status:FAILURE	latency:29.147	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:52.034	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:52.692	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:56.539	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:29:10Z	status:HEALTHY	latency:495.054	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:8.966	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59856	target_addr:172.64.147.104:443
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:8.575	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38248	target_addr:172.67.219.211:443
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:9.160	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38250	target_addr:172.67.219.211:443
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:10.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44486	target_addr:172.67.168.140:443
time:2026-10-03T13:34:10Z	status:UNKNOWN	latency:35.672	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:55.601	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:63.985	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:66.154	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:34:10Z	status:FAILURE	latency:187.170	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:34:10Z	status:HEALTHY	latency:203.407	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:39:10Z	status:UNKNOWN	latency:7.360	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:8.996	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53040	target_addr:172.64.147.104:443
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:9.402	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42606	target_addr:172.67.219.211:443
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:10.684	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34630	target_addr:172.67.168.140:443
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:12.272	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42614	target_addr:172.67.219.211:443
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:53.484	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:54.200	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:56.792	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:39:10Z	status:HEALTHY	latency:264.648	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:39:10Z	status:FAILURE	latency:1257.990	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:44:10Z	status:UNKNOWN	latency:5.780	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:10.782	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58908	target_addr:104.21.86.125:443
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:11.393	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51098	target_addr:172.64.147.104:443
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:11.698	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58758	target_addr:172.67.219.211:443
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:12.483	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48600	target_addr:172.67.168.140:443
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:50.479	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:52.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:57.601	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:44:10Z	status:FAILURE	latency:203.604	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:44:10Z	status:HEALTHY	latency:220.656	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:49:10Z	status:UNKNOWN	latency:9.653	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:9.258	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42834	target_addr:172.67.219.211:443
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:10.712	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57914	target_addr:172.64.147.104:443
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:10.808	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58832	target_addr:172.67.168.140:443
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:10.726	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42844	target_addr:172.67.219.211:443
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:52.497	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:54.140	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:67.617	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:49:10Z	status:HEALTHY	latency:232.096	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:49:10Z	status:FAILURE	latency:794.292	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:54:10Z	status:UNKNOWN	latency:8.654	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:9.645	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33676	target_addr:104.21.86.125:443
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:10.617	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50876	target_addr:104.21.26.208:443
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:10.654	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52846	target_addr:172.67.219.211:443
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:18.564	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41232	target_addr:172.64.147.104:443
time:2026-10-03T13:54:10Z	status:FAILURE	latency:27.279	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:54.012	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:55.274	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:207.661	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:54:10Z	status:HEALTHY	latency:686.973	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:59:10Z	status:UNKNOWN	latency:7.404	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:9.789	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52326	target_addr:104.21.26.208:443
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:10.015	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37092	target_addr:104.21.86.125:443
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:16.415	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52172	target_addr:172.67.219.211:443
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:23.225	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59276	target_addr:172.64.147.104:443
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:50.355	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:55.446	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:55.956	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:59:10Z	status:HEALTHY	latency:228.053	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T13:59:10Z	status:FAILURE	latency:1227.989	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:04:10Z	status:UNKNOWN	latency:7.100	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:9.137	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41954	target_addr:104.18.40.152:443
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:11.564	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45434	target_addr:172.67.168.140:443
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:12.165	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42332	target_addr:172.67.219.211:443
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:18.348	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57418	target_addr:104.21.86.125:443
time:2026-10-03T14:04:10Z	status:FAILURE	latency:21.869	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:50.297	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:52.520	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:141.446	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:04:10Z	status:HEALTHY	latency:593.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:10.024	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56912	target_addr:172.67.168.140:443
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:11.373	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35326	target_addr:172.67.219.211:443
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:11.155	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60408	target_addr:104.21.86.125:443
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:11.536	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51184	target_addr:104.18.40.152:443
time:2026-10-03T14:09:10Z	status:UNKNOWN	latency:19.638	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:57.178	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:59.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:62.692	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:09:10Z	status:HEALTHY	latency:215.421	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:09:10Z	status:FAILURE	latency:237.991	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:14:10Z	status:UNKNOWN	latency:6.836	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:8.771	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59924	target_addr:104.21.86.125:443
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:9.859	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35560	target_addr:104.18.40.152:443
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:9.693	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32918	target_addr:172.67.219.211:443
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:10.555	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46170	target_addr:104.21.26.208:443
time:2026-10-03T14:14:10Z	status:FAILURE	latency:24.979	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:171.915	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:488.656	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:503.619	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:14:10Z	status:HEALTHY	latency:747.178	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:9.849	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58572	target_addr:104.18.40.152:443
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:11.513	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58332	target_addr:172.67.219.211:443
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:13.367	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35484	target_addr:104.21.26.208:443
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:13.530	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56300	target_addr:104.21.86.125:443
time:2026-10-03T14:19:10Z	status:UNKNOWN	latency:46.683	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:199.031	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:19:10Z	status:FAILURE	latency:221.289	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:475.720	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:800.961	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:19:10Z	status:HEALTHY	latency:808.713	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:24:10Z	status:UNKNOWN	latency:6.993	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:10.271	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54544	target_addr:172.64.147.104:443
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:10.053	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54438	target_addr:172.67.219.211:443
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:10.582	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53042	target_addr:104.21.86.125:443
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:11.256	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47826	target_addr:104.21.26.208:443
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:212.505	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:24:10Z	status:FAILURE	latency:331.850	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:524.133	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:533.484	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:24:10Z	status:HEALTHY	latency:750.643	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:29:10Z	status:UNKNOWN	latency:8.042	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:11.132	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48268	target_addr:172.67.168.140:443
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:11.436	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41244	target_addr:104.21.86.125:443
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:16.198	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56598	target_addr:172.64.147.104:443
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:15.728	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41258	target_addr:104.21.86.125:443
time:2026-10-03T14:29:10Z	status:FAILURE	latency:26.720	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:427.496	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:433.540	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:456.124	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:29:10Z	status:HEALTHY	latency:520.922	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:34:10Z	status:UNKNOWN	latency:8.035	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:11.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59824	target_addr:172.64.147.104:443
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:11.321	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52576	target_addr:172.67.219.211:443
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:14.478	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57864	target_addr:104.21.26.208:443
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:14.292	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44250	target_addr:104.21.86.125:443
time:2026-10-03T14:34:10Z	status:FAILURE	latency:251.986	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:253.549	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:437.555	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:440.197	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:34:10Z	status:HEALTHY	latency:471.168	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:9.763	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35330	target_addr:172.67.219.211:443
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:11.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48244	target_addr:172.67.168.140:443
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:12.539	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35332	target_addr:172.67.219.211:443
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:13.295	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53660	target_addr:104.18.40.152:443
time:2026-10-03T14:39:10Z	status:FAILURE	latency:29.080	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:39:10Z	status:UNKNOWN	latency:34.594	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:98.909	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:451.735	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:475.846	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:39:10Z	status:HEALTHY	latency:684.166	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:9.342	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60960	target_addr:172.64.147.104:443
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:9.053	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37070	target_addr:104.21.86.125:443
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:10.007	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49856	target_addr:172.67.168.140:443
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:10.782	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36938	target_addr:172.67.219.211:443
time:2026-10-03T14:44:10Z	status:UNKNOWN	latency:33.256	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:193.460	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:44:10Z	status:FAILURE	latency:206.868	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:467.656	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:549.041	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:44:10Z	status:HEALTHY	latency:605.592	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:49:10Z	status:UNKNOWN	latency:7.181	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:8.910	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45648	target_addr:172.64.147.104:443
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:9.037	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33832	target_addr:104.21.86.125:443
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:10.957	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35888	target_addr:104.21.26.208:443
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:11.122	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47788	target_addr:172.67.219.211:443
time:2026-10-03T14:49:10Z	status:FAILURE	latency:24.509	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:52.629	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:53.631	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:198.788	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:49:10Z	status:HEALTHY	latency:358.716	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:54:10Z	status:UNKNOWN	latency:7.546	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:7.962	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52056	target_addr:104.18.40.152:443
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:9.307	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43330	target_addr:104.21.86.125:443
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:8.985	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43316	target_addr:104.21.86.125:443
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:9.799	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35026	target_addr:172.67.168.140:443
time:2026-10-03T14:54:10Z	status:FAILURE	latency:23.465	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:53.486	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:55.862	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:61.970	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:54:10Z	status:HEALTHY	latency:262.293	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:9.058	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51440	target_addr:104.21.26.208:443
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:10.981	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45254	target_addr:104.18.40.152:443
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:11.171	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33700	target_addr:172.67.219.211:443
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:11.180	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33702	target_addr:172.67.219.211:443
time:2026-10-03T14:59:10Z	status:UNKNOWN	latency:13.590	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:54.812	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:113.763	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:138.056	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:59:10Z	status:HEALTHY	latency:493.909	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T14:59:10Z	status:FAILURE	latency:1235.030	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:04:10Z	status:UNKNOWN	latency:7.467	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:8.915	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39254	target_addr:172.67.219.211:443
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:9.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36198	target_addr:104.21.86.125:443
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:9.923	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58424	target_addr:104.18.40.152:443
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:10.308	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37212	target_addr:104.21.26.208:443
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:53.711	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:54.727	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:76.103	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:04:10Z	status:HEALTHY	latency:216.244	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:04:10Z	status:FAILURE	latency:233.078	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:09:10Z	status:UNKNOWN	latency:7.695	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:9.128	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36196	target_addr:172.64.147.104:443
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:9.180	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43090	target_addr:172.67.219.211:443
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:9.167	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36790	target_addr:104.21.86.125:443
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:11.425	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36872	target_addr:104.21.26.208:443
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:203.628	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:09:10Z	status:FAILURE	latency:226.543	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:1068.733	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:1127.451	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:09:10Z	status:HEALTHY	latency:1362.386	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:14:10Z	status:UNKNOWN	latency:7.518	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:11.760	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52092	target_addr:172.67.219.211:443
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:11.977	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35918	target_addr:172.64.147.104:443
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:12.186	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59514	target_addr:172.67.168.140:443
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:12.571	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52106	target_addr:172.67.219.211:443
time:2026-10-03T15:14:10Z	status:FAILURE	latency:221.214	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:404.644	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:452.324	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:458.941	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:14:10Z	status:HEALTHY	latency:541.919	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:19:10Z	status:UNKNOWN	latency:7.272	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:11.955	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43192	target_addr:172.64.147.104:443
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:11.582	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49522	target_addr:172.67.168.140:443
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:11.637	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46314	target_addr:104.21.86.125:443
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:20.107	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38828	target_addr:172.67.219.211:443
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:206.161	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:19:10Z	status:FAILURE	latency:225.106	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:427.364	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:446.545	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:19:10Z	status:HEALTHY	latency:697.493	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:24:10Z	status:UNKNOWN	latency:8.208	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:11.433	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48410	target_addr:104.21.86.125:443
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:11.534	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55944	target_addr:172.67.219.211:443
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:11.858	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44476	target_addr:172.67.168.140:443
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:13.153	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38790	target_addr:172.64.147.104:443
time:2026-10-03T15:24:10Z	status:FAILURE	latency:76.861	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:228.230	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:440.595	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:590.725	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:24:10Z	status:HEALTHY	latency:600.641	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:29:10Z	status:UNKNOWN	latency:8.332	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:11.638	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60116	target_addr:104.21.26.208:443
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:11.349	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42844	target_addr:104.21.86.125:443
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:12.172	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40342	target_addr:172.64.147.104:443
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:23.474	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42858	target_addr:104.21.86.125:443
time:2026-10-03T15:29:10Z	status:FAILURE	latency:226.146	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:267.370	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:437.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:705.982	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:29:10Z	status:HEALTHY	latency:715.796	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:34:10Z	status:UNKNOWN	latency:8.857	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:9.183	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47682	target_addr:104.18.40.152:443
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:9.735	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35316	target_addr:172.67.219.211:443
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:11.100	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35330	target_addr:172.67.219.211:443
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:12.815	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42412	target_addr:104.21.26.208:443
time:2026-10-03T15:34:10Z	status:FAILURE	latency:45.239	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:205.543	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:510.550	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:545.301	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:34:10Z	status:HEALTHY	latency:560.340	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:39:10Z	status:UNKNOWN	latency:7.939	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:9.071	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43672	target_addr:104.21.26.208:443
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:10.479	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56428	target_addr:172.67.219.211:443
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:10.888	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44126	target_addr:104.21.86.125:443
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:30.296	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53832	target_addr:104.18.40.152:443
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:207.787	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:39:10Z	status:FAILURE	latency:224.589	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:498.958	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:540.305	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:39:10Z	status:HEALTHY	latency:542.562	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:44:10Z	status:UNKNOWN	latency:7.914	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:12.014	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59816	target_addr:172.64.147.104:443
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:11.944	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55692	target_addr:172.67.168.140:443
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:11.941	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36040	target_addr:104.21.86.125:443
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:12.708	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45588	target_addr:172.67.219.211:443
time:2026-10-03T15:44:10Z	status:FAILURE	latency:63.825	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:216.736	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:522.318	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:542.836	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:44:10Z	status:HEALTHY	latency:802.197	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:49:10Z	status:UNKNOWN	latency:7.544	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:12.648	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54764	target_addr:172.67.219.211:443
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:12.775	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34660	target_addr:104.18.40.152:443
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:13.187	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37370	target_addr:172.67.168.140:443
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:13.530	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47044	target_addr:104.21.86.125:443
time:2026-10-03T15:49:10Z	status:FAILURE	latency:37.687	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:244.073	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:438.012	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:439.716	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:49:10Z	status:HEALTHY	latency:522.913	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:54:10Z	status:UNKNOWN	latency:9.571	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:12.735	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34468	target_addr:104.21.86.125:443
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:12.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35874	target_addr:104.21.26.208:443
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:12.748	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55150	target_addr:172.67.219.211:443
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:13.263	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39778	target_addr:104.18.40.152:443
time:2026-10-03T15:54:10Z	status:FAILURE	latency:170.536	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:225.790	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:471.048	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:478.775	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:54:10Z	status:HEALTHY	latency:490.966	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:59:10Z	status:UNKNOWN	latency:7.371	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:9.684	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51282	target_addr:104.21.86.125:443
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:10.959	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51292	target_addr:104.21.86.125:443
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:11.077	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54308	target_addr:172.67.168.140:443
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:15.834	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44202	target_addr:104.18.40.152:443
time:2026-10-03T15:59:10Z	status:FAILURE	latency:173.352	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:225.161	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:420.602	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:425.561	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T15:59:10Z	status:HEALTHY	latency:438.249	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:04:10Z	status:UNKNOWN	latency:6.457	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:10.575	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33436	target_addr:104.18.40.152:443
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:10.268	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38548	target_addr:104.21.26.208:443
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:10.511	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37514	target_addr:172.67.219.211:443
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:11.971	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37526	target_addr:172.67.219.211:443
time:2026-10-03T16:04:10Z	status:FAILURE	latency:191.866	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:194.677	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:503.215	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:514.544	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:04:10Z	status:HEALTHY	latency:529.400	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:9.097	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56578	target_addr:172.67.219.211:443
time:2026-10-03T16:09:10Z	status:UNKNOWN	latency:9.628	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:12.332	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46830	target_addr:104.21.26.208:443
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:12.590	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60102	target_addr:104.21.86.125:443
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:12.766	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41772	target_addr:104.18.40.152:443
time:2026-10-03T16:09:10Z	status:FAILURE	latency:26.653	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:208.674	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:396.974	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:416.945	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:09:10Z	status:HEALTHY	latency:539.602	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:14:10Z	status:UNKNOWN	latency:8.148	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:11.463	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55208	target_addr:104.21.86.125:443
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:10.929	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54640	target_addr:172.67.219.211:443
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:11.494	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44444	target_addr:172.64.147.104:443
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:11.735	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60280	target_addr:172.67.168.140:443
time:2026-10-03T16:14:10Z	status:FAILURE	latency:229.147	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:335.958	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:474.943	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:565.455	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:14:10Z	status:HEALTHY	latency:593.661	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:19:10Z	status:UNKNOWN	latency:6.683	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:10.015	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58034	target_addr:172.67.168.140:443
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:11.439	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44490	target_addr:172.64.147.104:443
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:12.765	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47706	target_addr:104.21.86.125:443
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:16.985	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47712	target_addr:104.21.86.125:443
time:2026-10-03T16:19:10Z	status:FAILURE	latency:184.455	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:713.724	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:769.944	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:1222.347	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:19:10Z	status:HEALTHY	latency:1436.971	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:8.183	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54672	target_addr:172.67.168.140:443
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:8.500	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33724	target_addr:172.67.219.211:443
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:9.231	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37414	target_addr:104.18.40.152:443
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:11.168	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:172.67.219.211:443
time:2026-10-03T16:24:10Z	status:UNKNOWN	latency:35.339	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:210.968	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:24:10Z	status:FAILURE	latency:226.976	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:508.105	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:518.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:24:10Z	status:HEALTHY	latency:522.658	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:29:10Z	status:UNKNOWN	latency:7.905	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:8.080	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36928	target_addr:104.18.40.152:443
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:9.801	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45258	target_addr:104.21.86.125:443
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:11.301	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59660	target_addr:172.67.219.211:443
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:11.561	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50826	target_addr:172.67.168.140:443
time:2026-10-03T16:29:10Z	status:FAILURE	latency:210.129	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:236.216	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:434.586	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:660.918	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:29:10Z	status:HEALTHY	latency:662.558	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:8.950	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42406	target_addr:104.18.40.152:443
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:9.225	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46150	target_addr:172.67.219.211:443
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:11.320	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42554	target_addr:104.21.86.125:443
time:2026-10-03T16:34:10Z	status:UNKNOWN	latency:25.222	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:28.153	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40652	target_addr:104.21.26.208:443
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:218.438	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:34:10Z	status:FAILURE	latency:241.469	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:444.524	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:457.096	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:34:10Z	status:HEALTHY	latency:1037.487	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:39:10Z	status:UNKNOWN	latency:8.350	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:9.625	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56350	target_addr:104.18.40.152:443
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:9.580	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44952	target_addr:104.21.86.125:443
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:10.100	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59076	target_addr:172.67.219.211:443
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:10.682	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33484	target_addr:172.67.168.140:443
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:99.942	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:39:10Z	status:FAILURE	latency:189.504	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:420.797	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:423.832	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:39:10Z	status:HEALTHY	latency:432.176	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:44:11Z	status:UNKNOWN	latency:6.980	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:8.538	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43356	target_addr:172.67.219.211:443
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:8.987	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38432	target_addr:104.18.40.152:443
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:9.367	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50528	target_addr:104.21.86.125:443
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:9.335	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45106	target_addr:104.21.26.208:443
time:2026-10-03T16:44:11Z	status:FAILURE	latency:25.475	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:208.104	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:422.405	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:434.929	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:44:11Z	status:HEALTHY	latency:454.185	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:49:11Z	status:UNKNOWN	latency:8.154	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:8.975	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35556	target_addr:172.64.147.104:443
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:10.107	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50220	target_addr:104.21.86.125:443
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:14.799	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42762	target_addr:104.21.26.208:443
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:14.266	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50222	target_addr:104.21.86.125:443
time:2026-10-03T16:49:11Z	status:FAILURE	latency:211.483	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:226.590	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:515.121	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:527.970	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:49:11Z	status:HEALTHY	latency:544.237	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:54:11Z	status:UNKNOWN	latency:6.691	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:9.490	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58718	target_addr:104.21.26.208:443
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:9.960	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44470	target_addr:172.64.147.104:443
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:10.714	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46898	target_addr:104.21.86.125:443
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:13.143	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46908	target_addr:104.21.86.125:443
time:2026-10-03T16:54:11Z	status:FAILURE	latency:156.787	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:231.027	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:450.490	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:474.464	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:54:11Z	status:HEALTHY	latency:727.312	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:59:11Z	status:UNKNOWN	latency:8.919	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:11.204	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53544	target_addr:104.21.86.125:443
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:11.585	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36042	target_addr:172.64.147.104:443
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:11.008	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53552	target_addr:104.21.86.125:443
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:12.533	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52350	target_addr:104.21.26.208:443
time:2026-10-03T16:59:11Z	status:FAILURE	latency:143.703	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:190.235	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:422.807	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:427.797	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T16:59:11Z	status:HEALTHY	latency:522.974	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:11.255	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44506	target_addr:172.67.219.211:443
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:10.996	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52330	target_addr:104.18.40.152:443
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:11.746	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44508	target_addr:172.67.219.211:443
time:2026-10-03T17:04:11Z	status:UNKNOWN	latency:22.320	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:22.234	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52950	target_addr:104.21.26.208:443
time:2026-10-03T17:04:11Z	status:FAILURE	latency:175.550	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:268.528	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:458.563	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:468.590	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:04:11Z	status:HEALTHY	latency:468.970	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:09:11Z	status:UNKNOWN	latency:8.189	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:9.699	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60814	target_addr:172.67.219.211:443
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:11.853	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40846	target_addr:104.21.26.208:443
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:15.497	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47740	target_addr:104.21.86.125:443
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:16.741	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38286	target_addr:104.18.40.152:443
time:2026-10-03T17:09:11Z	status:FAILURE	latency:180.266	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:221.914	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:486.108	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:539.773	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:09:11Z	status:HEALTHY	latency:865.629	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:14:11Z	status:UNKNOWN	latency:7.530	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:10.199	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43402	target_addr:172.67.168.140:443
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:9.782	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59178	target_addr:172.67.219.211:443
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:10.182	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51800	target_addr:104.21.86.125:443
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:10.635	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39212	target_addr:172.64.147.104:443
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:192.779	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:14:11Z	status:FAILURE	latency:219.370	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:446.155	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:476.609	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:14:11Z	status:HEALTHY	latency:611.555	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:19:11Z	status:UNKNOWN	latency:7.434	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:9.360	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50436	target_addr:104.18.40.152:443
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:10.288	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41184	target_addr:104.21.86.125:443
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:10.748	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60548	target_addr:172.67.168.140:443
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:12.381	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41304	target_addr:172.67.219.211:443
time:2026-10-03T17:19:11Z	status:FAILURE	latency:203.520	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:223.799	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:420.296	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:434.857	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:19:11Z	status:HEALTHY	latency:437.060	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:24:11Z	status:UNKNOWN	latency:6.387	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:10.376	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40572	target_addr:172.67.168.140:443
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:11.167	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34560	target_addr:172.67.219.211:443
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:12.303	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59192	target_addr:104.21.86.125:443
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:17.944	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57386	target_addr:172.64.147.104:443
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:191.769	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:24:11Z	status:FAILURE	latency:203.935	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:505.916	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:510.896	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:24:11Z	status:HEALTHY	latency:524.361	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:29:11Z	status:UNKNOWN	latency:7.998	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:9.103	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54064	target_addr:172.67.219.211:443
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:10.189	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43412	target_addr:104.21.86.125:443
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:11.073	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45706	target_addr:104.18.40.152:443
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:19.074	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43866	target_addr:172.67.168.140:443
time:2026-10-03T17:29:11Z	status:FAILURE	latency:219.864	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:258.257	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:440.927	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:529.328	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:29:11Z	status:HEALTHY	latency:540.787	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:9.078	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42706	target_addr:172.67.168.140:443
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:9.583	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44858	target_addr:104.18.40.152:443
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:12.073	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48628	target_addr:104.21.86.125:443
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:12.800	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34654	target_addr:172.67.219.211:443
time:2026-10-03T17:34:11Z	status:FAILURE	latency:26.806	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:198.735	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:34:11Z	status:UNKNOWN	latency:243.540	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:425.598	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:427.722	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:34:11Z	status:HEALTHY	latency:521.129	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:39:11Z	status:UNKNOWN	latency:8.057	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:11.799	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44044	target_addr:172.67.219.211:443
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:11.917	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44058	target_addr:172.67.219.211:443
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:12.556	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51000	target_addr:104.21.26.208:443
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:14.573	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58172	target_addr:104.18.40.152:443
time:2026-10-03T17:39:11Z	status:FAILURE	latency:207.176	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:265.529	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:639.841	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:643.673	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:39:11Z	status:HEALTHY	latency:667.173	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:44:11Z	status:UNKNOWN	latency:7.637	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:8.118	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48942	target_addr:104.18.40.152:443
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:13.207	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51462	target_addr:104.21.86.125:443
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:13.364	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51450	target_addr:104.21.86.125:443
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:108.407	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:44:11Z	status:FAILURE	latency:208.476	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:441.675	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:714.376	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:44:11Z	status:HEALTHY	latency:891.103	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58796	target_addr:172.67.168.140:443
time:2026-10-03T17:44:11Z	status:FAILURE	latency:4945.237	target:https://go3-cn.xyz/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-10-03T17:49:11Z	status:UNKNOWN	latency:7.732	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:11.686	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44238	target_addr:104.18.40.152:443
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:11.305	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38750	target_addr:172.67.219.211:443
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:11.430	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43672	target_addr:104.21.86.125:443
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:11.381	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54400	target_addr:172.67.168.140:443
time:2026-10-03T17:49:11Z	status:FAILURE	latency:27.889	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:110.626	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:461.125	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:506.431	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:49:11Z	status:HEALTHY	latency:1321.131	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:9.763	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55918	target_addr:104.21.26.208:443
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:11.999	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48904	target_addr:172.64.147.104:443
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:11.565	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47282	target_addr:172.67.219.211:443
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:11.932	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47284	target_addr:172.67.219.211:443
time:2026-10-03T17:54:11Z	status:UNKNOWN	latency:32.539	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:54:11Z	status:FAILURE	latency:171.355	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:198.250	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:413.074	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:460.791	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:54:11Z	status:HEALTHY	latency:719.741	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:59:11Z	status:UNKNOWN	latency:7.684	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:10.437	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46164	target_addr:104.21.86.125:443
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:11.807	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47158	target_addr:172.67.219.211:443
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:27.029	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40050	target_addr:104.21.26.208:443
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:87.824	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47654	target_addr:172.64.147.104:443
time:2026-10-03T17:59:11Z	status:FAILURE	latency:201.281	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:229.456	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:483.588	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:488.934	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T17:59:11Z	status:HEALTHY	latency:491.968	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:04:11Z	status:UNKNOWN	latency:9.754	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:11.399	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50390	target_addr:104.18.40.152:443
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:13.096	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45554	target_addr:172.67.219.211:443
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:13.246	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45562	target_addr:172.67.219.211:443
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:14.656	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53298	target_addr:172.67.168.140:443
time:2026-10-03T18:04:11Z	status:FAILURE	latency:32.344	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:57.278	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:58.423	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:67.474	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:04:11Z	status:HEALTHY	latency:244.845	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:09:11Z	status:UNKNOWN	latency:7.565	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:11.174	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51770	target_addr:172.67.168.140:443
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:11.188	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52912	target_addr:172.67.219.211:443
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:12.112	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52918	target_addr:172.67.219.211:443
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:12.541	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57946	target_addr:104.18.40.152:443
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:56.443	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:57.066	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:63.888	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:09:11Z	status:HEALTHY	latency:189.539	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:09:11Z	status:FAILURE	latency:211.040	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:14:11Z	status:UNKNOWN	latency:7.984	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:10.392	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40314	target_addr:104.18.40.152:443
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:10.239	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43300	target_addr:172.67.219.211:443
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:11.129	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56304	target_addr:104.21.86.125:443
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:12.097	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36688	target_addr:104.21.26.208:443
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:55.581	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:58.335	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:59.551	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:14:11Z	status:FAILURE	latency:225.363	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:14:11Z	status:HEALTHY	latency:235.500	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:19:11Z	status:UNKNOWN	latency:7.572	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:11.484	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34410	target_addr:104.21.86.125:443
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:13.228	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37622	target_addr:104.21.26.208:443
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:19.564	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54746	target_addr:172.64.147.104:443
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:26.251	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58942	target_addr:172.67.219.211:443
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:61.571	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:69.668	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:86.621	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:19:11Z	status:FAILURE	latency:220.995	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:19:11Z	status:HEALTHY	latency:225.394	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:12.862	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47434	target_addr:104.18.40.152:443
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:14.079	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37422	target_addr:172.67.168.140:443
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:17.151	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48620	target_addr:104.21.86.125:443
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:21.402	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51786	target_addr:172.67.219.211:443
time:2026-10-03T18:24:11Z	status:UNKNOWN	latency:40.017	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:66.572	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:106.286	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:24:11Z	status:FAILURE	latency:190.094	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:212.429	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:24:11Z	status:HEALTHY	latency:257.596	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:29:11Z	status:UNKNOWN	latency:7.221	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:9.166	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44256	target_addr:104.21.86.125:443
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:9.448	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42186	target_addr:172.64.147.104:443
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:11.107	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33886	target_addr:172.67.168.140:443
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:12.004	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44270	target_addr:104.21.86.125:443
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:53.751	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:63.404	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:65.495	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:29:11Z	status:HEALTHY	latency:193.298	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:29:11Z	status:FAILURE	latency:651.173	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:34:11Z	status:UNKNOWN	latency:7.528	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:9.327	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55048	target_addr:104.21.86.125:443
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:10.752	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43354	target_addr:104.21.26.208:443
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:11.080	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55260	target_addr:172.64.147.104:443
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:10.736	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55058	target_addr:104.21.86.125:443
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:53.383	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:54.848	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:63.445	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:34:11Z	status:HEALTHY	latency:103.034	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:34:11Z	status:FAILURE	latency:213.837	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:9.208	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59440	target_addr:104.18.40.152:443
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:9.526	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55110	target_addr:172.67.168.140:443
time:2026-10-03T18:39:11Z	status:UNKNOWN	latency:10.333	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:11.799	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55736	target_addr:172.67.219.211:443
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:11.350	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53726	target_addr:104.21.86.125:443
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:59.814	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:74.821	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:84.791	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:39:11Z	status:FAILURE	latency:205.169	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:39:11Z	status:HEALTHY	latency:287.357	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:44:11Z	status:UNKNOWN	latency:7.592	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:10.440	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60584	target_addr:172.64.147.104:443
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:10.956	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41904	target_addr:172.67.219.211:443
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:11.085	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41906	target_addr:172.67.219.211:443
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:10.718	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59076	target_addr:172.67.168.140:443
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:55.134	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:56.740	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:81.465	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:44:11Z	status:FAILURE	latency:217.064	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:44:11Z	status:HEALTHY	latency:232.985	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:49:11Z	status:UNKNOWN	latency:7.512	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:9.215	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33470	target_addr:104.21.86.125:443
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:10.202	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33478	target_addr:104.21.86.125:443
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:10.211	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42966	target_addr:104.21.26.208:443
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:11.106	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36190	target_addr:172.64.147.104:443
time:2026-10-03T18:49:11Z	status:FAILURE	latency:28.083	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:52.298	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:60.629	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:65.071	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:49:11Z	status:HEALTHY	latency:250.973	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:54:11Z	status:UNKNOWN	latency:7.047	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:8.916	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45488	target_addr:172.67.219.211:443
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:9.765	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35986	target_addr:104.18.40.152:443
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:9.803	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42410	target_addr:172.67.168.140:443
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:25.347	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45504	target_addr:172.67.219.211:443
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:56.167	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:62.868	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:54:11Z	status:FAILURE	latency:203.224	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:238.121	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:54:11Z	status:HEALTHY	latency:361.344	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:59:11Z	status:UNKNOWN	latency:7.386	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:9.616	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60676	target_addr:172.67.168.140:443
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:11.065	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52314	target_addr:104.18.40.152:443
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:11.946	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55042	target_addr:104.21.86.125:443
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:19.273	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55040	target_addr:104.21.86.125:443
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:54.221	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:56.084	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:59:11Z	status:FAILURE	latency:168.965	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:220.111	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T18:59:11Z	status:HEALTHY	latency:257.940	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:04:11Z	status:UNKNOWN	latency:20.593	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:20.431	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42040	target_addr:104.21.86.125:443
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:21.302	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37360	target_addr:172.64.147.104:443
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:20.907	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42030	target_addr:104.21.86.125:443
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:33.387	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40162	target_addr:104.21.26.208:443
time:2026-10-03T19:04:11Z	status:FAILURE	latency:44.018	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:64.143	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:72.134	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:104.999	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:04:11Z	status:HEALTHY	latency:228.175	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:09:11Z	status:UNKNOWN	latency:7.405	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:8.500	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47086	target_addr:104.18.40.152:443
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:9.117	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43834	target_addr:104.21.86.125:443
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:10.227	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36642	target_addr:104.21.26.208:443
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:14.534	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60718	target_addr:172.67.219.211:443
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:58.241	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:60.561	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:160.673	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:09:11Z	status:FAILURE	latency:191.007	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:09:11Z	status:HEALTHY	latency:339.483	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:14:11Z	status:UNKNOWN	latency:8.096	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:9.465	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51626	target_addr:172.64.147.104:443
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:9.987	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33910	target_addr:104.21.86.125:443
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:9.877	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49502	target_addr:172.67.168.140:443
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:11.423	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33926	target_addr:104.21.86.125:443
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:52.923	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:59.663	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:62.136	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:14:11Z	status:FAILURE	latency:206.244	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:14:11Z	status:HEALTHY	latency:211.572	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:19:11Z	status:UNKNOWN	latency:8.441	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:9.377	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56586	target_addr:172.64.147.104:443
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:11.182	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51282	target_addr:172.67.219.211:443
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:11.196	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37054	target_addr:172.67.168.140:443
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:20.711	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51298	target_addr:172.67.219.211:443
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:56.118	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:57.842	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:58.380	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:19:11Z	status:HEALTHY	latency:208.847	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:19:11Z	status:FAILURE	latency:229.603	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:7.760	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49206	target_addr:172.64.147.104:443
time:2026-10-03T19:24:11Z	status:UNKNOWN	latency:8.558	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:10.282	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43908	target_addr:172.67.219.211:443
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:11.000	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34948	target_addr:172.67.168.140:443
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:11.470	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43922	target_addr:172.67.219.211:443
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:55.842	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:73.413	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:85.034	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:24:11Z	status:HEALTHY	latency:114.898	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:24:11Z	status:FAILURE	latency:177.497	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:9.139	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55972	target_addr:172.67.219.211:443
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:9.753	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34302	target_addr:104.18.40.152:443
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:10.936	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51138	target_addr:104.21.26.208:443
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:11.100	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55988	target_addr:172.67.219.211:443
time:2026-10-03T19:29:11Z	status:UNKNOWN	latency:36.528	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:54.454	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:68.270	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:129.601	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:29:11Z	status:FAILURE	latency:205.729	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:29:11Z	status:HEALTHY	latency:2271.710	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:10.397	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54710	target_addr:104.21.86.125:443
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:11.466	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54714	target_addr:104.21.86.125:443
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:11.490	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39892	target_addr:172.67.168.140:443
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:13.040	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47222	target_addr:104.18.40.152:443
time:2026-10-03T19:34:11Z	status:UNKNOWN	latency:17.999	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:56.522	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:57.715	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:84.563	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:34:11Z	status:FAILURE	latency:166.861	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:34:11Z	status:HEALTHY	latency:237.357	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:9.541	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57574	target_addr:172.64.147.104:443
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:10.279	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56198	target_addr:172.67.168.140:443
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:10.393	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42552	target_addr:172.67.219.211:443
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:10.431	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42540	target_addr:172.67.219.211:443
time:2026-10-03T19:39:11Z	status:UNKNOWN	latency:15.677	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:39:11Z	status:FAILURE	latency:20.655	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:52.226	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:54.682	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:71.656	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:39:11Z	status:HEALTHY	latency:4658.722	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:44:11Z	status:UNKNOWN	latency:7.998	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:11.033	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54542	target_addr:104.21.86.125:443
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:12.042	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58842	target_addr:104.21.26.208:443
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:12.475	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54558	target_addr:104.21.86.125:443
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:53.693	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:57.728	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38318	target_addr:104.18.40.152:443
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:58.253	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:88.348	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:44:11Z	status:FAILURE	latency:219.846	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:44:11Z	status:HEALTHY	latency:231.454	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:49:11Z	status:UNKNOWN	latency:8.619	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:10.381	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54680	target_addr:104.21.86.125:443
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:11.418	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55638	target_addr:172.67.168.140:443
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:12.970	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44482	target_addr:104.18.40.152:443
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:56.572	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:57.544	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:81.540	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:49:11Z	status:FAILURE	latency:208.845	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:216.743	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:49:11Z	status:HEALTHY	latency:1720.907	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34270	target_addr:172.67.219.211:443
time:2026-10-03T19:54:11Z	status:UNKNOWN	latency:7.047	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:9.275	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54508	target_addr:104.21.86.125:443
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:10.561	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39510	target_addr:172.67.168.140:443
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:34.260	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54524	target_addr:104.21.86.125:443
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:44.338	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52070	target_addr:172.64.147.104:443
time:2026-10-03T19:54:11Z	status:FAILURE	latency:145.663	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:237.186	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:392.541	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:420.488	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:54:11Z	status:HEALTHY	latency:5432.066	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:10.283	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43370	target_addr:104.21.26.208:443
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:9.954	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45718	target_addr:172.67.219.211:443
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:9.988	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45730	target_addr:172.67.219.211:443
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:11.030	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46116	target_addr:172.64.147.104:443
time:2026-10-03T19:59:11Z	status:UNKNOWN	latency:57.098	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T19:59:11Z	status:FAILURE	latency:198.787	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:285.521	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:406.322	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:423.789	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T19:59:11Z	status:HEALTHY	latency:457.120	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:7.651	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56540	target_addr:104.18.40.152:443
time:2026-10-03T20:04:12Z	status:UNKNOWN	latency:8.282	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:8.865	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58838	target_addr:104.21.86.125:443
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:10.363	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44352	target_addr:172.67.168.140:443
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:10.891	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58846	target_addr:104.21.86.125:443
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:51.342	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:55.241	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:69.442	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:04:12Z	status:FAILURE	latency:229.941	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:04:12Z	status:HEALTHY	latency:443.789	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:09:12Z	status:UNKNOWN	latency:7.641	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:9.367	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35726	target_addr:104.21.86.125:443
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:10.520	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59376	target_addr:172.67.219.211:443
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:12.759	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49272	target_addr:104.21.26.208:443
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:12.716	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57606	target_addr:172.64.147.104:443
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:56.214	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:57.097	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:58.317	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:09:12Z	status:FAILURE	latency:172.600	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:09:12Z	status:HEALTHY	latency:191.990	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:9.611	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41564	target_addr:172.67.219.211:443
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:10.017	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36036	target_addr:104.21.26.208:443
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:11.655	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36276	target_addr:172.64.147.104:443
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:11.596	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41576	target_addr:172.67.219.211:443
time:2026-10-03T20:14:12Z	status:UNKNOWN	latency:16.695	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:60.095	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:70.923	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:71.307	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:14:12Z	status:FAILURE	latency:166.821	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:14:12Z	status:HEALTHY	latency:226.389	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:8.860	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46954	target_addr:172.67.219.211:443
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:10.592	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46956	target_addr:172.67.219.211:443
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:15.565	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52494	target_addr:172.67.168.140:443
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:17.505	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33954	target_addr:104.18.40.152:443
time:2026-10-03T20:19:12Z	status:FAILURE	latency:23.692	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:19:12Z	status:UNKNOWN	latency:47.093	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:56.829	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:58.460	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:89.882	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:19:12Z	status:HEALTHY	latency:200.560	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:24:12Z	status:UNKNOWN	latency:7.887	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:8.949	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51510	target_addr:104.18.40.152:443
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:10.578	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59648	target_addr:104.21.86.125:443
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:10.776	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54918	target_addr:172.67.219.211:443
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:11.585	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54282	target_addr:172.67.168.140:443
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:52.378	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:59.284	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:60.352	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:24:12Z	status:FAILURE	latency:178.862	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:24:12Z	status:HEALTHY	latency:224.051	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:29:12Z	status:UNKNOWN	latency:7.691	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:9.584	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50532	target_addr:172.67.168.140:443
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:10.507	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58008	target_addr:104.21.86.125:443
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:12.468	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50632	target_addr:172.64.147.104:443
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:23.300	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58002	target_addr:104.21.86.125:443
time:2026-10-03T20:29:12Z	status:FAILURE	latency:28.805	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:56.691	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:60.695	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:96.538	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:29:12Z	status:HEALTHY	latency:197.842	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:9.239	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48810	target_addr:172.67.219.211:443
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:11.750	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48822	target_addr:172.67.219.211:443
time:2026-10-03T20:34:12Z	status:UNKNOWN	latency:12.045	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:12.250	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41688	target_addr:172.64.147.104:443
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:12.959	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41072	target_addr:172.67.168.140:443
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:49.728	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:55.578	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:81.729	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:34:12Z	status:FAILURE	latency:201.889	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:34:12Z	status:HEALTHY	latency:5068.307	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:39:12Z	status:UNKNOWN	latency:89.553	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:139.520	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55680	target_addr:172.67.168.140:443
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:142.121	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60802	target_addr:172.67.219.211:443
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:143.117	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60812	target_addr:172.67.219.211:443
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:145.930	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37790	target_addr:104.18.40.152:443
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:303.358	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:306.798	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:373.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:39:12Z	status:FAILURE	latency:482.763	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:39:12Z	status:HEALTHY	latency:676.684	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:12.227	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43506	target_addr:172.67.219.211:443
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:12.746	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59352	target_addr:172.64.147.104:443
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:12.735	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44584	target_addr:172.67.168.140:443
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:17.750	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43518	target_addr:172.67.219.211:443
time:2026-10-03T20:44:12Z	status:UNKNOWN	latency:55.970	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:61.116	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:67.909	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:82.560	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:44:12Z	status:HEALTHY	latency:206.883	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:44:12Z	status:FAILURE	latency:226.760	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:9.926	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37296	target_addr:172.67.168.140:443
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:10.293	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48828	target_addr:104.18.40.152:443
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:11.466	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51752	target_addr:104.21.86.125:443
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:11.849	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58406	target_addr:172.67.219.211:443
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:54.043	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:49:12Z	status:UNKNOWN	latency:58.237	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:62.781	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:146.339	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:49:12Z	status:FAILURE	latency:187.647	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:49:12Z	status:HEALTHY	latency:195.905	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:54:12Z	status:UNKNOWN	latency:6.756	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:9.332	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59182	target_addr:172.67.219.211:443
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:10.347	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40306	target_addr:104.21.86.125:443
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:12.182	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49348	target_addr:172.67.168.140:443
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:14.192	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53374	target_addr:172.64.147.104:443
time:2026-10-03T20:54:12Z	status:FAILURE	latency:23.467	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:62.205	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:86.064	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:99.266	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:54:12Z	status:HEALTHY	latency:236.158	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:59:12Z	status:UNKNOWN	latency:8.944	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:10.467	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43092	target_addr:104.21.26.208:443
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:11.118	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39764	target_addr:172.67.219.211:443
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:11.667	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44638	target_addr:172.64.147.104:443
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:12.758	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39770	target_addr:172.67.219.211:443
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:55.033	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:57.045	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:59.021	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T20:59:12Z	status:FAILURE	latency:223.920	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T20:59:12Z	status:HEALTHY	latency:226.375	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:04:12Z	status:UNKNOWN	latency:6.985	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:10.543	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35132	target_addr:172.64.147.104:443
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:12.382	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57534	target_addr:104.21.86.125:443
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:51.869	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47424	target_addr:172.67.168.140:443
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:56.468	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:65.810	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:68.347	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:04:12Z	status:FAILURE	latency:142.701	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:292.842	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:04:12Z	status:HEALTHY	latency:2233.575	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42518	target_addr:172.67.219.211:443
time:2026-10-03T21:09:12Z	status:UNKNOWN	latency:7.025	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:12.123	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56110	target_addr:104.18.40.152:443
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:16.346	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51304	target_addr:104.21.86.125:443
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:19.325	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58952	target_addr:172.67.168.140:443
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:59.497	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:74.157	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:94.377	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:09:12Z	status:FAILURE	latency:178.138	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:229.837	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:09:12Z	status:HEALTHY	latency:5024.481	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34324	target_addr:172.67.219.211:443
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:12.398	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57624	target_addr:104.18.40.152:443
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:11.983	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50548	target_addr:172.67.219.211:443
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:12.321	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50554	target_addr:172.67.219.211:443
time:2026-10-03T21:14:12Z	status:UNKNOWN	latency:16.507	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:51.579	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:57.880	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:62.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:190.276	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:14:12Z	status:FAILURE	latency:222.860	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:14:12Z	status:HEALTHY	latency:748.605	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34930	target_addr:104.21.26.208:443
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:10.300	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41434	target_addr:172.67.219.211:443
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:10.413	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55018	target_addr:172.64.147.104:443
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:12.518	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41442	target_addr:172.67.219.211:443
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:16.722	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51920	target_addr:104.21.26.208:443
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:60.630	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:71.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:19:12Z	status:UNKNOWN	latency:91.073	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:96.947	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:19:12Z	status:FAILURE	latency:201.676	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:19:12Z	status:HEALTHY	latency:1233.766	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:24:12Z	status:UNKNOWN	latency:6.563	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:10.489	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49374	target_addr:104.18.40.152:443
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:11.859	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43236	target_addr:172.67.219.211:443
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:13.228	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52368	target_addr:104.21.86.125:443
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:20.628	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41008	target_addr:104.21.26.208:443
time:2026-10-03T21:24:12Z	status:FAILURE	latency:23.632	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:57.555	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:60.542	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:239.338	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:24:12Z	status:HEALTHY	latency:558.350	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:29:12Z	status:UNKNOWN	latency:6.990	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:10.863	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55330	target_addr:172.64.147.104:443
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:12.313	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40406	target_addr:172.67.219.211:443
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:12.398	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60860	target_addr:104.21.86.125:443
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:12.811	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42838	target_addr:172.67.168.140:443
time:2026-10-03T21:29:12Z	status:FAILURE	latency:29.802	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:52.858	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:57.817	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:132.191	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:29:12Z	status:HEALTHY	latency:241.429	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:34:12Z	status:UNKNOWN	latency:8.243	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:8.109	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55186	target_addr:172.67.219.211:443
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:9.874	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55196	target_addr:172.67.219.211:443
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:13.119	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51924	target_addr:104.18.40.152:443
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:13.804	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38172	target_addr:104.21.26.208:443
time:2026-10-03T21:34:12Z	status:FAILURE	latency:26.319	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:64.825	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:65.175	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:66.099	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:34:12Z	status:HEALTHY	latency:234.401	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:39:12Z	status:UNKNOWN	latency:6.894	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:8.356	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50222	target_addr:172.67.219.211:443
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:9.485	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50238	target_addr:172.67.219.211:443
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:11.690	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56514	target_addr:104.18.40.152:443
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:14.981	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43016	target_addr:104.21.26.208:443
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:52.784	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:57.687	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:73.208	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:39:12Z	status:FAILURE	latency:204.242	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:39:12Z	status:HEALTHY	latency:265.918	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:44:12Z	status:UNKNOWN	latency:11.032	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:11.845	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34752	target_addr:104.21.86.125:443
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:12.071	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55182	target_addr:104.21.26.208:443
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:13.136	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56168	target_addr:104.18.40.152:443
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:13.207	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54868	target_addr:172.67.219.211:443
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:60.466	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:63.341	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:63.792	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:44:12Z	status:FAILURE	latency:227.024	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:44:12Z	status:HEALTHY	latency:417.267	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:49:12Z	status:UNKNOWN	latency:7.806	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:12.510	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32942	target_addr:104.18.40.152:443
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:12.207	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57078	target_addr:172.67.168.140:443
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:12.205	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45898	target_addr:104.21.86.125:443
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:12.309	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45886	target_addr:104.21.86.125:443
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:62.231	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:68.567	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:49:12Z	status:FAILURE	latency:200.173	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:228.255	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:49:12Z	status:HEALTHY	latency:1544.690	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:54:12Z	status:UNKNOWN	latency:8.477	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:11.915	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39366	target_addr:104.21.26.208:443
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:11.479	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37396	target_addr:172.67.219.211:443
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:13.035	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53844	target_addr:172.64.147.104:443
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:12.894	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49944	target_addr:104.21.86.125:443
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:65.414	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:66.727	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:242.063	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:54:12Z	status:FAILURE	latency:328.873	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:54:12Z	status:HEALTHY	latency:877.103	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:10.165	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50304	target_addr:172.67.168.140:443
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:13.315	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39264	target_addr:172.67.219.211:443
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:14.842	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39274	target_addr:172.67.219.211:443
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:80.026	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:85.458	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:111.206	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:184.668	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38610	target_addr:172.64.147.104:443
time:2026-10-03T21:59:12Z	status:FAILURE	latency:188.843	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T21:59:12Z	status:UNKNOWN	latency:244.972	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T21:59:12Z	status:HEALTHY	latency:536.456	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:04:12Z	status:UNKNOWN	latency:10.518	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:10.151	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39324	target_addr:104.21.86.125:443
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:10.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39178	target_addr:172.64.147.104:443
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:10.934	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50694	target_addr:172.67.168.140:443
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:11.638	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52430	target_addr:172.67.219.211:443
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:58.768	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:66.581	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:218.099	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:04:12Z	status:FAILURE	latency:225.565	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:04:12Z	status:HEALTHY	latency:2404.757	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:09:12Z	status:UNKNOWN	latency:7.829	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:8.603	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50528	target_addr:172.67.168.140:443
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:10.366	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34060	target_addr:172.64.147.104:443
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:10.799	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52244	target_addr:172.67.219.211:443
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:11.839	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50896	target_addr:104.21.86.125:443
time:2026-10-03T22:09:12Z	status:FAILURE	latency:20.869	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:54.162	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:58.721	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:70.014	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:09:12Z	status:HEALTHY	latency:222.694	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:14:12Z	status:UNKNOWN	latency:7.381	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:12.095	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35898	target_addr:104.21.86.125:443
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:13.213	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35908	target_addr:104.21.86.125:443
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:17.510	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33802	target_addr:104.21.26.208:443
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:22.901	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45480	target_addr:104.18.40.152:443
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:55.598	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:75.426	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:14:12Z	status:FAILURE	latency:203.068	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:223.584	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:14:12Z	status:HEALTHY	latency:1031.259	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:19:12Z	status:UNKNOWN	latency:7.533	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:9.042	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35398	target_addr:172.67.168.140:443
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:11.255	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43524	target_addr:172.64.147.104:443
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:12.177	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49806	target_addr:172.67.219.211:443
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:16.039	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51590	target_addr:104.21.86.125:443
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:53.977	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:59.756	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:86.729	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:19:12Z	status:FAILURE	latency:165.035	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:19:12Z	status:HEALTHY	latency:249.734	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:24:12Z	status:UNKNOWN	latency:9.029	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:9.951	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37832	target_addr:172.67.219.211:443
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:10.427	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54410	target_addr:104.21.86.125:443
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:10.639	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51988	target_addr:104.18.40.152:443
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:12.365	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37922	target_addr:104.21.26.208:443
time:2026-10-03T22:24:12Z	status:FAILURE	latency:198.952	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:501.543	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:510.272	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:517.412	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:24:12Z	status:HEALTHY	latency:903.382	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:29:12Z	status:UNKNOWN	latency:7.370	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:9.765	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43636	target_addr:172.67.219.211:443
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:11.111	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60818	target_addr:104.21.26.208:443
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:16.527	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44902	target_addr:172.64.147.104:443
time:2026-10-03T22:29:12Z	status:FAILURE	latency:207.886	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:294.695	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:723.020	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:1513.970	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:2422.911	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40528	target_addr:104.21.86.125:443
time:2026-10-03T22:29:12Z	status:HEALTHY	latency:3117.471	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:34:12Z	status:UNKNOWN	latency:8.828	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:10.787	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41884	target_addr:172.67.219.211:443
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:11.151	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41644	target_addr:104.21.86.125:443
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:14.167	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56212	target_addr:172.67.168.140:443
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:17.833	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44764	target_addr:172.64.147.104:443
time:2026-10-03T22:34:12Z	status:FAILURE	latency:23.657	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:236.357	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:399.999	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:400.430	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:34:12Z	status:HEALTHY	latency:494.909	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:39:12Z	status:UNKNOWN	latency:8.082	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:11.523	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42982	target_addr:172.67.219.211:443
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:12.100	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42870	target_addr:104.18.40.152:443
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:11.706	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42986	target_addr:172.67.219.211:443
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:12.922	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52474	target_addr:172.67.168.140:443
time:2026-10-03T22:39:12Z	status:FAILURE	latency:199.436	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:221.652	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:426.506	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:437.090	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:39:12Z	status:HEALTHY	latency:450.636	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:11.908	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44502	target_addr:104.21.86.125:443
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:12.090	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59782	target_addr:172.67.219.211:443
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:12.455	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58824	target_addr:172.67.168.140:443
time:2026-10-03T22:44:12Z	status:UNKNOWN	latency:15.050	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:16.226	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57752	target_addr:172.64.147.104:443
time:2026-10-03T22:44:12Z	status:FAILURE	latency:222.023	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:226.857	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:443.694	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:478.099	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:44:12Z	status:HEALTHY	latency:522.075	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:49:12Z	status:UNKNOWN	latency:8.131	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:11.082	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35044	target_addr:172.67.219.211:443
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:12.762	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36584	target_addr:172.64.147.104:443
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:12.036	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54650	target_addr:104.21.86.125:443
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:20.250	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35450	target_addr:104.21.26.208:443
time:2026-10-03T22:49:12Z	status:FAILURE	latency:34.806	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:296.685	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:413.357	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:421.870	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:49:12Z	status:HEALTHY	latency:753.917	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:54:13Z	status:UNKNOWN	latency:8.070	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:10.180	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56842	target_addr:104.18.40.152:443
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:10.654	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34008	target_addr:172.67.168.140:443
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:12.178	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34386	target_addr:104.21.86.125:443
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:12.273	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46644	target_addr:172.67.219.211:443
time:2026-10-03T22:54:13Z	status:FAILURE	latency:29.986	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:212.297	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:458.689	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:471.369	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:54:13Z	status:HEALTHY	latency:506.911	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:59:13Z	status:UNKNOWN	latency:9.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:9.295	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50216	target_addr:104.21.86.125:443
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:11.496	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50218	target_addr:104.21.86.125:443
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:12.970	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53950	target_addr:104.21.26.208:443
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:17.650	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52756	target_addr:172.64.147.104:443
time:2026-10-03T22:59:13Z	status:FAILURE	latency:40.164	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:276.360	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:445.620	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:505.355	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T22:59:13Z	status:HEALTHY	latency:1011.463	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:04:13Z	status:UNKNOWN	latency:9.701	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:12.506	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45188	target_addr:104.21.26.208:443
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:12.968	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57130	target_addr:172.67.219.211:443
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:15.487	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41566	target_addr:172.64.147.104:443
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:17.166	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57138	target_addr:172.67.219.211:443
time:2026-10-03T23:04:13Z	status:FAILURE	latency:191.327	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:259.127	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:563.533	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:569.165	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:04:13Z	status:HEALTHY	latency:786.388	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:09:13Z	status:UNKNOWN	latency:9.580	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:12.580	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49824	target_addr:172.64.147.104:443
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:11.954	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38482	target_addr:172.67.168.140:443
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:12.871	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57780	target_addr:104.21.86.125:443
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:19.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36330	target_addr:172.67.219.211:443
time:2026-10-03T23:09:13Z	status:FAILURE	latency:180.634	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:209.307	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:428.930	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:498.148	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:09:13Z	status:HEALTHY	latency:1429.642	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:9.382	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59268	target_addr:172.67.219.211:443
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:11.719	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43202	target_addr:172.67.168.140:443
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:12.414	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32814	target_addr:172.64.147.104:443
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:19.409	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59280	target_addr:172.67.219.211:443
time:2026-10-03T23:14:13Z	status:FAILURE	latency:30.110	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:14:13Z	status:UNKNOWN	latency:34.696	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:56.514	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:59.879	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:60.527	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:14:13Z	status:HEALTHY	latency:267.336	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:19:13Z	status:UNKNOWN	latency:7.875	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:8.650	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42312	target_addr:104.21.86.125:443
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:10.937	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36442	target_addr:172.67.219.211:443
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:12.759	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48730	target_addr:172.67.168.140:443
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:14.469	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42982	target_addr:104.18.40.152:443
time:2026-10-03T23:19:13Z	status:FAILURE	latency:25.561	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:55.893	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:56.354	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:83.566	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:19:13Z	status:HEALTHY	latency:219.593	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:9.159	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51498	target_addr:104.18.40.152:443
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:11.151	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45692	target_addr:104.21.86.125:443
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:11.420	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45688	target_addr:104.21.86.125:443
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:11.838	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56392	target_addr:104.21.26.208:443
time:2026-10-03T23:24:13Z	status:UNKNOWN	latency:57.299	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:24:13Z	status:FAILURE	latency:258.113	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:272.660	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:1317.547	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:1337.660	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:24:13Z	status:HEALTHY	latency:1371.349	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:10.878	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51980	target_addr:104.21.86.125:443
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:11.476	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51992	target_addr:104.21.86.125:443
time:2026-10-03T23:29:13Z	status:UNKNOWN	latency:11.617	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:13.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58054	target_addr:172.67.168.140:443
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:14.779	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49590	target_addr:172.64.147.104:443
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:246.941	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:433.513	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:29:13Z	status:FAILURE	latency:594.751	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:619.638	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:29:13Z	status:HEALTHY	latency:723.677	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:10.915	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51232	target_addr:104.21.86.125:443
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:13.279	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36644	target_addr:172.64.147.104:443
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:13.282	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50136	target_addr:104.21.26.208:443
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:12.933	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51246	target_addr:104.21.86.125:443
time:2026-10-03T23:34:13Z	status:UNKNOWN	latency:19.577	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:253.712	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:34:13Z	status:FAILURE	latency:343.016	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:422.976	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:502.541	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:34:13Z	status:HEALTHY	latency:787.816	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:11.509	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35444	target_addr:172.64.147.104:443
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:11.099	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36344	target_addr:104.21.86.125:443
time:2026-10-03T23:39:13Z	status:UNKNOWN	latency:11.809	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:11.651	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36356	target_addr:104.21.86.125:443
time:2026-10-03T23:39:13Z	status:FAILURE	latency:31.903	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:221.219	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48912	target_addr:172.67.168.140:443
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:266.378	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:451.818	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:456.345	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:39:13Z	status:HEALTHY	latency:716.201	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:44:13Z	status:UNKNOWN	latency:7.654	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:10.674	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34708	target_addr:104.18.40.152:443
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:11.077	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56286	target_addr:172.67.219.211:443
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:17.081	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45358	target_addr:104.21.86.125:443
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:16.877	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38918	target_addr:104.21.26.208:443
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:200.128	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:44:13Z	status:FAILURE	latency:231.018	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:429.899	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:447.393	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:44:13Z	status:HEALTHY	latency:447.904	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:49:13Z	status:UNKNOWN	latency:6.740	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:9.245	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43386	target_addr:172.67.219.211:443
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:9.694	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45136	target_addr:104.21.26.208:443
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:9.753	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32796	target_addr:104.21.86.125:443
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:11.464	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49980	target_addr:104.18.40.152:443
time:2026-10-03T23:49:13Z	status:FAILURE	latency:21.511	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:264.141	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:423.854	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:478.210	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:49:13Z	status:HEALTHY	latency:732.334	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:8.590	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53036	target_addr:172.64.147.104:443
time:2026-10-03T23:54:13Z	status:UNKNOWN	latency:9.125	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:11.261	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44336	target_addr:104.21.86.125:443
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:14.740	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44346	target_addr:104.21.86.125:443
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:21.524	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46888	target_addr:172.67.168.140:443
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:242.565	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:54:13Z	status:FAILURE	latency:245.724	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:450.665	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:485.830	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:54:13Z	status:HEALTHY	latency:513.395	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:59:13Z	status:UNKNOWN	latency:7.178	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:9.789	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57706	target_addr:172.67.219.211:443
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:10.702	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52686	target_addr:104.21.86.125:443
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:12.042	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36386	target_addr:172.67.168.140:443
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:24.911	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43318	target_addr:104.18.40.152:443
time:2026-10-03T23:59:13Z	status:FAILURE	latency:36.236	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:214.472	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:722.781	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:764.314	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-03T23:59:13Z	status:HEALTHY	latency:927.545	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:04:13Z	status:UNKNOWN	latency:7.246	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:8.691	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52486	target_addr:104.21.86.125:443
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:11.334	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33194	target_addr:172.64.147.104:443
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:11.055	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52502	target_addr:104.21.86.125:443
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:75.957	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54998	target_addr:104.21.26.208:443
time:2026-10-04T00:04:13Z	status:FAILURE	latency:223.942	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:229.107	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:546.351	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:827.215	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:04:13Z	status:HEALTHY	latency:837.341	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:09:13Z	status:UNKNOWN	latency:7.007	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:9.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41158	target_addr:104.21.86.125:443
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:10.034	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41150	target_addr:104.21.86.125:443
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:12.648	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47226	target_addr:104.18.40.152:443
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:21.823	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34740	target_addr:172.67.168.140:443
time:2026-10-04T00:09:13Z	status:FAILURE	latency:173.837	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:202.054	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:420.237	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:424.704	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:09:13Z	status:HEALTHY	latency:450.486	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:10.615	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53712	target_addr:172.64.147.104:443
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:13.851	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43936	target_addr:104.21.86.125:443
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:15.894	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36028	target_addr:104.21.26.208:443
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:18.751	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35844	target_addr:172.67.219.211:443
time:2026-10-04T00:14:13Z	status:UNKNOWN	latency:41.437	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:14:13Z	status:FAILURE	latency:217.195	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:246.964	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:441.186	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:442.995	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:14:13Z	status:HEALTHY	latency:444.954	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:19:13Z	status:UNKNOWN	latency:8.617	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:11.051	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40690	target_addr:172.67.219.211:443
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:11.616	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52370	target_addr:104.21.86.125:443
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:12.189	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57434	target_addr:104.21.26.208:443
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:12.534	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60216	target_addr:104.18.40.152:443
time:2026-10-04T00:19:13Z	status:FAILURE	latency:225.455	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:225.565	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:434.647	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:458.245	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:19:13Z	status:HEALTHY	latency:466.023	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:24:13Z	status:UNKNOWN	latency:6.893	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:9.443	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48122	target_addr:172.64.147.104:443
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:10.176	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33454	target_addr:104.21.86.125:443
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:11.094	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33456	target_addr:104.21.86.125:443
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:12.199	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45796	target_addr:104.21.26.208:443
time:2026-10-04T00:24:13Z	status:FAILURE	latency:45.657	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:214.920	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:443.576	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:903.081	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:24:13Z	status:HEALTHY	latency:1385.203	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:29:13Z	status:UNKNOWN	latency:8.295	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:10.146	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33526	target_addr:172.67.219.211:443
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:11.394	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51658	target_addr:172.67.168.140:443
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:14.901	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46900	target_addr:104.18.40.152:443
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:21.425	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33530	target_addr:172.67.219.211:443
time:2026-10-04T00:29:13Z	status:FAILURE	latency:188.963	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:192.222	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:426.540	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:436.936	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:29:13Z	status:HEALTHY	latency:437.899	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:10.626	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46246	target_addr:104.21.86.125:443
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:10.726	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41950	target_addr:172.67.219.211:443
time:2026-10-04T00:34:13Z	status:UNKNOWN	latency:12.796	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:13.291	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40050	target_addr:172.64.147.104:443
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:14.368	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56822	target_addr:104.21.26.208:443
time:2026-10-04T00:34:13Z	status:FAILURE	latency:233.410	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:248.980	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:444.140	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:466.412	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:34:13Z	status:HEALTHY	latency:941.528	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:39:13Z	status:UNKNOWN	latency:8.096	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:9.244	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58156	target_addr:104.21.26.208:443
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:9.272	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55568	target_addr:104.21.86.125:443
time:2026-10-04T00:39:13Z	status:FAILURE	latency:24.178	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:27.092	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47654	target_addr:172.67.219.211:443
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:33.372	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59814	target_addr:104.18.40.152:443
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:428.817	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:431.735	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:437.384	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:39:13Z	status:HEALTHY	latency:2217.338	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:44:13Z	status:UNKNOWN	latency:6.336	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:9.763	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44530	target_addr:104.18.40.152:443
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:9.739	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58094	target_addr:104.21.86.125:443
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:10.709	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54404	target_addr:172.67.168.140:443
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:11.389	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58110	target_addr:104.21.86.125:443
time:2026-10-04T00:44:13Z	status:FAILURE	latency:201.060	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:222.946	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:412.553	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:783.540	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:44:13Z	status:HEALTHY	latency:812.637	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:49:13Z	status:UNKNOWN	latency:8.500	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:10.312	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52292	target_addr:172.67.219.211:443
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:11.455	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54948	target_addr:104.18.40.152:443
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:14.784	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52296	target_addr:172.67.219.211:443
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:113.725	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48936	target_addr:104.21.26.208:443
time:2026-10-04T00:49:13Z	status:FAILURE	latency:276.320	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:295.173	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:455.925	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:461.963	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:49:13Z	status:HEALTHY	latency:6510.696	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:54:13Z	status:UNKNOWN	latency:7.712	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:11.325	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53774	target_addr:104.18.40.152:443
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:15.097	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53096	target_addr:172.67.219.211:443
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:29.364	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59622	target_addr:172.67.168.140:443
time:2026-10-04T00:54:13Z	status:FAILURE	latency:238.664	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:438.587	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:442.252	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:451.625	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:1542.269	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45544	target_addr:104.21.86.125:443
time:2026-10-04T00:54:13Z	status:HEALTHY	latency:6706.307	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:59:13Z	status:UNKNOWN	latency:8.260	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:9.420	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47016	target_addr:172.64.147.104:443
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:11.976	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52818	target_addr:172.67.219.211:443
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:41.179	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48952	target_addr:104.21.86.125:443
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:63.347	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38510	target_addr:172.67.168.140:443
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:88.496	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:59:13Z	status:FAILURE	latency:218.861	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:614.158	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:630.809	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T00:59:13Z	status:HEALTHY	latency:631.103	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:11.512	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55506	target_addr:104.21.26.208:443
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:11.692	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53168	target_addr:172.67.219.211:443
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:11.640	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53176	target_addr:172.67.219.211:443
time:2026-10-04T01:04:13Z	status:UNKNOWN	latency:38.955	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:130.945	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35602	target_addr:172.64.147.104:443
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:255.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:465.345	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:528.344	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:04:13Z	status:HEALTHY	latency:547.348	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:04:13Z	status:FAILURE	latency:708.037	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:09:13Z	status:UNKNOWN	latency:9.308	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:9.965	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47276	target_addr:104.21.86.125:443
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:11.583	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60374	target_addr:104.21.26.208:443
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:12.256	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39346	target_addr:172.64.147.104:443
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:22.637	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45872	target_addr:172.67.219.211:443
time:2026-10-04T01:09:13Z	status:FAILURE	latency:205.871	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:251.047	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:454.328	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:541.664	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:09:13Z	status:HEALTHY	latency:549.281	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:14:13Z	status:UNKNOWN	latency:8.808	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:11.706	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58816	target_addr:104.21.26.208:443
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:11.775	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59774	target_addr:172.64.147.104:443
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:13.682	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58394	target_addr:104.21.86.125:443
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:25.612	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60730	target_addr:172.67.219.211:443
time:2026-10-04T01:14:13Z	status:FAILURE	latency:203.918	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:270.230	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:518.265	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:629.039	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:14:13Z	status:HEALTHY	latency:5643.273	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:10.614	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58236	target_addr:104.18.40.152:443
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:12.130	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51974	target_addr:172.67.219.211:443
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:12.739	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51968	target_addr:172.67.219.211:443
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:12.970	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48126	target_addr:172.67.168.140:443
time:2026-10-04T01:19:13Z	status:UNKNOWN	latency:69.804	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:103.586	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:19:13Z	status:FAILURE	latency:225.929	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:428.571	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:443.597	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:19:13Z	status:HEALTHY	latency:803.703	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:24:13Z	status:UNKNOWN	latency:8.159	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:11.608	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50244	target_addr:104.21.26.208:443
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:11.533	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60810	target_addr:104.21.86.125:443
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:15.559	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49120	target_addr:172.64.147.104:443
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:19.806	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60820	target_addr:104.21.86.125:443
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:101.687	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:24:13Z	status:FAILURE	latency:336.266	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:548.395	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:625.740	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:24:13Z	status:HEALTHY	latency:866.103	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:29:13Z	status:UNKNOWN	latency:7.983	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:12.838	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34580	target_addr:172.64.147.104:443
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:28.654	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59472	target_addr:104.21.26.208:443
time:2026-10-04T01:29:13Z	status:FAILURE	latency:29.955	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:39.707	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47546	target_addr:172.67.219.211:443
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:57.106	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47556	target_addr:172.67.219.211:443
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:211.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:443.477	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:458.103	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:29:13Z	status:HEALTHY	latency:475.776	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:11.352	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38860	target_addr:172.67.168.140:443
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:12.660	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47854	target_addr:104.21.86.125:443
time:2026-10-04T01:34:13Z	status:UNKNOWN	latency:16.990	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:19.167	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53506	target_addr:172.64.147.104:443
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:28.613	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54316	target_addr:172.67.219.211:443
time:2026-10-04T01:34:13Z	status:FAILURE	latency:224.273	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:276.275	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:768.914	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:1343.750	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:34:13Z	status:HEALTHY	latency:1470.689	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:12.508	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42802	target_addr:172.67.219.211:443
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:12.559	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42418	target_addr:104.21.26.208:443
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:15.101	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52454	target_addr:104.18.40.152:443
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:14.754	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51684	target_addr:104.21.86.125:443
time:2026-10-04T01:39:13Z	status:FAILURE	latency:27.905	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:39:13Z	status:UNKNOWN	latency:57.306	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:283.324	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:528.342	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:538.072	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:39:13Z	status:HEALTHY	latency:923.778	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:10.213	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58492	target_addr:172.67.168.140:443
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:11.843	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52810	target_addr:104.18.40.152:443
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:11.561	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44974	target_addr:172.67.219.211:443
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:11.872	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44962	target_addr:172.67.219.211:443
time:2026-10-04T01:44:13Z	status:UNKNOWN	latency:57.283	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:44:13Z	status:FAILURE	latency:246.036	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:264.551	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:490.556	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:500.764	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:44:13Z	status:HEALTHY	latency:539.845	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:49:13Z	status:UNKNOWN	latency:8.052	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:12.302	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42230	target_addr:104.18.40.152:443
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:12.323	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42566	target_addr:172.67.219.211:443
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:11.973	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42558	target_addr:172.67.219.211:443
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:12.559	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43696	target_addr:104.21.26.208:443
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:242.169	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:49:13Z	status:FAILURE	latency:329.833	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:433.290	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:433.347	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:49:13Z	status:HEALTHY	latency:704.136	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:54:13Z	status:UNKNOWN	latency:8.774	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:12.024	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52604	target_addr:172.67.168.140:443
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:16.967	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55540	target_addr:172.67.219.211:443
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:18.465	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43926	target_addr:172.64.147.104:443
time:2026-10-04T01:54:13Z	status:FAILURE	latency:42.262	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:61.501	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55554	target_addr:172.67.219.211:443
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:211.018	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:480.833	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:490.980	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:54:13Z	status:HEALTHY	latency:560.838	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:11.811	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47500	target_addr:104.18.40.152:443
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:11.391	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50036	target_addr:172.67.219.211:443
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:11.802	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55808	target_addr:104.21.86.125:443
time:2026-10-04T01:59:13Z	status:UNKNOWN	latency:12.474	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:12.908	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50226	target_addr:172.67.168.140:443
time:2026-10-04T01:59:13Z	status:FAILURE	latency:191.301	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:263.866	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:456.821	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:462.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T01:59:13Z	status:HEALTHY	latency:519.826	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:04:13Z	status:UNKNOWN	latency:9.183	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:9.557	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45546	target_addr:172.67.219.211:443
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:13.233	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50694	target_addr:172.64.147.104:443
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:13.790	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45548	target_addr:172.67.219.211:443
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:19.948	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35866	target_addr:172.67.168.140:443
time:2026-10-04T02:04:13Z	status:FAILURE	latency:188.537	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:195.180	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:436.001	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:447.429	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:04:13Z	status:HEALTHY	latency:777.652	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:09:13Z	status:UNKNOWN	latency:7.040	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:10.060	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54514	target_addr:104.21.86.125:443
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:10.864	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47418	target_addr:104.18.40.152:443
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:12.749	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54526	target_addr:104.21.86.125:443
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:28.624	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57600	target_addr:104.21.26.208:443
time:2026-10-04T02:09:13Z	status:FAILURE	latency:215.418	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:254.503	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:442.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:443.758	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:09:13Z	status:HEALTHY	latency:444.819	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:14:13Z	status:UNKNOWN	latency:9.244	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:11.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43278	target_addr:104.21.86.125:443
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:11.633	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36018	target_addr:172.67.219.211:443
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:12.897	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55970	target_addr:104.18.40.152:443
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:13.391	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53492	target_addr:172.67.168.140:443
time:2026-10-04T02:14:13Z	status:FAILURE	latency:27.018	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:413.986	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:462.817	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:464.374	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:14:13Z	status:HEALTHY	latency:614.502	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:19:13Z	status:UNKNOWN	latency:7.639	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:10.104	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57948	target_addr:172.67.219.211:443
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:12.457	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52996	target_addr:172.64.147.104:443
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:12.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47096	target_addr:104.21.26.208:443
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:13.079	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57952	target_addr:172.67.219.211:443
time:2026-10-04T02:19:13Z	status:FAILURE	latency:31.616	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:211.855	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:436.438	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:449.909	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:19:13Z	status:HEALTHY	latency:701.033	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:11.802	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37434	target_addr:104.21.86.125:443
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:11.872	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55496	target_addr:104.21.26.208:443
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:12.620	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43160	target_addr:104.18.40.152:443
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:13.033	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37432	target_addr:104.21.86.125:443
time:2026-10-04T02:24:13Z	status:UNKNOWN	latency:14.953	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:24:13Z	status:FAILURE	latency:26.412	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:63.089	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:68.281	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:74.209	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:24:13Z	status:HEALTHY	latency:220.238	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:29:14Z	status:UNKNOWN	latency:7.940	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:9.311	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38762	target_addr:172.64.147.104:443
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:10.258	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60472	target_addr:104.21.26.208:443
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:9.854	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40012	target_addr:172.67.219.211:443
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:12.524	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40016	target_addr:172.67.219.211:443
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:63.003	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:72.554	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:86.189	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:29:14Z	status:HEALTHY	latency:240.205	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:29:14Z	status:FAILURE	latency:241.049	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:34:14Z	status:UNKNOWN	latency:9.543	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:9.573	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50266	target_addr:172.67.219.211:443
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:10.100	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59624	target_addr:104.18.40.152:443
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:10.257	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54122	target_addr:172.67.168.140:443
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:12.310	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50274	target_addr:172.67.219.211:443
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:62.011	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:119.525	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:34:14Z	status:FAILURE	latency:165.971	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:214.530	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:34:14Z	status:HEALTHY	latency:235.634	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:39:14Z	status:UNKNOWN	latency:7.861	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:10.109	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44638	target_addr:172.67.168.140:443
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:13.296	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34780	target_addr:104.21.86.125:443
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:15.811	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48370	target_addr:172.64.147.104:443
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:15.541	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39652	target_addr:172.67.219.211:443
time:2026-10-04T02:39:14Z	status:FAILURE	latency:34.004	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:235.166	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:404.631	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:428.106	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:39:14Z	status:HEALTHY	latency:749.744	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:44:14Z	status:UNKNOWN	latency:9.139	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:11.145	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42822	target_addr:104.21.26.208:443
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:11.245	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32974	target_addr:172.64.147.104:443
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:12.291	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56418	target_addr:172.67.219.211:443
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:57.886	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:62.832	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:70.145	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:307.190	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57520	target_addr:104.21.86.125:443
time:2026-10-04T02:44:14Z	status:HEALTHY	latency:333.433	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:44:14Z	status:FAILURE	latency:438.057	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:9.570	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36856	target_addr:104.21.26.208:443
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:10.585	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41606	target_addr:172.64.147.104:443
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:14.197	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60708	target_addr:104.21.86.125:443
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:48.084	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60722	target_addr:104.21.86.125:443
time:2026-10-04T02:49:14Z	status:UNKNOWN	latency:50.544	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:72.114	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:90.869	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:117.412	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:49:14Z	status:FAILURE	latency:211.826	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:49:14Z	status:HEALTHY	latency:262.723	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:54:14Z	status:UNKNOWN	latency:8.013	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:8.839	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47294	target_addr:104.21.86.125:443
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:10.214	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52708	target_addr:104.21.26.208:443
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:10.790	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40996	target_addr:104.18.40.152:443
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:11.027	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35376	target_addr:172.67.219.211:443
time:2026-10-04T02:54:14Z	status:FAILURE	latency:210.236	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:232.273	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:435.076	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:446.901	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:54:14Z	status:HEALTHY	latency:450.725	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:59:14Z	status:UNKNOWN	latency:7.561	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:9.862	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43210	target_addr:172.64.147.104:443
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:10.864	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43378	target_addr:172.67.168.140:443
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:12.328	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56172	target_addr:104.21.86.125:443
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:13.472	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56176	target_addr:104.21.86.125:443
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:58.196	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:62.419	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:63.284	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T02:59:14Z	status:FAILURE	latency:201.291	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T02:59:14Z	status:HEALTHY	latency:245.415	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:04:14Z	status:UNKNOWN	latency:6.794	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:13.652	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42178	target_addr:172.67.219.211:443
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:22.636	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37010	target_addr:172.64.147.104:443
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:57.619	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:61.439	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46530	target_addr:104.21.26.208:443
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:65.288	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:105.799	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42172	target_addr:172.67.219.211:443
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:121.317	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:04:14Z	status:FAILURE	latency:195.617	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:04:14Z	status:HEALTHY	latency:254.335	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:8.965	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32976	target_addr:172.67.219.211:443
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:9.849	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38376	target_addr:172.67.168.140:443
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:11.714	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36874	target_addr:104.21.86.125:443
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:17.855	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44696	target_addr:172.64.147.104:443
time:2026-10-04T03:09:14Z	status:UNKNOWN	latency:28.452	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:54.750	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:61.277	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:68.690	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:09:14Z	status:FAILURE	latency:219.507	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:09:14Z	status:HEALTHY	latency:259.269	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:14:14Z	status:UNKNOWN	latency:8.227	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:10.640	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39470	target_addr:104.21.86.125:443
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:12.380	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59264	target_addr:104.21.26.208:443
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:13.096	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42032	target_addr:172.64.147.104:443
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:20.487	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39726	target_addr:172.67.219.211:443
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:57.466	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:104.049	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:172.780	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:14:14Z	status:FAILURE	latency:204.403	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:14:14Z	status:HEALTHY	latency:270.257	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:19:14Z	status:UNKNOWN	latency:8.336	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:10.165	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49666	target_addr:172.67.168.140:443
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:10.791	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54104	target_addr:104.18.40.152:443
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:10.516	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32906	target_addr:172.67.219.211:443
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:13.951	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50388	target_addr:104.21.86.125:443
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:56.196	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:56.576	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:161.113	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:19:14Z	status:FAILURE	latency:170.777	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:19:14Z	status:HEALTHY	latency:239.226	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:24:14Z	status:UNKNOWN	latency:8.031	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:9.065	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57288	target_addr:104.18.40.152:443
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:13.252	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58610	target_addr:104.21.86.125:443
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:13.353	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37294	target_addr:172.67.168.140:443
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:13.694	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58596	target_addr:104.21.86.125:443
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:60.717	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:61.868	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:70.177	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:24:14Z	status:FAILURE	latency:202.660	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:24:14Z	status:HEALTHY	latency:227.142	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:29:14Z	status:UNKNOWN	latency:9.077	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:11.712	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50058	target_addr:172.67.219.211:443
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:12.635	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57022	target_addr:104.18.40.152:443
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:13.040	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50060	target_addr:172.67.219.211:443
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:18.169	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48136	target_addr:172.67.168.140:443
time:2026-10-04T03:29:14Z	status:FAILURE	latency:27.832	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:56.834	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:57.480	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:63.114	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:29:14Z	status:HEALTHY	latency:239.126	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:9.337	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36404	target_addr:172.64.147.104:443
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:9.979	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46526	target_addr:104.21.26.208:443
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:10.822	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39558	target_addr:172.67.219.211:443
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:13.299	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39568	target_addr:172.67.219.211:443
time:2026-10-04T03:34:14Z	status:UNKNOWN	latency:57.139	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:34:14Z	status:FAILURE	latency:177.373	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:242.303	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:449.372	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:454.492	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:34:14Z	status:HEALTHY	latency:471.953	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:8.665	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35352	target_addr:172.67.219.211:443
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:10.476	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57632	target_addr:104.21.86.125:443
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:11.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40310	target_addr:104.18.40.152:443
time:2026-10-04T03:39:14Z	status:UNKNOWN	latency:13.663	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:13.042	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57818	target_addr:172.67.168.140:443
time:2026-10-04T03:39:14Z	status:FAILURE	latency:27.495	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:264.363	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:374.628	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:481.432	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:39:14Z	status:HEALTHY	latency:488.012	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:44:14Z	status:UNKNOWN	latency:8.355	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:11.460	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37352	target_addr:172.64.147.104:443
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:11.685	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44674	target_addr:104.21.26.208:443
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:11.326	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33608	target_addr:172.67.219.211:443
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:13.016	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45762	target_addr:104.21.86.125:443
time:2026-10-04T03:44:14Z	status:FAILURE	latency:227.340	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:267.994	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:441.852	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:739.946	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:44:14Z	status:HEALTHY	latency:770.738	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:49:14Z	status:UNKNOWN	latency:6.303	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:10.703	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55360	target_addr:104.18.40.152:443
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:10.647	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56904	target_addr:172.67.219.211:443
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:11.220	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38674	target_addr:172.67.168.140:443
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:11.725	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56914	target_addr:172.67.219.211:443
time:2026-10-04T03:49:14Z	status:FAILURE	latency:34.967	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:261.101	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:479.986	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:537.127	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:49:14Z	status:HEALTHY	latency:537.378	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:54:14Z	status:UNKNOWN	latency:6.384	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:9.586	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44728	target_addr:104.21.86.125:443
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:10.755	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32794	target_addr:104.18.40.152:443
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:10.742	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49086	target_addr:104.21.26.208:443
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:10.602	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32866	target_addr:172.67.219.211:443
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:55.749	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:58.405	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:72.019	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:54:14Z	status:FAILURE	latency:324.330	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:54:14Z	status:HEALTHY	latency:446.985	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:59:14Z	status:UNKNOWN	latency:11.728	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:13.280	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38952	target_addr:172.64.147.104:443
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:13.266	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38272	target_addr:172.67.168.140:443
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:14.174	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53432	target_addr:104.21.86.125:443
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:14.892	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57408	target_addr:172.67.219.211:443
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:61.559	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:59:14Z	status:FAILURE	latency:60.565	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:71.990	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:313.188	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T03:59:14Z	status:HEALTHY	latency:1073.830	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:9.253	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45194	target_addr:172.67.219.211:443
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:10.688	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60630	target_addr:104.18.40.152:443
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:10.491	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37718	target_addr:104.21.86.125:443
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:12.793	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39458	target_addr:172.67.168.140:443
time:2026-10-04T04:04:14Z	status:UNKNOWN	latency:37.192	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:52.893	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:55.693	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:61.726	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:04:14Z	status:FAILURE	latency:200.274	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:04:14Z	status:HEALTHY	latency:215.631	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:09:14Z	status:UNKNOWN	latency:6.659	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:9.533	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56934	target_addr:104.18.40.152:443
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:10.815	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50674	target_addr:104.21.26.208:443
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:11.895	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43270	target_addr:104.21.86.125:443
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:15.262	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50532	target_addr:172.67.219.211:443
time:2026-10-04T04:09:14Z	status:FAILURE	latency:35.157	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:259.724	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:421.597	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:425.681	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:09:14Z	status:HEALTHY	latency:426.352	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:9.487	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46900	target_addr:172.64.147.104:443
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:11.496	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35178	target_addr:104.21.26.208:443
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:12.528	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40502	target_addr:172.67.219.211:443
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:13.050	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40514	target_addr:172.67.219.211:443
time:2026-10-04T04:14:14Z	status:UNKNOWN	latency:52.281	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:60.314	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:69.834	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:91.954	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:14:14Z	status:FAILURE	latency:248.670	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:14:14Z	status:HEALTHY	latency:310.496	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:7.559	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43000	target_addr:172.64.147.104:443
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:12.367	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50346	target_addr:104.21.26.208:443
time:2026-10-04T04:19:14Z	status:UNKNOWN	latency:22.945	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:30.772	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54322	target_addr:172.67.219.211:443
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:41.157	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39392	target_addr:104.21.86.125:443
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:51.020	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:52.296	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:86.351	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:19:14Z	status:HEALTHY	latency:201.905	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:19:14Z	status:FAILURE	latency:213.528	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:24:14Z	status:UNKNOWN	latency:10.267	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:12.710	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53056	target_addr:172.67.168.140:443
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:12.538	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36616	target_addr:104.21.86.125:443
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:12.784	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36632	target_addr:104.21.86.125:443
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:12.612	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34668	target_addr:104.18.40.152:443
time:2026-10-04T04:24:14Z	status:FAILURE	latency:25.764	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:63.622	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:64.805	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:65.721	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:24:14Z	status:HEALTHY	latency:216.441	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:11.075	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50102	target_addr:104.21.26.208:443
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:11.756	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57976	target_addr:172.64.147.104:443
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:12.230	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42198	target_addr:104.21.86.125:443
time:2026-10-04T04:29:14Z	status:UNKNOWN	latency:13.250	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:19.148	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42636	target_addr:172.67.219.211:443
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:56.475	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:58.304	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:29:14Z	status:FAILURE	latency:197.270	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:264.555	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:29:14Z	status:HEALTHY	latency:328.078	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:10.214	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56652	target_addr:104.21.26.208:443
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:10.747	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55356	target_addr:172.67.219.211:443
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:11.645	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55300	target_addr:104.18.40.152:443
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:22.826	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55370	target_addr:172.67.219.211:443
time:2026-10-04T04:34:14Z	status:FAILURE	latency:33.034	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:34:14Z	status:UNKNOWN	latency:36.084	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:58.455	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:74.398	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:92.584	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:34:14Z	status:HEALTHY	latency:248.737	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:39:14Z	status:UNKNOWN	latency:9.417	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:12.039	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45166	target_addr:172.67.168.140:443
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:12.838	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42780	target_addr:104.21.86.125:443
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:11.507	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37098	target_addr:172.67.219.211:443
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:19.379	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41590	target_addr:172.64.147.104:443
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:53.803	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:61.367	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:127.244	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:39:14Z	status:FAILURE	latency:198.009	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:39:14Z	status:HEALTHY	latency:245.503	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:9.637	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60164	target_addr:172.64.147.104:443
time:2026-10-04T04:44:14Z	status:UNKNOWN	latency:9.815	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:12.647	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58656	target_addr:104.21.26.208:443
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:12.949	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37472	target_addr:104.21.86.125:443
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:14.013	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34196	target_addr:172.67.219.211:443
time:2026-10-04T04:44:14Z	status:FAILURE	latency:28.995	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:63.568	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:83.588	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:254.058	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:44:14Z	status:HEALTHY	latency:1516.641	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:49:14Z	status:UNKNOWN	latency:7.740	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:9.843	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46906	target_addr:172.67.219.211:443
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:10.678	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46914	target_addr:172.67.219.211:443
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:15.185	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46690	target_addr:172.64.147.104:443
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:15.294	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56568	target_addr:104.21.26.208:443
time:2026-10-04T04:49:14Z	status:FAILURE	latency:27.642	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:58.157	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:76.927	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:146.435	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:49:14Z	status:HEALTHY	latency:278.891	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:8.689	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53456	target_addr:172.67.168.140:443
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:8.827	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37588	target_addr:104.21.86.125:443
time:2026-10-04T04:54:14Z	status:UNKNOWN	latency:9.610	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:11.899	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45516	target_addr:172.67.219.211:443
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:12.075	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52826	target_addr:104.18.40.152:443
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:61.133	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:64.117	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:67.979	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:54:14Z	status:FAILURE	latency:226.386	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:54:14Z	status:HEALTHY	latency:260.166	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:59:14Z	status:UNKNOWN	latency:8.237	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:9.430	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56994	target_addr:104.21.26.208:443
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:9.442	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35642	target_addr:172.64.147.104:443
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:10.612	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59528	target_addr:104.21.86.125:443
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:13.514	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59538	target_addr:104.21.86.125:443
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:56.324	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:58.808	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:71.223	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T04:59:14Z	status:FAILURE	latency:201.636	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T04:59:14Z	status:HEALTHY	latency:254.366	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:04:14Z	status:UNKNOWN	latency:7.831	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:10.622	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55444	target_addr:172.67.219.211:443
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:11.065	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55446	target_addr:172.67.219.211:443
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:12.825	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50086	target_addr:172.67.168.140:443
time:2026-10-04T05:04:14Z	status:FAILURE	latency:32.505	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:34.066	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59740	target_addr:172.64.147.104:443
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:54.446	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:64.224	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:106.556	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:04:14Z	status:HEALTHY	latency:216.726	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:09:14Z	status:UNKNOWN	latency:9.306	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:11.250	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52906	target_addr:172.67.168.140:443
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:10.925	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33020	target_addr:172.67.219.211:443
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:12.300	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49150	target_addr:172.64.147.104:443
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:12.135	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51896	target_addr:104.21.86.125:443
time:2026-10-04T05:09:14Z	status:FAILURE	latency:23.817	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:55.807	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:71.610	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:75.509	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:09:14Z	status:HEALTHY	latency:239.168	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:14:14Z	status:UNKNOWN	latency:9.408	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:10.465	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54256	target_addr:104.18.40.152:443
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:10.398	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48790	target_addr:104.21.26.208:443
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:11.437	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38906	target_addr:104.21.86.125:443
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:18.566	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39562	target_addr:172.67.219.211:443
time:2026-10-04T05:14:14Z	status:FAILURE	latency:26.766	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:56.877	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:58.737	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:59.640	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:14:14Z	status:HEALTHY	latency:286.279	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:19:14Z	status:UNKNOWN	latency:7.896	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:12.400	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49848	target_addr:104.21.86.125:443
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:12.192	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52352	target_addr:172.67.219.211:443
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:12.120	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53920	target_addr:104.21.26.208:443
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:12.381	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59684	target_addr:172.64.147.104:443
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:55.639	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:57.364	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:57.826	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:19:14Z	status:FAILURE	latency:204.849	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:19:14Z	status:HEALTHY	latency:275.311	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:24:14Z	status:UNKNOWN	latency:7.360	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:10.837	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46412	target_addr:172.67.219.211:443
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:11.543	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49662	target_addr:104.18.40.152:443
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:12.716	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56914	target_addr:104.21.26.208:443
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:12.829	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46420	target_addr:172.67.219.211:443
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:54.487	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:77.313	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:78.930	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:24:14Z	status:FAILURE	latency:140.397	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:24:14Z	status:HEALTHY	latency:259.060	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:29:14Z	status:UNKNOWN	latency:7.747	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:10.241	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53726	target_addr:172.67.219.211:443
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:10.958	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60642	target_addr:172.64.147.104:443
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:11.336	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44330	target_addr:104.21.26.208:443
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:21.016	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36520	target_addr:104.21.86.125:443
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:56.282	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:68.001	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:68.700	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:29:14Z	status:FAILURE	latency:211.267	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:29:14Z	status:HEALTHY	latency:270.601	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:11.369	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41882	target_addr:104.21.86.125:443
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:12.796	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55214	target_addr:172.67.219.211:443
time:2026-10-04T05:34:14Z	status:UNKNOWN	latency:20.750	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:24.034	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38068	target_addr:104.18.40.152:443
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:27.095	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59328	target_addr:104.21.26.208:443
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:60.785	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:61.033	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:68.443	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:34:14Z	status:FAILURE	latency:202.044	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:34:14Z	status:HEALTHY	latency:332.445	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:11.775	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36686	target_addr:172.67.219.211:443
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:12.309	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36698	target_addr:172.67.219.211:443
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:14.268	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34776	target_addr:104.21.26.208:443
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:26.276	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49140	target_addr:104.18.40.152:443
time:2026-10-04T05:39:14Z	status:UNKNOWN	latency:57.083	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:58.380	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:70.271	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:39:14Z	status:FAILURE	latency:204.984	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:266.736	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:39:14Z	status:HEALTHY	latency:310.039	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:44:14Z	status:UNKNOWN	latency:9.857	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:11.703	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50692	target_addr:172.67.168.140:443
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:13.663	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38726	target_addr:172.67.219.211:443
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:13.801	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32808	target_addr:104.21.86.125:443
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:14.209	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58656	target_addr:104.18.40.152:443
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:54.962	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:57.233	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:80.899	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:44:14Z	status:FAILURE	latency:205.315	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:44:14Z	status:HEALTHY	latency:265.060	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:10.311	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41426	target_addr:172.67.219.211:443
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:10.850	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47750	target_addr:104.21.86.125:443
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:12.284	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53990	target_addr:172.64.147.104:443
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:17.818	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34618	target_addr:104.21.26.208:443
time:2026-10-04T05:49:14Z	status:FAILURE	latency:25.741	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:49:14Z	status:UNKNOWN	latency:34.092	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:58.793	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:59.026	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:63.959	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:49:14Z	status:HEALTHY	latency:248.967	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:54:14Z	status:UNKNOWN	latency:8.808	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:9.342	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53758	target_addr:104.18.40.152:443
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:10.104	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43056	target_addr:104.21.86.125:443
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:10.183	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33066	target_addr:104.21.26.208:443
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:9.618	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43050	target_addr:104.21.86.125:443
time:2026-10-04T05:54:14Z	status:FAILURE	latency:30.110	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:60.772	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:61.545	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:65.897	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:54:14Z	status:HEALTHY	latency:227.319	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:59:14Z	status:UNKNOWN	latency:9.781	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:10.662	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40008	target_addr:172.67.219.211:443
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:14.102	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40018	target_addr:172.67.219.211:443
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:23.077	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46122	target_addr:104.21.26.208:443
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:47.174	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37946	target_addr:104.18.40.152:443
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:60.707	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:68.262	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:59:14Z	status:FAILURE	latency:169.348	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:247.605	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T05:59:14Z	status:HEALTHY	latency:780.819	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:9.736	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48088	target_addr:172.67.168.140:443
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:10.583	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46526	target_addr:172.67.219.211:443
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:14.272	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43120	target_addr:172.64.147.104:443
time:2026-10-04T06:04:15Z	status:UNKNOWN	latency:15.301	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:21.497	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46540	target_addr:172.67.219.211:443
time:2026-10-04T06:04:15Z	status:FAILURE	latency:30.227	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:50.975	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:56.797	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:61.913	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:04:15Z	status:HEALTHY	latency:295.026	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:10.029	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39450	target_addr:104.18.40.152:443
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:10.709	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59080	target_addr:104.21.86.125:443
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:11.650	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59090	target_addr:104.21.86.125:443
time:2026-10-04T06:09:15Z	status:UNKNOWN	latency:15.976	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:19.834	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48434	target_addr:172.67.168.140:443
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:52.395	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:55.726	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:86.683	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:09:15Z	status:FAILURE	latency:193.658	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:09:15Z	status:HEALTHY	latency:369.854	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:14:15Z	status:UNKNOWN	latency:8.225	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:13.004	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44678	target_addr:104.18.40.152:443
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:12.845	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47278	target_addr:172.67.219.211:443
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:14.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43894	target_addr:172.67.168.140:443
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:70.250	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:70.428	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54244	target_addr:104.21.86.125:443
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:71.472	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:73.431	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:14:15Z	status:FAILURE	latency:221.948	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:14:15Z	status:HEALTHY	latency:249.577	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:19:15Z	status:UNKNOWN	latency:6.387	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:9.261	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44316	target_addr:104.21.86.125:443
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:10.467	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59562	target_addr:172.64.147.104:443
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:10.476	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53814	target_addr:104.21.26.208:443
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:11.518	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59564	target_addr:172.67.219.211:443
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:54.439	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:56.435	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:60.555	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:19:15Z	status:FAILURE	latency:141.745	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:19:15Z	status:HEALTHY	latency:224.252	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:8.989	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59838	target_addr:172.64.147.104:443
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:9.359	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38890	target_addr:172.67.219.211:443
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:10.339	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38902	target_addr:172.67.219.211:443
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:11.579	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58486	target_addr:104.21.26.208:443
time:2026-10-04T06:24:15Z	status:UNKNOWN	latency:33.710	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:53.918	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:55.832	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:61.027	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:24:15Z	status:FAILURE	latency:223.025	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:24:15Z	status:HEALTHY	latency:247.682	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:29:15Z	status:UNKNOWN	latency:8.016	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:11.534	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53798	target_addr:104.18.40.152:443
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:12.534	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57362	target_addr:104.21.86.125:443
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:13.659	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57366	target_addr:104.21.86.125:443
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:26.141	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50552	target_addr:172.67.168.140:443
time:2026-10-04T06:29:15Z	status:FAILURE	latency:26.790	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:66.757	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:73.378	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:94.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:29:15Z	status:HEALTHY	latency:221.304	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:10.767	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41846	target_addr:104.21.26.208:443
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:12.019	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43962	target_addr:172.67.219.211:443
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:30.124	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58034	target_addr:104.18.40.152:443
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:59.299	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:59.629	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:65.443	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:34:15Z	status:UNKNOWN	latency:106.808	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:112.322	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43968	target_addr:172.67.219.211:443
time:2026-10-04T06:34:15Z	status:FAILURE	latency:185.170	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:34:15Z	status:HEALTHY	latency:264.385	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:39:15Z	status:UNKNOWN	latency:7.180	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:10.596	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58612	target_addr:104.21.26.208:443
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:12.055	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33494	target_addr:104.18.40.152:443
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:12.484	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34554	target_addr:172.67.219.211:443
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:17.845	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52268	target_addr:104.21.86.125:443
time:2026-10-04T06:39:15Z	status:FAILURE	latency:37.295	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:224.457	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:440.060	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:445.370	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:39:15Z	status:HEALTHY	latency:744.262	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:44:15Z	status:UNKNOWN	latency:7.783	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:9.517	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50682	target_addr:172.67.219.211:443
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:9.836	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50672	target_addr:172.67.219.211:443
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:11.781	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33674	target_addr:104.18.40.152:443
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:11.930	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52838	target_addr:104.21.26.208:443
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:52.523	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:56.460	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:59.253	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:44:15Z	status:HEALTHY	latency:198.911	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:44:15Z	status:FAILURE	latency:211.663	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:49:15Z	status:UNKNOWN	latency:7.545	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:9.320	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48744	target_addr:172.64.147.104:443
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:9.356	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58030	target_addr:172.67.168.140:443
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:9.374	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49070	target_addr:172.67.219.211:443
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:9.464	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49076	target_addr:172.67.219.211:443
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:54.693	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:81.133	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:91.776	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:49:15Z	status:HEALTHY	latency:188.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:49:15Z	status:FAILURE	latency:207.686	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:54:15Z	status:UNKNOWN	latency:8.071	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:9.722	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47114	target_addr:172.64.147.104:443
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:11.153	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58634	target_addr:172.67.219.211:443
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:11.432	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48696	target_addr:172.67.168.140:443
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:12.385	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58648	target_addr:172.67.219.211:443
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:57.713	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:60.959	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:64.697	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:54:15Z	status:FAILURE	latency:195.396	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:54:15Z	status:HEALTHY	latency:261.183	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:59:15Z	status:UNKNOWN	latency:7.384	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:10.710	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50304	target_addr:172.67.219.211:443
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:10.972	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48720	target_addr:104.21.26.208:443
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:11.135	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50308	target_addr:172.67.219.211:443
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:17.892	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34074	target_addr:172.64.147.104:443
time:2026-10-04T06:59:15Z	status:FAILURE	latency:225.532	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:245.213	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:461.353	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:467.161	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T06:59:15Z	status:HEALTHY	latency:485.547	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:04:15Z	status:UNKNOWN	latency:8.384	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:10.788	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48704	target_addr:172.64.147.104:443
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:11.433	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34600	target_addr:104.21.86.125:443
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:15.318	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34604	target_addr:104.21.86.125:443
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:34.748	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59990	target_addr:172.67.168.140:443
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:55.989	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:58.839	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:72.167	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:04:15Z	status:HEALTHY	latency:188.787	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:04:15Z	status:FAILURE	latency:771.034	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:9.129	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55736	target_addr:104.21.86.125:443
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:11.508	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47966	target_addr:104.21.26.208:443
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:52.276	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52758	target_addr:104.18.40.152:443
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:60.280	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55750	target_addr:104.21.86.125:443
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:64.429	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:09:15Z	status:UNKNOWN	latency:74.727	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:94.193	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:174.606	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:09:15Z	status:FAILURE	latency:191.360	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:09:15Z	status:HEALTHY	latency:276.238	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:14:15Z	status:UNKNOWN	latency:6.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:7.862	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56592	target_addr:172.64.147.104:443
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:9.923	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43230	target_addr:172.67.168.140:443
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:10.129	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59834	target_addr:172.67.219.211:443
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:11.170	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49416	target_addr:104.21.86.125:443
time:2026-10-04T07:14:15Z	status:FAILURE	latency:30.006	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:50.147	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:55.550	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:75.089	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:14:15Z	status:HEALTHY	latency:211.214	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:10.312	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53178	target_addr:104.21.86.125:443
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:11.070	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58174	target_addr:104.18.40.152:443
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:11.941	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53184	target_addr:104.21.86.125:443
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:13.682	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33028	target_addr:104.21.26.208:443
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:56.143	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:19:15Z	status:UNKNOWN	latency:59.424	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:58.883	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:19:15Z	status:FAILURE	latency:203.990	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:243.649	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:19:15Z	status:HEALTHY	latency:500.195	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:11.027	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39672	target_addr:104.21.86.125:443
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:11.805	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55880	target_addr:104.18.40.152:443
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:11.524	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35488	target_addr:172.67.168.140:443
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:11.797	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47780	target_addr:172.67.219.211:443
time:2026-10-04T07:24:15Z	status:UNKNOWN	latency:35.917	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:24:15Z	status:FAILURE	latency:36.864	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:54.232	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:60.219	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:60.245	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:24:15Z	status:HEALTHY	latency:236.913	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:29:15Z	status:UNKNOWN	latency:7.795	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:9.168	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60548	target_addr:172.67.168.140:443
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:9.518	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42106	target_addr:172.67.219.211:443
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:10.877	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42112	target_addr:172.67.219.211:443
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:25.765	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59416	target_addr:104.18.40.152:443
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:53.838	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:54.185	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:58.026	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:29:15Z	status:HEALTHY	latency:263.343	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:29:15Z	status:FAILURE	latency:327.170	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:34:15Z	status:UNKNOWN	latency:7.311	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:9.658	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49026	target_addr:172.64.147.104:443
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:11.103	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33644	target_addr:172.67.168.140:443
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:11.336	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33046	target_addr:172.67.219.211:443
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:12.439	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33058	target_addr:172.67.219.211:443
time:2026-10-04T07:34:15Z	status:FAILURE	latency:35.484	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:61.254	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:68.956	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:86.828	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:34:15Z	status:HEALTHY	latency:255.699	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:39:15Z	status:UNKNOWN	latency:7.902	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:11.468	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50412	target_addr:104.21.26.208:443
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:12.745	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59300	target_addr:104.18.40.152:443
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:13.139	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48512	target_addr:104.21.86.125:443
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:13.228	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37152	target_addr:172.67.219.211:443
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:56.102	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:63.247	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:81.989	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:39:15Z	status:FAILURE	latency:174.431	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:39:15Z	status:HEALTHY	latency:285.928	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:11.836	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46566	target_addr:172.67.168.140:443
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:12.010	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59638	target_addr:172.67.219.211:443
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:12.490	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55782	target_addr:104.18.40.152:443
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:14.432	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57568	target_addr:104.21.86.125:443
time:2026-10-04T07:44:15Z	status:UNKNOWN	latency:35.936	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:44:15Z	status:FAILURE	latency:42.444	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:60.966	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:60.957	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:67.644	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:44:15Z	status:HEALTHY	latency:206.949	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:7.857	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52466	target_addr:172.67.219.211:443
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:9.986	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51996	target_addr:104.18.40.152:443
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:9.666	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39494	target_addr:104.21.26.208:443
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:13.139	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35164	target_addr:104.21.86.125:443
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:52.901	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:49:15Z	status:UNKNOWN	latency:56.813	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:59.968	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:59.830	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:49:15Z	status:FAILURE	latency:264.084	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:49:15Z	status:HEALTHY	latency:363.762	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:18.078	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44854	target_addr:104.21.26.208:443
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:17.948	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45608	target_addr:172.67.219.211:443
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:18.167	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45616	target_addr:172.67.219.211:443
time:2026-10-04T07:54:15Z	status:UNKNOWN	latency:30.403	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:30.738	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53766	target_addr:104.18.40.152:443
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:60.368	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:62.576	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:72.976	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:54:15Z	status:FAILURE	latency:233.321	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:54:15Z	status:HEALTHY	latency:235.138	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:59:15Z	status:UNKNOWN	latency:7.560	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:9.505	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39134	target_addr:172.67.219.211:443
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:10.506	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42960	target_addr:172.67.168.140:443
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:13.095	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46558	target_addr:172.64.147.104:443
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:35.091	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42674	target_addr:104.21.86.125:443
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:56.838	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:56.901	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:57.296	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T07:59:15Z	status:FAILURE	latency:205.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T07:59:15Z	status:HEALTHY	latency:223.850	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:04:15Z	status:UNKNOWN	latency:8.105	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:9.085	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35772	target_addr:104.21.26.208:443
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:9.014	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46254	target_addr:104.18.40.152:443
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:9.564	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58144	target_addr:104.21.86.125:443
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:10.635	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58158	target_addr:104.21.86.125:443
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:52.730	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:64.550	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:70.858	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:04:15Z	status:FAILURE	latency:201.214	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:04:15Z	status:HEALTHY	latency:234.805	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:09:15Z	status:UNKNOWN	latency:7.516	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:8.707	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54216	target_addr:172.67.168.140:443
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:10.507	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36002	target_addr:172.64.147.104:443
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:11.121	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60346	target_addr:104.21.86.125:443
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:16.709	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33374	target_addr:172.67.219.211:443
time:2026-10-04T08:09:15Z	status:FAILURE	latency:24.610	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:51.506	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:52.082	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:56.217	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:09:15Z	status:HEALTHY	latency:86.426	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:14:15Z	status:UNKNOWN	latency:5012.894	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.4.4:53
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5014.602	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34368	target_addr:172.64.147.104:443
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5015.318	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42548	target_addr:104.21.86.125:443
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5015.585	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43600	target_addr:172.67.219.211:443
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5016.805	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51652	target_addr:172.67.168.140:443
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5062.510	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5066.689	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5076.731	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:14:15Z	status:FAILURE	latency:5215.521	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:14:15Z	status:HEALTHY	latency:5238.240	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:19:15Z	status:UNKNOWN	latency:8.930	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:10.606	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57594	target_addr:172.67.219.211:443
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:10.643	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47832	target_addr:104.21.86.125:443
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:11.234	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36594	target_addr:104.18.40.152:443
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:13.572	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53108	target_addr:104.21.26.208:443
time:2026-10-04T08:19:15Z	status:FAILURE	latency:32.527	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:52.947	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:86.144	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:99.491	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:19:15Z	status:HEALTHY	latency:234.254	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:24:15Z	status:UNKNOWN	latency:6.455	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:9.397	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36608	target_addr:104.21.86.125:443
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:11.502	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39636	target_addr:104.21.26.208:443
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:11.744	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36612	target_addr:104.21.86.125:443
time:2026-10-04T08:24:15Z	status:FAILURE	latency:24.503	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:39.119	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58872	target_addr:172.64.147.104:443
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:57.405	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:72.435	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:95.766	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:24:15Z	status:HEALTHY	latency:229.621	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:29:15Z	status:UNKNOWN	latency:7.388	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:10.762	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36190	target_addr:104.21.26.208:443
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:10.375	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33776	target_addr:104.21.86.125:443
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:10.685	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33772	target_addr:104.21.86.125:443
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:12.885	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60918	target_addr:104.18.40.152:443
time:2026-10-04T08:29:15Z	status:FAILURE	latency:24.447	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:52.014	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:53.290	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:53.918	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:29:15Z	status:HEALTHY	latency:88.313	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:34:15Z	status:UNKNOWN	latency:8.127	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:11.237	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48882	target_addr:104.21.86.125:443
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:11.328	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55458	target_addr:172.64.147.104:443
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:14.510	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35730	target_addr:104.21.26.208:443
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:14.612	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48886	target_addr:104.21.86.125:443
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:51.827	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:57.517	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:69.671	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:34:15Z	status:HEALTHY	latency:221.414	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:34:15Z	status:FAILURE	latency:235.153	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:9.800	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48084	target_addr:104.21.86.125:443
time:2026-10-04T08:39:15Z	status:UNKNOWN	latency:9.873	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:9.850	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58466	target_addr:172.64.147.104:443
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:12.430	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59090	target_addr:172.67.168.140:443
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:13.554	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48090	target_addr:104.21.86.125:443
time:2026-10-04T08:39:15Z	status:FAILURE	latency:22.131	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:52.795	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:74.217	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:85.496	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:39:15Z	status:HEALTHY	latency:251.558	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:7.794	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54790	target_addr:172.67.168.140:443
time:2026-10-04T08:44:15Z	status:UNKNOWN	latency:8.521	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:8.499	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36604	target_addr:104.18.40.152:443
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:10.136	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57694	target_addr:172.67.219.211:443
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:10.493	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38352	target_addr:104.21.86.125:443
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:57.796	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:61.951	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:62.997	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:44:15Z	status:FAILURE	latency:193.519	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:44:15Z	status:HEALTHY	latency:208.885	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:49:15Z	status:UNKNOWN	latency:6.790	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:8.834	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45846	target_addr:172.67.219.211:443
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:9.747	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36556	target_addr:104.18.40.152:443
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:11.942	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47516	target_addr:172.67.168.140:443
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:13.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46424	target_addr:104.21.86.125:443
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:49.856	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:60.955	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:79.663	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:49:15Z	status:FAILURE	latency:203.536	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:49:15Z	status:HEALTHY	latency:243.572	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:9.414	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44200	target_addr:104.21.86.125:443
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:9.735	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56282	target_addr:104.21.26.208:443
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:10.127	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54878	target_addr:172.67.219.211:443
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:12.921	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59260	target_addr:104.18.40.152:443
time:2026-10-04T08:54:15Z	status:UNKNOWN	latency:31.143	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:58.675	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:64.038	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:111.730	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:54:15Z	status:FAILURE	latency:137.609	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T08:54:15Z	status:HEALTHY	latency:364.194	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:59:15Z	status:UNKNOWN	latency:6.651	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:8.382	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40464	target_addr:104.21.86.125:443
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:9.354	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59448	target_addr:172.64.147.104:443
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:8.905	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40472	target_addr:104.21.86.125:443
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:22.220	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33802	target_addr:104.21.26.208:443
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:54.855	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:55.165	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:55.187	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:59:15Z	status:HEALTHY	latency:195.833	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T08:59:15Z	status:FAILURE	latency:221.687	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:15.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42708	target_addr:104.21.86.125:443
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:15.374	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42700	target_addr:104.21.86.125:443
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:15.369	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45226	target_addr:104.21.26.208:443
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:15.757	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52458	target_addr:104.18.40.152:443
time:2026-10-04T09:04:15Z	status:UNKNOWN	latency:34.935	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:04:15Z	status:FAILURE	latency:34.311	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:58.268	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:64.052	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:76.278	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:04:15Z	status:HEALTHY	latency:230.343	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:09:15Z	status:UNKNOWN	latency:7.083	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:9.697	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60122	target_addr:172.67.219.211:443
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:9.763	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34084	target_addr:104.21.26.208:443
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:10.609	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47034	target_addr:104.21.86.125:443
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:12.836	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56604	target_addr:104.18.40.152:443
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:50.354	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:51.931	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:52.694	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:09:15Z	status:HEALTHY	latency:197.554	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:09:15Z	status:FAILURE	latency:204.207	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:14:15Z	status:UNKNOWN	latency:7.477	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:8.843	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57948	target_addr:104.18.40.152:443
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:10.255	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55258	target_addr:104.21.86.125:443
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:10.230	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39884	target_addr:172.67.168.140:443
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:10.074	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55274	target_addr:104.21.86.125:443
time:2026-10-04T09:14:15Z	status:FAILURE	latency:26.516	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:53.911	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:65.021	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:71.804	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:14:15Z	status:HEALTHY	latency:347.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:19:15Z	status:UNKNOWN	latency:7.951	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:10.763	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52010	target_addr:104.21.86.125:443
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:11.156	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55720	target_addr:172.67.219.211:443
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:10.828	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42216	target_addr:172.67.168.140:443
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:14.123	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58540	target_addr:104.18.40.152:443
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:59.833	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:73.234	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:75.956	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:19:15Z	status:FAILURE	latency:182.721	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:19:15Z	status:HEALTHY	latency:212.454	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:9.751	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41094	target_addr:172.67.168.140:443
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:9.764	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43180	target_addr:104.18.40.152:443
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:12.474	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40556	target_addr:104.21.86.125:443
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:42.710	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46984	target_addr:172.67.219.211:443
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:51.227	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:53.906	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:24:15Z	status:UNKNOWN	latency:56.713	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:78.892	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:24:15Z	status:HEALTHY	latency:218.054	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:24:15Z	status:FAILURE	latency:224.957	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:29:15Z	status:UNKNOWN	latency:8.551	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:9.178	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59856	target_addr:172.67.219.211:443
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:11.393	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44296	target_addr:104.21.26.208:443
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:12.461	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52504	target_addr:104.21.86.125:443
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:16.088	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46664	target_addr:104.18.40.152:443
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:56.207	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:63.649	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:29:15Z	status:FAILURE	latency:205.310	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:242.058	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:29:15Z	status:HEALTHY	latency:395.895	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:34:15Z	status:UNKNOWN	latency:7.833	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:8.736	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39710	target_addr:172.67.168.140:443
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:10.001	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42838	target_addr:172.67.219.211:443
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:12.973	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33150	target_addr:172.64.147.104:443
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:13.542	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33076	target_addr:104.21.86.125:443
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:52.092	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:75.741	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:87.567	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:34:15Z	status:HEALTHY	latency:209.708	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:34:15Z	status:FAILURE	latency:215.812	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:8.853	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37590	target_addr:172.67.219.211:443
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:11.782	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42838	target_addr:104.18.40.152:443
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:12.593	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37604	target_addr:172.67.219.211:443
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:13.921	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41692	target_addr:104.21.26.208:443
time:2026-10-04T09:39:15Z	status:UNKNOWN	latency:36.744	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:39:15Z	status:FAILURE	latency:171.619	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:304.801	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:381.101	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:422.282	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:39:15Z	status:HEALTHY	latency:548.412	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:44:15Z	status:UNKNOWN	latency:9.984	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:12.480	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40870	target_addr:104.21.86.125:443
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:12.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43598	target_addr:172.64.147.104:443
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:13.045	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48066	target_addr:104.21.26.208:443
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:12.584	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55884	target_addr:172.67.219.211:443
time:2026-10-04T09:44:15Z	status:FAILURE	latency:29.403	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:213.316	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:426.393	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:439.348	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:44:15Z	status:HEALTHY	latency:442.172	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:8.825	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35154	target_addr:172.64.147.104:443
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:11.059	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49320	target_addr:172.67.168.140:443
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:11.152	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42128	target_addr:104.21.86.125:443
time:2026-10-04T09:49:15Z	status:UNKNOWN	latency:16.958	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:186.012	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:49:15Z	status:FAILURE	latency:213.192	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:215.806	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42130	target_addr:104.21.86.125:443
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:374.768	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:493.442	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:49:15Z	status:HEALTHY	latency:505.429	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:54:16Z	status:UNKNOWN	latency:10.393	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:12.319	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55716	target_addr:104.21.86.125:443
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:12.875	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57944	target_addr:172.64.147.104:443
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:13.269	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47026	target_addr:172.67.219.211:443
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:13.912	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48884	target_addr:172.67.168.140:443
time:2026-10-04T09:54:16Z	status:FAILURE	latency:171.329	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:228.849	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:448.140	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:449.398	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:54:16Z	status:HEALTHY	latency:458.378	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:59:16Z	status:UNKNOWN	latency:9.057	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:9.837	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46788	target_addr:172.67.219.211:443
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:12.650	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46802	target_addr:172.67.219.211:443
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:12.340	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59064	target_addr:104.18.40.152:443
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:12.240	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38896	target_addr:172.67.168.140:443
time:2026-10-04T09:59:16Z	status:FAILURE	latency:172.386	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:220.078	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:428.107	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:460.444	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T09:59:16Z	status:HEALTHY	latency:763.342	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:7.878	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33242	target_addr:104.18.40.152:443
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:9.391	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47160	target_addr:104.21.26.208:443
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:10.720	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50008	target_addr:104.21.86.125:443
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:10.440	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50000	target_addr:104.21.86.125:443
time:2026-10-04T10:04:16Z	status:UNKNOWN	latency:16.951	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:04:16Z	status:FAILURE	latency:33.217	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:269.086	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:477.384	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:483.882	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:04:16Z	status:HEALTHY	latency:506.704	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:09:16Z	status:UNKNOWN	latency:7.830	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:8.821	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53882	target_addr:172.67.168.140:443
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:9.898	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53478	target_addr:104.21.86.125:443
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:12.837	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53492	target_addr:104.21.86.125:443
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:13.502	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49482	target_addr:172.64.147.104:443
time:2026-10-04T10:09:16Z	status:FAILURE	latency:177.288	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:233.879	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:419.425	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:426.998	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:09:16Z	status:HEALTHY	latency:462.546	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:14:16Z	status:UNKNOWN	latency:8.917	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:9.341	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58322	target_addr:104.21.86.125:443
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:10.543	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46294	target_addr:104.18.40.152:443
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:11.682	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58332	target_addr:104.21.86.125:443
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:12.431	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57736	target_addr:172.67.168.140:443
time:2026-10-04T10:14:16Z	status:FAILURE	latency:24.835	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:220.163	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:429.214	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:443.574	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:14:16Z	status:HEALTHY	latency:508.716	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:19:16Z	status:UNKNOWN	latency:8.279	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:8.766	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43610	target_addr:104.18.40.152:443
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:9.134	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47254	target_addr:172.67.219.211:443
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:9.567	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47258	target_addr:172.67.219.211:443
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:11.610	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43942	target_addr:172.67.168.140:443
time:2026-10-04T10:19:16Z	status:FAILURE	latency:143.113	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:205.693	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:532.587	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:534.096	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:19:16Z	status:HEALTHY	latency:538.455	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:24:16Z	status:UNKNOWN	latency:9.280	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:10.322	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42100	target_addr:172.67.219.211:443
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:10.107	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60548	target_addr:172.67.168.140:443
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:12.011	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54774	target_addr:104.18.40.152:443
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:12.993	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51354	target_addr:104.21.86.125:443
time:2026-10-04T10:24:16Z	status:FAILURE	latency:31.903	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:248.900	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:378.000	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:385.657	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:24:16Z	status:HEALTHY	latency:499.486	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:14.073	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44432	target_addr:104.21.86.125:443
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:14.051	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55030	target_addr:172.67.168.140:443
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:14.246	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44428	target_addr:104.21.86.125:443
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:14.232	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42944	target_addr:104.18.40.152:443
time:2026-10-04T10:29:16Z	status:UNKNOWN	latency:16.818	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:29:16Z	status:FAILURE	latency:227.681	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:291.018	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:506.896	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:508.274	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:29:16Z	status:HEALTHY	latency:511.032	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:10.105	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51698	target_addr:172.67.219.211:443
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:10.089	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48140	target_addr:172.64.147.104:443
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:10.078	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56478	target_addr:104.21.86.125:443
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:10.766	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58134	target_addr:172.67.168.140:443
time:2026-10-04T10:34:16Z	status:UNKNOWN	latency:16.408	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:34:16Z	status:FAILURE	latency:25.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:207.416	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:426.353	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:428.135	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:34:16Z	status:HEALTHY	latency:5397.801	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:39:16Z	status:UNKNOWN	latency:9.388	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:10.545	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37942	target_addr:172.67.168.140:443
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:12.124	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49674	target_addr:172.67.219.211:443
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:12.748	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60162	target_addr:104.18.40.152:443
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:13.568	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49662	target_addr:172.67.219.211:443
time:2026-10-04T10:39:16Z	status:FAILURE	latency:209.311	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:237.370	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:495.534	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:505.586	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:39:16Z	status:HEALTHY	latency:505.976	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:44:16Z	status:UNKNOWN	latency:9.300	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:10.780	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38916	target_addr:104.18.40.152:443
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:11.536	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36806	target_addr:104.21.86.125:443
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:12.695	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49990	target_addr:172.67.219.211:443
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:14.495	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38274	target_addr:104.21.26.208:443
time:2026-10-04T10:44:16Z	status:FAILURE	latency:22.940	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:242.882	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:422.011	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:422.109	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:44:16Z	status:HEALTHY	latency:425.129	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:49:16Z	status:UNKNOWN	latency:7.850	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:8.118	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39714	target_addr:104.21.26.208:443
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:10.128	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43486	target_addr:172.64.147.104:443
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:10.181	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60208	target_addr:104.21.86.125:443
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:10.782	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60212	target_addr:104.21.86.125:443
time:2026-10-04T10:49:16Z	status:FAILURE	latency:178.473	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:202.249	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:513.157	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:515.462	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:49:16Z	status:HEALTHY	latency:517.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:54:16Z	status:UNKNOWN	latency:7.640	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:11.781	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49290	target_addr:104.21.86.125:443
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:12.953	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60500	target_addr:172.67.168.140:443
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:20.620	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54614	target_addr:104.18.40.152:443
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:20.428	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49298	target_addr:104.21.86.125:443
time:2026-10-04T10:54:16Z	status:FAILURE	latency:202.146	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:215.289	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:444.847	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:460.750	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:54:16Z	status:HEALTHY	latency:5426.212	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:59:16Z	status:UNKNOWN	latency:6.973	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:9.614	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43746	target_addr:172.67.219.211:443
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:10.391	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49582	target_addr:104.21.26.208:443
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:11.345	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41616	target_addr:104.18.40.152:443
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:27.016	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43748	target_addr:172.67.219.211:443
time:2026-10-04T10:59:16Z	status:FAILURE	latency:200.749	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:227.996	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:445.100	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:467.607	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T10:59:16Z	status:HEALTHY	latency:468.874	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:04:16Z	status:UNKNOWN	latency:7.815	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:9.889	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60702	target_addr:104.21.26.208:443
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:10.115	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42090	target_addr:104.21.86.125:443
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:10.563	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42096	target_addr:104.21.86.125:443
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:13.415	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54772	target_addr:104.18.40.152:443
time:2026-10-04T11:04:16Z	status:FAILURE	latency:24.727	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:236.516	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:504.255	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:524.001	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:04:16Z	status:HEALTHY	latency:537.647	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:09:16Z	status:UNKNOWN	latency:7.518	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:9.687	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48240	target_addr:172.67.219.211:443
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:10.444	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52660	target_addr:104.21.26.208:443
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:19.040	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48718	target_addr:172.64.147.104:443
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:31.173	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50278	target_addr:104.21.86.125:443
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:185.228	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:09:16Z	status:FAILURE	latency:223.954	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:410.776	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:419.736	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:09:16Z	status:HEALTHY	latency:441.739	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:14:16Z	status:UNKNOWN	latency:7.395	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:10.077	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58074	target_addr:172.67.219.211:443
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:11.326	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33522	target_addr:172.67.168.140:443
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:11.289	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33732	target_addr:172.64.147.104:443
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:11.726	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59102	target_addr:104.21.86.125:443
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:206.629	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:14:16Z	status:FAILURE	latency:213.877	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:432.051	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:435.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:14:16Z	status:HEALTHY	latency:459.400	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:19:16Z	status:UNKNOWN	latency:7.693	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:9.621	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58198	target_addr:172.67.219.211:443
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:9.619	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58200	target_addr:172.67.219.211:443
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:10.997	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58410	target_addr:172.64.147.104:443
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:11.004	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38100	target_addr:104.21.26.208:443
time:2026-10-04T11:19:16Z	status:FAILURE	latency:108.712	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:209.446	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:409.926	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:412.025	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:19:16Z	status:HEALTHY	latency:437.062	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:24:16Z	status:UNKNOWN	latency:6.655	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:8.561	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34220	target_addr:104.18.40.152:443
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:8.695	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38794	target_addr:104.21.26.208:443
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:8.760	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57094	target_addr:104.21.86.125:443
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:11.510	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36044	target_addr:172.67.219.211:443
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:195.188	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:24:16Z	status:FAILURE	latency:337.964	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:413.583	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:419.412	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:24:16Z	status:HEALTHY	latency:422.108	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:9.306	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58580	target_addr:104.18.40.152:443
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:10.907	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42842	target_addr:172.67.219.211:443
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:14.258	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41816	target_addr:104.21.26.208:443
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:17.247	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42856	target_addr:172.67.219.211:443
time:2026-10-04T11:29:16Z	status:FAILURE	latency:24.504	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:29:16Z	status:UNKNOWN	latency:33.625	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:165.761	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:410.950	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:411.773	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:29:16Z	status:HEALTHY	latency:417.450	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:7.683	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51806	target_addr:104.18.40.152:443
time:2026-10-04T11:34:16Z	status:UNKNOWN	latency:8.036	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:10.001	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53714	target_addr:104.21.86.125:443
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:10.989	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38958	target_addr:172.67.219.211:443
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:11.455	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51176	target_addr:172.67.168.140:443
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:214.501	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:34:16Z	status:FAILURE	latency:220.273	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:422.411	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:468.591	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:34:16Z	status:HEALTHY	latency:484.778	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:39:16Z	status:UNKNOWN	latency:7.728	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:10.797	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55428	target_addr:172.67.168.140:443
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:10.835	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44762	target_addr:104.21.86.125:443
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:11.842	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57726	target_addr:172.64.147.104:443
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:11.606	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44764	target_addr:104.21.86.125:443
time:2026-10-04T11:39:16Z	status:FAILURE	latency:22.525	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:199.970	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:421.140	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:426.702	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:39:16Z	status:HEALTHY	latency:727.105	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:44:16Z	status:UNKNOWN	latency:8.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:9.134	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47434	target_addr:104.21.86.125:443
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:10.635	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53140	target_addr:172.67.219.211:443
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:12.548	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50770	target_addr:104.21.26.208:443
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:20.868	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46936	target_addr:104.18.40.152:443
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:79.023	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:44:16Z	status:FAILURE	latency:215.703	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:450.778	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:451.669	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:44:16Z	status:HEALTHY	latency:602.007	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:49:16Z	status:UNKNOWN	latency:8.076	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:8.905	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34322	target_addr:104.18.40.152:443
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:10.887	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59636	target_addr:104.21.86.125:443
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:12.017	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58016	target_addr:172.67.219.211:443
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:14.772	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49856	target_addr:104.21.26.208:443
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:194.209	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:49:16Z	status:FAILURE	latency:210.415	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:440.915	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:473.833	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:49:16Z	status:HEALTHY	latency:557.473	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:54:16Z	status:UNKNOWN	latency:7.446	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:8.438	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57168	target_addr:104.21.86.125:443
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:9.532	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51486	target_addr:172.67.168.140:443
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:10.458	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60648	target_addr:104.18.40.152:443
time:2026-10-04T11:54:16Z	status:FAILURE	latency:26.026	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:45.846	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38984	target_addr:172.67.219.211:443
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:251.065	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:420.901	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:428.059	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:54:16Z	status:HEALTHY	latency:433.778	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:59:16Z	status:UNKNOWN	latency:6.532	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:9.668	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37938	target_addr:104.18.40.152:443
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:10.093	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52778	target_addr:172.67.219.211:443
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:10.112	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50608	target_addr:172.67.168.140:443
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:11.352	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52774	target_addr:172.67.219.211:443
time:2026-10-04T11:59:16Z	status:FAILURE	latency:25.603	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:178.809	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:400.743	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:476.700	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T11:59:16Z	status:HEALTHY	latency:488.183	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:04:16Z	status:UNKNOWN	latency:8.022	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:9.040	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57798	target_addr:104.21.26.208:443
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:9.833	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35976	target_addr:172.64.147.104:443
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:9.825	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59942	target_addr:172.67.219.211:443
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:9.745	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54802	target_addr:104.21.86.125:443
time:2026-10-04T12:04:16Z	status:FAILURE	latency:24.423	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:48.877	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:51.394	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:69.342	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:04:16Z	status:HEALTHY	latency:194.398	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:9.540	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48038	target_addr:172.64.147.104:443
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:9.000	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47942	target_addr:172.67.219.211:443
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:9.717	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37714	target_addr:172.67.168.140:443
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:10.182	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44806	target_addr:104.21.86.125:443
time:2026-10-04T12:09:16Z	status:FAILURE	latency:22.748	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:09:16Z	status:UNKNOWN	latency:44.158	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:55.421	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:73.031	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:76.122	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:09:16Z	status:HEALTHY	latency:132.074	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:14:16Z	status:UNKNOWN	latency:7.072	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:8.910	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42090	target_addr:104.21.26.208:443
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:10.130	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40484	target_addr:172.67.219.211:443
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:10.202	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40492	target_addr:172.67.219.211:443
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:11.049	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56580	target_addr:104.18.40.152:443
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:52.290	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:52.586	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:14:16Z	status:FAILURE	latency:204.692	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:205.646	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:14:16Z	status:HEALTHY	latency:284.248	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:19:16Z	status:UNKNOWN	latency:7.108	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:8.546	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58708	target_addr:104.21.86.125:443
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:9.523	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57478	target_addr:172.67.168.140:443
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:10.267	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50686	target_addr:104.18.40.152:443
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:11.809	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58710	target_addr:104.21.86.125:443
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:56.053	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:61.147	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:77.190	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:19:16Z	status:HEALTHY	latency:203.072	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:19:16Z	status:FAILURE	latency:242.098	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:24:16Z	status:UNKNOWN	latency:6.783	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:9.650	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39244	target_addr:104.18.40.152:443
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:9.816	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56578	target_addr:104.21.86.125:443
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:10.337	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56592	target_addr:104.21.86.125:443
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:14.285	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56586	target_addr:104.21.26.208:443
time:2026-10-04T12:24:16Z	status:FAILURE	latency:23.717	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:54.341	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:62.570	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:74.908	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:24:16Z	status:HEALTHY	latency:244.238	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:29:16Z	status:UNKNOWN	latency:6.961	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:9.777	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44094	target_addr:172.67.219.211:443
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:10.361	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42106	target_addr:104.18.40.152:443
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:10.750	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40194	target_addr:172.67.168.140:443
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:12.143	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55764	target_addr:104.21.86.125:443
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:54.363	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:76.510	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:29:16Z	status:FAILURE	latency:166.866	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:279.393	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:29:16Z	status:HEALTHY	latency:436.049	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:34:16Z	status:UNKNOWN	latency:6.656	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:8.937	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34548	target_addr:172.67.219.211:443
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:9.290	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41176	target_addr:172.64.147.104:443
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:9.425	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44968	target_addr:104.21.86.125:443
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:9.194	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58114	target_addr:172.67.168.140:443
time:2026-10-04T12:34:16Z	status:FAILURE	latency:19.806	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:51.343	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:55.631	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:57.983	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:34:16Z	status:HEALTHY	latency:197.960	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:8.425	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50176	target_addr:172.64.147.104:443
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:8.861	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44984	target_addr:172.67.219.211:443
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:10.462	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34654	target_addr:172.67.168.140:443
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:10.775	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33148	target_addr:104.21.86.125:443
time:2026-10-04T12:39:16Z	status:UNKNOWN	latency:33.340	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:50.710	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:57.690	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:63.713	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:39:16Z	status:FAILURE	latency:194.997	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:39:16Z	status:HEALTHY	latency:199.484	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:44:16Z	status:UNKNOWN	latency:9.106	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:12.355	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41292	target_addr:172.67.168.140:443
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:11.979	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40504	target_addr:172.67.219.211:443
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:12.277	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57374	target_addr:104.21.86.125:443
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:12.906	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59732	target_addr:104.18.40.152:443
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:167.519	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:44:16Z	status:FAILURE	latency:313.716	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:418.894	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:425.055	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:44:16Z	status:HEALTHY	latency:960.372	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:49:16Z	status:UNKNOWN	latency:7.480	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:10.072	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48436	target_addr:172.67.219.211:443
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:10.268	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38092	target_addr:104.18.40.152:443
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:14.066	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38458	target_addr:172.67.168.140:443
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:13.826	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40042	target_addr:104.21.86.125:443
time:2026-10-04T12:49:16Z	status:FAILURE	latency:185.543	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:246.636	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:380.555	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:408.162	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:49:16Z	status:HEALTHY	latency:723.119	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:54:16Z	status:UNKNOWN	latency:5.755	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:10.019	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44190	target_addr:104.18.40.152:443
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:10.351	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44736	target_addr:104.21.26.208:443
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:10.822	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37708	target_addr:104.21.86.125:443
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:20.301	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37724	target_addr:104.21.86.125:443
time:2026-10-04T12:54:16Z	status:FAILURE	latency:148.224	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:217.629	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:393.283	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:491.673	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:54:16Z	status:HEALTHY	latency:858.335	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:59:16Z	status:UNKNOWN	latency:8.356	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:8.324	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49034	target_addr:104.18.40.152:443
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:9.976	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48998	target_addr:104.21.86.125:443
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:10.789	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49008	target_addr:104.21.86.125:443
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:11.371	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58300	target_addr:104.21.26.208:443
time:2026-10-04T12:59:16Z	status:FAILURE	latency:26.911	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:451.055	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:462.600	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:738.548	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T12:59:16Z	status:HEALTHY	latency:1408.795	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:04:16Z	status:UNKNOWN	latency:6.903	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:9.284	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34850	target_addr:172.64.147.104:443
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:9.012	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50370	target_addr:104.21.86.125:443
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:9.148	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50382	target_addr:104.21.86.125:443
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:10.064	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45906	target_addr:104.21.26.208:443
time:2026-10-04T13:04:16Z	status:FAILURE	latency:31.617	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:203.313	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:488.085	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:521.017	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:04:16Z	status:HEALTHY	latency:858.043	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:09:16Z	status:UNKNOWN	latency:8.788	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:9.970	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45414	target_addr:172.67.219.211:443
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:11.730	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45416	target_addr:172.67.219.211:443
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:21.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33528	target_addr:104.18.40.152:443
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:28.976	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58898	target_addr:104.21.26.208:443
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:205.133	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:09:16Z	status:FAILURE	latency:222.589	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:514.928	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:776.988	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:09:16Z	status:HEALTHY	latency:1526.161	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:14:16Z	status:UNKNOWN	latency:5.835	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:9.094	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55196	target_addr:172.67.168.140:443
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:9.803	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60372	target_addr:172.64.147.104:443
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:10.176	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33688	target_addr:172.67.219.211:443
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:10.354	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53750	target_addr:104.21.86.125:443
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:175.259	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:14:16Z	status:FAILURE	latency:309.431	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:423.902	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:434.979	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:14:16Z	status:HEALTHY	latency:435.315	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:19:16Z	status:UNKNOWN	latency:6.644	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:9.352	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55468	target_addr:172.67.219.211:443
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:9.320	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44344	target_addr:104.21.26.208:443
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:10.954	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50604	target_addr:104.21.86.125:443
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:12.626	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47704	target_addr:172.64.147.104:443
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:198.291	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:19:16Z	status:FAILURE	latency:207.740	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:492.968	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:494.166	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:19:16Z	status:HEALTHY	latency:497.683	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:24:16Z	status:UNKNOWN	latency:7.751	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:10.017	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48832	target_addr:104.18.40.152:443
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:11.178	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32938	target_addr:104.21.26.208:443
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:12.112	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57386	target_addr:104.21.86.125:443
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:15.304	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45538	target_addr:172.67.219.211:443
time:2026-10-04T13:24:16Z	status:FAILURE	latency:141.604	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:258.194	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:440.250	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:473.696	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:24:16Z	status:HEALTHY	latency:504.551	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:12.150	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59814	target_addr:104.21.26.208:443
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:12.897	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54526	target_addr:104.21.86.125:443
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:13.362	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41710	target_addr:104.18.40.152:443
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:13.509	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54530	target_addr:104.21.86.125:443
time:2026-10-04T13:29:16Z	status:UNKNOWN	latency:42.910	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:92.527	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:29:16Z	status:FAILURE	latency:221.143	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:429.322	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:439.849	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:29:16Z	status:HEALTHY	latency:452.012	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:34:16Z	status:UNKNOWN	latency:7.890	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:8.470	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49194	target_addr:104.21.26.208:443
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:8.680	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54606	target_addr:104.18.40.152:443
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:9.008	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34828	target_addr:172.67.219.211:443
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:11.461	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42842	target_addr:104.21.86.125:443
time:2026-10-04T13:34:16Z	status:FAILURE	latency:42.547	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:194.336	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:424.940	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:692.945	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:34:16Z	status:HEALTHY	latency:702.453	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:10.946	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56496	target_addr:172.67.168.140:443
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:11.293	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59322	target_addr:104.18.40.152:443
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:11.029	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34754	target_addr:104.21.86.125:443
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:12.815	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35960	target_addr:172.67.219.211:443
time:2026-10-04T13:39:16Z	status:UNKNOWN	latency:34.676	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:192.766	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:39:16Z	status:FAILURE	latency:222.489	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:430.284	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:438.954	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:39:16Z	status:HEALTHY	latency:5656.522	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:44:16Z	status:UNKNOWN	latency:8.569	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:10.663	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36314	target_addr:104.21.86.125:443
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:11.412	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58508	target_addr:172.64.147.104:443
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:12.384	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49364	target_addr:172.67.168.140:443
time:2026-10-04T13:44:16Z	status:FAILURE	latency:152.833	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:201.244	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:274.389	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49990	target_addr:172.67.219.211:443
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:449.863	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:460.487	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:44:16Z	status:HEALTHY	latency:462.245	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:49:16Z	status:UNKNOWN	latency:6.719	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:8.696	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42106	target_addr:172.64.147.104:443
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:8.788	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54494	target_addr:172.67.219.211:443
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:8.885	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54632	target_addr:172.67.168.140:443
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:17.456	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54496	target_addr:172.67.219.211:443
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:208.051	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:49:16Z	status:FAILURE	latency:212.292	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:441.152	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:447.551	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:49:16Z	status:HEALTHY	latency:703.339	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:54:16Z	status:UNKNOWN	latency:7.293	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:8.736	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36086	target_addr:104.21.26.208:443
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:9.183	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36550	target_addr:172.67.219.211:443
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:9.939	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50454	target_addr:104.18.40.152:443
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:10.519	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57040	target_addr:104.21.86.125:443
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:223.292	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:461.628	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:465.946	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:54:16Z	status:HEALTHY	latency:467.397	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:54:16Z	status:FAILURE	latency:744.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:59:16Z	status:UNKNOWN	latency:5.694	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:10.444	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51488	target_addr:104.21.86.125:443
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:11.790	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51500	target_addr:104.21.86.125:443
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:13.945	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53844	target_addr:172.64.147.104:443
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:19.650	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43366	target_addr:172.67.168.140:443
time:2026-10-04T13:59:16Z	status:FAILURE	latency:217.580	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:224.953	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:425.544	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:435.069	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T13:59:16Z	status:HEALTHY	latency:439.867	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:04:16Z	status:UNKNOWN	latency:7.477	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:10.506	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48134	target_addr:104.21.86.125:443
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:10.131	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53766	target_addr:172.64.147.104:443
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:10.563	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33540	target_addr:104.21.26.208:443
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:10.752	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48138	target_addr:104.21.86.125:443
time:2026-10-04T14:04:16Z	status:FAILURE	latency:194.309	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:236.222	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:500.475	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:545.847	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:04:16Z	status:HEALTHY	latency:1526.211	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:09:16Z	status:UNKNOWN	latency:7.445	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:10.251	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43206	target_addr:172.67.219.211:443
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:10.464	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43908	target_addr:104.21.86.125:443
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:10.986	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37738	target_addr:172.64.147.104:443
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:14.205	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44074	target_addr:172.67.168.140:443
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:213.487	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:477.404	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:480.866	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:09:16Z	status:FAILURE	latency:494.916	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:09:16Z	status:HEALTHY	latency:580.778	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:14:16Z	status:UNKNOWN	latency:7.756	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:10.552	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56884	target_addr:104.21.86.125:443
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:11.002	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34918	target_addr:104.18.40.152:443
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:12.489	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44176	target_addr:172.67.168.140:443
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:12.409	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56888	target_addr:104.21.86.125:443
time:2026-10-04T14:14:16Z	status:FAILURE	latency:199.873	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:210.165	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:513.062	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:520.005	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:14:16Z	status:HEALTHY	latency:536.936	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:19:16Z	status:UNKNOWN	latency:7.442	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:9.100	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60286	target_addr:104.18.40.152:443
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:10.227	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54504	target_addr:172.67.168.140:443
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:10.549	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35864	target_addr:104.21.86.125:443
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:10.950	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35852	target_addr:104.21.86.125:443
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:229.029	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:19:16Z	status:FAILURE	latency:237.081	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:445.209	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:450.272	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:19:16Z	status:HEALTHY	latency:467.351	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:24:17Z	status:UNKNOWN	latency:10.032	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:14.239	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38964	target_addr:172.64.147.104:443
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:13.968	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51892	target_addr:104.21.86.125:443
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:13.816	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51894	target_addr:104.21.86.125:443
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:19.163	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54782	target_addr:172.67.168.140:443
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:206.293	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:24:17Z	status:FAILURE	latency:318.731	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:437.508	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:440.255	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:24:17Z	status:HEALTHY	latency:547.510	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:29:17Z	status:UNKNOWN	latency:6.945	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:8.400	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40004	target_addr:172.64.147.104:443
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:9.885	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35740	target_addr:172.67.219.211:443
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:9.849	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35734	target_addr:172.67.219.211:443
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:10.486	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47342	target_addr:172.67.168.140:443
time:2026-10-04T14:29:17Z	status:FAILURE	latency:32.981	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:204.749	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:417.545	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:417.795	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:29:17Z	status:HEALTHY	latency:425.133	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:34:17Z	status:UNKNOWN	latency:7.991	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:10.648	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59318	target_addr:172.64.147.104:443
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:11.575	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53166	target_addr:104.21.26.208:443
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:11.723	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49486	target_addr:104.21.86.125:443
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:12.435	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49210	target_addr:172.67.219.211:443
time:2026-10-04T14:34:17Z	status:FAILURE	latency:29.434	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:216.785	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:375.262	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:384.817	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:34:17Z	status:HEALTHY	latency:400.223	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:39:17Z	status:UNKNOWN	latency:7.798	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:8.961	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35684	target_addr:172.67.219.211:443
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:9.011	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35694	target_addr:172.67.219.211:443
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:10.426	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54306	target_addr:104.21.26.208:443
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:10.947	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43184	target_addr:104.18.40.152:443
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:181.302	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:39:17Z	status:FAILURE	latency:214.697	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:518.477	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:520.277	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:39:17Z	status:HEALTHY	latency:520.822	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:44:17Z	status:UNKNOWN	latency:8.227	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:13.462	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59222	target_addr:104.21.26.208:443
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:20.223	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48246	target_addr:172.64.147.104:443
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:37.541	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51476	target_addr:104.21.86.125:443
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:48.053	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51472	target_addr:104.21.86.125:443
time:2026-10-04T14:44:17Z	status:FAILURE	latency:199.721	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:201.591	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:427.765	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:452.412	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:44:17Z	status:HEALTHY	latency:1565.431	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:49:17Z	status:UNKNOWN	latency:7.101	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:9.659	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49324	target_addr:104.21.86.125:443
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:11.997	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41238	target_addr:104.18.40.152:443
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:12.042	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60936	target_addr:172.67.219.211:443
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:18.123	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33254	target_addr:172.67.168.140:443
time:2026-10-04T14:49:17Z	status:FAILURE	latency:177.959	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:231.435	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:461.424	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:472.366	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:49:17Z	status:HEALTHY	latency:477.366	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:54:17Z	status:UNKNOWN	latency:8.079	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:8.509	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47418	target_addr:172.64.147.104:443
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:10.218	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57212	target_addr:104.21.26.208:443
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:10.268	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44206	target_addr:172.67.219.211:443
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:10.910	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44212	target_addr:172.67.219.211:443
time:2026-10-04T14:54:17Z	status:FAILURE	latency:24.305	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:167.342	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:435.358	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:474.249	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:54:17Z	status:HEALTHY	latency:534.969	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:59:17Z	status:UNKNOWN	latency:7.749	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:12.018	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49114	target_addr:172.64.147.104:443
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:15.142	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34678	target_addr:104.21.86.125:443
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:15.137	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42530	target_addr:172.67.219.211:443
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:15.309	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33386	target_addr:172.67.168.140:443
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:206.074	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:59:17Z	status:FAILURE	latency:279.768	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:480.499	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:499.242	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T14:59:17Z	status:HEALTHY	latency:535.143	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:04:17Z	status:UNKNOWN	latency:7.028	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:9.330	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43292	target_addr:172.67.219.211:443
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:11.101	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36720	target_addr:104.18.40.152:443
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:14.500	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43112	target_addr:104.21.26.208:443
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:17.952	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40510	target_addr:104.21.86.125:443
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:201.225	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:424.310	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:04:17Z	status:FAILURE	latency:501.093	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:509.426	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:04:17Z	status:HEALTHY	latency:529.818	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:9.767	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39436	target_addr:104.21.86.125:443
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:9.868	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59016	target_addr:172.67.219.211:443
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:11.345	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33808	target_addr:172.67.168.140:443
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:13.085	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54428	target_addr:104.18.40.152:443
time:2026-10-04T15:09:17Z	status:UNKNOWN	latency:35.451	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:205.218	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:09:17Z	status:FAILURE	latency:235.611	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:571.357	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:576.438	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:09:17Z	status:HEALTHY	latency:675.351	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:7.806	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51168	target_addr:104.18.40.152:443
time:2026-10-04T15:14:17Z	status:UNKNOWN	latency:9.406	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:10.509	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36994	target_addr:104.21.26.208:443
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:10.874	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37874	target_addr:172.67.219.211:443
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:10.859	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37864	target_addr:172.67.219.211:443
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:189.667	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:14:17Z	status:FAILURE	latency:226.703	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:475.233	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:481.669	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:14:17Z	status:HEALTHY	latency:488.570	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:19:17Z	status:UNKNOWN	latency:5.932	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:8.498	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54500	target_addr:172.67.219.211:443
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:9.041	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42746	target_addr:104.21.26.208:443
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:9.756	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54516	target_addr:172.67.219.211:443
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:10.086	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58518	target_addr:104.18.40.152:443
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:196.715	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:19:17Z	status:FAILURE	latency:263.516	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:440.444	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:475.180	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:19:17Z	status:HEALTHY	latency:475.732	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:24:17Z	status:UNKNOWN	latency:7.439	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:9.310	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60890	target_addr:172.67.219.211:443
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:9.425	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41694	target_addr:104.18.40.152:443
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:10.720	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36980	target_addr:172.67.168.140:443
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:10.226	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39280	target_addr:104.21.86.125:443
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:215.982	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:24:17Z	status:FAILURE	latency:232.751	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:432.573	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:447.070	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:24:17Z	status:HEALTHY	latency:473.699	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:29:17Z	status:UNKNOWN	latency:6.709	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:10.218	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50696	target_addr:172.67.219.211:443
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:10.625	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42020	target_addr:172.64.147.104:443
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:10.528	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50688	target_addr:172.67.219.211:443
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:10.476	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48668	target_addr:172.67.168.140:443
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:207.191	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:29:17Z	status:FAILURE	latency:214.422	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:445.108	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:451.721	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:29:17Z	status:HEALTHY	latency:507.101	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:34:17Z	status:UNKNOWN	latency:7.854	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:8.780	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39612	target_addr:104.18.40.152:443
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:9.980	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40880	target_addr:104.21.26.208:443
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:10.057	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36698	target_addr:104.21.86.125:443
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:10.607	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36714	target_addr:104.21.86.125:443
time:2026-10-04T15:34:17Z	status:FAILURE	latency:45.437	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:204.678	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:407.701	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:408.066	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:34:17Z	status:HEALTHY	latency:415.749	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:39:17Z	status:UNKNOWN	latency:7.672	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:9.427	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38204	target_addr:172.67.168.140:443
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:9.853	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58684	target_addr:172.64.147.104:443
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:9.388	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57990	target_addr:172.67.219.211:443
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:9.687	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38624	target_addr:104.21.86.125:443
time:2026-10-04T15:39:17Z	status:FAILURE	latency:209.044	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:227.369	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:433.884	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:454.077	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:39:17Z	status:HEALTHY	latency:746.209	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:44:17Z	status:UNKNOWN	latency:7.251	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:12.891	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57384	target_addr:104.21.86.125:443
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:13.241	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34512	target_addr:172.67.168.140:443
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:13.728	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51396	target_addr:172.64.147.104:443
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:13.652	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44316	target_addr:172.67.219.211:443
time:2026-10-04T15:44:17Z	status:FAILURE	latency:24.076	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:220.301	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:523.005	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:550.057	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:44:17Z	status:HEALTHY	latency:982.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:8.031	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38138	target_addr:172.64.147.104:443
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:10.547	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47834	target_addr:172.67.168.140:443
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:10.659	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39242	target_addr:172.67.219.211:443
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:11.232	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58520	target_addr:104.21.86.125:443
time:2026-10-04T15:49:17Z	status:UNKNOWN	latency:37.318	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:303.814	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:49:17Z	status:FAILURE	latency:326.822	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:445.153	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:447.210	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:49:17Z	status:HEALTHY	latency:897.988	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:54:17Z	status:UNKNOWN	latency:8.183	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:11.776	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39260	target_addr:104.21.26.208:443
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:12.491	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42192	target_addr:104.18.40.152:443
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:11.921	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37226	target_addr:104.21.86.125:443
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:12.097	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60028	target_addr:172.67.219.211:443
time:2026-10-04T15:54:17Z	status:FAILURE	latency:31.152	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:214.122	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:488.884	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:490.281	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:54:17Z	status:HEALTHY	latency:603.988	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:59:17Z	status:UNKNOWN	latency:8.963	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:10.018	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34514	target_addr:104.21.86.125:443
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:13.374	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52368	target_addr:172.67.168.140:443
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:14.873	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34528	target_addr:104.21.86.125:443
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:18.009	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54154	target_addr:104.18.40.152:443
time:2026-10-04T15:59:17Z	status:FAILURE	latency:185.034	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:197.366	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:536.193	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:537.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T15:59:17Z	status:HEALTHY	latency:548.831	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:04:17Z	status:UNKNOWN	latency:8.597	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:11.063	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41064	target_addr:104.21.86.125:443
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:10.931	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37346	target_addr:172.67.219.211:443
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:11.594	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59936	target_addr:172.64.147.104:443
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:12.134	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52856	target_addr:104.21.26.208:443
time:2026-10-04T16:04:17Z	status:FAILURE	latency:227.011	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:254.420	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:522.182	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:548.953	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:04:17Z	status:HEALTHY	latency:553.440	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:09:17Z	status:UNKNOWN	latency:7.178	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:10.860	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53078	target_addr:172.67.168.140:443
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:11.780	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57612	target_addr:172.64.147.104:443
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:11.003	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60382	target_addr:104.21.86.125:443
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:15.560	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60394	target_addr:104.21.86.125:443
time:2026-10-04T16:09:17Z	status:FAILURE	latency:165.339	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:240.411	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:380.801	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:509.687	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:09:17Z	status:HEALTHY	latency:527.690	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:8.506	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42866	target_addr:104.18.40.152:443
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:9.194	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35962	target_addr:104.21.86.125:443
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:9.694	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58518	target_addr:104.21.26.208:443
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:11.079	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55984	target_addr:172.67.219.211:443
time:2026-10-04T16:14:17Z	status:UNKNOWN	latency:37.271	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:194.820	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:14:17Z	status:FAILURE	latency:231.872	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:418.655	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:421.584	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:14:17Z	status:HEALTHY	latency:449.214	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:19:17Z	status:UNKNOWN	latency:7.033	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:10.088	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60942	target_addr:104.21.86.125:443
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:10.664	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52196	target_addr:172.67.219.211:443
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:10.720	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36464	target_addr:104.18.40.152:443
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:11.243	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45774	target_addr:104.21.26.208:443
time:2026-10-04T16:19:17Z	status:FAILURE	latency:24.199	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:263.543	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:412.287	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:449.054	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:19:17Z	status:HEALTHY	latency:524.573	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:24:17Z	status:UNKNOWN	latency:7.998	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:10.051	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57134	target_addr:172.67.219.211:443
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:10.402	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60680	target_addr:172.64.147.104:443
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:10.585	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44744	target_addr:104.21.26.208:443
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:10.831	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58624	target_addr:104.21.86.125:443
time:2026-10-04T16:24:17Z	status:FAILURE	latency:193.622	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:198.521	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:529.905	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:530.312	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:24:17Z	status:HEALTHY	latency:534.740	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:29:17Z	status:UNKNOWN	latency:7.137	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:9.432	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53880	target_addr:172.67.168.140:443
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:11.366	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34074	target_addr:104.21.86.125:443
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:11.209	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53286	target_addr:172.67.219.211:443
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:24.315	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42214	target_addr:104.18.40.152:443
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:83.669	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:29:17Z	status:FAILURE	latency:337.494	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:470.028	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:472.578	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:29:17Z	status:HEALTHY	latency:474.952	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:9.575	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57684	target_addr:104.21.86.125:443
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:10.030	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55060	target_addr:172.67.168.140:443
time:2026-10-04T16:34:17Z	status:UNKNOWN	latency:10.331	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:11.729	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57698	target_addr:104.21.86.125:443
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:16.129	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58930	target_addr:104.18.40.152:443
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:245.046	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:441.794	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:445.004	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:34:17Z	status:HEALTHY	latency:459.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:34:17Z	status:FAILURE	latency:1223.848	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:39:17Z	status:UNKNOWN	latency:9.585	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:12.573	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40146	target_addr:104.21.86.125:443
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:12.103	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54828	target_addr:104.21.26.208:443
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:12.629	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40150	target_addr:104.21.86.125:443
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:13.322	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37448	target_addr:172.64.147.104:443
time:2026-10-04T16:39:17Z	status:FAILURE	latency:205.693	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:250.266	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:382.771	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:550.265	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:39:17Z	status:HEALTHY	latency:570.608	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:44:17Z	status:UNKNOWN	latency:5.651	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:7.922	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43034	target_addr:104.21.86.125:443
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:9.198	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39162	target_addr:104.18.40.152:443
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:11.584	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52398	target_addr:172.67.168.140:443
time:2026-10-04T16:44:17Z	status:FAILURE	latency:20.958	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:23.756	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43044	target_addr:104.21.86.125:443
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:218.044	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:470.930	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:481.072	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:44:17Z	status:HEALTHY	latency:635.516	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:49:17Z	status:UNKNOWN	latency:7.548	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:10.251	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55678	target_addr:104.18.40.152:443
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:10.129	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44018	target_addr:104.21.26.208:443
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:11.793	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51376	target_addr:104.21.86.125:443
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:13.095	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51378	target_addr:104.21.86.125:443
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:93.479	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:49:17Z	status:FAILURE	latency:229.349	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:427.958	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:445.962	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:49:17Z	status:HEALTHY	latency:550.364	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:54:17Z	status:UNKNOWN	latency:6.910	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:9.991	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39162	target_addr:172.64.147.104:443
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:10.153	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41874	target_addr:172.67.219.211:443
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:10.806	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37848	target_addr:172.67.168.140:443
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:11.215	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41886	target_addr:172.67.219.211:443
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:109.485	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:54:17Z	status:FAILURE	latency:171.077	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:427.017	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:440.938	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:54:17Z	status:HEALTHY	latency:681.555	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:59:17Z	status:UNKNOWN	latency:7.100	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:9.012	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60312	target_addr:104.21.26.208:443
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:9.825	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40712	target_addr:104.21.86.125:443
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:11.176	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40720	target_addr:104.21.86.125:443
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:33.259	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47434	target_addr:172.64.147.104:443
time:2026-10-04T16:59:17Z	status:FAILURE	latency:255.592	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:256.053	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:554.192	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:737.159	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T16:59:17Z	status:HEALTHY	latency:1235.834	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:04:17Z	status:UNKNOWN	latency:6.645	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:8.093	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44338	target_addr:172.64.147.104:443
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:8.849	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50946	target_addr:104.21.26.208:443
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:9.536	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33434	target_addr:172.67.219.211:443
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:11.374	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33444	target_addr:172.67.219.211:443
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:177.972	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:04:17Z	status:FAILURE	latency:183.326	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:542.135	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:542.878	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:04:17Z	status:HEALTHY	latency:617.134	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:09:17Z	status:UNKNOWN	latency:8.073	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:9.776	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56804	target_addr:172.67.219.211:443
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:11.372	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44694	target_addr:104.21.26.208:443
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:14.400	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55184	target_addr:104.21.86.125:443
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:29.196	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45544	target_addr:172.64.147.104:443
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:221.594	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:09:17Z	status:FAILURE	latency:239.942	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:517.568	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:525.520	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:09:17Z	status:HEALTHY	latency:552.997	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:14:17Z	status:UNKNOWN	latency:8.305	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:11.106	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46290	target_addr:172.67.168.140:443
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:11.417	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35734	target_addr:104.18.40.152:443
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:11.288	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46338	target_addr:104.21.86.125:443
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:11.635	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59914	target_addr:172.67.219.211:443
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:109.468	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:14:17Z	status:FAILURE	latency:219.175	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:463.120	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:547.233	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:14:17Z	status:HEALTHY	latency:576.390	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:19:17Z	status:UNKNOWN	latency:7.694	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:19:17Z	status:HEALTHY	latency:8.577	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45054	target_addr:172.64.147.104:443
time:2026-10-04T17:19:17Z	status:HEALTHY	latency:10.802	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50740	target_addr:104.21.86.125:443
time:2026-10-04T17:19:17Z	status:HEALTHY	latency:14.938	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55260	target_addr:104.21.26.208:443
time:2026-10-04T17:19:17Z	status:HEALTHY	latency:15.710	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50736	target_addr:104.21.86.125:443
time:2026-10-04T17:19:17Z	status:FAILURE	latency:147.865	target:https://go3-cn.online/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-10-04T17:19:17Z	status:FAILURE	latency:150.768	target:https://go3-cn.xyz/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-10-04T17:19:17Z	status:FAILURE	latency:151.626	target:https://go3-cn.blog/	message:503 Service Unavailable	proto:HTTP/2.0	status_code:503
time:2026-10-04T17:19:17Z	status:FAILURE	latency:172.163	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:19:17Z	status:HEALTHY	latency:211.473	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:24:17Z	status:UNKNOWN	latency:7.530	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:9.611	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36728	target_addr:172.67.219.211:443
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:11.187	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49214	target_addr:172.64.147.104:443
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:12.119	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36744	target_addr:172.67.219.211:443
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:15.472	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43570	target_addr:172.67.168.140:443
time:2026-10-04T17:24:17Z	status:FAILURE	latency:53.045	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:220.922	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:368.767	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:384.444	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:24:17Z	status:HEALTHY	latency:548.104	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:29:17Z	status:UNKNOWN	latency:7.882	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:8.681	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42360	target_addr:172.67.168.140:443
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:9.051	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59778	target_addr:104.21.86.125:443
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:10.581	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52294	target_addr:172.64.147.104:443
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:11.022	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59786	target_addr:104.21.86.125:443
time:2026-10-04T17:29:17Z	status:FAILURE	latency:202.323	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:205.544	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:483.634	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:537.244	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:29:17Z	status:HEALTHY	latency:836.711	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:10.976	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39666	target_addr:172.67.219.211:443
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:11.488	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49690	target_addr:104.18.40.152:443
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:12.894	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39678	target_addr:172.67.219.211:443
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:14.306	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34804	target_addr:104.21.26.208:443
time:2026-10-04T17:34:17Z	status:UNKNOWN	latency:36.754	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:34:17Z	status:FAILURE	latency:203.545	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:228.895	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:421.035	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:429.573	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:34:17Z	status:HEALTHY	latency:430.083	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:9.857	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43550	target_addr:104.18.40.152:443
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:10.304	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51280	target_addr:172.67.219.211:443
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:11.088	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48178	target_addr:104.21.86.125:443
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:13.168	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35298	target_addr:104.21.26.208:443
time:2026-10-04T17:39:17Z	status:UNKNOWN	latency:33.149	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:202.220	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:39:17Z	status:FAILURE	latency:331.528	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:380.332	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:387.913	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:39:17Z	status:HEALTHY	latency:457.668	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:44:17Z	status:UNKNOWN	latency:7.219	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:7.842	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33666	target_addr:172.67.219.211:443
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:11.158	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42904	target_addr:104.21.26.208:443
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:15.088	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39632	target_addr:104.21.86.125:443
time:2026-10-04T17:44:17Z	status:FAILURE	latency:27.976	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:31.758	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46922	target_addr:172.64.147.104:443
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:184.172	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:425.062	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:427.915	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:44:17Z	status:HEALTHY	latency:430.433	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:49:17Z	status:UNKNOWN	latency:7.731	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:9.510	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57378	target_addr:172.67.219.211:443
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:10.107	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46986	target_addr:104.18.40.152:443
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:11.039	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54384	target_addr:104.21.86.125:443
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:12.001	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46752	target_addr:104.21.26.208:443
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:227.805	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:388.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:427.694	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:49:17Z	status:HEALTHY	latency:485.676	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:49:17Z	status:FAILURE	latency:593.444	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:54:17Z	status:UNKNOWN	latency:7.695	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:11.956	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34700	target_addr:172.67.168.140:443
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:12.432	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57324	target_addr:172.67.219.211:443
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:12.217	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57326	target_addr:172.67.219.211:443
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:13.343	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36400	target_addr:172.64.147.104:443
time:2026-10-04T17:54:17Z	status:FAILURE	latency:171.769	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:229.198	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:479.018	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:536.104	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:54:17Z	status:HEALTHY	latency:549.933	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:59:17Z	status:UNKNOWN	latency:8.423	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:11.469	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50480	target_addr:172.67.219.211:443
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:11.982	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44244	target_addr:172.64.147.104:443
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:12.047	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53296	target_addr:104.21.26.208:443
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:13.038	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50496	target_addr:172.67.219.211:443
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:201.261	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:443.021	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:515.804	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:59:17Z	status:HEALTHY	latency:523.857	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T17:59:17Z	status:FAILURE	latency:1984.633	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:04:17Z	status:UNKNOWN	latency:6.811	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:9.915	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44196	target_addr:104.21.86.125:443
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:9.451	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45338	target_addr:172.67.219.211:443
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:9.924	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45242	target_addr:104.18.40.152:443
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:20.915	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57368	target_addr:104.21.26.208:443
time:2026-10-04T18:04:17Z	status:FAILURE	latency:226.295	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:263.415	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:448.134	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:450.404	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:04:17Z	status:HEALTHY	latency:469.724	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:09:17Z	status:UNKNOWN	latency:8.665	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:9.546	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50366	target_addr:104.21.26.208:443
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:11.564	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60164	target_addr:172.67.219.211:443
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:12.318	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52194	target_addr:104.18.40.152:443
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:15.525	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60166	target_addr:172.67.219.211:443
time:2026-10-04T18:09:17Z	status:FAILURE	latency:157.193	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:238.443	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:462.837	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:464.842	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:09:17Z	status:HEALTHY	latency:483.554	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:9.274	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53952	target_addr:172.67.219.211:443
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:15.793	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43074	target_addr:104.21.26.208:443
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:19.534	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53960	target_addr:172.67.219.211:443
time:2026-10-04T18:14:17Z	status:FAILURE	latency:23.138	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:14:17Z	status:UNKNOWN	latency:33.892	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:58.492	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52726	target_addr:104.18.40.152:443
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:244.964	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:455.373	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:472.989	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:14:17Z	status:HEALTHY	latency:522.378	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:19:17Z	status:UNKNOWN	latency:7.911	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:9.372	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54922	target_addr:104.18.40.152:443
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:9.240	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33118	target_addr:172.67.219.211:443
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:10.590	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33122	target_addr:172.67.219.211:443
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:11.354	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59642	target_addr:172.67.168.140:443
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:210.415	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:485.531	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:486.464	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:19:17Z	status:HEALTHY	latency:554.103	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:19:17Z	status:FAILURE	latency:4131.665	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:24:18Z	status:UNKNOWN	latency:8.565	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:9.902	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38180	target_addr:172.64.147.104:443
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:9.722	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59220	target_addr:172.67.168.140:443
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:11.947	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38430	target_addr:104.21.86.125:443
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:28.071	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38444	target_addr:104.21.86.125:443
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:194.566	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:24:18Z	status:FAILURE	latency:230.527	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:455.300	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:467.826	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:24:18Z	status:HEALTHY	latency:524.857	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:9.337	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54478	target_addr:172.64.147.104:443
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:9.779	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35936	target_addr:172.67.168.140:443
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:9.800	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43850	target_addr:104.21.86.125:443
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:11.307	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43860	target_addr:104.21.86.125:443
time:2026-10-04T18:29:18Z	status:UNKNOWN	latency:55.703	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:197.957	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:29:18Z	status:FAILURE	latency:228.084	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:485.114	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:490.763	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:29:18Z	status:HEALTHY	latency:616.438	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:9.865	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47984	target_addr:172.64.147.104:443
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:10.204	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40770	target_addr:104.21.86.125:443
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:11.662	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36278	target_addr:172.67.168.140:443
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:11.965	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59846	target_addr:172.67.219.211:443
time:2026-10-04T18:34:18Z	status:UNKNOWN	latency:62.405	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:34:18Z	status:FAILURE	latency:141.922	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:225.274	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:453.479	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:722.495	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:34:18Z	status:HEALTHY	latency:1293.855	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:39:18Z	status:UNKNOWN	latency:8.036	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:10.374	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47222	target_addr:104.21.86.125:443
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:14.324	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51440	target_addr:172.67.219.211:443
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:14.698	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36702	target_addr:172.64.147.104:443
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:18.492	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59938	target_addr:104.21.26.208:443
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:197.601	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:39:18Z	status:FAILURE	latency:203.299	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:541.501	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:567.030	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:39:18Z	status:HEALTHY	latency:745.220	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:44:18Z	status:UNKNOWN	latency:9.811	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:10.190	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51448	target_addr:104.21.86.125:443
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:10.671	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37516	target_addr:104.18.40.152:443
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:10.041	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50976	target_addr:172.67.219.211:443
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:10.879	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58764	target_addr:104.21.26.208:443
time:2026-10-04T18:44:18Z	status:FAILURE	latency:27.022	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:304.033	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:423.786	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:439.498	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:44:18Z	status:HEALTHY	latency:479.094	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:49:18Z	status:UNKNOWN	latency:7.794	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:9.762	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36852	target_addr:104.18.40.152:443
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:10.006	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38808	target_addr:104.21.86.125:443
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:10.479	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52272	target_addr:172.67.168.140:443
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:17.831	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38822	target_addr:104.21.86.125:443
time:2026-10-04T18:49:18Z	status:FAILURE	latency:229.043	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:267.021	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:446.613	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:472.319	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:49:18Z	status:HEALTHY	latency:707.853	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:54:18Z	status:UNKNOWN	latency:5.515	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:9.717	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41212	target_addr:104.21.86.125:443
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:10.504	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37444	target_addr:104.21.26.208:443
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:10.318	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44836	target_addr:104.18.40.152:443
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:16.617	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41216	target_addr:104.21.86.125:443
time:2026-10-04T18:54:18Z	status:FAILURE	latency:179.496	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:213.000	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:469.474	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:561.334	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:54:18Z	status:HEALTHY	latency:572.754	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:59:18Z	status:UNKNOWN	latency:6.135	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:10.385	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59568	target_addr:104.21.86.125:443
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:11.267	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60090	target_addr:172.64.147.104:443
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:11.357	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53846	target_addr:172.67.168.140:443
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:51.503	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34046	target_addr:172.67.219.211:443
time:2026-10-04T18:59:18Z	status:FAILURE	latency:205.307	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:295.251	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:480.605	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:490.405	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T18:59:18Z	status:HEALTHY	latency:497.955	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:04:18Z	status:UNKNOWN	latency:7.347	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:9.154	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49748	target_addr:172.67.219.211:443
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:10.675	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52598	target_addr:172.64.147.104:443
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:12.828	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49762	target_addr:172.67.219.211:443
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:24.483	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48652	target_addr:104.21.26.208:443
time:2026-10-04T19:04:18Z	status:FAILURE	latency:31.062	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:51.390	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:59.351	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:67.322	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:04:18Z	status:HEALTHY	latency:220.199	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:09:18Z	status:UNKNOWN	latency:7.341	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:10.407	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50384	target_addr:172.67.219.211:443
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:15.847	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42994	target_addr:172.64.147.104:443
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:29.075	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44592	target_addr:172.67.168.140:443
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:60.186	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:75.397	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50392	target_addr:172.67.219.211:443
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:99.940	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:09:18Z	status:FAILURE	latency:154.451	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:336.698	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:09:18Z	status:HEALTHY	latency:471.517	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:9.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41252	target_addr:172.64.147.104:443
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:9.980	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51976	target_addr:104.21.86.125:443
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:10.217	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51990	target_addr:104.21.86.125:443
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:11.446	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59956	target_addr:104.21.26.208:443
time:2026-10-04T19:14:18Z	status:FAILURE	latency:23.491	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:14:18Z	status:UNKNOWN	latency:35.595	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:83.684	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:95.857	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:102.021	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:14:18Z	status:HEALTHY	latency:223.163	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:9.615	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57832	target_addr:172.67.219.211:443
time:2026-10-04T19:19:18Z	status:UNKNOWN	latency:10.310	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:11.447	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33798	target_addr:172.64.147.104:443
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:11.954	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57840	target_addr:172.67.219.211:443
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:16.994	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51048	target_addr:172.67.168.140:443
time:2026-10-04T19:19:18Z	status:FAILURE	latency:32.546	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:52.043	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:64.771	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:92.531	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:19:18Z	status:HEALTHY	latency:209.989	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:24:18Z	status:UNKNOWN	latency:9.394	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:11.841	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47940	target_addr:104.18.40.152:443
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:12.756	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39688	target_addr:172.67.219.211:443
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:13.830	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59030	target_addr:172.67.168.140:443
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:16.174	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39704	target_addr:172.67.219.211:443
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:61.254	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:68.877	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:71.599	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:24:18Z	status:FAILURE	latency:202.048	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:24:18Z	status:HEALTHY	latency:212.211	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:9.783	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47672	target_addr:104.21.26.208:443
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:10.556	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41694	target_addr:172.64.147.104:443
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:12.743	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56238	target_addr:104.21.86.125:443
time:2026-10-04T19:29:18Z	status:UNKNOWN	latency:16.004	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:16.544	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59848	target_addr:172.67.219.211:443
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:58.020	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:57.775	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:71.210	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:29:18Z	status:FAILURE	latency:201.073	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:29:18Z	status:HEALTHY	latency:442.186	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:9.954	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50086	target_addr:172.67.168.140:443
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:9.660	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48420	target_addr:104.21.86.125:443
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:16.672	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48424	target_addr:104.21.86.125:443
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:23.696	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33352	target_addr:104.18.40.152:443
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:55.250	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:34:18Z	status:UNKNOWN	latency:58.098	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:72.868	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:199.691	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:34:18Z	status:HEALTHY	latency:330.377	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:34:18Z	status:FAILURE	latency:692.699	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:39:18Z	status:UNKNOWN	latency:7.976	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:10.312	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59874	target_addr:104.21.86.125:443
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:10.876	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34972	target_addr:172.64.147.104:443
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:10.183	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59882	target_addr:104.21.86.125:443
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:11.233	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52728	target_addr:172.67.168.140:443
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:55.040	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:59.485	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:61.411	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:39:18Z	status:FAILURE	latency:142.837	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:39:18Z	status:HEALTHY	latency:242.427	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:44:18Z	status:UNKNOWN	latency:8.898	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:10.098	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37012	target_addr:172.64.147.104:443
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:11.944	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35250	target_addr:172.67.219.211:443
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:16.820	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35402	target_addr:104.21.86.125:443
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:16.559	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52464	target_addr:104.21.26.208:443
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:60.723	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:60.392	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:60.221	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:44:18Z	status:HEALTHY	latency:273.867	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:44:18Z	status:FAILURE	latency:405.450	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:49:18Z	status:UNKNOWN	latency:8.332	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:11.404	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34498	target_addr:104.21.26.208:443
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:12.189	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35748	target_addr:172.64.147.104:443
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:13.867	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57200	target_addr:104.21.86.125:443
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:15.192	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41294	target_addr:172.67.219.211:443
time:2026-10-04T19:49:18Z	status:FAILURE	latency:175.328	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:217.365	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:429.293	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:455.730	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:49:18Z	status:HEALTHY	latency:940.326	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:54:18Z	status:UNKNOWN	latency:7.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:9.520	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42378	target_addr:172.67.219.211:443
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:10.610	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43388	target_addr:104.21.26.208:443
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:11.069	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41438	target_addr:104.18.40.152:443
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:10.503	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42392	target_addr:172.67.219.211:443
time:2026-10-04T19:54:18Z	status:FAILURE	latency:191.237	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:200.722	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:546.324	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:827.291	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:54:18Z	status:HEALTHY	latency:1272.257	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:59:18Z	status:UNKNOWN	latency:6.935	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:8.844	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37402	target_addr:104.21.26.208:443
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:10.863	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53942	target_addr:104.21.86.125:443
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:11.416	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53950	target_addr:104.21.86.125:443
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:11.530	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40322	target_addr:172.64.147.104:443
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:201.273	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:59:18Z	status:FAILURE	latency:210.500	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:508.919	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:834.415	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T19:59:18Z	status:HEALTHY	latency:878.532	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:04:18Z	status:UNKNOWN	latency:7.173	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:8.633	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48006	target_addr:104.18.40.152:443
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:8.641	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46396	target_addr:172.67.219.211:443
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:10.692	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57558	target_addr:172.67.168.140:443
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:11.490	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46408	target_addr:172.67.219.211:443
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:303.258	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:04:18Z	status:FAILURE	latency:309.339	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:511.111	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:536.245	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:04:18Z	status:HEALTHY	latency:546.168	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:09:18Z	status:UNKNOWN	latency:8.252	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:9.193	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33126	target_addr:104.21.26.208:443
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:10.494	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56540	target_addr:104.18.40.152:443
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:13.324	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36856	target_addr:172.67.219.211:443
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:13.594	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36866	target_addr:172.67.219.211:443
time:2026-10-04T20:09:18Z	status:FAILURE	latency:27.353	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:65.410	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:83.180	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:228.010	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:09:18Z	status:HEALTHY	latency:241.028	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:14:18Z	status:UNKNOWN	latency:7.046	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:9.045	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47346	target_addr:172.64.147.104:443
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:9.644	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42656	target_addr:172.67.219.211:443
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:10.310	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47546	target_addr:104.21.26.208:443
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:11.452	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58756	target_addr:104.21.86.125:443
time:2026-10-04T20:14:18Z	status:FAILURE	latency:29.759	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:51.632	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:60.186	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:133.527	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:14:18Z	status:HEALTHY	latency:230.619	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:10.653	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35684	target_addr:172.67.219.211:443
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:10.829	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51486	target_addr:104.21.26.208:443
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:12.692	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49480	target_addr:104.21.86.125:443
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:13.970	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52644	target_addr:172.64.147.104:443
time:2026-10-04T20:19:18Z	status:UNKNOWN	latency:37.398	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:54.949	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:56.303	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:59.838	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:19:18Z	status:FAILURE	latency:182.586	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:19:18Z	status:HEALTHY	latency:223.232	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:24:18Z	status:UNKNOWN	latency:7.013	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:9.188	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40514	target_addr:172.67.219.211:443
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:14.932	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40516	target_addr:172.67.219.211:443
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:15.802	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35920	target_addr:104.21.26.208:443
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:18.599	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43260	target_addr:172.64.147.104:443
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:59.030	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:60.364	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:90.395	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:24:18Z	status:HEALTHY	latency:220.685	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:24:18Z	status:FAILURE	latency:270.947	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:29:18Z	status:UNKNOWN	latency:7.853	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:9.439	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43184	target_addr:104.18.40.152:443
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:10.392	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55908	target_addr:104.21.26.208:443
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:11.245	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47600	target_addr:104.21.86.125:443
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:12.825	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47614	target_addr:104.21.86.125:443
time:2026-10-04T20:29:18Z	status:FAILURE	latency:28.313	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:51.214	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:56.685	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:106.724	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:29:18Z	status:HEALTHY	latency:220.191	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:34:18Z	status:UNKNOWN	latency:6.935	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:8.935	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60590	target_addr:104.18.40.152:443
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:9.986	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46708	target_addr:172.67.168.140:443
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:11.066	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36612	target_addr:172.67.219.211:443
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:19.168	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45852	target_addr:104.21.86.125:443
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:110.952	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:480.246	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:727.544	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:34:18Z	status:HEALTHY	latency:932.264	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:34:18Z	status:FAILURE	latency:5204.893	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:39:18Z	status:UNKNOWN	latency:7.429	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:10.978	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44928	target_addr:104.18.40.152:443
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:11.565	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60284	target_addr:104.21.26.208:443
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:11.281	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33922	target_addr:172.67.219.211:443
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:16.324	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33932	target_addr:172.67.219.211:443
time:2026-10-04T20:39:18Z	status:FAILURE	latency:202.507	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:224.278	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:496.240	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:645.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:39:18Z	status:HEALTHY	latency:1467.113	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:10.877	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53188	target_addr:172.67.219.211:443
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:10.808	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40992	target_addr:172.67.168.140:443
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:10.833	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34602	target_addr:104.21.86.125:443
time:2026-10-04T20:44:18Z	status:UNKNOWN	latency:15.107	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:25.034	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40204	target_addr:172.64.147.104:443
time:2026-10-04T20:44:18Z	status:FAILURE	latency:213.722	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:231.252	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:518.905	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:544.292	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:44:18Z	status:HEALTHY	latency:548.255	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:11.590	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56670	target_addr:172.67.219.211:443
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:16.413	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33364	target_addr:104.21.26.208:443
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:16.788	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59348	target_addr:104.21.86.125:443
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:25.131	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34616	target_addr:172.64.147.104:443
time:2026-10-04T20:49:18Z	status:UNKNOWN	latency:38.293	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:49:18Z	status:FAILURE	latency:208.186	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:242.337	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:438.218	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:460.386	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:49:18Z	status:HEALTHY	latency:1035.351	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:54:18Z	status:UNKNOWN	latency:6.950	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:10.297	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34396	target_addr:172.67.168.140:443
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:10.585	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32828	target_addr:104.21.86.125:443
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:10.872	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:32838	target_addr:104.21.86.125:443
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:12.007	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50216	target_addr:172.64.147.104:443
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:230.934	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:421.697	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:528.457	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:54:18Z	status:HEALTHY	latency:1141.232	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:54:18Z	status:FAILURE	latency:1865.599	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:59:18Z	status:UNKNOWN	latency:8.578	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:10.176	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47106	target_addr:172.64.147.104:443
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:10.326	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37710	target_addr:172.67.168.140:443
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:10.667	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38268	target_addr:104.21.86.125:443
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:19.120	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38280	target_addr:104.21.86.125:443
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:235.601	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:59:18Z	status:FAILURE	latency:253.421	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:469.719	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:512.524	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T20:59:18Z	status:HEALTHY	latency:1384.249	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:04:18Z	status:UNKNOWN	latency:10.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:13.711	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47170	target_addr:172.67.219.211:443
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:13.781	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33326	target_addr:104.21.26.208:443
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:16.050	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59990	target_addr:172.64.147.104:443
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:34.174	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47160	target_addr:172.67.219.211:443
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:66.440	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:73.647	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:90.018	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:04:18Z	status:HEALTHY	latency:236.359	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:04:18Z	status:FAILURE	latency:763.490	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:09:18Z	status:UNKNOWN	latency:7.255	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:9.216	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38380	target_addr:172.67.219.211:443
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:9.692	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38396	target_addr:172.67.219.211:443
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:11.138	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55830	target_addr:104.21.26.208:443
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:15.850	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46696	target_addr:104.18.40.152:443
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:58.682	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:60.173	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:73.924	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:09:18Z	status:HEALTHY	latency:89.891	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:09:18Z	status:FAILURE	latency:214.627	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:14:18Z	status:UNKNOWN	latency:8.962	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:9.800	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43220	target_addr:104.21.86.125:443
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:10.185	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38668	target_addr:104.21.26.208:443
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:12.607	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60486	target_addr:172.67.219.211:443
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:15.438	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35760	target_addr:172.64.147.104:443
time:2026-10-04T21:14:18Z	status:FAILURE	latency:26.210	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:55.629	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:57.146	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:58.849	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:14:18Z	status:HEALTHY	latency:218.547	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:19:18Z	status:UNKNOWN	latency:7.939	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:7.992	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57220	target_addr:104.21.26.208:443
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:9.882	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58846	target_addr:172.67.219.211:443
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:10.402	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58854	target_addr:172.67.219.211:443
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:60.924	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:73.685	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:76.651	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51468	target_addr:172.64.147.104:443
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:98.454	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:19:18Z	status:FAILURE	latency:226.175	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:19:18Z	status:HEALTHY	latency:228.206	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:24:18Z	status:UNKNOWN	latency:7.981	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:10.448	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33736	target_addr:172.67.219.211:443
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:10.798	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37342	target_addr:172.67.168.140:443
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:12.138	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58754	target_addr:104.21.86.125:443
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:13.024	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47116	target_addr:104.18.40.152:443
time:2026-10-04T21:24:18Z	status:FAILURE	latency:25.556	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:53.973	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:63.502	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:68.062	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:24:18Z	status:HEALTHY	latency:219.942	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:29:18Z	status:UNKNOWN	latency:9.593	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:11.117	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44646	target_addr:172.64.147.104:443
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:12.270	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57928	target_addr:104.21.86.125:443
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:12.629	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57932	target_addr:104.21.86.125:443
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:30.620	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56250	target_addr:104.21.26.208:443
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:55.639	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:57.169	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:66.503	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:29:18Z	status:HEALTHY	latency:252.988	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:29:18Z	status:FAILURE	latency:1658.841	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:9.656	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42592	target_addr:172.67.168.140:443
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:13.509	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53796	target_addr:104.18.40.152:443
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:14.845	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54792	target_addr:104.21.86.125:443
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:16.446	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54802	target_addr:104.21.86.125:443
time:2026-10-04T21:34:18Z	status:UNKNOWN	latency:35.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:61.858	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:61.705	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:70.035	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:34:18Z	status:HEALTHY	latency:237.638	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:34:18Z	status:FAILURE	latency:319.872	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:39:18Z	status:UNKNOWN	latency:8.444	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:10.936	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44128	target_addr:172.67.219.211:443
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:11.499	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57328	target_addr:172.67.168.140:443
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:11.696	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44138	target_addr:172.67.219.211:443
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:15.626	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41258	target_addr:172.64.147.104:443
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:59.558	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:83.050	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:39:18Z	status:FAILURE	latency:166.093	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:244.200	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:39:18Z	status:HEALTHY	latency:389.029	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:44:18Z	status:UNKNOWN	latency:10.215	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:9.795	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44400	target_addr:172.67.168.140:443
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:13.365	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42158	target_addr:172.67.219.211:443
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:14.588	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50496	target_addr:104.18.40.152:443
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:18.880	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38942	target_addr:104.21.86.125:443
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:54.080	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:55.263	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:58.905	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:44:18Z	status:FAILURE	latency:203.149	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:44:18Z	status:HEALTHY	latency:220.157	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:49:18Z	status:UNKNOWN	latency:7.658	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:9.853	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52916	target_addr:104.21.86.125:443
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:10.983	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53024	target_addr:172.67.168.140:443
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:12.634	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39402	target_addr:172.64.147.104:443
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:17.534	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52926	target_addr:104.21.86.125:443
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:58.773	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:82.164	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:118.749	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:49:18Z	status:FAILURE	latency:217.585	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:49:18Z	status:HEALTHY	latency:289.311	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:54:18Z	status:UNKNOWN	latency:8.559	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:8.707	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44534	target_addr:172.67.219.211:443
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:9.336	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51512	target_addr:104.21.26.208:443
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:9.540	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57006	target_addr:104.21.86.125:443
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:11.472	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34538	target_addr:172.64.147.104:443
time:2026-10-04T21:54:18Z	status:FAILURE	latency:189.662	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:200.505	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:460.474	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:468.227	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:54:18Z	status:HEALTHY	latency:678.384	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:59:18Z	status:UNKNOWN	latency:9.165	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:11.061	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52600	target_addr:104.21.86.125:443
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:12.728	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57386	target_addr:104.18.40.152:443
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:11.503	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52004	target_addr:104.21.26.208:443
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:11.530	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52614	target_addr:104.21.86.125:443
time:2026-10-04T21:59:18Z	status:FAILURE	latency:28.456	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:137.775	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:564.992	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:570.587	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T21:59:18Z	status:HEALTHY	latency:994.742	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:04:18Z	status:UNKNOWN	latency:7.410	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:9.741	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45894	target_addr:172.67.168.140:443
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:9.748	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56782	target_addr:104.18.40.152:443
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:11.761	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39732	target_addr:172.67.219.211:443
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:14.096	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39734	target_addr:172.67.219.211:443
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:189.125	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:04:18Z	status:FAILURE	latency:210.338	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:445.948	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:504.525	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:04:18Z	status:HEALTHY	latency:517.445	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:10.757	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36870	target_addr:172.67.168.140:443
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:10.301	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54174	target_addr:104.21.86.125:443
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:12.874	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54798	target_addr:172.67.219.211:443
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:18.718	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40958	target_addr:172.64.147.104:443
time:2026-10-04T22:09:18Z	status:UNKNOWN	latency:56.255	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:09:18Z	status:FAILURE	latency:189.163	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:287.577	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:425.552	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:434.168	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:09:18Z	status:HEALTHY	latency:456.602	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:14:18Z	status:UNKNOWN	latency:7.824	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:8.584	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40030	target_addr:104.21.86.125:443
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:15.296	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40612	target_addr:104.18.40.152:443
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:23.195	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59956	target_addr:172.67.219.211:443
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:26.898	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34394	target_addr:172.67.168.140:443
time:2026-10-04T22:14:18Z	status:FAILURE	latency:199.664	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:220.406	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:590.645	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:597.958	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:14:18Z	status:HEALTHY	latency:635.752	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:19:18Z	status:UNKNOWN	latency:7.782	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:8.931	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37654	target_addr:172.64.147.104:443
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:11.791	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60986	target_addr:104.21.86.125:443
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:12.612	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47752	target_addr:172.67.219.211:443
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:13.135	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42884	target_addr:172.67.168.140:443
time:2026-10-04T22:19:18Z	status:FAILURE	latency:191.315	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:215.938	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:508.471	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:529.192	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:19:18Z	status:HEALTHY	latency:912.685	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:24:18Z	status:UNKNOWN	latency:7.874	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:10.020	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53076	target_addr:104.21.86.125:443
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:10.575	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48270	target_addr:104.21.26.208:443
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:10.406	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40772	target_addr:172.67.219.211:443
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:10.790	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49634	target_addr:172.64.147.104:443
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:59.755	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:61.810	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:68.377	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:24:18Z	status:HEALTHY	latency:228.613	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:24:18Z	status:FAILURE	latency:1742.427	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:29:18Z	status:UNKNOWN	latency:6.818	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:9.632	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59498	target_addr:104.18.40.152:443
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:10.317	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47152	target_addr:172.67.219.211:443
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:10.930	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37712	target_addr:104.21.26.208:443
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:12.710	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43600	target_addr:104.21.86.125:443
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:59.491	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:60.297	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:65.397	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:29:18Z	status:FAILURE	latency:209.104	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:29:18Z	status:HEALTHY	latency:295.675	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:9.371	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45838	target_addr:104.21.86.125:443
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:11.349	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58328	target_addr:172.67.168.140:443
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:15.118	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39256	target_addr:172.67.219.211:443
time:2026-10-04T22:34:19Z	status:UNKNOWN	latency:24.556	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:27.096	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58278	target_addr:172.64.147.104:443
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:58.714	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:60.456	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:69.544	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:34:19Z	status:FAILURE	latency:168.040	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:34:19Z	status:HEALTHY	latency:273.942	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:11.230	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47206	target_addr:104.21.26.208:443
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:11.289	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42002	target_addr:172.67.219.211:443
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:15.769	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53058	target_addr:104.18.40.152:443
time:2026-10-04T22:39:19Z	status:UNKNOWN	latency:20.723	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:39:19Z	status:FAILURE	latency:32.104	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:41.309	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42006	target_addr:172.67.219.211:443
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:54.979	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:56.789	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:58.771	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:39:19Z	status:HEALTHY	latency:204.432	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:44:19Z	status:UNKNOWN	latency:8.536	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:9.087	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51596	target_addr:104.18.40.152:443
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:12.713	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35268	target_addr:172.67.168.140:443
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:13.013	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55100	target_addr:172.67.219.211:443
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:56.974	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:68.010	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:93.027	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45986	target_addr:104.21.86.125:443
time:2026-10-04T22:44:19Z	status:FAILURE	latency:192.321	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:228.796	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:44:19Z	status:HEALTHY	latency:241.508	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:10.178	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38474	target_addr:172.64.147.104:443
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:10.112	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36572	target_addr:104.21.86.125:443
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:10.474	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59658	target_addr:172.67.168.140:443
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:12.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51286	target_addr:172.67.219.211:443
time:2026-10-04T22:49:19Z	status:UNKNOWN	latency:56.196	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:57.997	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:74.665	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:89.751	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:49:19Z	status:FAILURE	latency:188.903	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:49:19Z	status:HEALTHY	latency:221.661	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:54:19Z	status:UNKNOWN	latency:7.533	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:11.284	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59654	target_addr:172.64.147.104:443
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:11.437	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38594	target_addr:104.21.26.208:443
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:11.550	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39356	target_addr:172.67.219.211:443
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:18.646	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42966	target_addr:104.21.86.125:443
time:2026-10-04T22:54:19Z	status:FAILURE	latency:23.329	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:55.875	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:57.858	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:157.313	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:54:19Z	status:HEALTHY	latency:254.253	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:59:19Z	status:UNKNOWN	latency:7.935	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:9.027	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53722	target_addr:172.67.219.211:443
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:9.169	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34926	target_addr:172.67.168.140:443
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:10.595	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52886	target_addr:104.18.40.152:443
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:11.063	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39882	target_addr:104.21.86.125:443
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:56.461	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:82.308	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:118.013	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T22:59:19Z	status:FAILURE	latency:225.115	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T22:59:19Z	status:HEALTHY	latency:230.955	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:04:19Z	status:UNKNOWN	latency:7.270	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:10.289	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39658	target_addr:104.21.26.208:443
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:10.624	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47216	target_addr:104.21.86.125:443
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:11.962	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47218	target_addr:104.21.86.125:443
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:12.044	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52274	target_addr:104.18.40.152:443
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:54.258	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:58.148	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:96.111	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:04:19Z	status:HEALTHY	latency:261.368	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:04:19Z	status:FAILURE	latency:311.541	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:09:19Z	status:UNKNOWN	latency:9.030	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:10.133	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55100	target_addr:172.67.219.211:443
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:10.380	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55096	target_addr:172.67.219.211:443
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:10.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57454	target_addr:172.64.147.104:443
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:12.083	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37832	target_addr:172.67.168.140:443
time:2026-10-04T23:09:19Z	status:FAILURE	latency:28.595	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:59.623	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:76.257	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:117.253	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:09:19Z	status:HEALTHY	latency:232.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:14:19Z	status:UNKNOWN	latency:8.688	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:11.683	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46258	target_addr:172.67.219.211:443
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:11.793	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42062	target_addr:104.18.40.152:443
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:12.458	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33812	target_addr:172.67.168.140:443
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:28.584	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51040	target_addr:104.21.86.125:443
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:59.083	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:79.204	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:86.086	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:14:19Z	status:HEALTHY	latency:242.452	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:14:19Z	status:FAILURE	latency:326.703	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:19:19Z	status:UNKNOWN	latency:10.243	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:10.114	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43716	target_addr:172.67.219.211:443
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:10.159	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47168	target_addr:104.21.26.208:443
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:10.698	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43722	target_addr:172.67.219.211:443
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:14.643	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42618	target_addr:172.64.147.104:443
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:58.513	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:59.139	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:192.799	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:19:19Z	status:FAILURE	latency:213.098	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:19:19Z	status:HEALTHY	latency:318.680	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:24:19Z	status:UNKNOWN	latency:7.022	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:9.645	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34812	target_addr:104.21.86.125:443
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:10.209	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34802	target_addr:104.21.86.125:443
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:11.630	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37904	target_addr:104.21.26.208:443
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:12.864	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52378	target_addr:172.64.147.104:443
time:2026-10-04T23:24:19Z	status:FAILURE	latency:168.354	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:183.019	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:436.999	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:443.859	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:24:19Z	status:HEALTHY	latency:450.463	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:29:19Z	status:UNKNOWN	latency:6.778	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:9.386	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50418	target_addr:172.67.168.140:443
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:10.109	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43758	target_addr:104.21.86.125:443
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:14.230	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36500	target_addr:104.18.40.152:443
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:14.348	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39492	target_addr:172.67.219.211:443
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:220.189	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:457.876	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:463.456	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:29:19Z	status:HEALTHY	latency:471.077	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:29:19Z	status:FAILURE	latency:1592.451	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:11.299	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41448	target_addr:104.18.40.152:443
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:11.972	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35094	target_addr:104.21.86.125:443
time:2026-10-04T23:34:19Z	status:UNKNOWN	latency:12.701	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:14.590	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35420	target_addr:172.67.168.140:443
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:41.860	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35100	target_addr:104.21.86.125:443
time:2026-10-04T23:34:19Z	status:FAILURE	latency:212.080	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:268.691	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:443.316	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:452.839	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:34:19Z	status:HEALTHY	latency:456.487	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:11.909	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51006	target_addr:104.18.40.152:443
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:12.159	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58422	target_addr:172.67.168.140:443
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:27.525	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43770	target_addr:104.21.86.125:443
time:2026-10-04T23:39:19Z	status:UNKNOWN	latency:35.736	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:60.162	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:64.593	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46960	target_addr:172.67.219.211:443
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:72.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:76.800	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:39:19Z	status:HEALTHY	latency:243.644	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:39:19Z	status:FAILURE	latency:616.278	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:44:19Z	status:UNKNOWN	latency:8.239	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:9.353	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37292	target_addr:104.18.40.152:443
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:10.502	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52146	target_addr:172.67.219.211:443
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:11.826	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50378	target_addr:172.67.168.140:443
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:12.274	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52884	target_addr:104.21.86.125:443
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:58.458	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:63.270	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:232.626	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:44:19Z	status:HEALTHY	latency:257.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:44:19Z	status:FAILURE	latency:792.513	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:49:19Z	status:UNKNOWN	latency:6.740	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:9.097	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55182	target_addr:104.21.26.208:443
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:11.366	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55866	target_addr:172.67.219.211:443
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:14.881	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45966	target_addr:172.64.147.104:443
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:17.467	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55874	target_addr:172.67.219.211:443
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:60.176	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:75.841	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:83.583	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:49:19Z	status:FAILURE	latency:222.158	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:49:19Z	status:HEALTHY	latency:453.693	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:54:19Z	status:UNKNOWN	latency:6.863	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:9.524	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52092	target_addr:172.67.219.211:443
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:9.225	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51248	target_addr:104.21.26.208:443
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:13.207	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33084	target_addr:172.64.147.104:443
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:12.841	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46304	target_addr:104.21.86.125:443
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:54.598	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:56.960	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:68.797	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:54:19Z	status:FAILURE	latency:195.390	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:54:19Z	status:HEALTHY	latency:236.618	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:59:19Z	status:UNKNOWN	latency:8.259	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:11.397	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39914	target_addr:104.18.40.152:443
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:11.727	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37448	target_addr:172.67.168.140:443
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:11.286	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45928	target_addr:172.67.219.211:443
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:11.881	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45926	target_addr:172.67.219.211:443
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:59.230	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:68.515	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:72.484	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-04T23:59:19Z	status:FAILURE	latency:186.319	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-04T23:59:19Z	status:HEALTHY	latency:218.833	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:04:19Z	status:UNKNOWN	latency:7.465	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:11.102	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40796	target_addr:172.64.147.104:443
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:11.882	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49066	target_addr:104.21.26.208:443
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:13.183	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44796	target_addr:172.67.219.211:443
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:14.568	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44810	target_addr:172.67.219.211:443
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:56.681	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:58.990	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:71.596	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:04:19Z	status:FAILURE	latency:226.569	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:04:19Z	status:HEALTHY	latency:289.427	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:09:19Z	status:UNKNOWN	latency:6.894	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:9.890	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48952	target_addr:172.67.219.211:443
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:9.633	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41144	target_addr:172.67.168.140:443
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:10.463	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42750	target_addr:104.21.86.125:443
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:12.133	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54948	target_addr:172.64.147.104:443
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:59.640	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:70.125	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:173.575	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:09:19Z	status:FAILURE	latency:197.534	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:09:19Z	status:HEALTHY	latency:253.767	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:9.293	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54498	target_addr:104.21.86.125:443
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:13.473	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57458	target_addr:104.21.26.208:443
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:13.974	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52594	target_addr:172.64.147.104:443
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:15.109	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57060	target_addr:172.67.219.211:443
time:2026-10-05T00:14:19Z	status:FAILURE	latency:28.325	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:58.777	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:14:19Z	status:UNKNOWN	latency:59.945	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:59.721	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:67.706	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:14:19Z	status:HEALTHY	latency:205.693	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:19:19Z	status:UNKNOWN	latency:8.756	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:12.378	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53418	target_addr:104.21.86.125:443
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:12.722	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38288	target_addr:104.21.26.208:443
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:12.336	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40202	target_addr:172.67.219.211:443
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:14.487	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34246	target_addr:104.18.40.152:443
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:56.257	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:67.009	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:73.423	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:19:19Z	status:FAILURE	latency:230.310	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:19:19Z	status:HEALTHY	latency:237.847	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:24:19Z	status:UNKNOWN	latency:5.930	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:9.224	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:49002	target_addr:104.18.40.152:443
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:9.706	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56904	target_addr:172.67.219.211:443
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:10.247	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56916	target_addr:172.67.219.211:443
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:13.814	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53504	target_addr:104.21.26.208:443
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:219.366	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:24:19Z	status:FAILURE	latency:333.093	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:512.770	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:695.897	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:24:19Z	status:HEALTHY	latency:707.880	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:29:19Z	status:UNKNOWN	latency:7.983	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:9.962	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40232	target_addr:104.21.26.208:443
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:12.178	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42072	target_addr:172.67.219.211:443
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:12.690	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42080	target_addr:172.67.219.211:443
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:14.326	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36318	target_addr:172.64.147.104:443
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:61.093	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:62.394	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:63.700	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:29:19Z	status:FAILURE	latency:173.030	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:29:19Z	status:HEALTHY	latency:248.948	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:34:19Z	status:UNKNOWN	latency:10.372	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:11.244	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33212	target_addr:172.67.219.211:443
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:13.629	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33220	target_addr:172.67.219.211:443
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:14.362	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48710	target_addr:104.21.26.208:443
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:19.798	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33860	target_addr:104.18.40.152:443
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:59.891	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:73.017	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:87.280	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:34:19Z	status:FAILURE	latency:208.580	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:34:19Z	status:HEALTHY	latency:289.935	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:10.498	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45090	target_addr:104.21.86.125:443
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:10.966	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57966	target_addr:172.64.147.104:443
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:12.805	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47512	target_addr:172.67.168.140:443
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:12.868	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48512	target_addr:172.67.219.211:443
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:57.218	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:60.487	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:39:19Z	status:UNKNOWN	latency:69.421	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:94.171	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:39:19Z	status:HEALTHY	latency:112.012	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:39:19Z	status:FAILURE	latency:996.211	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:44:19Z	status:UNKNOWN	latency:9.026	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:11.655	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36730	target_addr:172.67.168.140:443
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:12.008	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46896	target_addr:104.21.86.125:443
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:16.540	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46900	target_addr:104.21.86.125:443
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:17.314	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34348	target_addr:172.64.147.104:443
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:55.664	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:66.183	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:44:19Z	status:FAILURE	latency:213.396	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:215.217	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:44:19Z	status:HEALTHY	latency:998.813	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:49:19Z	status:UNKNOWN	latency:11.908	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:16.413	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42246	target_addr:172.67.219.211:443
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:16.320	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:32820	target_addr:104.21.26.208:443
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:16.239	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57770	target_addr:104.21.86.125:443
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:17.622	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58598	target_addr:172.64.147.104:443
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:61.902	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:65.824	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:94.356	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:49:19Z	status:HEALTHY	latency:220.884	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:49:19Z	status:FAILURE	latency:333.367	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:9.155	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47222	target_addr:172.64.147.104:443
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:9.890	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35412	target_addr:104.21.26.208:443
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:10.991	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40228	target_addr:104.21.86.125:443
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:13.742	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43330	target_addr:172.67.219.211:443
time:2026-10-05T00:54:19Z	status:UNKNOWN	latency:35.828	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:57.914	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:64.795	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:66.828	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:54:19Z	status:HEALTHY	latency:220.453	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:54:19Z	status:FAILURE	latency:246.345	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:59:19Z	status:UNKNOWN	latency:8.863	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:14.412	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55388	target_addr:104.18.40.152:443
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:14.200	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60056	target_addr:104.21.86.125:443
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:14.512	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55254	target_addr:172.67.168.140:443
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:14.131	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60058	target_addr:104.21.86.125:443
time:2026-10-05T00:59:19Z	status:FAILURE	latency:23.952	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:62.783	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:62.879	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:70.413	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T00:59:19Z	status:HEALTHY	latency:245.469	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:9.257	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47540	target_addr:172.64.147.104:443
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:10.970	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39974	target_addr:172.67.219.211:443
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:11.241	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48548	target_addr:104.21.86.125:443
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:12.762	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:34444	target_addr:104.21.26.208:443
time:2026-10-05T01:04:19Z	status:UNKNOWN	latency:57.133	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:57.061	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:68.439	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:81.782	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:04:19Z	status:FAILURE	latency:206.748	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:04:19Z	status:HEALTHY	latency:242.367	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:09:19Z	status:UNKNOWN	latency:6.994	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:9.854	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40428	target_addr:104.21.86.125:443
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:11.333	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60044	target_addr:104.18.40.152:443
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:12.752	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:60238	target_addr:104.21.26.208:443
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:13.744	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40434	target_addr:104.21.86.125:443
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:54.196	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:67.092	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:87.243	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:09:19Z	status:FAILURE	latency:176.247	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:09:19Z	status:HEALTHY	latency:217.535	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:14:19Z	status:UNKNOWN	latency:9.918	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:11.969	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45984	target_addr:172.67.168.140:443
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:18.000	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47734	target_addr:104.21.86.125:443
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:18.333	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54910	target_addr:104.18.40.152:443
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:20.861	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47748	target_addr:104.21.86.125:443
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:71.855	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:72.133	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:72.168	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:14:19Z	status:FAILURE	latency:210.843	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:14:19Z	status:HEALTHY	latency:259.103	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:19:19Z	status:UNKNOWN	latency:7.058	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:11.448	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53456	target_addr:172.67.168.140:443
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:18.173	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32986	target_addr:104.18.40.152:443
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:28.272	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38974	target_addr:104.21.86.125:443
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:28.244	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48294	target_addr:172.67.219.211:443
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:59.963	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:68.416	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:90.632	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:19:19Z	status:FAILURE	latency:197.756	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:19:19Z	status:HEALTHY	latency:217.110	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:24:19Z	status:UNKNOWN	latency:6.392	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:10.223	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53382	target_addr:172.64.147.104:443
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:13.114	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:40944	target_addr:172.67.168.140:443
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:37.319	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36742	target_addr:104.21.86.125:443
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:42.002	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50126	target_addr:172.67.219.211:443
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:54.125	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:69.074	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:87.355	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:24:19Z	status:FAILURE	latency:198.187	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:24:19Z	status:HEALTHY	latency:217.720	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:29:19Z	status:UNKNOWN	latency:12.264	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:12.318	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40232	target_addr:172.64.147.104:443
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:12.217	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43672	target_addr:104.21.86.125:443
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:11.799	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43684	target_addr:104.21.86.125:443
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:55.127	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52930	target_addr:172.67.168.140:443
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:61.731	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:66.385	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:67.790	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:29:19Z	status:FAILURE	latency:231.516	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:29:19Z	status:HEALTHY	latency:234.657	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:34:19Z	status:UNKNOWN	latency:8.586	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:11.005	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58966	target_addr:104.21.26.208:443
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:11.640	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:39004	target_addr:172.64.147.104:443
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:19.036	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37208	target_addr:172.67.219.211:443
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:27.373	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38472	target_addr:104.21.86.125:443
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:61.225	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:67.660	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:86.642	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:34:19Z	status:FAILURE	latency:216.438	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:34:19Z	status:HEALTHY	latency:234.648	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:8.975	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53494	target_addr:104.21.86.125:443
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:10.535	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52170	target_addr:172.64.147.104:443
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:16.004	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59990	target_addr:172.67.219.211:443
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:16.116	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46034	target_addr:172.67.168.140:443
time:2026-10-05T01:39:19Z	status:UNKNOWN	latency:38.094	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:57.608	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:63.445	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:78.290	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:39:19Z	status:FAILURE	latency:217.512	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:39:19Z	status:HEALTHY	latency:230.347	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:44:19Z	status:UNKNOWN	latency:9.664	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:14.553	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42132	target_addr:104.21.86.125:443
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:14.804	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42124	target_addr:104.21.86.125:443
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:16.408	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57846	target_addr:104.18.40.152:443
time:2026-10-05T01:44:19Z	status:FAILURE	latency:27.697	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:57.405	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54966	target_addr:104.21.26.208:443
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:58.732	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:60.704	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:74.288	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:44:19Z	status:HEALTHY	latency:261.029	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:49:19Z	status:UNKNOWN	latency:11.122	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:11.209	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58068	target_addr:104.21.26.208:443
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:11.150	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41202	target_addr:104.21.86.125:443
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:11.374	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56654	target_addr:104.18.40.152:443
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:13.431	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57490	target_addr:172.67.219.211:443
time:2026-10-05T01:49:19Z	status:FAILURE	latency:54.451	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:58.050	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:57.907	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:69.034	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:49:19Z	status:HEALTHY	latency:236.414	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:12.465	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57138	target_addr:172.64.147.104:443
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:15.667	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56298	target_addr:172.67.219.211:443
time:2026-10-05T01:54:19Z	status:UNKNOWN	latency:16.195	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:20.907	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41510	target_addr:172.67.168.140:443
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:21.095	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56310	target_addr:172.67.219.211:443
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:63.159	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:77.697	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:80.340	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:54:19Z	status:FAILURE	latency:228.550	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:54:19Z	status:HEALTHY	latency:468.546	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:59:19Z	status:UNKNOWN	latency:7.330	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:10.437	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58764	target_addr:172.67.219.211:443
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:10.918	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44890	target_addr:172.67.168.140:443
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:11.543	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58768	target_addr:172.67.219.211:443
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:12.266	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48536	target_addr:172.64.147.104:443
time:2026-10-05T01:59:19Z	status:FAILURE	latency:27.819	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:55.619	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:58.209	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:60.786	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T01:59:19Z	status:HEALTHY	latency:261.271	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:11.318	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36692	target_addr:172.67.219.211:443
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:11.236	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36706	target_addr:172.67.219.211:443
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:12.196	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42276	target_addr:104.21.26.208:443
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:22.077	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51644	target_addr:104.18.40.152:443
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:55.816	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:63.433	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:67.710	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:04:19Z	status:UNKNOWN	latency:74.664	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:04:19Z	status:HEALTHY	latency:235.433	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:04:19Z	status:FAILURE	latency:623.604	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:09:19Z	status:UNKNOWN	latency:8.020	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:9.519	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47036	target_addr:104.21.86.125:443
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:10.161	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47216	target_addr:104.18.40.152:443
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:14.214	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47046	target_addr:172.67.168.140:443
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:14.432	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47040	target_addr:104.21.86.125:443
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:59.574	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:59.977	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:74.952	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:09:19Z	status:FAILURE	latency:216.743	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:09:19Z	status:HEALTHY	latency:235.024	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:14:20Z	status:UNKNOWN	latency:10.131	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:11.543	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43088	target_addr:104.21.86.125:443
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:12.223	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33448	target_addr:172.67.219.211:443
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:14.414	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57474	target_addr:104.18.40.152:443
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:15.519	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53242	target_addr:172.67.168.140:443
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:67.197	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:66.522	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:159.796	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:14:20Z	status:FAILURE	latency:226.474	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:14:20Z	status:HEALTHY	latency:362.417	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:19:20Z	status:UNKNOWN	latency:10.127	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:13.725	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33692	target_addr:104.18.40.152:443
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:13.423	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36044	target_addr:172.67.219.211:443
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:14.116	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51404	target_addr:172.67.168.140:443
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:17.844	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36054	target_addr:172.67.219.211:443
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:60.277	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:60.541	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:69.371	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:19:20Z	status:FAILURE	latency:206.543	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:19:20Z	status:HEALTHY	latency:440.703	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:24:20Z	status:UNKNOWN	latency:10.847	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:11.531	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46112	target_addr:104.21.86.125:443
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:13.747	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46122	target_addr:104.21.86.125:443
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:22.474	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46032	target_addr:172.64.147.104:443
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:53.635	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:60.570	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:67.885	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:24:20Z	status:FAILURE	latency:186.767	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:248.088	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:24:20Z	status:HEALTHY	latency:479.833	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37854	target_addr:104.21.26.208:443
time:2026-10-05T02:29:20Z	status:UNKNOWN	latency:11.105	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:14.168	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47222	target_addr:172.67.168.140:443
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:14.106	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51462	target_addr:104.21.86.125:443
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:14.379	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51468	target_addr:104.21.86.125:443
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:34.001	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56732	target_addr:172.64.147.104:443
time:2026-10-05T02:29:20Z	status:FAILURE	latency:34.718	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:61.622	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:72.064	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:81.080	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:29:20Z	status:HEALTHY	latency:216.304	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:34:20Z	status:UNKNOWN	latency:7.296	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:9.074	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57906	target_addr:172.67.219.211:443
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:10.023	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:42192	target_addr:172.64.147.104:443
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:19.492	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54994	target_addr:104.21.26.208:443
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:19.542	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:50252	target_addr:104.21.86.125:443
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:55.755	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:56.380	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:66.522	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:34:20Z	status:FAILURE	latency:215.779	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:34:20Z	status:HEALTHY	latency:245.184	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:39:20Z	status:UNKNOWN	latency:8.103	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:9.712	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33952	target_addr:172.67.219.211:443
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:10.641	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33956	target_addr:172.67.219.211:443
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:15.960	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43690	target_addr:104.18.40.152:443
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:59.779	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:67.539	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:77.567	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:39:20Z	status:FAILURE	latency:188.978	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:218.421	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:39:20Z	status:HEALTHY	latency:912.433	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47792	target_addr:172.67.168.140:443
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:9.651	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56796	target_addr:104.18.40.152:443
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:10.447	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44020	target_addr:172.67.219.211:443
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:11.211	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39326	target_addr:104.21.26.208:443
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:10.899	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44030	target_addr:172.67.219.211:443
time:2026-10-05T02:44:20Z	status:UNKNOWN	latency:21.529	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:81.620	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:82.327	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:87.452	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:44:20Z	status:HEALTHY	latency:244.100	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:44:20Z	status:FAILURE	latency:343.904	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:49:20Z	status:UNKNOWN	latency:7.207	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:10.344	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44334	target_addr:104.21.86.125:443
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:11.196	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47150	target_addr:172.67.219.211:443
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:19.316	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56638	target_addr:104.18.40.152:443
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:60.298	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:62.849	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:49:20Z	status:FAILURE	latency:201.285	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:258.690	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:267.822	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:49:20Z	status:HEALTHY	latency:853.148	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56314	target_addr:172.67.168.140:443
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:12.358	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48014	target_addr:172.67.219.211:443
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:12.696	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47148	target_addr:172.67.168.140:443
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:12.911	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56992	target_addr:172.64.147.104:443
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:18.244	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40090	target_addr:104.21.86.125:443
time:2026-10-05T02:54:20Z	status:UNKNOWN	latency:37.385	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:54:20Z	status:FAILURE	latency:38.848	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:57.540	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:58.091	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:111.496	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:54:20Z	status:HEALTHY	latency:345.712	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:59:20Z	status:UNKNOWN	latency:6.832	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:10.199	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49316	target_addr:172.67.219.211:443
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:11.138	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57320	target_addr:172.64.147.104:443
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:11.308	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49332	target_addr:172.67.219.211:443
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:41.588	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44136	target_addr:104.21.26.208:443
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:60.184	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:65.173	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:59:20Z	status:FAILURE	latency:172.735	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:250.046	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T02:59:20Z	status:HEALTHY	latency:365.378	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:04:20Z	status:UNKNOWN	latency:7.724	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:11.656	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60996	target_addr:172.64.147.104:443
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:11.077	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42734	target_addr:172.67.219.211:443
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:11.343	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42750	target_addr:172.67.219.211:443
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:15.119	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53714	target_addr:172.67.168.140:443
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:63.162	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:63.653	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:74.468	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:04:20Z	status:FAILURE	latency:229.154	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:04:20Z	status:HEALTHY	latency:242.757	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:09:20Z	status:UNKNOWN	latency:6.827	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:9.813	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54560	target_addr:172.67.168.140:443
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:10.409	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44132	target_addr:104.21.86.125:443
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:10.619	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44138	target_addr:104.21.86.125:443
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:11.143	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35204	target_addr:104.18.40.152:443
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:54.684	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:55.255	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:56.512	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:09:20Z	status:FAILURE	latency:259.637	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:09:20Z	status:HEALTHY	latency:281.810	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:10.654	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45878	target_addr:172.67.168.140:443
time:2026-10-05T03:14:20Z	status:UNKNOWN	latency:11.226	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:12.358	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54638	target_addr:104.21.86.125:443
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:12.708	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56364	target_addr:104.18.40.152:443
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:16.617	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35022	target_addr:172.67.219.211:443
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:67.242	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:67.376	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:103.260	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:14:20Z	status:FAILURE	latency:229.709	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:14:20Z	status:HEALTHY	latency:377.996	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:10.051	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35506	target_addr:172.67.168.140:443
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:10.838	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48622	target_addr:172.67.219.211:443
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:12.339	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44894	target_addr:104.18.40.152:443
time:2026-10-05T03:19:20Z	status:UNKNOWN	latency:20.288	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:28.431	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48634	target_addr:172.67.219.211:443
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:54.999	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:57.393	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:81.280	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:19:20Z	status:FAILURE	latency:180.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:19:20Z	status:HEALTHY	latency:210.106	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:11.370	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53626	target_addr:104.21.26.208:443
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:11.893	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:46372	target_addr:104.18.40.152:443
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:11.523	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51648	target_addr:104.21.86.125:443
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:11.636	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51664	target_addr:104.21.86.125:443
time:2026-10-05T03:24:20Z	status:UNKNOWN	latency:32.863	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:57.081	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:63.077	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:69.394	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:24:20Z	status:HEALTHY	latency:243.666	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:24:20Z	status:FAILURE	latency:309.655	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:29:20Z	status:UNKNOWN	latency:8.047	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:11.014	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60506	target_addr:172.67.219.211:443
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:12.188	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59774	target_addr:104.21.86.125:443
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:14.194	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51504	target_addr:104.21.26.208:443
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:22.782	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:32982	target_addr:104.18.40.152:443
time:2026-10-05T03:29:20Z	status:FAILURE	latency:25.492	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:64.191	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:69.607	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:81.929	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:29:20Z	status:HEALTHY	latency:226.652	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:12.089	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:37112	target_addr:172.67.168.140:443
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:12.168	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55666	target_addr:172.67.219.211:443
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:12.361	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41778	target_addr:172.64.147.104:443
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:12.482	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55672	target_addr:172.67.219.211:443
time:2026-10-05T03:34:20Z	status:UNKNOWN	latency:57.472	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:66.815	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:71.994	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:176.566	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:34:20Z	status:FAILURE	latency:223.797	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:34:20Z	status:HEALTHY	latency:224.717	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:39:20Z	status:UNKNOWN	latency:8.885	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:9.219	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54904	target_addr:104.18.40.152:443
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:12.286	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37558	target_addr:104.21.86.125:443
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:13.578	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33370	target_addr:172.67.219.211:443
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:55.321	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51954	target_addr:172.67.168.140:443
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:55.828	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:56.424	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:95.473	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:39:20Z	status:FAILURE	latency:199.533	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:39:20Z	status:HEALTHY	latency:286.477	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:44:20Z	status:UNKNOWN	latency:5.581	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:9.664	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:48696	target_addr:104.18.40.152:443
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:9.365	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:42116	target_addr:104.21.86.125:443
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:10.377	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53940	target_addr:172.67.168.140:443
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:19.496	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34370	target_addr:172.67.219.211:443
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:57.951	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:83.621	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:44:20Z	status:FAILURE	latency:153.352	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:458.071	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:44:20Z	status:HEALTHY	latency:679.762	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:7.941	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43754	target_addr:172.64.147.104:443
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:9.702	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55538	target_addr:104.21.26.208:443
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:10.222	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41922	target_addr:172.67.219.211:443
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:10.865	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41934	target_addr:172.67.219.211:443
time:2026-10-05T03:49:20Z	status:UNKNOWN	latency:33.262	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:58.729	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:64.021	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:97.526	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:49:20Z	status:FAILURE	latency:198.245	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:49:20Z	status:HEALTHY	latency:249.352	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:8.885	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56292	target_addr:172.67.168.140:443
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:10.786	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52452	target_addr:172.64.147.104:443
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:11.184	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51392	target_addr:172.67.219.211:443
time:2026-10-05T03:54:20Z	status:FAILURE	latency:25.018	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:54:20Z	status:UNKNOWN	latency:28.464	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:32.140	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51406	target_addr:172.67.219.211:443
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:54.674	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:56.722	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:66.471	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:54:20Z	status:HEALTHY	latency:242.682	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:9.677	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43570	target_addr:104.18.40.152:443
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:9.307	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46666	target_addr:104.21.86.125:443
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:10.635	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49450	target_addr:172.67.168.140:443
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:11.386	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38870	target_addr:172.67.219.211:443
time:2026-10-05T03:59:20Z	status:UNKNOWN	latency:39.115	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:53.039	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:63.058	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:63.105	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T03:59:20Z	status:FAILURE	latency:223.695	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T03:59:20Z	status:HEALTHY	latency:241.813	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:10.959	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43242	target_addr:104.21.26.208:443
time:2026-10-05T04:04:20Z	status:UNKNOWN	latency:11.517	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:12.361	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:59880	target_addr:104.18.40.152:443
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:13.340	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49018	target_addr:104.21.86.125:443
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:13.752	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49028	target_addr:104.21.86.125:443
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:60.953	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:67.586	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:68.150	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:04:20Z	status:FAILURE	latency:213.397	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:04:20Z	status:HEALTHY	latency:273.615	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:09:20Z	status:UNKNOWN	latency:7.140	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:10.490	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54054	target_addr:172.64.147.104:443
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:10.476	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33052	target_addr:172.67.219.211:443
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:11.703	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33068	target_addr:172.67.219.211:443
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:15.385	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45856	target_addr:104.21.26.208:443
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:53.128	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:57.101	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:64.804	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:09:20Z	status:FAILURE	latency:216.917	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:09:20Z	status:HEALTHY	latency:292.709	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:14:20Z	status:UNKNOWN	latency:7.397	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:9.811	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44356	target_addr:172.67.168.140:443
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:9.744	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51750	target_addr:104.21.86.125:443
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:11.113	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54318	target_addr:104.18.40.152:443
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:21.652	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:51694	target_addr:172.67.219.211:443
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:63.303	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:83.100	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:113.621	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:14:20Z	status:HEALTHY	latency:272.390	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:14:20Z	status:FAILURE	latency:532.933	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:9.474	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39412	target_addr:172.67.168.140:443
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:10.360	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34334	target_addr:104.21.86.125:443
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:10.462	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56078	target_addr:172.67.219.211:443
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:11.132	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:35276	target_addr:104.18.40.152:443
time:2026-10-05T04:19:20Z	status:UNKNOWN	latency:34.160	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:65.236	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:78.597	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:93.332	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:19:20Z	status:HEALTHY	latency:228.358	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:19:20Z	status:FAILURE	latency:248.943	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:10.922	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57864	target_addr:172.64.147.104:443
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:11.906	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34848	target_addr:104.21.86.125:443
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:11.736	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45924	target_addr:104.21.26.208:443
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:13.166	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43156	target_addr:172.67.219.211:443
time:2026-10-05T04:24:20Z	status:FAILURE	latency:22.536	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:24:20Z	status:UNKNOWN	latency:33.612	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:54.792	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:60.271	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:73.613	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:24:20Z	status:HEALTHY	latency:247.315	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:29:20Z	status:UNKNOWN	latency:9.086	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:10.069	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44656	target_addr:172.67.219.211:443
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:11.902	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41190	target_addr:172.67.168.140:443
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:14.327	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44672	target_addr:172.67.219.211:443
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:47.942	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41920	target_addr:172.64.147.104:443
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:57.786	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:60.733	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:65.803	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:29:20Z	status:FAILURE	latency:216.996	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:29:20Z	status:HEALTHY	latency:217.900	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:34:20Z	status:UNKNOWN	latency:8.621	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:11.916	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40280	target_addr:172.64.147.104:443
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:11.649	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34864	target_addr:172.67.219.211:443
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:12.397	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52236	target_addr:104.21.26.208:443
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:12.976	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34878	target_addr:172.67.219.211:443
time:2026-10-05T04:34:20Z	status:FAILURE	latency:28.520	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:76.148	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:82.620	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:244.190	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:34:20Z	status:HEALTHY	latency:327.295	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:39:20Z	status:UNKNOWN	latency:7.505	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:11.633	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:43036	target_addr:172.67.168.140:443
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:11.053	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35182	target_addr:104.21.86.125:443
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:13.230	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44376	target_addr:104.18.40.152:443
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:13.752	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52008	target_addr:172.67.219.211:443
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:52.726	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:54.016	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:60.940	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:39:20Z	status:FAILURE	latency:189.564	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:39:20Z	status:HEALTHY	latency:251.876	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:44:20Z	status:UNKNOWN	latency:10.277	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:16.107	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39462	target_addr:172.67.168.140:443
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:16.065	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36218	target_addr:172.67.219.211:443
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:16.570	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36432	target_addr:104.18.40.152:443
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:19.063	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36224	target_addr:172.67.219.211:443
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:66.878	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:68.785	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:70.943	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:44:20Z	status:FAILURE	latency:211.795	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:44:20Z	status:HEALTHY	latency:267.622	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:49:20Z	status:UNKNOWN	latency:6.755	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:9.052	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54930	target_addr:172.64.147.104:443
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:13.314	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53998	target_addr:104.21.26.208:443
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:15.723	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46730	target_addr:172.67.219.211:443
time:2026-10-05T04:49:20Z	status:FAILURE	latency:24.510	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:55.925	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:61.407	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:46744	target_addr:172.67.219.211:443
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:80.446	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:92.123	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:49:20Z	status:HEALTHY	latency:260.714	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:54:20Z	status:UNKNOWN	latency:7.013	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:11.189	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:44418	target_addr:104.18.40.152:443
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:10.888	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35504	target_addr:172.67.219.211:443
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:12.115	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:45378	target_addr:104.21.26.208:443
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:12.308	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35520	target_addr:172.67.219.211:443
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:59.075	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:60.640	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:76.189	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:54:20Z	status:HEALTHY	latency:220.754	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:54:20Z	status:FAILURE	latency:296.875	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:57:15Z	status:FAILURE	latency:0.000	target:ayd:endpoint:status.html	message:write tcp 172.17.0.2:9000->172.17.0.1:48318: write: broken pipe
time:2026-10-05T04:59:20Z	status:UNKNOWN	latency:7.145	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:10.474	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46026	target_addr:104.21.26.208:443
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:10.924	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43436	target_addr:104.18.40.152:443
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:22.418	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48636	target_addr:104.21.86.125:443
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:59.185	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:64.943	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:59:20Z	status:FAILURE	latency:219.940	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:261.003	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:292.196	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T04:59:20Z	status:HEALTHY	latency:1015.731	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:48648	target_addr:104.21.86.125:443
time:2026-10-05T05:04:20Z	status:UNKNOWN	latency:7.953	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:13.144	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:59622	target_addr:104.21.26.208:443
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:12.848	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55626	target_addr:172.67.219.211:443
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:12.840	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45192	target_addr:104.21.86.125:443
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:13.307	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:45872	target_addr:172.64.147.104:443
time:2026-10-05T05:04:20Z	status:FAILURE	latency:31.010	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:67.792	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:68.315	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:68.098	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:04:20Z	status:HEALTHY	latency:227.815	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:09:20Z	status:UNKNOWN	latency:6.967	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:10.071	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40836	target_addr:104.18.40.152:443
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:10.552	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60044	target_addr:104.21.86.125:443
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:13.234	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49826	target_addr:104.21.26.208:443
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:21.144	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34866	target_addr:172.67.219.211:443
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:54.915	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:56.866	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:57.863	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:09:20Z	status:HEALTHY	latency:200.373	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:09:20Z	status:FAILURE	latency:1585.651	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:8.180	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37142	target_addr:104.21.86.125:443
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:12.317	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38424	target_addr:172.67.168.140:443
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:12.579	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57058	target_addr:104.18.40.152:443
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:32.200	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59480	target_addr:172.67.219.211:443
time:2026-10-05T05:14:20Z	status:UNKNOWN	latency:35.128	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:58.404	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:64.980	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:66.254	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:14:20Z	status:FAILURE	latency:240.321	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:14:20Z	status:HEALTHY	latency:256.291	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:9.254	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:56084	target_addr:104.21.26.208:443
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:10.234	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38496	target_addr:104.21.86.125:443
time:2026-10-05T05:19:20Z	status:UNKNOWN	latency:10.719	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:11.201	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36548	target_addr:172.67.219.211:443
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:12.866	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50428	target_addr:172.64.147.104:443
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:59.530	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:71.339	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:224.432	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:19:20Z	status:FAILURE	latency:227.227	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:19:20Z	status:HEALTHY	latency:246.520	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:24:20Z	status:UNKNOWN	latency:7.748	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:9.771	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:36372	target_addr:104.18.40.152:443
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:10.808	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57048	target_addr:104.21.86.125:443
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:11.181	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:33524	target_addr:104.21.26.208:443
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:13.154	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49940	target_addr:172.67.219.211:443
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:60.076	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:70.010	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:202.887	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:24:20Z	status:FAILURE	latency:227.391	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:24:20Z	status:HEALTHY	latency:446.272	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:29:20Z	status:UNKNOWN	latency:8.710	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:10.006	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57666	target_addr:104.21.86.125:443
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:11.161	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47434	target_addr:104.18.40.152:443
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:11.485	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42344	target_addr:104.21.26.208:443
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:12.816	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55226	target_addr:172.67.219.211:443
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:57.526	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:61.338	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:109.305	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:29:20Z	status:HEALTHY	latency:291.218	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:29:20Z	status:FAILURE	latency:3496.526	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:10.499	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47858	target_addr:104.21.86.125:443
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:18.102	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47864	target_addr:104.21.86.125:443
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:19.663	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54856	target_addr:104.21.26.208:443
time:2026-10-05T05:34:20Z	status:UNKNOWN	latency:22.105	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:33.401	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38716	target_addr:172.64.147.104:443
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:55.707	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:60.105	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:96.835	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:34:20Z	status:FAILURE	latency:202.373	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:34:20Z	status:HEALTHY	latency:213.006	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:39:20Z	status:UNKNOWN	latency:9.368	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:12.917	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35880	target_addr:172.67.219.211:443
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:12.704	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41626	target_addr:172.67.168.140:443
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:12.650	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:35840	target_addr:104.21.86.125:443
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:13.094	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51402	target_addr:172.64.147.104:443
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:62.562	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:71.725	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:39:20Z	status:FAILURE	latency:212.600	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:243.910	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:39:20Z	status:HEALTHY	latency:409.754	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:10.516	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41860	target_addr:104.21.86.125:443
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:11.592	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:37832	target_addr:172.67.219.211:443
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:11.980	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:55460	target_addr:172.67.168.140:443
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:13.890	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:53066	target_addr:172.64.147.104:443
time:2026-10-05T05:44:20Z	status:FAILURE	latency:35.517	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:53.776	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:44:20Z	status:UNKNOWN	latency:55.506	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:102.424	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:244.295	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:44:20Z	status:HEALTHY	latency:966.081	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:49:20Z	status:UNKNOWN	latency:8.050	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:9.449	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38716	target_addr:172.67.219.211:443
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:10.300	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:52828	target_addr:172.64.147.104:443
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:10.695	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38732	target_addr:172.67.219.211:443
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:12.327	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:44116	target_addr:104.21.26.208:443
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:52.955	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:57.851	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:59.444	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:49:20Z	status:FAILURE	latency:146.625	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:49:20Z	status:HEALTHY	latency:196.756	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:54:20Z	status:UNKNOWN	latency:7.023	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:10.874	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:33176	target_addr:172.67.219.211:443
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:11.123	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:54568	target_addr:104.21.26.208:443
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:11.415	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55766	target_addr:104.21.86.125:443
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:12.003	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41850	target_addr:172.64.147.104:443
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:54.216	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:62.005	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:67.564	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:54:20Z	status:FAILURE	latency:238.500	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T05:54:20Z	status:HEALTHY	latency:246.933	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:59:20Z	status:UNKNOWN	latency:7.279	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:8.694	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59126	target_addr:172.67.219.211:443
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:10.536	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:41714	target_addr:172.64.147.104:443
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:11.291	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48672	target_addr:172.67.168.140:443
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:26.110	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:59132	target_addr:172.67.219.211:443
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:59.537	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:60.983	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:87.394	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:59:20Z	status:HEALTHY	latency:270.622	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T05:59:20Z	status:FAILURE	latency:758.317	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:04:20Z	status:UNKNOWN	latency:7.383	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:9.910	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40876	target_addr:172.64.147.104:443
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:9.748	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54844	target_addr:172.67.219.211:443
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:10.212	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58460	target_addr:104.21.26.208:443
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:19.826	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54850	target_addr:172.67.219.211:443
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:51.090	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:58.685	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:60.073	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:04:20Z	status:FAILURE	latency:236.717	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:04:20Z	status:HEALTHY	latency:250.393	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:09:20Z	status:UNKNOWN	latency:7.387	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:9.309	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47392	target_addr:104.18.40.152:443
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:10.083	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39120	target_addr:172.67.168.140:443
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:10.555	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39466	target_addr:172.67.219.211:443
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:12.661	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:39482	target_addr:172.67.219.211:443
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:57.182	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:58.077	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:62.353	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:09:20Z	status:HEALTHY	latency:169.727	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:09:20Z	status:FAILURE	latency:176.659	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:8.905	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:35354	target_addr:104.21.26.208:443
time:2026-10-05T06:14:20Z	status:UNKNOWN	latency:10.255	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:10.827	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43354	target_addr:172.64.147.104:443
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:11.527	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55378	target_addr:172.67.219.211:443
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:11.514	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55292	target_addr:104.21.86.125:443
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:59.094	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:59.461	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:74.336	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:14:20Z	status:HEALTHY	latency:216.602	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:14:20Z	status:FAILURE	latency:234.614	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:19:20Z	status:UNKNOWN	latency:8.732	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:8.989	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49078	target_addr:172.67.219.211:443
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:9.663	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51236	target_addr:104.21.26.208:443
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:9.439	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60456	target_addr:104.21.86.125:443
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:10.915	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:58256	target_addr:172.64.147.104:443
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:56.519	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:57.713	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:142.442	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:19:20Z	status:HEALTHY	latency:279.374	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:19:20Z	status:FAILURE	latency:806.162	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:24:20Z	status:UNKNOWN	latency:6.805	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:10.038	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:36058	target_addr:172.67.168.140:443
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:11.719	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50882	target_addr:104.18.40.152:443
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:12.020	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34044	target_addr:172.67.219.211:443
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:25.515	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36244	target_addr:104.21.86.125:443
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:54.139	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:69.759	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:90.847	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:24:20Z	status:HEALTHY	latency:187.732	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:24:20Z	status:FAILURE	latency:220.007	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:29:20Z	status:UNKNOWN	latency:6.504	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:9.448	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56188	target_addr:172.67.219.211:443
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:10.570	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:41086	target_addr:172.67.168.140:443
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:12.337	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:47992	target_addr:172.64.147.104:443
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:12.370	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:56194	target_addr:172.67.219.211:443
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:62.125	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:62.313	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:29:20Z	status:FAILURE	latency:218.498	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:280.509	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:29:20Z	status:HEALTHY	latency:1128.858	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:9.122	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:39540	target_addr:104.21.26.208:443
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:11.165	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45934	target_addr:104.21.86.125:443
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:56.825	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:58.006	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:34:20Z	status:UNKNOWN	latency:67.923	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:68.947	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45928	target_addr:104.21.86.125:443
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:72.376	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:50952	target_addr:172.64.147.104:443
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:126.230	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:34:20Z	status:HEALTHY	latency:208.031	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:34:20Z	status:FAILURE	latency:355.151	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:39:20Z	status:UNKNOWN	latency:9.882	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:14.395	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43212	target_addr:172.67.219.211:443
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:14.126	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43224	target_addr:172.67.219.211:443
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:16.649	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51102	target_addr:104.18.40.152:443
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:72.853	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:75.822	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:91.954	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:125.269	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:47678	target_addr:172.67.168.140:443
time:2026-10-05T06:39:20Z	status:HEALTHY	latency:215.541	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:39:20Z	status:FAILURE	latency:223.454	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:44:20Z	status:UNKNOWN	latency:8.456	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:10.597	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:58120	target_addr:172.67.219.211:443
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:10.585	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:46128	target_addr:104.21.26.208:443
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:11.980	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:40306	target_addr:104.18.40.152:443
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:12.237	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:43646	target_addr:104.21.86.125:443
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:57.926	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:59.830	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:235.946	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:44:20Z	status:HEALTHY	latency:993.369	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:44:20Z	status:FAILURE	latency:1134.450	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:49:20Z	status:UNKNOWN	latency:8.048	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:8.974	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52972	target_addr:104.21.26.208:443
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:9.648	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57396	target_addr:104.18.40.152:443
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:10.214	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55196	target_addr:172.67.219.211:443
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:10.021	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:49340	target_addr:104.21.86.125:443
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:53.998	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:55.853	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:59.045	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:49:20Z	status:FAILURE	latency:203.657	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:49:20Z	status:HEALTHY	latency:242.060	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:54:20Z	status:UNKNOWN	latency:8.221	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:11.240	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47234	target_addr:104.21.86.125:443
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:20.369	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:47240	target_addr:104.21.86.125:443
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:43.171	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:43566	target_addr:172.64.147.104:443
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:46.365	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:52554	target_addr:104.21.26.208:443
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:55.592	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:55.325	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:83.053	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:54:20Z	status:FAILURE	latency:179.044	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:54:20Z	status:HEALTHY	latency:229.532	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:59:20Z	status:UNKNOWN	latency:8.616	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:12.376	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:57578	target_addr:104.21.26.208:443
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:11.957	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52710	target_addr:172.67.219.211:443
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:12.435	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:57140	target_addr:104.21.86.125:443
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:13.478	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37324	target_addr:104.18.40.152:443
time:2026-10-05T06:59:20Z	status:FAILURE	latency:31.787	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:55.006	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:63.135	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:64.250	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T06:59:20Z	status:HEALTHY	latency:303.372	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:04:20Z	status:UNKNOWN	latency:8.221	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:9.694	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:38288	target_addr:104.18.40.152:443
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:10.501	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53384	target_addr:172.67.168.140:443
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:10.785	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34130	target_addr:104.21.86.125:443
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:11.331	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55214	target_addr:172.67.219.211:443
time:2026-10-05T07:04:20Z	status:FAILURE	latency:23.981	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:58.086	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:60.052	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:66.550	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:04:20Z	status:HEALTHY	latency:242.788	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:9.239	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51872	target_addr:104.21.26.208:443
time:2026-10-05T07:09:20Z	status:UNKNOWN	latency:9.429	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:10.154	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38928	target_addr:172.67.219.211:443
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:11.002	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51628	target_addr:104.18.40.152:443
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:11.116	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:38930	target_addr:172.67.219.211:443
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:57.068	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:57.658	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:68.126	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:09:20Z	status:FAILURE	latency:224.068	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:09:20Z	status:HEALTHY	latency:238.856	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:14:21Z	status:UNKNOWN	latency:10.252	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:13.280	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:37832	target_addr:104.18.40.152:443
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:13.192	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44542	target_addr:172.67.219.211:443
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:13.368	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:48270	target_addr:172.67.168.140:443
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:16.533	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45132	target_addr:104.21.86.125:443
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:55.427	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:57.034	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:103.463	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:14:21Z	status:HEALTHY	latency:214.049	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:14:21Z	status:FAILURE	latency:224.898	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:19:21Z	status:UNKNOWN	latency:11.438	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:14.776	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:56218	target_addr:104.18.40.152:443
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:14.730	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:41606	target_addr:172.67.219.211:443
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:14.724	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49768	target_addr:172.67.168.140:443
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:23.911	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:34280	target_addr:104.21.86.125:443
time:2026-10-05T07:19:21Z	status:FAILURE	latency:40.900	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:62.197	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:62.850	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:62.945	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:19:21Z	status:HEALTHY	latency:231.153	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:24:21Z	status:UNKNOWN	latency:7.876	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:10.077	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52480	target_addr:104.21.86.125:443
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:10.166	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:38596	target_addr:172.67.168.140:443
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:10.735	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:34762	target_addr:172.64.147.104:443
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:10.715	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:52492	target_addr:104.21.86.125:443
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:52.756	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:53.984	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:54.871	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:24:21Z	status:HEALTHY	latency:206.150	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:24:21Z	status:FAILURE	latency:229.903	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:29:21Z	status:UNKNOWN	latency:7.743	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:9.475	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55766	target_addr:104.21.86.125:443
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:10.074	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:42776	target_addr:104.21.26.208:443
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:10.291	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:54626	target_addr:104.18.40.152:443
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:9.757	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:55770	target_addr:104.21.86.125:443
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:55.044	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:56.858	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:59.489	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:29:21Z	status:FAILURE	latency:198.012	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:29:21Z	status:HEALTHY	latency:205.265	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:34:21Z	status:UNKNOWN	latency:7.073	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:10.701	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:53200	target_addr:104.21.86.125:443
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:11.164	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:55940	target_addr:172.64.147.104:443
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:11.551	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:54240	target_addr:172.67.219.211:443
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:11.621	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:58498	target_addr:172.67.168.140:443
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:53.601	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:54.477	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:57.982	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:34:21Z	status:FAILURE	latency:207.063	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:34:21Z	status:HEALTHY	latency:208.736	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:39:21Z	status:UNKNOWN	latency:7.425	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:8.490	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36672	target_addr:172.67.219.211:443
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:9.114	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:57720	target_addr:104.18.40.152:443
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:9.650	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:49490	target_addr:172.67.168.140:443
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:10.422	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:36674	target_addr:172.67.219.211:443
time:2026-10-05T07:39:21Z	status:FAILURE	latency:22.961	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:50.938	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:58.037	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:62.686	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:39:21Z	status:HEALTHY	latency:413.094	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:44:21Z	status:UNKNOWN	latency:8.483	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:9.826	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45522	target_addr:172.67.219.211:443
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:10.117	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:45518	target_addr:172.67.219.211:443
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:10.898	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:51868	target_addr:172.64.147.104:443
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:13.639	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:50110	target_addr:104.21.26.208:443
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:56.696	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:57.803	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:69.496	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:44:21Z	status:FAILURE	latency:206.512	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:44:21Z	status:HEALTHY	latency:210.503	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:49:21Z	status:UNKNOWN	latency:7.774	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:9.581	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:60724	target_addr:104.18.40.152:443
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:9.483	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:40584	target_addr:172.67.219.211:443
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:11.228	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:44166	target_addr:104.21.86.125:443
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:11.177	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:53846	target_addr:172.67.168.140:443
time:2026-10-05T07:49:21Z	status:FAILURE	latency:26.572	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:51.092	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:52.097	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:57.619	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:49:21Z	status:HEALTHY	latency:188.469	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:54:21Z	status:UNKNOWN	latency:8.502	target:https://6666ddasd.com/	message:lookup 6666ddasd.com: not found on 8.8.8.8:53
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:8.804	target:tcp://nlzq.one:443	message:succeed to connect	source_addr:172.17.0.2:51946	target_addr:104.21.26.208:443
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:10.018	target:tcp://notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60560	target_addr:172.67.219.211:443
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:10.604	target:tcp://classic.notfun.one:443	message:succeed to connect	source_addr:172.17.0.2:60550	target_addr:172.67.219.211:443
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:11.326	target:tcp://ao3-mirror.cc:443	message:succeed to connect	source_addr:172.17.0.2:33658	target_addr:172.64.147.104:443
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:53.397	target:https://go3-cn.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:53.909	target:https://go3-cn.blog/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:54.223	target:https://go3-cn.online/	message:200 OK	proto:HTTP/2.0	status_code:200
time:2026-10-05T07:54:21Z	status:FAILURE	latency:223.541	target:https://www.ao3-cn.com/	message:403 Forbidden	proto:HTTP/2.0	status_code:403
time:2026-10-05T07:54:21Z	status:HEALTHY	latency:229.717	target:https://www.ao3.xyz/	message:200 OK	proto:HTTP/2.0	status_code:200