Skip to main content
Tunnel verified at last checkLast result: 2026-10-22 15:28:24 UTC

Connection and verification

Protocol
VLESS
Address
hinet1.2yly.com:24215
Transport / security
TCP / REALITY
Last verified exit IP
61.230.160.34
Last verified handshake
2,560 ms
Last verified HTTPS first byte
3,149 ms
Download speed
1.173 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-14 01:55:16 UTC
Recorded tunnel checks
27
Successful tunnel checks
25
Recorded tunnel success rate
92.6%

Handshake is tunnel setup time; HTTPS first byte includes the request through that tunnel. Neither is an ICMP ping or a bandwidth measurement. The success rate covers stored full-tunnel attempts only; it is not continuous uptime.

Performance history

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
85310 09-14 01:5510-21 09:56Check time (UTC)
HTTPS first byte (ms)
91510 09-14 01:5510-21 09:56Check time (UTC)

Check history

Latest 34 stored checks, up to 100 per configuration. Checks belong to this configuration’s stable public ID; different configurations on the same host have separate histories. Preflight and policy results do not count as successful tunnels.

Recorded VLESS checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Policy blockedNot measuredNot measuredNot verified
Tunnel ok2,560 ms3,149 ms61.230.160.34
Tunnel ok4,538 ms5,241 ms61.230.160.34
Tunnel ok1,382 ms1,929 ms61.230.160.34
Tunnel ok1,374 ms1,987 ms118.167.219.24
Tunnel ok1,472 ms2,111 ms118.167.248.243
Tunnel ok1,511 ms3,234 ms118.167.248.243
Tunnel ok2,624 ms3,260 ms61.230.162.88
Tunnel ok2,388 ms3,003 ms61.230.162.88
Policy blockedNot measuredNot measuredNot verified
Preflight okNot measuredNot measuredNot verified
Tunnel ok8,531 ms9,151 ms61.230.172.241
Policy blockedNot measuredNot measuredNot verified
Tunnel ok4,093 ms4,667 ms118.167.235.241
Tunnel ok2,253 ms2,932 ms118.167.235.241
Tunnel ok4,102 ms5,564 ms118.167.235.241
Policy blockedNot measuredNot measuredNot verified
Tunnel ok1,694 ms2,365 ms118.167.207.194
Tunnel ok1,171 ms1,711 ms118.167.207.194
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok2,130 ms2,663 ms118.167.230.191
Tunnel ok1,465 ms2,031 ms118.167.230.191
Tunnel ok1,030 ms1,547 ms118.167.206.152
Tunnel ok3,081 ms3,871 ms118.167.206.152
Tunnel ok830 ms1,373 ms118.167.206.152
Tunnel ok1,390 ms1,894 ms118.167.246.43
Tunnel ok1,210 ms1,733 ms118.167.246.43
Tunnel ok965 ms1,472 ms118.167.246.43
Policy blockedNot measuredNot measuredNot verified
Tunnel ok4,984 ms6,133 ms118.167.212.163
Tunnel ok1,590 ms2,172 ms118.167.212.163
Policy blockedNot measuredNot measuredNot verified
Tunnel ok1,555 ms2,067 ms118.167.209.5

How to use this VLESS configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VLESS-compatible client, preserving all required transport, security and authentication parameters.
  3. Connect and verify your connection with the IP tool and VPN leak test.

If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.

What does a successful check prove?

The external checker completed a VLESS tunnel, carried an HTTPS request and verified a changed public exit IP. This measures technical availability at that time, not the operator’s trustworthiness or performance from your network.

Read the VLESS guide, our checking methodology and public VPN risks.