VLESS server 3.0.111.82:12972
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:25:51 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
- 995 ms
- Last verified HTTPS first byte
- 1,484 ms
- Download speed
- 1.735 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-10 12:45:26 UTC
- Recorded tunnel checks
- 23
- Successful tunnel checks
- 23
- Recorded tunnel success rate
- 100.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 26 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 | 995 ms | 1,484 ms | 3.0.111.82 | |
| Tunnel ok | 1,311 ms | 1,783 ms | 3.0.111.82 | |
| Tunnel ok | 3,790 ms | 4,813 ms | 3.0.111.82 | |
| Tunnel ok | 1,483 ms | 1,959 ms | 3.0.111.82 | |
| Tunnel ok | 862 ms | 1,423 ms | 3.0.111.82 | |
| Tunnel ok | 771 ms | 1,322 ms | 3.0.111.82 | |
| Tunnel ok | 1,783 ms | 2,308 ms | 3.0.111.82 | |
| Tunnel ok | 1,005 ms | 1,473 ms | 3.0.111.82 | |
| Tunnel ok | 751 ms | 1,226 ms | 3.0.111.82 | |
| Tunnel ok | 700 ms | 1,170 ms | 3.0.111.82 | |
| Tunnel ok | 755 ms | 1,223 ms | 3.0.111.82 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 780 ms | 1,339 ms | 3.0.111.82 | |
| Tunnel ok | 1,517 ms | 2,086 ms | 3.0.111.82 | |
| Tunnel ok | 760 ms | 1,304 ms | 3.0.111.82 | |
| Tunnel ok | 730 ms | 1,202 ms | 3.0.111.82 | |
| Tunnel ok | 9,148 ms | 11,061 ms | 3.0.111.82 | |
| Tunnel ok | 1,007 ms | 1,486 ms | 3.0.111.82 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,963 ms | 3,683 ms | 3.0.111.82 | |
| Tunnel ok | 1,232 ms | 1,874 ms | 3.0.111.82 | |
| Tunnel ok | 1,380 ms | 3,848 ms | 3.0.111.82 | |
| Tunnel ok | 1,045 ms | 1,614 ms | 3.0.111.82 | |
| Tunnel ok | 1,476 ms | 2,277 ms | 3.0.111.82 | |
| Tunnel ok | 1,067 ms | 1,704 ms | 3.0.111.82 | |
| Preflight ok | Not measured | Not measured | Not verified |
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.