VLESS server 185.253.96.117: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 8 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 | 384 ms | 582 ms | 185.253.96.117 | |
| Tunnel ok | 387 ms | 589 ms | 185.253.96.117 | |
| Tunnel ok | 368 ms | 561 ms | 185.253.96.117 | |
| Tunnel ok | 411 ms | 601 ms | 185.253.96.117 | |
| Tunnel ok | 359 ms | 557 ms | 185.253.96.117 | |
| Tunnel ok | 858 ms | 1,154 ms | 185.253.96.117 | |
| Tunnel ok | 495 ms | 734 ms | 185.253.96.117 | |
| Tunnel ok | 413 ms | 619 ms | 185.253.96.117 |
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.