最低配置4美刀/月 无需实名
NodeQuality链接:(https://nodequality.com/r/YHJAx5Vi7wmJyuJIfyXbN1nOH47DdEuy)
三网去回检测:https://naiba-taiwan-route-report.souldance4.chatgpt.site/report/msujlyce-10825b32
商家连结:https://client.ncse.tw/index.php?rp=/store/taiwan-vps-new
🎬IP质量
########################################################################
[1mIP质量体检报告:[36m23.146.*.*[0m
[4mhttps://github.com/xykt/IPQuality[0m
bash <(curl -sL https://Check.Place) -I
报告时间:2026-08-16 00:01:14 CST 脚本版本:v2026-08-09
########################################################################
一、基础信息([3mMaxmind 数据库[0m)
[36m自治系统号: [32mAS204844[0m
[36m组织: [32mNcse Network Ltd[0m
[36m坐标: [32m97°49′19″W, 37°45′4″N[0m
[36m地图: [4m[32mhttps://check.place/37.751,-97.822,13,cn[0m
[36m城市: [32mN/A[0m
[36m使用地: [32m[TW]台湾[0m[32m, [NA]北美洲[0m
[36m注册地: [32m[US]美国[0m
[36m时区: [32mAmerica/Chicago[0m
[36mIP类型: [41m[1m[37m 广播IP [0m
二、IP类型属性
[36m数据库: [3m IPinfo ipregistry ipapi IP2Location AbuseIPDB [0m
[36m使用类型: [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m
[36m公司类型: [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m
三、风险评分
[36m风险等级: [3m[37m[42m极低 低 [43m 中等 [41m 高 极高[0m
[36mIP2Location:[37m[1m [42m3|[43m[41m[0m[32m[1m低风险[0m
[36mScamalytics:[37m[1m 0[42m|[43m[41m[0m[32m[1m低风险[0m
[36mipapi:[37m[1m [42m 0.39%|[43m[41m[0m[32m[1m低风险[0m
[36mAbuseIPDB:[37m[1m 0[42m|[43m[41m[0m[32m[1m低风险[0m
[36mDB-IP:[37m[1m [42m|[43m[41m[0m[32m[1m低风险[0m
四、风险因子
[36m库: [3mIP2Location ipapi ipregistry IPQS Scamalytics ipdata IPinfo DB-IP[0m
[36m地区: [0m [32m[TW][0m [32m[TW][0m [32m[TW][0m [32m[1m 无 [0m [32m[TW][0m [32m[TW][0m [32m[TW][0m [32m[TW][0m
[36m代理: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m
[36mTor: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m
[36mVPN: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 无 [0m
[36m服务器:[0m [31m[1m 是 [0m [31m[1m 是 [0m [31m[1m 是 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [31m[1m 是 [0m [32m[1m 无 [0m
[36m滥用: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 无 [0m
[36m机器人:[0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 无 [0m [32m[1m 否 [0m
五、流媒体及AI服务解锁检测
[36m服务商: [3m TikTok Disney+ Netflix Youtube AmazonPV Reddit ChatGPT [0m
[36m状态: [42m[37m 解锁 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [0m
[36m地区: [32m [TW] [TW] [TW] [TW] [TW] [TW] [TW] [0m
[36m方式: [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [0m
六、邮局连通性及黑名单检测
[36m本地25端口出站:[0m[32m可用[0m
[36m通信:[0m[30m-[0m[41m[37m[1mGmail[0m[30m+[0m[42m[37m[1mOutlook[0m[30m+[0m[42m[37m[1mYahoo[0m[30m+[0m[42m[37m[1mApple[0m[30m-[0m[41m[37m[1mQQ[0m[30m+[0m[42m[37m[1mMailRU[0m[30m+[0m[42m[37m[1mAOL[0m[30m+[0m[42m[37m[1mGMX[0m[30m+[0m[42m[37m[1mMailCOM[0m[30m+[0m[42m[37m[1m163[0m[30m+[0m[42m[37m[1mSohu[0m[30m+[0m[42m[37m[1mSina[0m
[36mIP地址黑名单数据库: [0m[36m有效 [1m423 [0m[32m正常 [1m421 [0m[33m已标记 [1m2 [0m[31m黑名单 [1m0[0m
========================================================================
[3m今日IP检测量:4011;总检测量:1955098。感谢使用xy系列脚本! [0m
[3m报告链接:[4mhttps://Report.Check.Place/ip/1LMHVWL3P.svg[0m
########################################################################
[1mIP质量体检报告:[36m2602:faad:5:*:*:*:*:*[0m
[4mhttps://github.com/xykt/IPQuality[0m
bash <(curl -sL https://Check.Place) -I
报告时间:2026-08-16 00:01:14 CST 脚本版本:v2026-08-09
########################################################################
一、基础信息([3mMaxmind 数据库[0m)
[36m自治系统号: [32mAS204844[0m
[36m组织: [32mNcse Network Ltd[0m
[36m坐标: [32m97°49′19″W, 37°45′4″N[0m
[36m地图: [4m[32mhttps://check.place/37.751,-97.822,13,cn[0m
[36m城市: [32mN/A[0m
[36m使用地: [32m[US]美国[0m[32m, [NA]北美洲[0m
[36m注册地: [32m[US]美国[0m
[36m时区: [32mAmerica/Chicago[0m
[36mIP类型: [42m[1m[37m 原生IP [0m
二、IP类型属性
[36m数据库: [3m IPinfo ipregistry ipapi IP2Location AbuseIPDB [0m
[36m使用类型: [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m
[36m公司类型: [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m [41m[37m[1m 机房 [0m
三、风险评分
[36m风险等级: [3m[37m[42m极低 低 [43m 中等 [41m 高 极高[0m
[36mIP2Location:[37m[1m [42m3|[43m[41m[0m[32m[1m低风险[0m
[36mScamalytics:[37m[1m 0[42m|[43m[41m[0m[32m[1m低风险[0m
[36mipapi:[37m[1m 0.00%[42m|[43m[41m[0m[32m[1m极低风险[0m
[36mAbuseIPDB:[37m[1m 0[42m|[43m[41m[0m[32m[1m低风险[0m
[36mDB-IP:[37m[1m [42m|[43m[41m[0m[32m[1m低风险[0m
四、风险因子
[36m库: [3mIP2Location ipapi ipregistry IPQS Scamalytics ipdata IPinfo DB-IP[0m
[36m地区: [0m [32m[US][0m [32m[US][0m [32m[TW][0m [32m[1m 无 [0m [32m[US][0m [32m[US][0m [32m[TW][0m [32m[TW][0m
[36m代理: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m
[36mTor: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m
[36mVPN: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 无 [0m
[36m服务器:[0m [31m[1m 是 [0m [31m[1m 是 [0m [31m[1m 是 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [31m[1m 是 [0m [32m[1m 无 [0m
[36m滥用: [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 无 [0m
[36m机器人:[0m [32m[1m 否 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 无 [0m [32m[1m 否 [0m [32m[1m 无 [0m [32m[1m 无 [0m [32m[1m 否 [0m
五、流媒体及AI服务解锁检测
[36m服务商: [3m TikTok Disney+ Netflix Youtube AmazonPV Reddit ChatGPT [0m
[36m状态: [41m[37m 失败 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [41m[37m 屏蔽 [0m [42m[37m 解锁 [0m [42m[37m 解锁 [0m [0m
[36m地区: [32m [US] [US] [GB] [US] [TW] [0m
[36m方式: [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [42m[37m 原生 [0m [0m
六、邮局连通性及黑名单检测
[36m本地25端口出站:[0m[31m阻断[0m
[36m通信:[0m[30m+[0m[42m[37m[1mGmail[0m[30m-[0m[41m[37m[1mOutlook[0m[30m-[0m[41m[37m[1mYahoo[0m[30m-[0m[41m[37m[1mApple[0m[30m+[0m[42m[37m[1mQQ[0m[30m-[0m[41m[37m[1mMailRU[0m[30m-[0m[41m[37m[1mAOL[0m[30m-[0m[41m[37m[1mGMX[0m[30m-[0m[41m[37m[1mMailCOM[0m[30m-[0m[41m[37m[1m163[0m[30m-[0m[41m[37m[1mSohu[0m[30m-[0m[41m[37m[1mSina[0m
========================================================================
[3m今日IP检测量:4019;总检测量:1955106。感谢使用xy系列脚本! [0m
[3m报告链接:[4mhttps://Report.Check.Place/ip/1P71GVDRC.svg[0m
🌐网络质量

📍回程路由

💻基本信息
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[1m硬件质量体检报告:[36m23.146.*.*[0m
[4mhttps://github.com/xykt/HardwareQuality[0m
bash <(curl -sL https://Check.Place) -H
报告时间:2026-08-15 23:50:56 CST 脚本版本:v2026-05-21
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
一、操作系统信息
[36m容器/虚拟化: [32mKVM 虚拟机[0m
[36m架构: [32mx86_64[0m
[36m操作系统/内核: [32mDebian GNU/Linux 12 (bookworm) 6.12.85+deb13-amd64[0m
[36m运行时间: [32m0 天 0 小时 36 分钟[0m
[36m负载: [32m0.54[0m[32m, [32m0.20[0m[32m, [32m0.10[0m[0m
[36m进程: [32m3 用户,91 进程,14/158 活跃/总服务[0m
[36m区域设置: [32mC, UTF-8, Etc/UTC UTC +0000[0m
二、主板信息
[36mBIOS: [32mSeaBIOS, 版本rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org[0m
[36m芯片组: [32mIntel 82371SB PIIX3 ISA [Natoma/Triton II][0m
[32mIntel 440FX - 82441FX PMC [Natoma][0m
[36m网卡: [32mRed Hat, Inc. Virtio network device[0m
三、CPU测评
[36mCPU: [1m[4m[47m[30mQEMU Virtual version 2.5+ 步进1 (15代) 32/64-bit[0m
[1m[47m[30m ╚═ 1核心, 1线程, 1995.317MHz, 利用率14%[0m[47m [0m
[36m缓存: [32mL1d 32 KiB, L1i 32 KiB, L2 4 MiB, L3 16 MiB[0m
[36m指令集: [0m[41m ✘ VT-x/AMD-V [0m [42m ✔ AES-NI [0m [42m ✔ AVX2 [0m [42m ✔ BMI1/2 [0m [41m ✘ EPT/NPT [0m
[36mSysbench:[32m单线程 344.45 [0m
[36m详细结果:[32m[4mhttps://browser.geekbench.com/v5/cpu/24539920[0m
五、内存测评
[36m内存: [1m[4m[47m[30m总容量 967 MB, 已用 284 MB(29%), 可用 684 MB(71%)[0m[47m[0m
[36m超开指标:[0m[41m ✔ 气球回收 [0m [42m ✘ KSM 复用 [0m
[36mSysbench:[33m读取 17621.1 MB/s[0m [31m写入 13566.4 MB/s[0m [31m延迟 259 ns[0m
六、硬盘测评
[36m硬盘: [0m[47m[30m[1m[4m数量 1, 总容量 15G, 已用容量 3.0G(20%), 可用容量 11G(80%)[0m[47m[0m
[36m测试设备:[32msda1(/r**t) -> DISK[0m
[36mCrystal: RND4K/Q1 IOPS||RND4K/Q32 IOPS||SEQ1M/Q1 IOPS||SEQ1M/Q8 IOPS[0m
[36m读取: [0m[43m21.1M[0m[33mB/s 5.4k[0m[36m||[0m[43m272MB/s [0m[33m 70k[0m[36m||[0m[42m1299MB/s [0m[32m1.3k[0m[36m||[0m[42m3367MB/s 3.[0m[32m4k[0m
[36m写入: [0m[43m39.2MB[0m[33m/s 10k[0m[36m||[0m[43m208MB/s [0m[33m 53k[0m[36m||[0m[42m1339MB/s 1[0m[32m.3k[0m[36m||[0m[42m3314MB/s 3.[0m[32m3k[0m
[36mATTO: READ IOPS||WRITE IOPS[0m
[36m512B [0m[43m16.6MB/s [0m[33m 34k[0m[36m||[0m[43m14.0MB/s [0m[33m 29k[0m
[36m1K [0m[43m29.6MB/s [0m[33m 30k[0m[36m||[0m[43m25.4MB/s [0m[33m 26k[0m
[36m2K [0m[43m61.3MB/s [0m[33m 31k[0m[36m||[0m[43m53.0MB/s [0m[33m 27k[0m
[36m4K [0m[43m124MB/s [0m[33m 32k[0m[36m||[0m[43m107MB/s [0m[33m 27k[0m
[36m8K [0m[43m228MB/s [0m[33m 29k[0m[36m||[0m[43m205MB/s [0m[33m 26k[0m
[36m16K [0m[43m417MB/s [0m[33m 27k[0m[36m||[0m[43m369MB/s [0m[33m 24k[0m
[36m32K [0m[43m681MB/s [0m[33m 22k[0m[36m||[0m[43m658MB/s [0m[33m 21k[0m
[36m64K [0m[42m1060MB/s [0m[32m 17k[0m[36m||[0m[42m1198MB/s [0m[32m 19k[0m
[36m128K [0m[42m1641MB/s [0m[32m 13k[0m[36m||[0m[42m1753MB/s [0m[32m 14k[0m
[36m256K [0m[42m2264MB/s [0m[32m 9.1k[0m[36m||[0m[42m2288MB/s [0m[32m 9.2k[0m
[36m512K [0m[42m2622MB/s [0m[32m 5.2k[0m[36m||[0m[42m2783MB/s [0m[32m 5.6k[0m
[36m1M [0m[42m3062MB/s [0m[32m 3.1k[0m[36m||[0m[42m3205MB/s [0m[32m 3.2k[0m
[36m2M [0m[42m3354MB/s [0m[32m 1.7k[0m[36m||[0m[42m3346MB/s [0m[32m 1.7k[0m
[36m4M [0m[42m3383MB/s [0m[32m 845[0m[36m||[0m[42m3303MB/s [0m[32m 825[0m
[36m8M [0m[42m3362MB/s [0m[32m 420[0m[36m||[0m[42m3346MB/s [0m[32m 418[0m
[36m16M [0m[42m3363MB/s [0m[32m 210[0m[36m||[0m[42m3298MB/s [0m[32m 206[0m
[36m32M [0m[42m3369MB/s [0m[32m 105[0m[36m||[0m[42m3352MB/s [0m[32m 104[0m
[36m64M [0m[42m3359MB/s [0m[32m 52[0m[36m||[0m[42m3298MB/s [0m[32m 51[0m
七、HQ硬件加权评分
[36m项目: 总 分 CPU GPU 内 存 硬 盘 [0m
[36m分数: [0m[46m[37m[1m 7182 [0m [36m[1m=[0m [46m[37m[1m N/A [0m [36m[1m+[0m [46m[37m[1m N/A [0m [36m[1m+[0m [46m[37m[1m 5138 [0m [36m[1m+[0m [46m[37m[1m 2044 [0m
[36m排名: [0m[32m[1m 0.1% N/A N/A 0.8% 6.2% [0m
================================================================================
[3m今日硬件检测量:773;总检测量:148426。感谢使用xy系列脚本! [0m
[3m报告链接:[4mhttps://Report.Check.Place/hardware/QVQWH4QD6.svg[0m
☄️落地測速及分流
![]() |
![]() |
|---|---|
![]() |
![]() |


TQ🗽检测






🗽三网去程/回程检测
中国电信 · 深圳
- 探针/目标: 23.146..
- 路径: 深圳 → 东京 → 台北
- 骨干: CHINANET
- 结果: 第 15 跳到达
- 延迟: 258.99 ms
- 判读: 深圳电信经 CHINANET,路径依次经过东京,并在台北第 15 跳到达;目标端 PING 为 0.00–258.99 ms。
- MapTrace 路由图
1 OpenWrt.lan (10.0.0.1) 0.54ms 0.36–0.54 ms 0.36–0.54 ms
2 192.168.1.1 1.33ms 0.88–1.33 ms 0.81–1.33 ms
3 100.64.0.1 3.53ms 2.70–3.53 ms 2.70–3.53 ms
4 14.148.148.69 4.73ms 140318 Chaozhou, Guangdong Province, China 电信 0.00–4.73 ms 0.00–4.73 ms
5 14.148.146.41 8.12ms 4134 Chaozhou, Guangdong Province, China chinatelecom.com.cn 电信 0.00–8.12 ms 0.00–8.12 ms
06 *
07 *
8 203.215.237.154 136.23ms Tokyo, Tokyo, Japan 电信 135.61–136.23 ms 0.00–136.23 ms
09 *
10 ae-4.r24.taiptw01.tw.bb.gin.ntt.net (129.250.7.6) 102.76ms 2914 Taipei City, Taiwan, China gin.ntt.net 102.47–102.76 ms 0.00–102.76 ms
11 *
12 *
13 *
14 gw.core.ncse.tw (23.146.248.1) 298.90ms 204844 London, England, United Kingdom ncse.tw 264.54–298.90 ms 264.46–298.90 ms
15 23-146-248-183.ip.ncse.tw (23.146.*.*) 258.99ms 204844 Taipei, Taiwan ncse.tw 0.00–258.99 ms 0.00–258.99 ms
中国联通 · Tianjin
- 探针/目标: 23.146..
- 路径: Tianjin → 北京 → 东京 → 台北
- 骨干: CU169
- 结果: 最后响应第 15 跳
- 延迟: 162.38–1186.05 ms
- 判读: Tianjin联通经 CU169,路径依次经过北京、东京;目标未回应,目前只能确认到台北的最后响应第 15 跳,30 跳只是探测上限。最后响应 PING 为 157.00–1186.05 ms。
- MapTrace 路由图
1 10.4.0.1 0.30ms 0.28–0.30 ms 0.28–0.35 ms
2 dns1.online.tj.cn (111.163.88.1) 8.29ms 4837 Tianjin, China chinaunicom.cn 联通 7.33–8.29 ms 2.38–8.29 ms
03 *
04 *
5 219.158.7.37 3041.10ms 4837 Beijing, China chinaunicom.cn 联通 6.73–3041.10 ms 0.00–3041.10 ms
6 219.158.5.146 1008.18ms 4837 Beijing, China chinaunicom.cn 联通 0.00–1008.18 ms 0.00–1008.18 ms
07 *
8 219.158.33.50 125.01ms 4837 Osaka, Japan chinaunicom.cn 联通 125.01–128.27 ms 125.01–130.97 ms
9 129.250.6.108 194.22ms 2914 Osaka, Japan gin.ntt.net 192.69–194.22 ms 183.15–194.22 ms
10 129.250.7.80 1094.89ms 2914 Tokyo, Tokyo, Japan gin.ntt.net 70.77–1094.89 ms 70.77–3096.63 ms
11 ae-4.r24.taiptw01.tw.bb.gin.ntt.net (129.250.7.6) 100.11ms 2914 Taipei City, Taiwan, China gin.ntt.net 100.11–100.26 ms 100.11–100.40 ms
12 *
13 *
14 *
15 gw.core.ncse.tw (23.146.248.1) 162.38ms 204844 London, England, United Kingdom ncse.tw 157.00–162.38 ms 157.00–1186.05 ms
16 *
中国移动 · 泰山
- 探针/目标: 23.146..
- 路径: 泰山 → 江门 → 广州 → 圣何塞 → 香港 → 台北
- 骨干: CMI + CMNET
- 结果: 第 18 跳到达
- 延迟: 194.67–194.89 ms
- 判读: 泰山移动经 CMI + CMNET,路径依次经过江门、广州、圣何塞、香港,并在台北第 18 跳到达;目标端 PING 为 194.47–194.89 ms。
- MapTrace 路由图
1 setup.ui.com (10.201.8.1) 1.35ms 1.35–1.43 ms 1.26–1.43 ms
2 192.168.1.1 4.42ms 4.42–5.94 ms 1.62–5.94 ms
3 172.16.0.1 7.03ms 7.03–8.57 ms 7.03–8.57 ms
4 183.233.106.125 8.02ms 9808 Jiangmen, Guangdong, China chinamobileltd.com 移动 8.02–11.11 ms 0.00–11.11 ms
05 *
06 *
07 *
8 221.183.92.18 12.36ms 9808 Guangzhou, Guangdong Province, China chinamobileltd.com 移动 0.00–12.36 ms 0.00–12.36 ms
9 221.183.68.126 22.74ms 9808 Guangzhou, Guangdong Province, China chinamobileltd.com 移动 22.74–24.94 ms 22.52–24.94 ms
10 223.120.13.157 201.08ms 58453 San Jose, California, United States cmi.chinamobile.com 移动 201.08–209.45 ms 0.00–209.45 ms
11 223.120.6.70 244.50ms 58453 San Jose, California, United States cmi.chinamobile.com 移动 222.35–244.50 ms 205.76–244.50 ms
12 63-220-197-86.static.as3491.net (63.220.197.86) 219.43ms 3491 San Jose, California, United States pccwglobal.com 195.78–219.43 ms 0.00–219.43 ms
13 HundredGE0-1-0-0.br03.hkg08.as3491.net (63.223.29.142) 386.72ms 3491 Hong Kong, China pccwglobal.com 356.53–386.72 ms 347.91–386.72 ms
14 *
15 *
16 *
17 gw.core.ncse.tw (23.146.248.1) 188.38ms 204844 London, England, United Kingdom ncse.tw 187.80–188.38 ms 187.80–188.38 ms
18 23-146-248-183.ip.ncse.tw (23.146.*.*) 194.67ms 204844 Taipei, Taiwan ncse.tw 194.67–194.89 ms 194.47–194.89 ms
中国电信 · 西安
- 探针/目标: 2602:faad::
- 路径: 西安 → 东京 → 台北
- 骨干: CHINANET
- 结果: 第 13 跳到达
- 延迟: 295.76–295.90 ms
- 判读: 西安电信经 CHINANET,路径依次经过东京,并在台北第 13 跳到达;目标端 PING 为 0.00–295.90 ms。
- MapTrace 路由图
1 240e:358:d7c:1300:: 0.62ms 4134 Xi'An, Shaanxi, China chinatelecom.com.cn 电信 0.49–0.62 ms 0.49–0.95 ms
2 240e:f:0:1::28 5.94ms 4134 Xi'An, Shaanxi, China chinatelecom.com.cn 电信 3.26–5.94 ms 0.00–5.94 ms
3 240e:f:3:8804::2 4.38ms 4134 Xi'An, Shaanxi, China chinatelecom.com.cn 电信 4.38–25.93 ms 4.38–25.93 ms
04 *
05 *
06 *
7 240e:0:a::c9:3609 24.06ms 4134 China chinatelecom.com.cn 电信 0.00–24.06 ms 0.00–24.06 ms
08 *
9 2001:550:2:1f::85:1 168.37ms 174 United States cogentco.com 0.00–168.37 ms 0.00–168.37 ms
10 be3696.ccr81.tyo01.atlas.cogentco.com (2001:550:0:1000::9a36:568a) 274.43ms 174 Tokyo, Tokyo, Japan cogentco.com 274.15–274.43 ms 0.00–274.43 ms
11 be2012.ccr71.tpe01.atlas.cogentco.com (2001:550:0:1000::421c:4ea) 301.44ms 174 Taipei City, Taiwan, China cogentco.com 301.44–303.24 ms 0.00–303.24 ms
12 2402:4480:2:6::10:1d 290.55ms 174 cogentco.com 290.44–290.55 ms 290.33–290.55 ms
13 2602:faad:****:**** 295.76ms 204844 ncse.tw 295.76–295.90 ms 0.00–295.90 ms
中国联通 · 长沙
- 探针/目标: 2602:faad::
- 路径: 长沙 → 北京 → 洛杉矶
- 骨干: CU169
- 结果: 最后响应第 9 跳
- 延迟: 200.61–1214.52 ms
- 判读: 长沙联通经 CU169,路径依次经过北京;目标未回应,目前只能确认到洛杉矶的最后响应第 9 跳,30 跳只是探测上限。最后响应 PING 为 200.61–1214.52 ms。
- MapTrace 路由图
1 2408:8352:e60:10c4::1 1.23ms 4837 Changsha, Hunan, China chinaunicom.cn 联通 1.21–1.23 ms 1.21–1.23 ms
2 2408:8001:2000::38 4.37ms 4837 Changsha, Hunan, China chinaunicom.cn 4.37–5.31 ms 4.37–5.31 ms
3 2408:8001:2000:1::6e8 5.17ms 4837 Changsha, Hunan, China chinaunicom.cn 5.17–1015.10 ms 0.00–1015.10 ms
4 2408:8001:2000:1::20 2041.42ms 4837 Changsha, Hunan, China chinaunicom.cn 5.58–2041.42 ms 4.68–2041.42 ms
05 *
6 2408:8000:2:8044::1 1034.35ms 4837 Beijing, China chinaunicom.cn 联通 0.00–1034.35 ms 0.00–1034.35 ms
7 2408:8000:2:65d:: 26.97ms 4837 Beijing, China chinaunicom.cn 联通 26.97–29.69 ms 0.00–29.69 ms
08 *
9 bundle-ether14.core1.lax2.he.net (2001:470:0:217::1) 200.61ms 6939 Los Angeles, California, United States he.net 200.61–1214.52 ms 200.61–1214.52 ms
10 *
中国移动 · 泰山
- 探针/目标: 2602:faad::
- 路径: 泰山 → 江门 → 广州 → 北京 → … → 台北
- 骨干: CMNET
- 结果: 最后响应第 17 跳
- 延迟: 3421.63 ms
- 判读: 泰山移动经 CMNET,路径依次经过江门、广州、北京、…;目标未回应,目前只能确认到台北的最后响应第 17 跳,30 跳只是探测上限。最后响应 PING 为 350.50–3421.63 ms。
- MapTrace 路由图
1 setup.ui.com (2409:8a55:5c85:7990:9e05:d6ff:fe36:b39b) 1.75ms 9808 Jiangmen, Guangdong, China chinamobileltd.com 移动 1.67–1.75 ms 1.50–1.75 ms
2 2409:8a55:5c85:7990:36d7:2fff:fe62:6120 69.64ms 9808 Jiangmen, Guangdong, China chinamobileltd.com 移动 2.17–69.64 ms 2.10–69.64 ms
3 2409:8054:38::101f 38.23ms 9808 Jiangmen, Guangdong, China chinamobileltd.com 移动 7.75–38.23 ms 6.92–38.23 ms
4 2409:8055:38:11f0::1 6.93ms 9808 Jiangmen, Guangdong, China chinamobileltd.com 移动 6.93–2036.24 ms 6.93–2086.10 ms
5 2409:8055:38:208::1 1042.42ms 9808 Jiangmen, Guangdong Province, China chinamobileltd.com 0.00–1042.42 ms 0.00–1042.42 ms
6 2409:8080:0:2:306:37a:: 2041.91ms 9808 Guangzhou, Guangdong Province, China chinamobileltd.com 移动 13.28–2041.91 ms 0.00–2041.91 ms
7 2409:8080:0:1:106:307:: 3154.99ms 9808 Beijing, China chinamobileltd.com 移动 1093.54–3154.99 ms 0.00–3154.99 ms
8 2409:8080:0:1:106:1c2:0:1 45.46ms 9808 Beijing, China chinamobileltd.com 移动 45.46–1069.75 ms 0.00–1069.75 ms
9 2409:8080:0:1:1c1:1f1:1:1 48.04ms 9808 Beijing, China chinamobileltd.com 移动 48.04–3096.91 ms 0.00–3096.91 ms
10 2409:8080:0:4:1f1:193:2:1 3152.38ms 9808 Beijing, China chinamobileltd.com 移动 3144.12–3152.38 ms 0.00–3152.38 ms
11 *
12 *
13 2001:550:2:67::2f:24 1252.84ms 174 Los Angeles, California, United States cogentco.com 219.41–1252.84 ms 219.41–1252.84 ms
14 be3243.ccr41.lax01.atlas.cogentco.com (2001:550:0:1000::9a36:1b75) 1272.67ms 174 Los Angeles, California, United States cogentco.com 232.72–1272.67 ms 232.72–2261.08 ms
15 be3360.ccr41.lax04.atlas.cogentco.com (2001:550:0:1000::9a36:2a66) 1286.48ms 174 Los Angeles, California, United States cogentco.com 226.62–1286.48 ms 226.62–2294.73 ms
16 be2079.ccr81.tyo01.atlas.cogentco.com (2001:550:0:1000::9a36:a4d2) 1338.01ms 174 Tokyo, Tokyo, Japan cogentco.com 347.80–1338.01 ms 0.00–1338.01 ms
17 be2012.ccr71.tpe01.atlas.cogentco.com (2001:550:0:1000::421c:4ea) 3421.63ms 174 Taipei City, Taiwan, China cogentco.com 350.50–3421.63 ms 350.50–3421.63 ms
18 *
回程 / RETURN
中国电信 · 上海
- 探针/目标: 202.96.209.5
- 路径: NCES台湾 → 上海
- 骨干: CHINANET
- 结果: 第 12 跳到达
- 延迟: 329.78–331.60 ms
- 判读: NCES台湾 回程经 CHINANET,已识别 CHINANET 骨干,并在上海第 12 跳到达;目标端 PING 为 329.78–331.60 ms。
- MapTrace 路由图
1 gw.core.ncse.tw (23.146.248.1) 0.42ms 204844 London, England, United Kingdom ncse.tw 0.42 ms 0.41–0.42 ms
2 172.18.1.173 0.40ms 0.37–0.40 ms 0.37–1.33 ms
3 172.23.7.9 0.50ms 0.50–0.60 ms 0.50–0.69 ms
04 *
5 BE42.br02.frf08.as3491.net (63.218.14.54) 211.13ms 3491 Frankfurt, Hessen, Germany pccwglobal.com
6 81.173.21.41 255.18ms 4134 Frankfurt, Hesse, Germany chinatelecom.com.cn 电信 214.00–255.18 ms 203.84–255.18 ms
7 202.97.63.25 237.91ms 4134 Shanghai, China chinatelecom.com.cn 电信 237.61–237.91 ms
08 *
9 202.97.57.154 252.22ms 4134 Shanghai, China chinatelecom.com.cn 电信
10 61.152.25.225 253.84ms 4812 Shanghai, China chinatelecom.cn 电信 251.55–253.84 ms 251.55–253.84 ms
11 61.172.92.30 259.83ms 4812 Shanghai, China chinatelecom.cn 电信
12 ns-px.online.sh.cn (202.96.209.5) 329.78ms 4812 Shanghai, China chinatelecom.cn 电信 329.78–331.60 ms
中国联通 · 上海
- 探针/目标: 210.22.70.3
- 路径: NCES台湾 → 上海
- 骨干: CU169
- 结果: 最后响应第 13 跳
- 延迟: 153.82–154.07 ms
- 判读: NCES台湾 回程经 CU169,已识别 CU169 骨干;目标未回应,目前只能确认到上海的最后响应第 13 跳,30 跳只是探测上限。最后响应 PING 为 153.77–154.07 ms。
- MapTrace 路由图
1 gw.core.ncse.tw (23.146.248.1) 0.57ms 204844 London, England, United Kingdom ncse.tw 0.29–0.57 ms 0.29–0.57 ms
2 172.18.1.173 0.64ms 0.43–0.64 ms 0.43–0.64 ms
3 172.23.7.9 0.69ms 0.69–7.95 ms 0.56–7.95 ms
04 *
05 *
06 *
07 *
8 ae-8.a02.osakjp02.jp.bb.gin.ntt.net (129.250.6.109) 38.09ms 2914 Osaka, Japan gin.ntt.net 38.06–38.09 ms 38.06–38.20 ms
9 ae-0.cnc-g.osakjp02.jp.bb.gin.ntt.net (129.250.66.138) 150.75ms 2914 Osaka, Japan gin.ntt.net
10 219.158.6.209 152.32ms 4837 Shanghai, China chinaunicom.cn 联通 152.32–152.87 ms
11 219.158.7.129 152.46ms 4837 Shanghai, China chinaunicom.cn 联通
12 *
13 139.226.211.154 153.82ms 17621 Shanghai, China chinaunicom.cn 联通 153.82–154.07 ms 153.77–154.07 ms
14 *
15 *
16 *
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
中国移动 · 上海
- 探针/目标: 211.136.112.50
- 路径: NCES台湾 → 香港 → 上海 → 北京 → 上海
- 骨干: CMI + CMNET
- 结果: 第 17 跳到达
- 延迟: 67.44–67.59 ms
- 判读: NCES台湾 回程经 CMI + CMNET,路径依次经过香港、上海、北京,并在上海第 17 跳到达;目标端 PING 为 67.44–67.59 ms。
- MapTrace 路由图
1 gw.core.ncse.tw (23.146.248.1) 0.46ms 204844 London, England, United Kingdom ncse.tw 0.29–0.46 ms 0.29–0.46 ms
2 172.18.1.173 0.48ms 0.48–1.70 ms 0.38–1.70 ms
3 172.23.7.9 0.69ms 0.57–0.69 ms 0.46–0.69 ms
04 *
05 *
06 *
7 ae-18.a00.chwahk03.hk.bb.gin.ntt.net (129.250.2.149) 14.29ms 2914 Hong Kong, China gin.ntt.net 14.29–16.14 ms 14.29–29.46 ms
08 *
09 *
10 223.120.3.198 196.85ms 58453 Shanghai, China cmi.chinamobile.com 移动
11 221.183.89.182 201.32ms 9808 Shanghai, China chinamobileltd.com 移动 201.32–201.44 ms 201.23–201.44 ms
12 *
13 221.183.89.50 202.20ms 9808 Shanghai, China chinamobileltd.com 移动
14 221.183.184.165 211.34ms 9808 Beijing, China chinamobileltd.com
15 221.183.46.178 67.21ms 9808 Beijing, China chinamobileltd.com 移动 66.78–67.21 ms 66.78–67.21 ms
16 221.183.130.142 70.50ms 9808 Beijing, China chinamobileltd.com 移动 70.50–70.59 ms
17 dns1.sh.cnmobile.net (211.136.112.50) 67.44ms 24400 Shanghai, China sh.10086.cn 移动 67.44–67.59 ms
中国电信 · 上海
- 探针/目标: 240e:96c:6000:2100::cf
- 路径: NCES台湾 → 台北 → 上海
- 骨干: CHINANET
- 结果: 第 17 跳到达
- 延迟: 270.73 ms
- 判读: NCES台湾 回程经 CHINANET,路径依次经过台北,并在上海第 17 跳到达;目标端 PING 为 270.62–270.73 ms。
- MapTrace 路由图
1 gw.core.ncse.tw (2602:faad:2::1) 0.44ms 204844 China, Taiwan, China ncse.tw 0.44 ms 0.44–0.52 ms
2 2405:7e00:1:7408:113:21:82:101 0.77ms 17408 Taiwan, China chief.com.tw 0.57–0.77 ms 0.57–0.77 ms
3 17-253-123-103-static.chief.net.tw (103.123.253.17) 0.95ms Taipei City, Taiwan, China chief.net.tw 是方电讯 0.95–1.52 ms 0.95–1.52 ms
4 142-64-26-223-static.chief.net.tw (223.26.64.142) 1.01ms 1.01–1.07 ms 1.01–1.07 ms
5 2405:7e00:1:7408:223:26:67:113 1.25ms 17408 Taiwan, China chief.com.tw 1.25–2.44 ms 1.16–2.44 ms
06 *
07 *
08 *
09 *
10 *
11 240e:0:a::cb:1bd4 292.82ms 4134 Shanghai, China chinatelecom.com.cn 电信 292.32–292.82 ms 292.13–292.82 ms
12 240e:0:a::c9:5520 272.03ms 4134 Shanghai, China chinatelecom.com.cn 电信
13 *
14 240e:18:10:4304::89 271.51ms 4812 Shanghai, China chinatelecom.cn 271.51–271.99 ms
15 240e:18:10:2b89::99 310.40ms 4812 Shanghai, China chinatelecom.cn 310.40–310.60 ms 310.40–310.60 ms
16 240e:96c:6000:2200::3 284.43ms 4811 Shanghai, China chinatelecom.cn 电信 284.26–284.43 ms 284.26–284.43 ms
17 240e:96c:6000:2100::cf 270.73ms 4811 Shanghai, China chinatelecom.cn 电信 270.64–270.73 ms 270.62–270.73 ms
中国联通 · 上海
- 探针/目标: 2408:8000:9000:0:4000::437
- 路径: NCES台湾 → 台北 → 圣何塞 → 上海
- 骨干: CU169
- 结果: 第 19 跳到达
- 延迟: 331.24 ms
- 判读: NCES台湾 回程经 CU169,路径依次经过台北、圣何塞,并在上海第 19 跳到达;目标端 PING 为 328.89–331.24 ms。
- MapTrace 路由图
1 gw.core.ncse.tw (2602:faad:2::1) 0.36ms 204844 China, Taiwan, China ncse.tw 0.36–0.38 ms 0.36–0.42 ms
2 2405:7e00:1:7408:113:21:82:101 0.70ms 17408 Taiwan, China chief.com.tw 0.57–0.70 ms 0.57–0.79 ms
3 17-253-123-103-static.chief.net.tw (103.123.253.17) 1.14ms Taipei City, Taiwan, China chief.net.tw 是方电讯 1.14 ms 1.04–1.14 ms
4 142-64-26-223-static.chief.net.tw (223.26.64.142) 1.05ms 0.90–1.05 ms 0.90–3.34 ms
5 2405:7e00:1:7408:223:26:67:113 0.99ms 17408 Taiwan, China chief.com.tw 0.99–1.03 ms 0.99–2.00 ms
06 *
07 *
08 *
9 be1.core1.sea1.he.net (2001:470:0:268::1) 113.46ms 6939 Seattle, Washington, United States he.net
10 *
11 be7.core1.pao1.he.net (2001:470:0:3f1::1) 131.88ms 6939 Palo Alto, California, United States he.net 131.88–135.01 ms 131.88–135.01 ms
12 be7.core1.sjc2.he.net (2001:470:e:85::1) 134.56ms 6939 San Jose, California, United States he.net
13 *
14 *
15 2408:8000:2:80b0:: 301.62ms 4837 Shanghai, China chinaunicom.cn 联通 301.62–303.12 ms 301.62–304.17 ms
16 2408:8000:2:3cd:: 307.71ms 4837 Shanghai, China chinaunicom.cn 联通 307.71–309.51 ms 307.71–312.36 ms
17 2408:8000:2:3d1:: 313.90ms 4837 Shanghai, China chinaunicom.cn 联通 313.90–315.91 ms
18 *
19 2408:8000:9000:0:4000::437 331.24ms 17621 Shanghai, China chinaunicom.cn 联通 329.50–331.24 ms 328.89–331.24 ms
中国移动 · 上海
- 探针/目标: 2409:801e:f0:1::4e1
- 路径: NCES台湾 → 台北 → 上海
- 骨干: CMNET
- 结果: 第 17 跳到达
- 延迟: 360.88–361.07 ms
- 判读: NCES台湾 回程经 CMNET,路径依次经过台北,并在上海第 17 跳到达;目标端 PING 为 360.88–361.07 ms。
- MapTrace 路由图
1 gw.core.ncse.tw (2602:faad:2::1) 0.37ms 204844 China, Taiwan, China ncse.tw 0.37–0.43 ms 0.36–0.43 ms
2 2405:7e00:1:7408:113:21:82:101 0.84ms 17408 Taiwan, China chief.com.tw 0.55–0.84 ms 0.55–0.84 ms
3 17-253-123-103-static.chief.net.tw (103.123.253.17) 1.49ms Taipei City, Taiwan, China chief.net.tw 是方电讯 0.95–1.49 ms 0.91–1.49 ms
4 2405:7e00:1:7408:223:26:67:131 0.95ms 17408 Taiwan, China chief.com.tw 0.95–72.80 ms 0.95–72.80 ms
5 2001:1a00:acca:150e::2a 0.87ms 15412 flagtel.com 0.87–0.89 ms 0.75–0.89 ms
06 *
07 *
08 *
9 be1.core1.sea1.he.net (2001:470:0:268::1) 115.25ms 6939 Seattle, Washington, United States he.net 115.19–115.25 ms 115.19–115.73 ms
10 *
11 *
12 *
13 *
14 2409:8080:0:4:2c6:2f6:2:1 359.84ms 9808 Shanghai, China chinamobileltd.com 移动 359.68–359.84 ms
15 2409:8080:0:1:206:2c6:: 359.77ms 9808 Shanghai, China chinamobileltd.com 移动 359.13–359.77 ms
16 2409:8080:0:2:206:276:0:1 359.97ms 9808 Shanghai, China chinamobileltd.com 移动 359.68–359.97 ms 359.50–359.97 ms
17 2409:801e:f0:1::4e1 360.88ms 24400 Shanghai, China sh.10086.cn 移动 360.88–360.98 ms 360.88–361.07 ms




更好奇能不能直连HiNet
绕路这样了
落地机