VLESS server 169.40.42.235:443
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-25 01:28:55 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.235:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 185.195.57.170
- Last verified handshake
- 674 ms
- Last verified HTTPS first byte
- 853 ms
- Download speed
- 4.579 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-10-15 07:44:06 UTC
- Recorded tunnel checks
- 8
- Successful tunnel checks
- 8
- 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.
Check history
Latest 8 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 674 ms | 853 ms | 185.195.57.170 | |
| Tunnel ok | 564 ms | 743 ms | 185.195.57.170 | |
| Tunnel ok | 657 ms | 830 ms | 185.195.57.170 | |
| Tunnel ok | 600 ms | 776 ms | 185.195.57.170 | |
| Tunnel ok | 688 ms | 863 ms | 185.195.57.170 | |
| Tunnel ok | 723 ms | 901 ms | 185.195.57.170 | |
| Tunnel ok | 3,610 ms | 3,792 ms | 185.195.57.170 | |
| Tunnel ok | 674 ms | 845 ms | 185.195.57.170 |
No recorded checks match this filter.
How to use this VLESS configuration
- Download the current configuration while a fresh verification is available.
- Import it into a VLESS-compatible client, preserving all required transport, security and authentication parameters.
- 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.