Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:28:25 UTC

Connection and verification

Protocol
VLESS
Address
217.217.254.126:2053
Transport / security
TCP / REALITY
Last verified exit IP
217.217.254.126
Last verified handshake
825 ms
Last verified HTTPS first byte
1,335 ms
Download speed
2.809 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-15 22:22:44 UTC
Recorded tunnel checks
18
Successful tunnel checks
18
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)
15170 09-15 22:2210-09 06:28Check time (UTC)
HTTPS first byte (ms)
19910 09-15 22:2210-09 06:28Check time (UTC)

Check history

Latest 18 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 ok825 ms1,335 ms217.217.254.126
Tunnel ok1,017 ms1,683 ms217.217.254.126
Tunnel ok1,188 ms1,708 ms217.217.254.126
Tunnel ok1,017 ms1,589 ms217.217.254.126
Tunnel ok816 ms1,304 ms217.217.254.126
Tunnel ok1,082 ms1,652 ms217.217.254.126
Tunnel ok1,089 ms1,640 ms217.217.254.126
Tunnel ok759 ms1,231 ms217.217.254.126
Tunnel ok787 ms1,291 ms217.217.254.126
Tunnel ok767 ms1,254 ms217.217.254.126
Tunnel ok753 ms1,234 ms217.217.254.126
Tunnel ok1,517 ms1,991 ms217.217.254.126
Tunnel ok934 ms1,556 ms217.217.254.126
Tunnel ok902 ms1,401 ms217.217.254.126
Tunnel ok1,092 ms1,675 ms217.217.254.126
Tunnel ok741 ms1,235 ms217.217.254.126
Tunnel ok745 ms1,230 ms217.217.254.126
Tunnel ok713 ms1,173 ms217.217.254.126

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.