VLESS server 3.0.111.82:17623
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:25:56 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.0.111.82:17623
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.0.111.82
- Last verified handshake
- 903 ms
- Last verified HTTPS first byte
- 1,375 ms
- Download speed
- 1.729 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 21:07:27 UTC
- Recorded tunnel checks
- 25
- Successful tunnel checks
- 24
- Recorded tunnel success rate
- 96.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 |
|---|---|---|---|---|
| Tunnel ok | 903 ms | 1,375 ms | 3.0.111.82 | |
| Tunnel ok | 1,227 ms | 1,764 ms | 3.0.111.82 | |
| Tunnel ok | 3,825 ms | 4,892 ms | 3.0.111.82 | |
| Tunnel ok | 850 ms | 1,714 ms | 3.0.111.82 | |
| Tunnel ok | 1,170 ms | 1,655 ms | 3.0.111.82 | |
| Tunnel ok | 859 ms | 1,339 ms | 3.0.111.82 | |
| Tunnel ok | 2,045 ms | 2,522 ms | 3.0.111.82 | |
| Tunnel ok | 742 ms | 1,217 ms | 3.0.111.82 | |
| Tunnel ok | 786 ms | 1,254 ms | 3.0.111.82 | |
| Tunnel ok | 841 ms | 1,290 ms | 3.0.111.82 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,367 ms | 2,279 ms | 3.0.111.82 | |
| Tunnel ok | 986 ms | 1,824 ms | 3.0.111.82 | |
| Tunnel ok | 763 ms | 1,234 ms | 3.0.111.82 | |
| Tunnel ok | 792 ms | 1,264 ms | 3.0.111.82 | |
| Tunnel ok | 783 ms | 1,264 ms | 3.0.111.82 | |
| Tunnel ok | 741 ms | 1,213 ms | 3.0.111.82 | |
| Tunnel ok | 1,013 ms | 1,483 ms | 3.0.111.82 | |
| Tunnel ok | 1,912 ms | 2,627 ms | 3.0.111.82 | |
| Tunnel ok | 1,580 ms | 2,138 ms | 3.0.111.82 | |
| Tunnel ok | 791 ms | 1,350 ms | 3.0.111.82 | |
| Tunnel ok | 1,871 ms | 2,662 ms | 3.0.111.82 | |
| Tunnel ok | 794 ms | 1,333 ms | 3.0.111.82 | |
| Tunnel ok | 2,176 ms | 2,957 ms | 3.0.111.82 | |
| Tunnel ok | 984 ms | 1,542 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.