Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 07:08:59 UTC

Connection and verification

Protocol
VLESS
Address
169.40.42.89:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.175
Last verified handshake
918 ms
Last verified HTTPS first byte
1,114 ms
Download speed
2.684 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-16 04:23:01 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)
69530 09-16 04:2310-09 07:08Check time (UTC)
HTTPS first byte (ms)
81420 09-16 04:2310-09 07:08Check 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 ok918 ms1,114 ms185.195.57.175
Tunnel ok6,953 ms8,142 ms185.195.57.175
Tunnel ok642 ms813 ms185.195.57.175
Tunnel ok547 ms723 ms185.195.57.175
Tunnel ok635 ms812 ms185.195.57.175
Tunnel ok583 ms760 ms185.195.57.175
Tunnel ok646 ms819 ms185.195.57.175
Tunnel ok533 ms704 ms185.195.57.175
Tunnel ok663 ms845 ms185.195.57.175
Tunnel ok533 ms712 ms185.195.57.175
Policy blockedNot measuredNot measuredNot verified
Tunnel ok608 ms835 ms185.195.57.175
Tunnel ok611 ms796 ms185.195.57.175
Tunnel ok556 ms741 ms185.195.57.175
Tunnel ok630 ms814 ms185.195.57.175
Tunnel ok706 ms886 ms185.195.57.175
Tunnel ok551 ms731 ms185.195.57.175
Tunnel ok623 ms804 ms185.195.57.175

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.