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

Connection and verification

Protocol
VLESS
Address
66.70.179.198:2053
Transport / security
TCP / REALITY
Last verified exit IP
66.70.179.198
Last verified handshake
1,296 ms
Last verified HTTPS first byte
1,532 ms
Download speed
1.911 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-22 11:18:44 UTC
Recorded tunnel checks
17
Successful tunnel checks
17
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)
21500 09-22 11:1810-09 05:39Check time (UTC)
HTTPS first byte (ms)
26510 09-22 11:1810-09 05:39Check 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 ok1,296 ms1,532 ms66.70.179.198
Tunnel ok623 ms845 ms66.70.179.198
Tunnel ok627 ms851 ms66.70.179.198
Tunnel ok622 ms850 ms66.70.179.198
Tunnel ok634 ms865 ms66.70.179.198
Tunnel ok856 ms1,140 ms66.70.179.198
Tunnel ok616 ms839 ms66.70.179.198
Preflight okNot measuredNot measuredNot verified
Tunnel ok656 ms897 ms66.70.179.198
Tunnel ok683 ms1,009 ms66.70.179.198
Tunnel ok638 ms858 ms66.70.179.198
Tunnel ok748 ms1,150 ms66.70.179.198
Tunnel ok634 ms860 ms66.70.179.198
Tunnel ok2,150 ms2,651 ms66.70.179.198
Tunnel ok2,060 ms2,340 ms66.70.179.198
Tunnel ok618 ms863 ms66.70.179.198
Tunnel ok631 ms836 ms66.70.179.198
Tunnel ok641 ms860 ms66.70.179.198

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.