VLESS server 147.45.60.160:8444
GRPC / REALITY · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-25 01:20:58 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 147.45.60.160:8444
- Transport / security
- GRPC / REALITY
- Last verified exit IP
- 147.45.60.160
- Last verified handshake
- 651 ms
- Last verified HTTPS first byte
- 879 ms
- Download speed
- 5.429 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-10-11 23:52:56 UTC
- Recorded tunnel checks
- 10
- Successful tunnel checks
- 9
- Recorded tunnel success rate
- 90.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 10 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 | 651 ms | 879 ms | 147.45.60.160 | |
| Tunnel ok | 623 ms | 844 ms | 147.45.60.160 | |
| Tunnel ok | 594 ms | 801 ms | 147.45.60.160 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 582 ms | 791 ms | 147.45.60.72 | |
| Tunnel ok | 754 ms | 1,004 ms | 147.45.60.72 | |
| Tunnel ok | 585 ms | 795 ms | 147.45.60.72 | |
| Tunnel ok | 573 ms | 776 ms | 147.45.60.72 | |
| Tunnel ok | 587 ms | 795 ms | 147.45.60.72 | |
| Tunnel ok | 574 ms | 779 ms | 147.45.60.72 |
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.