VLESS server 3.0.111.82:10574
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 05:39:03 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
- 1,246 ms
- Last verified HTTPS first byte
- 1,800 ms
- Download speed
- 1.431 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 20:18:00 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 24 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,246 ms | 1,800 ms | 3.0.111.82 | |
| Tunnel ok | 758 ms | 1,222 ms | 3.0.111.82 | |
| Tunnel ok | 1,097 ms | 1,569 ms | 3.0.111.82 | |
| Tunnel ok | 983 ms | 1,544 ms | 3.0.111.82 | |
| Tunnel ok | 778 ms | 1,255 ms | 3.0.111.82 | |
| Tunnel ok | 880 ms | 1,431 ms | 3.0.111.82 | |
| Tunnel ok | 835 ms | 1,316 ms | 3.0.111.82 | |
| Tunnel ok | 807 ms | 1,339 ms | 3.0.111.82 | |
| Tunnel ok | 849 ms | 1,404 ms | 3.0.111.82 | |
| Tunnel ok | 971 ms | 1,459 ms | 3.0.111.82 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 7,871 ms | 8,346 ms | 3.0.111.82 | |
| Tunnel ok | 676 ms | 1,142 ms | 3.0.111.82 | |
| Tunnel ok | 1,613 ms | 2,214 ms | 3.0.111.82 | |
| Tunnel ok | 803 ms | 1,346 ms | 3.0.111.82 | |
| Tunnel ok | 904 ms | 1,400 ms | 3.0.111.82 | |
| Tunnel ok | 1,178 ms | 1,734 ms | 3.0.111.82 | |
| Tunnel ok | 797 ms | 1,264 ms | 3.0.111.82 | |
| Tunnel ok | 741 ms | 1,230 ms | 3.0.111.82 | |
| Tunnel ok | 2,306 ms | 3,087 ms | 3.0.111.82 | |
| Tunnel ok | 842 ms | 1,305 ms | 3.0.111.82 | |
| Tunnel ok | 857 ms | 1,415 ms | 3.0.111.82 | |
| Tunnel ok | 2,434 ms | 3,310 ms | 3.0.111.82 | |
| Tunnel ok | 1,126 ms | 1,760 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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.