VLESS server 3.0.111.82:12972
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 09:09:01 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.0.111.82:12972
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.0.111.82
- Last verified handshake
- 1,930 ms
- Last verified HTTPS first byte
- 2,499 ms
- Download speed
- 1.411 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 11:59:45 UTC
- Recorded tunnel checks
- 23
- Successful tunnel checks
- 22
- Recorded tunnel success rate
- 95.7%
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 23 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,930 ms | 2,499 ms | 3.0.111.82 | |
| Tunnel ok | 1,119 ms | 1,603 ms | 3.0.111.82 | |
| Tunnel ok | 4,158 ms | 5,255 ms | 3.0.111.82 | |
| Tunnel ok | 1,372 ms | 2,002 ms | 3.0.111.82 | |
| Tunnel ok | 1,713 ms | 2,199 ms | 3.0.111.82 | |
| Tunnel ok | 850 ms | 1,412 ms | 3.0.111.82 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 728 ms | 1,195 ms | 3.0.111.82 | |
| Tunnel ok | 677 ms | 1,201 ms | 3.0.111.82 | |
| Tunnel ok | 748 ms | 1,211 ms | 3.0.111.82 | |
| Tunnel ok | 930 ms | 1,402 ms | 3.0.111.82 | |
| Tunnel ok | 902 ms | 1,455 ms | 3.0.111.82 | |
| Tunnel ok | 735 ms | 1,229 ms | 3.0.111.82 | |
| Tunnel ok | 2,576 ms | 3,783 ms | 3.0.111.82 | |
| Tunnel ok | 697 ms | 1,246 ms | 3.0.111.82 | |
| Tunnel ok | 2,481 ms | 3,595 ms | 3.0.111.82 | |
| Tunnel ok | 3,098 ms | 3,955 ms | 3.0.111.82 | |
| Tunnel ok | 999 ms | 1,478 ms | 3.0.111.82 | |
| Tunnel ok | 1,860 ms | 2,422 ms | 3.0.111.82 | |
| Tunnel ok | 1,539 ms | 2,320 ms | 3.0.111.82 | |
| Tunnel ok | 1,509 ms | 2,070 ms | 3.0.111.82 | |
| Tunnel ok | 1,036 ms | 1,593 ms | 3.0.111.82 | |
| Tunnel ok | 1,646 ms | 2,446 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.