VLESS server 169.40.42.179:443
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 05:38:15 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.179:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 185.195.57.174
- Last verified handshake
- 642 ms
- Last verified HTTPS first byte
- 811 ms
- Download speed
- 4.951 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 19:29:53 UTC
- Recorded tunnel checks
- 21
- Successful tunnel checks
- 21
- 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 21 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 | 642 ms | 811 ms | 185.195.57.174 | |
| Tunnel ok | 658 ms | 839 ms | 185.195.57.174 | |
| Tunnel ok | 666 ms | 837 ms | 185.195.57.174 | |
| Tunnel ok | 528 ms | 700 ms | 185.195.57.174 | |
| Tunnel ok | 537 ms | 712 ms | 185.195.57.174 | |
| Tunnel ok | 2,457 ms | 2,631 ms | 185.195.57.174 | |
| Tunnel ok | 578 ms | 751 ms | 185.195.57.174 | |
| Tunnel ok | 2,079 ms | 2,370 ms | 185.195.57.174 | |
| Tunnel ok | 660 ms | 835 ms | 185.195.57.174 | |
| Tunnel ok | 705 ms | 896 ms | 185.195.57.174 | |
| Tunnel ok | 1,878 ms | 2,116 ms | 185.195.57.174 | |
| Tunnel ok | 648 ms | 841 ms | 185.195.57.174 | |
| Tunnel ok | 625 ms | 817 ms | 185.195.57.174 | |
| Tunnel ok | 542 ms | 721 ms | 185.195.57.174 | |
| Tunnel ok | 609 ms | 786 ms | 185.195.57.174 | |
| Tunnel ok | 735 ms | 937 ms | 185.195.57.174 | |
| Tunnel ok | 625 ms | 817 ms | 185.195.57.174 | |
| Tunnel ok | 1,127 ms | 1,317 ms | 185.195.57.174 | |
| Tunnel ok | 593 ms | 783 ms | 185.195.57.174 | |
| Tunnel ok | 598 ms | 781 ms | 185.195.57.174 | |
| Tunnel ok | 621 ms | 803 ms | 185.195.57.174 |
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.