VLESS server 169.40.42.202:443
TCP / REALITY · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 03:45:16 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 169.40.42.202:443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 45.144.112.54
- Last verified handshake
- 547 ms
- Last verified HTTPS first byte
- 726 ms
- Download speed
- 2.98 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-13 19:58:47 UTC
- Recorded tunnel checks
- 24
- Successful tunnel checks
- 23
- Recorded tunnel success rate
- 95.8%
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 | 547 ms | 726 ms | 45.144.112.54 | |
| Tunnel ok | 633 ms | 814 ms | 45.144.112.54 | |
| Tunnel ok | 657 ms | 827 ms | 45.144.112.54 | |
| Tunnel ok | 524 ms | 695 ms | 45.144.112.54 | |
| Tunnel ok | 657 ms | 831 ms | 45.144.112.54 | |
| Tunnel ok | 539 ms | 729 ms | 45.144.112.54 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 604 ms | 775 ms | 45.144.112.54 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 676 ms | 848 ms | 45.144.112.54 | |
| Tunnel ok | 601 ms | 785 ms | 45.144.112.54 | |
| Tunnel ok | 3,690 ms | 4,125 ms | 45.144.112.54 | |
| Tunnel ok | 763 ms | 943 ms | 45.144.112.54 | |
| Tunnel ok | 693 ms | 892 ms | 45.144.112.54 | |
| Tunnel ok | 700 ms | 886 ms | 45.144.112.54 | |
| Tunnel ok | 718 ms | 899 ms | 45.144.112.54 | |
| Tunnel ok | 639 ms | 820 ms | 45.144.112.54 | |
| Tunnel ok | 566 ms | 965 ms | 45.144.112.54 | |
| Tunnel ok | 705 ms | 886 ms | 45.144.112.54 | |
| Tunnel ok | 915 ms | 1,451 ms | 45.144.112.54 | |
| Tunnel ok | 596 ms | 783 ms | 45.144.112.54 | |
| Tunnel ok | 618 ms | 806 ms | 45.144.112.54 | |
| Tunnel ok | 5,818 ms | 6,029 ms | 45.144.112.54 | |
| Tunnel ok | 682 ms | 859 ms | 45.144.112.54 | |
| Tunnel ok | 621 ms | 806 ms | 45.144.112.54 |
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.