Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 21:38:11 UTC

Connection and verification

Protocol
VLESS
Address
uae.unixzone.us:22573
Transport / security
WEBSOCKET / NONE
Last verified exit IP
84.235.244.108
Last verified handshake
1,128 ms
Last verified HTTPS first byte
1,573 ms
Download speed
3.262 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-21 12:38:42 UTC
Recorded tunnel checks
13
Successful tunnel checks
13
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)
16150 09-23 00:2010-08 21:38Check time (UTC)
HTTPS first byte (ms)
21950 09-23 00:2010-08 21:38Check 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 ok1,128 ms1,573 ms84.235.244.108
Tunnel ok1,611 ms2,040 ms84.235.244.108
Tunnel ok1,158 ms1,603 ms84.235.244.108
Tunnel ok1,054 ms1,487 ms84.235.244.108
Tunnel ok1,615 ms2,195 ms84.235.244.108
Tunnel ok954 ms1,398 ms84.235.244.108
Tunnel ok1,089 ms1,513 ms84.235.244.108
Tunnel ok956 ms1,386 ms84.235.244.108
Tunnel ok1,369 ms1,790 ms84.235.244.108
Tunnel ok1,264 ms1,697 ms84.235.244.108
Tunnel ok1,240 ms1,681 ms84.235.244.108
Tunnel ok1,125 ms1,570 ms84.235.244.108
Tunnel ok1,170 ms1,604 ms84.235.244.108
Unsupported checkerNot measuredNot measuredNot verified

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.