VLESS server 162.159.254.3:443
WEBSOCKET / TLS · rjsxrd secure tunnel-tested configs
Inactive — did not pass verificationLast result: 2026-10-08 14:09:16 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.
Connection and verification
- Protocol
- VLESS
- Address
- 162.159.254.3:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 158.101.158.101
- Last verified handshake
- 4,730 ms
- Last verified HTTPS first byte
- 18,295 ms
- Download speed
- Not measured
- Source
- rjsxrd secure tunnel-tested configs
- First recorded check
- 2026-09-19 07:27:35 UTC
- Recorded tunnel checks
- 13
- Successful tunnel checks
- 11
- Recorded tunnel success rate
- 84.6%
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 15 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 | 4,730 ms | 18,295 ms | 158.101.158.101 | |
| Tunnel ok | 5,181 ms | 5,781 ms | 158.101.158.101 | |
| Tunnel ok | 3,550 ms | 4,263 ms | 158.101.158.101 | |
| Tunnel ok | 3,960 ms | 5,443 ms | 158.101.158.101 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,226 ms | 2,730 ms | 158.101.158.101 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 4,179 ms | 4,954 ms | 158.101.158.101 | |
| Tunnel ok | 1,063 ms | 1,575 ms | 158.101.158.101 | |
| Tunnel ok | 1,392 ms | 2,642 ms | 158.101.158.101 | |
| Tunnel ok | 1,470 ms | 1,977 ms | 158.101.158.101 | |
| Tunnel ok | 1,754 ms | 2,254 ms | 158.101.158.101 | |
| Tunnel ok | 1,398 ms | 1,901 ms | 158.101.158.101 |
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.