Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 04:24:15 UTC

Connection and verification

Protocol
VLESS
Address
169.40.42.225:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.176
Last verified handshake
517 ms
Last verified HTTPS first byte
686 ms
Download speed
4.627 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-30 06:07:46 UTC
Recorded tunnel checks
10
Successful tunnel checks
10
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)
14630 09-30 06:0710-09 04:24Check time (UTC)
HTTPS first byte (ms)
16570 09-30 06:0710-09 04:24Check time (UTC)

Check history

Latest 10 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 ok517 ms686 ms185.195.57.176
Tunnel ok745 ms919 ms185.195.57.176
Tunnel ok597 ms774 ms185.195.57.176
Tunnel ok522 ms694 ms185.195.57.176
Tunnel ok533 ms706 ms185.195.57.176
Tunnel ok1,463 ms1,657 ms185.195.57.176
Tunnel ok536 ms712 ms185.195.57.176
Tunnel ok618 ms788 ms185.195.57.176
Tunnel ok644 ms813 ms185.195.57.176
Tunnel ok583 ms750 ms185.195.57.176

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.