VLESS server 169.40.42.212:443
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:38:31 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.212:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 185.195.57.170
- Last verified handshake
- 656 ms
- Last verified HTTPS first byte
- 936 ms
- Download speed
- 3.413 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 20:02:50 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 26 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 | 656 ms | 936 ms | 185.195.57.170 | |
| Tunnel ok | 713 ms | 884 ms | 185.195.57.170 | |
| Tunnel ok | 588 ms | 760 ms | 185.195.57.170 | |
| Tunnel ok | 559 ms | 761 ms | 185.195.57.170 | |
| Tunnel ok | 638 ms | 811 ms | 185.195.57.170 | |
| Tunnel ok | 649 ms | 822 ms | 185.195.57.170 | |
| Tunnel ok | 5,927 ms | 6,098 ms | 185.195.57.170 | |
| Tunnel ok | 633 ms | 804 ms | 185.195.57.170 | |
| Tunnel ok | 663 ms | 842 ms | 185.195.57.170 | |
| Tunnel ok | 528 ms | 695 ms | 185.195.57.170 | |
| Tunnel ok | 663 ms | 841 ms | 185.195.57.170 | |
| Tunnel ok | 919 ms | 1,087 ms | 185.195.57.170 | |
| Tunnel ok | 582 ms | 922 ms | 185.195.57.170 | |
| Tunnel ok | 530 ms | 698 ms | 185.195.57.170 | |
| Tunnel ok | 573 ms | 742 ms | 185.195.57.170 | |
| Tunnel ok | 552 ms | 732 ms | 185.195.57.170 | |
| Tunnel ok | 542 ms | 720 ms | 185.195.57.170 | |
| Tunnel ok | 742 ms | 1,012 ms | 185.195.57.170 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,748 ms | 1,924 ms | 185.195.57.170 | |
| Tunnel ok | 684 ms | 866 ms | 185.195.57.170 | |
| Tunnel ok | 1,903 ms | 2,553 ms | 185.195.57.170 | |
| Tunnel ok | 691 ms | 880 ms | 185.195.57.170 | |
| Tunnel ok | 662 ms | 858 ms | 185.195.57.170 | |
| Tunnel ok | 578 ms | 766 ms | 185.195.57.170 | |
| Tunnel ok | 571 ms | 758 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.