Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 04:48:54 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
799 ms
Last verified HTTPS first byte
1,335 ms
Download speed
2.106 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-26 10:23:13 UTC
Recorded tunnel checks
14
Successful tunnel checks
13
Recorded tunnel success rate
92.9%

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)
115190 09-26 10:2310-09 04:48Check time (UTC)
HTTPS first byte (ms)
123800 09-26 10:2310-09 04:48Check time (UTC)

Check history

Latest 14 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 ok799 ms1,335 ms217.217.254.126
Tunnel ok839 ms1,350 ms217.217.254.126
Tunnel ok891 ms1,388 ms217.217.254.126
Tunnel ok766 ms1,242 ms217.217.254.126
Tunnel ok1,214 ms1,758 ms217.217.254.126
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,061 ms1,605 ms217.217.254.126
Tunnel ok775 ms1,259 ms217.217.254.126
Tunnel ok737 ms1,211 ms217.217.254.126
Tunnel ok743 ms1,701 ms217.217.254.126
Tunnel ok763 ms1,293 ms217.217.254.126
Tunnel ok11,519 ms12,380 ms217.217.254.126
Tunnel ok833 ms1,543 ms217.217.254.126
Tunnel ok827 ms1,358 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.