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

Connection and verification

Protocol
VLESS
Address
169.40.42.133:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.171
Last verified handshake
637 ms
Last verified HTTPS first byte
806 ms
Download speed
3.591 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-13 17:17:32 UTC
Recorded tunnel checks
20
Successful tunnel checks
20
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)
86040 09-13 17:1710-09 05:38Check time (UTC)
HTTPS first byte (ms)
89630 09-13 17:1710-09 05:38Check time (UTC)

Check history

Latest 20 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 ok637 ms806 ms185.195.57.171
Tunnel ok558 ms760 ms185.195.57.171
Tunnel ok668 ms840 ms185.195.57.171
Tunnel ok617 ms821 ms185.195.57.171
Tunnel ok582 ms765 ms185.195.57.171
Tunnel ok2,482 ms2,735 ms185.195.57.171
Tunnel ok646 ms816 ms185.195.57.171
Tunnel ok8,604 ms8,963 ms185.195.57.171
Tunnel ok535 ms706 ms185.195.57.171
Tunnel ok645 ms815 ms185.195.57.171
Tunnel ok578 ms747 ms185.195.57.171
Tunnel ok3,080 ms3,412 ms185.195.57.171
Tunnel ok645 ms814 ms185.195.57.171
Tunnel ok627 ms809 ms185.195.57.171
Tunnel ok609 ms792 ms185.195.57.171
Tunnel ok675 ms853 ms185.195.57.171
Tunnel ok555 ms737 ms185.195.57.171
Tunnel ok682 ms1,097 ms185.195.57.171
Tunnel ok698 ms935 ms185.195.57.171
Tunnel ok1,271 ms1,520 ms185.195.57.171

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.