Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:39:40 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
570 ms
Last verified HTTPS first byte
738 ms
Download speed
4.938 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-15 22:58:22 UTC
Recorded tunnel checks
18
Successful tunnel checks
18
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)
35980 09-15 22:5810-09 06:39Check time (UTC)
HTTPS first byte (ms)
62310 09-15 22:5810-09 06:39Check time (UTC)

Check history

Latest 19 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 ok570 ms738 ms185.195.57.171
Tunnel ok745 ms923 ms185.195.57.171
Preflight okNot measuredNot measuredNot verified
Tunnel ok658 ms828 ms185.195.57.171
Tunnel ok647 ms819 ms185.195.57.171
Tunnel ok577 ms747 ms185.195.57.171
Tunnel ok615 ms794 ms185.195.57.171
Tunnel ok581 ms757 ms185.195.57.171
Tunnel ok558 ms735 ms185.195.57.171
Tunnel ok536 ms710 ms185.195.57.171
Tunnel ok580 ms759 ms185.195.57.171
Tunnel ok3,598 ms6,231 ms185.195.57.171
Tunnel ok598 ms769 ms185.195.57.171
Tunnel ok636 ms805 ms185.195.57.171
Tunnel ok610 ms844 ms185.195.57.171
Tunnel ok616 ms795 ms185.195.57.171
Tunnel ok619 ms801 ms185.195.57.171
Tunnel ok706 ms896 ms185.195.57.171
Tunnel ok702 ms890 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.