VLESS server 169.40.42.232:443
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:24:58 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.232:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 185.195.57.172
- Last verified handshake
- 584 ms
- Last verified HTTPS first byte
- 755 ms
- Download speed
- 4.314 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-15 04:38:16 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.
Check history
Latest 24 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 | 584 ms | 755 ms | 185.195.57.172 | |
| Tunnel ok | 530 ms | 701 ms | 185.195.57.172 | |
| Tunnel ok | 532 ms | 908 ms | 185.195.57.172 | |
| Tunnel ok | 663 ms | 839 ms | 185.195.57.172 | |
| Tunnel ok | 672 ms | 843 ms | 185.195.57.172 | |
| Tunnel ok | 548 ms | 728 ms | 185.195.57.172 | |
| Tunnel ok | 1,258 ms | 1,431 ms | 185.195.57.172 | |
| Tunnel ok | 530 ms | 704 ms | 185.195.57.172 | |
| Tunnel ok | 613 ms | 784 ms | 185.195.57.172 | |
| Tunnel ok | 653 ms | 829 ms | 185.195.57.172 | |
| Tunnel ok | 749 ms | 953 ms | 185.195.57.172 | |
| Tunnel ok | 798 ms | 991 ms | 185.195.57.172 | |
| Tunnel ok | 536 ms | 891 ms | 185.195.57.172 | |
| Tunnel ok | 531 ms | 712 ms | 185.195.57.172 | |
| Tunnel ok | 671 ms | 859 ms | 185.195.57.172 | |
| Tunnel ok | 1,628 ms | 2,032 ms | 185.195.57.172 | |
| Tunnel ok | 2,085 ms | 2,273 ms | 185.195.57.172 | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified |
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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.