VLESS server 3.114.220.22:18007
TCP / REALITY · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 06:28:52 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
- 1,401 ms
- Last verified HTTPS first byte
- 1,951 ms
- Download speed
- 1.588 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-13 22:49:37 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 | 1,401 ms | 1,951 ms | 3.114.220.22 | |
| Tunnel ok | 915 ms | 1,447 ms | 3.114.220.22 | |
| Tunnel ok | 965 ms | 1,457 ms | 3.114.220.22 | |
| Tunnel ok | 1,319 ms | 1,869 ms | 3.114.220.22 | |
| Tunnel ok | 901 ms | 1,385 ms | 3.114.220.22 | |
| Tunnel ok | 901 ms | 1,369 ms | 3.114.220.22 | |
| Tunnel ok | 2,628 ms | 4,352 ms | 3.114.220.22 | |
| Tunnel ok | 910 ms | 2,509 ms | 3.114.220.22 | |
| Tunnel ok | 950 ms | 1,437 ms | 3.114.220.22 | |
| Tunnel ok | 997 ms | 1,476 ms | 3.114.220.22 | |
| Tunnel ok | 1,059 ms | 1,605 ms | 3.114.220.22 | |
| Tunnel ok | 1,366 ms | 1,919 ms | 3.114.220.22 | |
| Tunnel ok | 3,538 ms | 4,084 ms | 3.114.220.22 | |
| Tunnel ok | 855 ms | 1,489 ms | 3.114.220.22 | |
| Tunnel ok | 1,105 ms | 1,665 ms | 3.114.220.22 | |
| Tunnel ok | 983 ms | 1,667 ms | 3.114.220.22 | |
| Tunnel ok | 2,103 ms | 2,896 ms | 3.114.220.22 | |
| Tunnel ok | 903 ms | 1,541 ms | 3.114.220.22 | |
| Tunnel ok | 1,288 ms | 1,846 ms | 3.114.220.22 | |
| Tunnel ok | 836 ms | 1,379 ms | 3.114.220.22 | |
| Tunnel ok | 912 ms | 1,353 ms | 3.114.220.22 | |
| Tunnel ok | 924 ms | 1,402 ms | 3.114.220.22 | |
| Tunnel ok | 1,035 ms | 1,521 ms | 3.114.220.22 | |
| Tunnel ok | 985 ms | 1,474 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.