测试/Claw.cloud/$25.2/年/2C/2G/40G/1T@200Mbps/东京/香港/新加坡
2月21日更新• claw.cloud • paypal • 低价vps•其他VPS•阅读:60次
写在前面
最近Claw的活动价格满吸引人的。 活动时间：2月13日至2月28日（新加坡时间）
$25.2/年/2C/2G/40G/1T@200Mbps 永久优惠码：L204UYZHE7
$12.6/年/1C/1/20G/500G@200Mbps 永久优惠码：W8A0EKAA41
$67.2/年/4C/4G/80G/2T@200Mbps 永久优惠码：PKA7FOY4G7
支付方式：PayPal、信用卡、支付宝、支付宝HK
测试
以$25.2/年的东京为例，做个测试
基础信息
带宽测试
延迟测试
回程测试
广州电信
traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 32 byte packets
1 *
2 *
3 11.60.67.177 6.16 ms http: 403 http: 403
4 *
5 203.160.66.249 3.57 ms http: 403 http: 403
6 203.160.66.245 29.25 ms http: 403 http: 403
7 219.158.24.25 32.58 ms http: 403 http: 403
8 219.158.19.86 31.64 ms http: 403 http: 403
9 *
10 *
11 219.158.9.30 61.46 ms http: 403 http: 403
12 *
13 *
14 113.96.255.86 68.39 ms http: 403 http: 403
15 *
16 178.72.145.61.broad.fs.gd.dynamic.163data.com.cn (61.145.72.178) 66.44 ms http: 403 http: 403
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *
----------------------------------------------------------------------
上海电信
traceroute to 202.96.209.133 (202.96.209.133), 30 hops max, 32 byte packets
1 11.73.1.42 1.88 ms http: 403 http: 403
2 *
3 11.60.67.201 2.32 ms http: 403 http: 403
4 *
5 203.160.66.253 4.34 ms http: 403 http: 403
6 203.160.66.237 2.95 ms http: 403 http: 403
7 219.158.16.49 33.22 ms http: 403 http: 403
8 219.158.8.173 35.68 ms http: 403 http: 403
9 *
10 219.158.109.174 34.92 ms http: 403 http: 403
11 *
12 *
13 *
14 61.172.64.54 33.84 ms http: 403 http: 403
15 ns-pd.online.sh.cn (202.96.209.133) 30.88 ms http: 403 http: 403
----------------------------------------------------------------------
厦门电信
traceroute to 117.28.254.129 (117.28.254.129), 30 hops max, 32 byte packets
1 11.73.1.42 2.14 ms http: 403 http: 403
2 11.73.1.73 5.21 ms http: 403 http: 403
3 11.60.67.217 2.36 ms http: 403 http: 403
4 10.216.146.210 2.96 ms http: 403 http: 403
5 101.203.70.85 3.51 ms http: 403 http: 403
6 *
7 *
8 *
9 *
10 HundredGE0-5-0-1.br03.hkg15.as3491.net (63.223.15.210) 54.84 ms http: 403 http: 403
11 63.216.143.46 54.81 ms http: 403 http: 403
12 59.43.250.77 58.44 ms http: 403 http: 403
13 59.43.250.49 55.31 ms http: 403 http: 403
14 59.43.16.181 63.34 ms http: 403 http: 403
15 59.43.140.34 79.18 ms http: 403 http: 403
16 *
17 27.148.195.98 71.50 ms http: 403 http: 403
18 *
19 *
20 117.28.254.129 72.04 ms http: 403 http: 403
----------------------------------------------------------------------
重庆联通
traceroute to 113.207.25.138 (113.207.25.138), 30 hops max, 32 byte packets
1 *
2 *
3 11.60.67.65 2.10 ms http: 403 http: 403
4 10.216.157.162 2.75 ms http: 403 http: 403
5 203.160.66.253 3.42 ms http: 403 http: 403
6 203.160.66.190 2.95 ms http: 403 http: 403
7 203.160.66.245 29.34 ms http: 403 http: 403
8 219.158.16.213 34.20 ms http: 403 http: 403
9 219.158.19.90 29.69 ms http: 403 http: 403
10 *
11 219.158.106.254 74.09 ms http: 403 http: 403
12 113.207.25.138 61.85 ms http: 403 http: 403
----------------------------------------------------------------------
成都联通
traceroute to 119.6.6.6 (119.6.6.6), 30 hops max, 32 byte packets
1 *
2 *
3 11.60.67.185 8.12 ms http: 403 http: 403
4 *
5 203.160.66.249 3.99 ms http: 403 http: 403
6 203.160.66.245 29.16 ms http: 403 http: 403
7 219.158.16.213 33.08 ms http: 403 http: 403
8 219.158.19.90 29.79 ms http: 403 http: 403
9 *
10 *
11 *
12 119.6.195.34 65.58 ms http: 403 http: 403
13 119.6.6.6 69.81 ms http: 403 http: 403
----------------------------------------------------------------------
上海移动
traceroute to 120.204.197.126 (120.204.197.126), 30 hops max, 32 byte packets
1 *
2 *
3 11.60.67.65 2.10 ms http: 403 http: 403
4 10.216.157.162 2.68 ms http: 403 http: 403
5 223.119.6.117 3.45 ms http: 403 http: 403
6 223.118.4.241 2.93 ms http: 403 http: 403
7 223.120.22.122 34.49 ms http: 403 http: 403
8 221.183.89.170 35.54 ms http: 403 http: 403
9 221.183.89.33 35.49 ms http: 403 http: 403
10 *
11 *
12 117.185.10.130 37.80 ms http: 403 http: 403
13 120.204.194.14 44.32 ms http: 403 http: 403
14 120.204.197.126 38.02 ms http: 403 http: 403
----------------------------------------------------------------------
成都移动
traceroute to 183.221.253.100 (183.221.253.100), 30 hops max, 32 byte packets
1 11.73.1.42 2.18 ms http: 403 http: 403
2 *
3 11.60.66.105 2.41 ms http: 403 http: 403
4 *
5 223.119.6.109 3.41 ms http: 403 http: 403
6 223.120.14.234 58.13 ms http: 403 http: 403
7 221.183.92.201 57.61 ms http: 403 http: 403
8 221.183.92.213 60.77 ms http: 403 http: 403
9 *
10 221.183.71.82 74.35 ms http: 403 http: 403
11 221.183.110.170 69.03 ms http: 403 http: 403
12 183.221.253.100 67.89 ms http: 403 http: 403
----------------------------------------------------------------------
成都教育网
traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 32 byte packets
1 11.73.1.42 1.77 ms http: 403 http: 403
2 *
3 11.60.67.249 2.16 ms http: 403 http: 403
4 *
5 101.203.70.81 3.45 ms http: 403 http: 403
6 *
7 *
8 softbank221110131230.bbtec.net (221.110.131.230) 4.55 ms http: 403 http: 403
9 HundredGE0-0-0-1.clbr02.hkg04.as3491.net (63.223.17.242) 56.29 ms http: 403 http: 403
10 tsingHua.hu0-0-0-9.clbr02.hkg04.as3491.net (63.218.115.14) 55.42 ms http: 403 http: 403
11 101.4.114.221 90.20 ms http: 403 http: 403
12 101.4.114.169 87.53 ms http: 403 http: 403
13 *
14 101.4.112.14 88.93 ms http: 403 http: 403
15 101.4.112.49 91.39 ms http: 403 http: 403
16 *
17 *
18 *
19 *
20 *
21 *
22 202.112.14.151 105.65 ms http: 403 http: 403
---------------------------------------------------AI评价
从提供的 traceroute 结果来看，回程路由（即数据包从目标地址返回源地址的路径）并没有显式显示出来。traceroute 命令默认显示的是从源地址到目标地址的数据包路径，但它并不直接显示回程路径。如果你想查看回程路由，通常需要另外执行一次 traceroute，并确定其返回的路径。
但是，我们可以从这些 traceroute 数据中提取一些有关网络结构的关键信息，以下是几条观察：
- 响应状态“http: 403”：
- 在所有的路由跳数中，都有出现“http: 403”错误，这表示目标服务器或中间的路由器拒绝了 HTTP 请求。这个错误通常是由于访问控制或防火墙策略导致的，意味着目标设备或网络不允许 traceroute 流量通过。这是一个可能的安全设置或网络策略限制。
- 丢包与跳数：
- 很多跳数（如第1、2、9、16跳等）出现了
*，表示这些节点没有回应。这可能是由于防火墙、ACL（访问控制列表）设置或其他安全机制阻止了这些 ICMP 请求。无回应并不一定意味着网络中断，通常这些跳数的设备选择不响应 ICMP 包，以提高安全性或减少资源占用。
- 很多跳数（如第1、2、9、16跳等）出现了
- 路由优化：
- 从不同城市（如广州、上海、厦门、成都等）的 traceroute 结果来看，网络路径上会经过一些大运营商（如电信、联通和移动等）分布式的交换设备。这意味着，在长途通信过程中，数据会在多个路由器和不同地区的网络节点间进行跳转。这种分布式设计有助于优化网络流量、避免瓶颈，并且通过冗余路径保证网络的可靠性。
- 中间节点的地理分布：
- 各地的 traceroute 数据中，数据包经过的节点都显示了不同的网络提供商，如“广州市电信”、“上海移动”等。数据流可能会通过不同的运营商间的互联网交换点，这可以说明不同地区的网络之间的互联性。不同的运营商之间互联也能影响最终数据包的延迟。
- 延迟与跳数：
- 延迟（例如最小延迟为1ms，最大延迟为105ms）和跳数反映了网络路径的物理距离和网络节点的处理能力。一般来说，电信运营商的网络设计和优先级策略会影响这一部分的表现，而每次跨越较远地理位置的跳数，延迟也会相应增加。
综上所述，尽管 traceroute 显示的是从源到目标的路径，但你无法直接获得回程路径的详细信息。若要全面分析回程路由，可能需要进一步的工具或使用如 ping 的反向测试来追踪。
流媒体
** 正在测试 IPv4 解锁情况
--------------------------------
** 您的网络为: Alibaba (8.209.*.*)
============[ Multination ]============
Dazn: Failed (Error: )
Disney+: No (IP Banned By Disney+ 1)
Netflix: Originals Only
YouTube Premium: Yes (Region: JP)
Amazon Prime Video: Yes (Region: JP)
TVBAnywhere+: Yes
Spotify Registration: Yes (Region: JP)
OneTrust Region: JP [Tokyo]
iQyi Oversea Region: JP
Bing Region: JP
Apple Region: JP
YouTube CDN: Failed (Network Connection)
Netflix Preferred CDN: Failed (CDN IP Not Found)
ChatGPT: Yes
Google Gemini: Yes (Region: JPN)
Claude: Yes
Wikipedia Editability: No
Google Play Store: Japan
Google Search CAPTCHA Free: Yes
Steam Currency: JPY
---Forum---
Reddit: No
=======================================
===============[ Japan ]===============
DMM: Yes
DMM TV: No
Abema.TV: No
Niconico: No (Official Live Unavailable. LiveID: lv346962279)
Telasa: Yes
U-NEXT: Yes
Hulu Japan: No
TVer: Yes
Lemino: Yes
AnimeFesta: No
WOWOW: No
VideoMarket: Yes
D Anime Store: No
FOD(Fuji TV): Yes
Radiko: Yes (City: TOKYO)
Karaoke@DAM: Yes
J:com On Demand: Yes
WATCHA: Yes
Rakuten TV JP: No
---Game---
Kancolle Japan: Failed (Network Connection)
Pretty Derby Japan: Failed (Network Connection)
Konosuba Fantastic Days: Yes
Princess Connect Re:Dive Japan: Failed (Network Connection)
Project Sekai: Colorful Stage: No
---Music---
Mora: Yes
music.jp: No
---Forum---
EroGameSpace: Failed (Network Connection)
=======================================
** 正在测试 IPv6 解锁情况
--------------------------------
** 您的网络为: Alibaba (240b:4009:25a:*:*)
============[ Multination ]============
Dazn: IPv6 Is Not Currently Supported
Disney+: IPv6 Is Not Currently Supported
Netflix: Originals Only
YouTube Premium: Yes (Region: JP)
Amazon Prime Video: IPv6 Is Not Currently Supported
TVBAnywhere+: IPv6 Is Not Currently Supported
Spotify Registration: Yes (Region: JP)
OneTrust Region: JP [Tokyo]
iQyi Oversea Region: IPv6 Is Not Currently Supported
Bing Region: JP
Apple Region: JP
YouTube CDN: Failed (Network Connection)
Netflix Preferred CDN: Failed (CDN IP Not Found)
ChatGPT: Failed (Network Connection)
Google Gemini: Yes (Region: JPN)
Claude: Yes
Wikipedia Editability: No
Google Play Store: Japan
Google Search CAPTCHA Free: No
Steam Currency: IPv6 Is Not Currently Supported
Tiktok Region: 【JP】(可能为IDC IP)
---Forum---
Reddit: IPv6 Is Not Currently Supported
=======================================
===============[ Japan ]===============
DMM: IPv6 Is Not Currently Supported
DMM TV: IPv6 Is Not Currently Supported
Abema.TV: IPv6 Is Not Currently Supported
Niconico: IPv6 Is Not Currently Supported
Telasa: No
U-NEXT: Yes
Hulu Japan: IPv6 Is Not Currently Supported
TVer: IPv6 Is Not Currently Supported
Lemino: No
AnimeFesta: Failed (Network Connection)
WOWOW: IPv6 Is Not Currently Supported
VideoMarket: IPv6 Is Not Currently Supported
D Anime Store: IPv6 Is Not Currently Supported
FOD(Fuji TV): IPv6 Is Not Currently Supported
Radiko: IPv6 Is Not Currently Supported
Karaoke@DAM: IPv6 Is Not Currently Supported
J:com On Demand: Yes
WATCHA: IPv6 Is Not Currently Supported
Rakuten TV JP: IPv6 Is Not Currently Supported
---Game---
Kancolle Japan: IPv6 Is Not Currently Supported
Pretty Derby Japan: Failed (Network Connection)
Konosuba Fantastic Days: IPv6 Is Not Currently Supported
Princess Connect Re:Dive Japan: IPv6 Is Not Currently Supported
Project Sekai: Colorful Stage: IPv6 Is Not Currently Supported
---Music---
Mora: IPv6 Is Not Currently Supported
music.jp: IPv6 Is Not Currently Supported
---Forum---
EroGameSpace: IPv6 Is Not Currently Supported
=======================================写在后面
经过博主使用下来的情况看，联通的使用感受非常好，ytp 4k瞬时拖拉。