HK MagicRoute 01 / 02 / MagicTunnel 已下调至x0.7

等会上KOR AnyRoute / MagicTunnel
还有其他调整也在慢慢端上来

DoriyaNet 的第一个 AnyTLS 节点

其实技术上anytls的确是不比vless reality的，但是它确实比vless reality多一个东西
tcp快速打开，而这个东西其实感知非常明显，特别在于一些聊天的即时软件里

JPN MagicRoute 01 / 02 / MagicTunnel 已下调至x0.7

同时就是
原 JPN 05 NeroCloud -> JPN 01
原 JPN 01 NTT 家宽 -> JPN 04
新落地 Akamai Japan -> JPN 05
把速度快的落地的编号往前调了

现在的 JPN MagicRoute 是默认去 改了之后的 JPN 01 的，会比以前更有速度

HKG 04 AnyRoute IEPL 上线

KOR 01 AnyRoute IEPL 上线

HKG 05 Direct 都已经被墙了还怎么做到25个人在用的
神奇

SGP 01 明天会从Oracle改到DigitalOcean
现在这个速度太慢了，有问题

改好了 现在速度会好很多应该

以下为 中国移动蜂窝网络 -> DoriyaNet HK CMI(中国移动优化海外入口) tcping 测试

TCPinging domain on port 43366
Reply from domain (ip) on port 43366 TCP_conn=1 time=99.933 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No response received for 1 second
Reply from domain (ip) on port 43366 TCP_conn=1 time=41.713 ms
Reply from domain (ip) on port 43366 TCP_conn=2 time=38.112 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No reply from domain (ip) on port 43366 TCP_conn=3
No reply from domain (ip) on port 43366 TCP_conn=4
No response received for 4 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=206.579 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No response received for 1 second
Reply from domain (ip) on port 43366 TCP_conn=1 time=38.525 ms
Reply from domain (ip) on port 43366 TCP_conn=2 time=41.690 ms
Reply from domain (ip) on port 43366 TCP_conn=3 time=95.936 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No response received for 2 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=44.373 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No reply from domain (ip) on port 43366 TCP_conn=3
No response received for 3 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=277.301 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No response received for 1 second
Reply from domain (ip) on port 43366 TCP_conn=1 time=64.683 ms
Reply from domain (ip) on port 43366 TCP_conn=2 time=213.619 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No reply from domain (ip) on port 43366 TCP_conn=3
No response received for 3 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=70.940 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No response received for 1 second
Reply from domain (ip) on port 43366 TCP_conn=1 time=34.682 ms
Reply from domain (ip) on port 43366 TCP_conn=2 time=33.936 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No response received for 1 second
Reply from domain (ip) on port 43366 TCP_conn=1 time=42.013 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No reply from domain (ip) on port 43366 TCP_conn=3
No reply from domain (ip) on port 43366 TCP_conn=4
No response received for 4 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=33.971 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No reply from domain (ip) on port 43366 TCP_conn=3
No reply from domain (ip) on port 43366 TCP_conn=4
No response received for 4 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=32.597 ms
No reply from domain (ip) on port 43366 TCP_conn=1
No reply from domain (ip) on port 43366 TCP_conn=2
No reply from domain (ip) on port 43366 TCP_conn=3
No response received for 3 seconds
Reply from domain (ip) on port 43366 TCP_conn=1 time=36.141 ms
No reply from domain (ip) on port 43366 TCP_conn=1 

--- domain (ip) TCPing statistics ---
47 probes transmitted on port 43366 | 18 received, 61.70% packet loss
successful probes: 18
unsuccessful probes: 29
last successful probe: 2026-04-24 00:07:39
last unsuccessful probe: 2026-04-24 00:07:40
total uptime: 18 seconds
total downtime: 29 seconds
longest consecutive uptime: 3 seconds from 2026-04-24 00:07:04 to 2026-04-24 00:07:07
longest consecutive downtime: 4 seconds from 2026-04-24 00:07:26 to 2026-04-24 00:07:30
retried to resolve hostname 0 times
rtt min/avg/max: 32.597/80.375/277.301 ms
TCPing started at: 2026-04-24 00:06:54
TCPing ended at: 2026-04-24 00:07:41
duration (HH:MM:SS): 00:00:47

以下为 中国移动蜂窝网络 -> DoriyaNet HK CMI(中国移动优化海外入口) icmp-ping 测试

正在 Ping domain [ip] 具有 32 字节的数据:

来自 ip 的回复: 字节=32 时间=40ms TTL=45

来自 ip 的回复: 字节=32 时间=30ms TTL=45

来自 ip 的回复: 字节=32 时间=26ms TTL=45

来自 ip 的回复: 字节=32 时间=30ms TTL=45

来自 ip 的回复: 字节=32 时间=61ms TTL=45

来自 ip 的回复: 字节=32 时间=35ms TTL=45

来自 ip 的回复: 字节=32 时间=78ms TTL=45

来自 ip 的回复: 字节=32 时间=31ms TTL=45

来自 ip 的回复: 字节=32 时间=40ms TTL=45

来自 ip 的回复: 字节=32 时间=30ms TTL=45

来自 ip 的回复: 字节=32 时间=32ms TTL=45

来自 ip 的回复: 字节=32 时间=30ms TTL=45

来自 ip 的回复: 字节=32 时间=35ms TTL=45

来自 ip 的回复: 字节=32 时间=40ms TTL=45

来自 ip 的回复: 字节=32 时间=36ms TTL=45

来自 ip 的回复: 字节=32 时间=47ms TTL=45

来自 ip 的回复: 字节=32 时间=35ms TTL=45

来自 ip 的回复: 字节=32 时间=38ms TTL=45

来自 ip 的回复: 字节=32 时间=31ms TTL=45

来自 ip 的回复: 字节=32 时间=25ms TTL=45

来自 ip 的回复: 字节=32 时间=35ms TTL=45

来自 ip 的回复: 字节=32 时间=35ms TTL=45

来自 ip 的回复: 字节=32 时间=38ms TTL=45

以下为 中国移动蜂窝网络IPv6 -> Akamai JPN IPv6 tcping 测试

TCPinging ip on port 12036
Reply from ip (ip) on port 12036 TCP_conn=1 time=104.030 ms
No reply from ip (ip) on port 12036 TCP_conn=1
No response received for 1 second
Reply from ip (ip) on port 12036 TCP_conn=1 time=101.318 ms
Reply from ip (ip) on port 12036 TCP_conn=2 time=105.803 ms
Reply from ip (ip) on port 12036 TCP_conn=3 time=118.998 ms
Reply from ip (ip) on port 12036 TCP_conn=4 time=96.313 ms
Reply from ip (ip) on port 12036 TCP_conn=5 time=176.902 ms
Reply from ip (ip) on port 12036 TCP_conn=6 time=509.196 ms
Reply from ip (ip) on port 12036 TCP_conn=7 time=224.917 ms
No reply from ip (ip) on port 12036 TCP_conn=1
No response received for 1 second
Reply from ip (ip) on port 12036 TCP_conn=1 time=378.271 ms
Reply from ip (ip) on port 12036 TCP_conn=2 time=153.074 ms
Reply from ip (ip) on port 12036 TCP_conn=3 time=162.016 ms
Reply from ip (ip) on port 12036 TCP_conn=4 time=97.131 ms
Reply from ip (ip) on port 12036 TCP_conn=5 time=118.109 ms
Reply from ip (ip) on port 12036 TCP_conn=6 time=96.364 ms
Reply from ip (ip) on port 12036 TCP_conn=7 time=102.175 ms
Reply from ip (ip) on port 12036 TCP_conn=8 time=137.965 ms
Reply from ip (ip) on port 12036 TCP_conn=9 time=96.622 ms
Reply from ip (ip) on port 12036 TCP_conn=10 time=120.011 ms
Reply from ip (ip) on port 12036 TCP_conn=11 time=101.609 ms
Reply from ip (ip) on port 12036 TCP_conn=12 time=117.519 ms
Reply from ip (ip) on port 12036 TCP_conn=13 time=100.594 ms
Reply from ip (ip) on port 12036 TCP_conn=14 time=118.025 ms
Reply from ip (ip) on port 12036 TCP_conn=15 time=111.086 ms
Reply from ip (ip) on port 12036 TCP_conn=16 time=103.533 ms
Reply from ip (ip) on port 12036 TCP_conn=17 time=115.822 ms
Reply from ip (ip) on port 12036 TCP_conn=18 time=204.437 ms
Reply from ip (ip) on port 12036 TCP_conn=19 time=112.260 ms
Reply from ip (ip) on port 12036 TCP_conn=20 time=101.819 ms
Reply from ip (ip) on port 12036 TCP_conn=21 time=102.386 ms
Reply from ip (ip) on port 12036 TCP_conn=22 time=96.077 ms
Reply from ip (ip) on port 12036 TCP_conn=23 time=112.378 ms
Reply from ip (ip) on port 12036 TCP_conn=24 time=117.719 ms
Reply from ip (ip) on port 12036 TCP_conn=25 time=94.949 ms
Reply from ip (ip) on port 12036 TCP_conn=26 time=173.273 ms
Reply from ip (ip) on port 12036 TCP_conn=27 time=102.936 ms
Reply from ip (ip) on port 12036 TCP_conn=28 time=97.031 ms
Reply from ip (ip) on port 12036 TCP_conn=29 time=106.598 ms
Reply from ip (ip) on port 12036 TCP_conn=30 time=96.640 ms
Reply from ip (ip) on port 12036 TCP_conn=31 time=146.686 ms
Reply from ip (ip) on port 12036 TCP_conn=32 time=99.019 ms
Reply from ip (ip) on port 12036 TCP_conn=33 time=119.227 ms
Reply from ip (ip) on port 12036 TCP_conn=34 time=256.809 ms
Reply from ip (ip) on port 12036 TCP_conn=35 time=112.213 ms
Reply from ip (ip) on port 12036 TCP_conn=36 time=116.977 ms
Reply from ip (ip) on port 12036 TCP_conn=37 time=101.330 ms
Reply from ip (ip) on port 12036 TCP_conn=38 time=140.760 ms
Reply from ip (ip) on port 12036 TCP_conn=39 time=99.578 ms
Reply from ip (ip) on port 12036 TCP_conn=40 time=135.456 ms
Reply from ip (ip) on port 12036 TCP_conn=41 time=97.359 ms
Reply from ip (ip) on port 12036 TCP_conn=42 time=103.768 ms

--- ip TCPing statistics ---
52 probes transmitted on port 12036 | 50 received, 3.85% packet loss
successful probes: 50
unsuccessful probes: 2
last successful probe: 2026-04-24 00:17:10
last unsuccessful probe: 2026-04-24 00:16:28
total uptime: 50 seconds
total downtime: 2 seconds
longest consecutive uptime: 41 seconds from 2026-04-24 00:16:29 to 2026-04-24 00:17:11
longest consecutive downtime: 1 second from 2026-04-24 00:16:28 to 2026-04-24 00:16:29
rtt min/avg/max: 94.949/134.302/509.196 ms
TCPing started at: 2026-04-24 00:16:19
TCPing ended at: 2026-04-24 00:17:11
duration (HH:MM:SS): 00:00:52

还行

整了篇小报告
虽然技术含量其实挺低的，就是ping两下的事情x
不过挺多人没有注意到这个点的倒是

以后将不会发布任何关于未来线路变动的提前预告
并不是不会变动了，但的确是，需要先闭嘴，以及画饼实则无用

JPN 04 Direct 也被墙了
甚至都是Vless Reality + 整流
还蛮神奇的，毕竟如果是被盯上了的话 其他直连倒是又没墙

估计是cloudinnovation的ip太黑了