VLESS server 3.0.111.82:10574
TCP / REALITY · Au1rxx verified downloadable configs
Inactive — did not pass verificationLast result: 2026-10-08 23:43:23 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.
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
- 862 ms
- Last verified HTTPS first byte
- 1,403 ms
- Download speed
- 2.042 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 20:18:28 UTC
- Recorded tunnel checks
- 17
- Successful tunnel checks
- 17
- 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 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 | 862 ms | 1,403 ms | 3.0.111.82 | |
| Tunnel ok | 801 ms | 1,266 ms | 3.0.111.82 | |
| Tunnel ok | 949 ms | 1,483 ms | 3.0.111.82 | |
| Tunnel ok | 738 ms | 1,277 ms | 3.0.111.82 | |
| Tunnel ok | 790 ms | 1,262 ms | 3.0.111.82 | |
| Tunnel ok | 893 ms | 1,364 ms | 3.0.111.82 | |
| Tunnel ok | 943 ms | 1,414 ms | 3.0.111.82 | |
| Tunnel ok | 793 ms | 1,262 ms | 3.0.111.82 | |
| Tunnel ok | 694 ms | 1,160 ms | 3.0.111.82 | |
| Tunnel ok | 750 ms | 1,217 ms | 3.0.111.82 | |
| Tunnel ok | 983 ms | 1,533 ms | 3.0.111.82 | |
| Tunnel ok | 713 ms | 1,185 ms | 3.0.111.82 | |
| Tunnel ok | 1,366 ms | 1,978 ms | 3.0.111.82 | |
| Tunnel ok | 984 ms | 1,539 ms | 3.0.111.82 | |
| Tunnel ok | 753 ms | 1,238 ms | 3.0.111.82 | |
| Tunnel ok | 923 ms | 2,066 ms | 3.0.111.82 | |
| Tunnel ok | 666 ms | 1,139 ms | 3.0.111.82 | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | Not measured | Not measured | Not verified | |
| Unsupported checker | 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.