VLESS server 162.55.242.208:2053
TCP / REALITY · 0xRadikal verified downloadable configs
TCP / REALITY · 0xRadikal verified downloadable configs
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.
Hover or focus a point for check details. Click or tap to keep them open.
Latest 9 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 | 449 ms | 649 ms | 162.55.242.208 | |
| Tunnel ok | 349 ms | 549 ms | 162.55.242.208 | |
| Tunnel ok | 358 ms | 545 ms | 162.55.242.208 | |
| Tunnel ok | 311 ms | 500 ms | 162.55.242.208 | |
| Tunnel ok | 335 ms | 525 ms | 162.55.242.208 | |
| Tunnel ok | 305 ms | 492 ms | 162.55.242.208 | |
| Tunnel ok | 341 ms | 536 ms | 162.55.242.208 | |
| Tunnel ok | 332 ms | 533 ms | 162.55.242.208 | |
| Tunnel ok | 286 ms | 464 ms | 162.55.242.208 |
No recorded checks match this filter.
If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.
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.