VLESS server 3.114.220.22:18007
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:42:38 UTC
Connection and verification
- Protocol
- VLESS
- Address
- 3.114.220.22:18007
- Transport / security
- TCP / REALITY
- Last verified exit IP
- 3.114.220.22
- Last verified handshake
- 900 ms
- Last verified HTTPS first byte
- 1,451 ms
- Download speed
- 1.727 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-14 13:23:05 UTC
- Recorded tunnel checks
- 24
- Successful tunnel checks
- 24
- 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 24 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 | 900 ms | 1,451 ms | 3.114.220.22 | |
| Tunnel ok | 1,105 ms | 1,693 ms | 3.114.220.22 | |
| Tunnel ok | 969 ms | 1,467 ms | 3.114.220.22 | |
| Tunnel ok | 1,460 ms | 2,244 ms | 3.114.220.22 | |
| Tunnel ok | 887 ms | 1,358 ms | 3.114.220.22 | |
| Tunnel ok | 5,614 ms | 6,203 ms | 3.114.220.22 | |
| Tunnel ok | 1,071 ms | 3,652 ms | 3.114.220.22 | |
| Tunnel ok | 2,135 ms | 3,611 ms | 3.114.220.22 | |
| Tunnel ok | 1,327 ms | 1,895 ms | 3.114.220.22 | |
| Tunnel ok | 1,266 ms | 1,821 ms | 3.114.220.22 | |
| Tunnel ok | 836 ms | 1,284 ms | 3.114.220.22 | |
| Tunnel ok | 3,317 ms | 3,935 ms | 3.114.220.22 | |
| Tunnel ok | 1,199 ms | 1,753 ms | 3.114.220.22 | |
| Tunnel ok | 910 ms | 1,383 ms | 3.114.220.22 | |
| Tunnel ok | 922 ms | 1,408 ms | 3.114.220.22 | |
| Tunnel ok | 867 ms | 1,350 ms | 3.114.220.22 | |
| Tunnel ok | 1,041 ms | 1,518 ms | 3.114.220.22 | |
| Tunnel ok | 986 ms | 1,523 ms | 3.114.220.22 | |
| Tunnel ok | 1,225 ms | 1,697 ms | 3.114.220.22 | |
| Tunnel ok | 905 ms | 1,390 ms | 3.114.220.22 | |
| Tunnel ok | 866 ms | 1,348 ms | 3.114.220.22 | |
| Tunnel ok | 1,203 ms | 1,682 ms | 3.114.220.22 | |
| Tunnel ok | 969 ms | 1,519 ms | 3.114.220.22 | |
| Tunnel ok | 1,214 ms | 1,696 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.