VLESS server hk3n.wxgqlfx.vip:35193
TCP / REALITY · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:08:29 UTC
Connection and verification
- Protocol
- VLESS
- Address
- hk3n.wxgqlfx.vip:35193
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 156.226.168.221
- Last verified handshake
- 1,590 ms
- Last verified HTTPS first byte
- 2,079 ms
- Download speed
- Not measured
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-14 08:33:10 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 25 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 | 1,590 ms | 2,079 ms | 156.226.168.221 | |
| Tunnel ok | 1,298 ms | 1,795 ms | 156.226.168.221 | |
| Tunnel ok | 1,057 ms | 1,546 ms | 156.226.168.221 | |
| Tunnel ok | 1,662 ms | 2,336 ms | 156.226.168.221 | |
| Tunnel ok | 8,006 ms | 12,747 ms | 156.226.168.221 | |
| Tunnel ok | 3,694 ms | 4,260 ms | 156.226.168.221 | |
| Tunnel ok | 9,325 ms | 13,257 ms | 156.226.168.221 | |
| Tunnel ok | 1,426 ms | 3,812 ms | 156.226.168.221 | |
| Tunnel ok | 5,755 ms | 6,555 ms | 156.226.168.221 | |
| Tunnel ok | 4,359 ms | 6,684 ms | 156.226.168.221 | |
| Tunnel ok | 1,235 ms | 1,735 ms | 156.226.168.221 | |
| Tunnel ok | 2,388 ms | 2,975 ms | 156.226.168.221 | |
| Tunnel ok | 1,239 ms | 1,811 ms | 156.226.168.221 | |
| Tunnel ok | 7,058 ms | 8,357 ms | 156.226.168.221 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 8,755 ms | 16,731 ms | 156.226.168.221 | |
| Tunnel ok | 1,425 ms | 2,018 ms | 156.226.168.221 | |
| Tunnel ok | 1,211 ms | 1,806 ms | 156.226.168.221 | |
| Tunnel ok | 2,340 ms | 2,934 ms | 156.226.168.221 | |
| Tunnel ok | 2,188 ms | 3,485 ms | 156.226.168.221 | |
| Tunnel ok | 1,408 ms | 2,001 ms | 156.226.168.221 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 3,044 ms | 3,893 ms | 156.226.168.221 | |
| Tunnel ok | 1,533 ms | 2,129 ms | 156.226.168.221 | |
| Tunnel ok | 1,141 ms | 1,670 ms | 156.226.168.221 |
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.