VLESS server 169.40.42.173:443
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 07:28:27 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.173:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 185.195.57.173
- Last verified handshake
- 3,752 ms
- Last verified HTTPS first byte
- 4,132 ms
- Download speed
- 2.694 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 19:22:52 UTC
- Recorded tunnel checks
- 25
- Successful tunnel checks
- 25
- 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 27 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 | 3,752 ms | 4,132 ms | 185.195.57.173 | |
| Tunnel ok | 823 ms | 1,025 ms | 185.195.57.173 | |
| Tunnel ok | 11,850 ms | 14,489 ms | 185.195.57.173 | |
| Tunnel ok | 593 ms | 775 ms | 185.195.57.173 | |
| Tunnel ok | 555 ms | 730 ms | 185.195.57.173 | |
| Tunnel ok | 3,395 ms | 3,605 ms | 185.195.57.173 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 813 ms | 1,112 ms | 185.195.57.173 | |
| Tunnel ok | 552 ms | 720 ms | 185.195.57.173 | |
| Tunnel ok | 662 ms | 829 ms | 185.195.57.173 | |
| Tunnel ok | 552 ms | 731 ms | 185.195.57.173 | |
| Tunnel ok | 673 ms | 864 ms | 185.195.57.173 | |
| Tunnel ok | 573 ms | 907 ms | 185.195.57.173 | |
| Tunnel ok | 652 ms | 822 ms | 185.195.57.173 | |
| Tunnel ok | 810 ms | 977 ms | 185.195.57.173 | |
| Tunnel ok | 609 ms | 788 ms | 185.195.57.173 | |
| Tunnel ok | 687 ms | 869 ms | 185.195.57.173 | |
| Tunnel ok | 645 ms | 830 ms | 185.195.57.173 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Tunnel ok | 539 ms | 716 ms | 185.195.57.173 | |
| Tunnel ok | 1,266 ms | 1,449 ms | 185.195.57.173 | |
| Tunnel ok | 701 ms | 885 ms | 185.195.57.173 | |
| Tunnel ok | 564 ms | 750 ms | 185.195.57.173 | |
| Tunnel ok | 940 ms | 1,134 ms | 185.195.57.173 | |
| Tunnel ok | 672 ms | 898 ms | 185.195.57.173 | |
| Tunnel ok | 821 ms | 1,012 ms | 185.195.57.173 | |
| Tunnel ok | 562 ms | 746 ms | 185.195.57.173 |
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.