VLESS server 108.61.164.217:4443
TCP / REALITY · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 02:12:01 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 108.61.164.217:4443
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 108.61.164.217
- Last verified handshake
- 346 ms
- Last verified HTTPS first byte
- 543 ms
- Download speed
- 1.318 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-19 13:38:07 UTC
- Recorded tunnel checks
- 17
- Successful tunnel checks
- 17
- Recorded tunnel success rate
- 100.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 20 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 | 346 ms | 543 ms | 108.61.164.217 | |
| Tunnel ok | 322 ms | 520 ms | 108.61.164.217 | |
| Tunnel ok | 417 ms | 639 ms | 108.61.164.217 | |
| Tunnel ok | 478 ms | 765 ms | 108.61.164.217 | |
| Tunnel ok | 331 ms | 534 ms | 108.61.164.217 | |
| Tunnel ok | 307 ms | 482 ms | 108.61.164.217 | |
| Tunnel ok | 286 ms | 475 ms | 108.61.164.217 | |
| Tunnel ok | 324 ms | 509 ms | 108.61.164.217 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 290 ms | 469 ms | 108.61.164.217 | |
| Tunnel ok | 364 ms | 572 ms | 108.61.164.217 | |
| Tunnel ok | 317 ms | 521 ms | 108.61.164.217 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 305 ms | 489 ms | 108.61.164.217 | |
| Tunnel ok | 292 ms | 478 ms | 108.61.164.217 | |
| Tunnel ok | 1,694 ms | 2,417 ms | 108.61.164.217 | |
| Tunnel ok | 271 ms | 441 ms | 108.61.164.217 | |
| Tunnel ok | 282 ms | 456 ms | 108.61.164.217 | |
| Tunnel ok | 297 ms | 489 ms | 108.61.164.217 | |
| Policy blocked | Not measured | Not measured | Not verified |
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.