VLESS server 2.27.71.53:443
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 5 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 | 400 ms | 628 ms | 2.27.71.53 | |
| Tunnel ok | 367 ms | 564 ms | 2.27.71.53 | |
| Tunnel ok | 356 ms | 626 ms | 2.27.71.53 | |
| Tunnel ok | 410 ms | 621 ms | 2.27.71.53 | |
| Tunnel ok | 398 ms | 611 ms | 2.27.71.53 |
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.