Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:37:46 UTC

Connection and verification

Protocol
VLESS
Address
169.40.42.16:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.177
Last verified handshake
585 ms
Last verified HTTPS first byte
756 ms
Download speed
2.746 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-14 21:23:00 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)
59070 09-14 21:2310-09 06:37Check time (UTC)
HTTPS first byte (ms)
62130 09-14 21:2310-09 06:37Check 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 ok585 ms756 ms185.195.57.177
Tunnel ok5,907 ms6,213 ms185.195.57.177
Tunnel ok647 ms821 ms185.195.57.177
Tunnel ok601 ms776 ms185.195.57.177
Tunnel ok834 ms1,023 ms185.195.57.177
Tunnel ok1,248 ms1,510 ms185.195.57.177
Tunnel ok638 ms822 ms185.195.57.177
Tunnel ok600 ms770 ms185.195.57.177
Tunnel ok540 ms713 ms185.195.57.177
Tunnel ok530 ms707 ms185.195.57.177
Tunnel ok5,244 ms5,414 ms185.195.57.177
Policy blockedNot measuredNot measuredNot verified
Tunnel ok713 ms910 ms185.195.57.177
Tunnel ok576 ms758 ms185.195.57.177
Tunnel ok574 ms763 ms185.195.57.177
Tunnel ok1,832 ms2,071 ms185.195.57.177
Tunnel ok549 ms731 ms185.195.57.177
Tunnel ok548 ms732 ms185.195.57.177

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.