VLESS server 104.16.10.185:443
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-23 07:56:50 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 104.16.10.185:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 158.101.158.101
- Last verified handshake
- 1,263 ms
- Last verified HTTPS first byte
- 1,692 ms
- Download speed
- 1.349 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-26 09:19:58 UTC
- Recorded tunnel checks
- 21
- Successful tunnel checks
- 17
- Recorded tunnel success rate
- 81.0%
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 |
|---|---|---|---|---|
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,263 ms | 1,692 ms | 158.101.158.101 | |
| Tunnel ok | 2,609 ms | 3,078 ms | 158.101.158.101 | |
| Tunnel ok | 2,096 ms | 2,911 ms | 158.101.158.101 | |
| Tunnel ok | 2,279 ms | 3,381 ms | 158.101.158.101 | |
| Tunnel ok | 1,001 ms | 1,852 ms | 158.101.158.101 | |
| Tunnel ok | 3,269 ms | 3,850 ms | 158.101.158.101 | |
| Tunnel ok | 1,916 ms | 2,391 ms | 158.101.158.101 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,068 ms | 1,485 ms | 158.101.158.101 | |
| Timeout | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,834 ms | 3,319 ms | 158.101.158.101 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 3,495 ms | 3,916 ms | 158.101.158.101 | |
| Tunnel ok | 3,644 ms | 4,825 ms | 158.101.158.101 | |
| Tunnel ok | 2,249 ms | 2,727 ms | 158.101.158.101 | |
| Tunnel ok | 2,849 ms | 3,298 ms | 158.101.158.101 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,522 ms | 2,981 ms | 158.101.158.101 | |
| Tunnel ok | 4,960 ms | 5,604 ms | 158.101.158.101 | |
| Tunnel ok | 7,767 ms | 8,207 ms | 158.101.158.101 | |
| Tunnel ok | 2,626 ms | 3,124 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.