Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 01:57:12 UTC

Connection and verification

Protocol
VLESS
Address
t9.qifei.app:443
Transport / security
TCP / REALITY
Last verified exit IP
153.121.36.102
Last verified handshake
1,151 ms
Last verified HTTPS first byte
1,583 ms
Download speed
3.093 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-10-05 05:53:27 UTC
Recorded tunnel checks
5
Successful tunnel checks
5
Recorded tunnel success rate
100.0%

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)
48450 10-05 05:5310-09 01:57Check time (UTC)
HTTPS first byte (ms)
64200 10-05 05:5310-09 01:57Check time (UTC)

Check history

Latest 5 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
Tunnel ok1,151 ms1,583 ms153.121.36.102
Tunnel ok1,162 ms1,655 ms153.121.36.102
Tunnel ok1,109 ms1,574 ms153.121.36.102
Tunnel ok4,845 ms6,420 ms153.121.36.102
Tunnel ok4,076 ms4,541 ms153.121.36.102

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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.