Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 05:38:57 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
809 ms
Last verified HTTPS first byte
1,278 ms
Download speed
2.039 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-18 10:07:01 UTC
Recorded tunnel checks
21
Successful tunnel checks
21
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)
27860 09-18 10:0710-09 05:38Check time (UTC)
HTTPS first byte (ms)
34220 09-18 10:0710-09 05:38Check time (UTC)

Check history

Latest 21 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 ok809 ms1,278 ms217.217.254.126
Tunnel ok765 ms1,301 ms217.217.254.126
Tunnel ok1,158 ms1,632 ms217.217.254.126
Tunnel ok1,041 ms1,541 ms217.217.254.126
Tunnel ok823 ms1,361 ms217.217.254.126
Tunnel ok747 ms1,300 ms217.217.254.126
Tunnel ok764 ms1,252 ms217.217.254.126
Tunnel ok858 ms1,354 ms217.217.254.126
Tunnel ok939 ms1,553 ms217.217.254.126
Tunnel ok909 ms1,555 ms217.217.254.126
Tunnel ok774 ms1,250 ms217.217.254.126
Tunnel ok828 ms1,311 ms217.217.254.126
Tunnel ok928 ms1,467 ms217.217.254.126
Tunnel ok2,140 ms2,657 ms217.217.254.126
Tunnel ok2,106 ms2,614 ms217.217.254.126
Tunnel ok772 ms1,330 ms217.217.254.126
Tunnel ok871 ms1,380 ms217.217.254.126
Tunnel ok1,877 ms2,539 ms217.217.254.126
Tunnel ok2,786 ms3,422 ms217.217.254.126
Tunnel ok784 ms1,276 ms217.217.254.126
Tunnel ok761 ms1,265 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.