VLESS server 3.114.220.22:10583
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:26:00 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.114.220.22:10583
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.114.220.22
- Last verified handshake
- 878 ms
- Last verified HTTPS first byte
- 1,378 ms
- Download speed
- 2.588 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 19:31:53 UTC
- Recorded tunnel checks
- 25
- Successful tunnel checks
- 25
- 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 | 878 ms | 1,378 ms | 3.114.220.22 | |
| Tunnel ok | 1,120 ms | 1,680 ms | 3.114.220.22 | |
| Tunnel ok | 869 ms | 1,352 ms | 3.114.220.22 | |
| Tunnel ok | 1,015 ms | 1,618 ms | 3.114.220.22 | |
| Tunnel ok | 899 ms | 1,393 ms | 3.114.220.22 | |
| Tunnel ok | 898 ms | 1,343 ms | 3.114.220.22 | |
| Tunnel ok | 947 ms | 1,387 ms | 3.114.220.22 | |
| Tunnel ok | 956 ms | 1,833 ms | 3.114.220.22 | |
| Tunnel ok | 876 ms | 1,365 ms | 3.114.220.22 | |
| Tunnel ok | 999 ms | 1,487 ms | 3.114.220.22 | |
| Tunnel ok | 1,315 ms | 1,816 ms | 3.114.220.22 | |
| Tunnel ok | 1,124 ms | 1,632 ms | 3.114.220.22 | |
| Tunnel ok | 1,335 ms | 1,889 ms | 3.114.220.22 | |
| Tunnel ok | 872 ms | 1,311 ms | 3.114.220.22 | |
| Tunnel ok | 983 ms | 1,461 ms | 3.114.220.22 | |
| Tunnel ok | 943 ms | 1,414 ms | 3.114.220.22 | |
| Tunnel ok | 1,026 ms | 1,481 ms | 3.114.220.22 | |
| Tunnel ok | 999 ms | 1,487 ms | 3.114.220.22 | |
| Tunnel ok | 830 ms | 1,247 ms | 3.114.220.22 | |
| Tunnel ok | 881 ms | 1,373 ms | 3.114.220.22 | |
| Tunnel ok | 922 ms | 1,384 ms | 3.114.220.22 | |
| Tunnel ok | 885 ms | 1,435 ms | 3.114.220.22 | |
| Tunnel ok | 871 ms | 1,343 ms | 3.114.220.22 | |
| Tunnel ok | 915 ms | 1,466 ms | 3.114.220.22 | |
| Tunnel ok | 1,166 ms | 1,634 ms | 3.114.220.22 |
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.