VLESS server 169.40.42.229:443
TCP / REALITY · Au1rxx verified downloadable configs
Inactive — did not pass verificationLast result: 2026-10-08 23:24:24 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.229:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 162.120.69.84
- Last verified handshake
- 655 ms
- Last verified HTTPS first byte
- 838 ms
- Download speed
- 1.86 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-14 04:38:23 UTC
- Recorded tunnel checks
- 18
- Successful tunnel checks
- 18
- 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 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 655 ms | 838 ms | 162.120.69.84 | |
| Tunnel ok | 707 ms | 880 ms | 162.120.69.84 | |
| Tunnel ok | 2,432 ms | 2,606 ms | 162.120.69.84 | |
| Tunnel ok | 650 ms | 842 ms | 162.120.69.84 | |
| Tunnel ok | 994 ms | 1,394 ms | 162.120.69.84 | |
| Tunnel ok | 893 ms | 1,069 ms | 162.120.69.84 | |
| Tunnel ok | 1,508 ms | 2,023 ms | 162.120.69.84 | |
| Tunnel ok | 651 ms | 846 ms | 162.120.69.84 | |
| Tunnel ok | 985 ms | 1,879 ms | 162.120.69.84 | |
| Tunnel ok | 1,302 ms | 1,522 ms | 162.120.69.84 | |
| Tunnel ok | 2,426 ms | 2,645 ms | 162.120.69.84 | |
| Tunnel ok | 560 ms | 746 ms | 162.120.69.84 | |
| Tunnel ok | 586 ms | 774 ms | 162.120.69.84 | |
| Tunnel ok | 688 ms | 873 ms | 162.120.69.84 | |
| Tunnel ok | 642 ms | 855 ms | 162.120.69.84 | |
| Tunnel ok | 555 ms | 742 ms | 162.120.69.84 | |
| Tunnel ok | 905 ms | 1,102 ms | 162.120.69.84 | |
| Tunnel ok | 747 ms | 927 ms | 162.120.69.84 |
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.