VLESS server 3.0.111.82:10574
TCP / REALITY · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 09:24:54 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.0.111.82:10574
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.0.111.82
- Last verified handshake
- 925 ms
- Last verified HTTPS first byte
- 1,542 ms
- Download speed
- 1.389 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-13 18:42:58 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 25
- Recorded tunnel success rate
- 96.2%
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 27 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 | 925 ms | 1,542 ms | 3.0.111.82 | |
| Tunnel ok | 949 ms | 1,491 ms | 3.0.111.82 | |
| Tunnel ok | 1,258 ms | 1,801 ms | 3.0.111.82 | |
| Tunnel ok | 959 ms | 1,568 ms | 3.0.111.82 | |
| Tunnel ok | 1,341 ms | 2,099 ms | 3.0.111.82 | |
| Tunnel ok | 1,968 ms | 2,516 ms | 3.0.111.82 | |
| Tunnel ok | 1,724 ms | 2,588 ms | 3.0.111.82 | |
| Tunnel ok | 1,646 ms | 4,111 ms | 3.0.111.82 | |
| Tunnel ok | 1,013 ms | 1,483 ms | 3.0.111.82 | |
| Tunnel ok | 765 ms | 1,239 ms | 3.0.111.82 | |
| Tunnel ok | 943 ms | 1,408 ms | 3.0.111.82 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 978 ms | 1,559 ms | 3.0.111.82 | |
| Tunnel ok | 765 ms | 1,234 ms | 3.0.111.82 | |
| Tunnel ok | 864 ms | 1,415 ms | 3.0.111.82 | |
| Tunnel ok | 771 ms | 1,250 ms | 3.0.111.82 | |
| Tunnel ok | 721 ms | 1,277 ms | 3.0.111.82 | |
| Tunnel ok | 680 ms | 1,155 ms | 3.0.111.82 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 7,367 ms | 9,627 ms | 3.0.111.82 | |
| Tunnel ok | 1,198 ms | 1,684 ms | 3.0.111.82 | |
| Tunnel ok | 900 ms | 1,449 ms | 3.0.111.82 | |
| Tunnel ok | 880 ms | 1,434 ms | 3.0.111.82 | |
| Tunnel ok | 1,187 ms | 1,828 ms | 3.0.111.82 | |
| Tunnel ok | 4,979 ms | 6,207 ms | 3.0.111.82 | |
| Tunnel ok | 1,202 ms | 1,848 ms | 3.0.111.82 | |
| Tunnel ok | 1,006 ms | 1,615 ms | 3.0.111.82 |
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.